[LON-CAPA-admin] problem updating to 1.3.3

[Guy Albertelli II]

Hi Nathan,

> I would guess it's the killall commands.  There was no lond.pid or lonc.pid
> files, but I wonder if there were extraneous lond and lonc processes that
> weren't getting killed by the /etc/init.d/loncontrol stop. 

Hrrm, loncontrol stop does a 
    system("killall -q -0 $killallname");
then if any were found
	system("killall -q $killallname");

Hrrm.

> I did the update to our access server(s) and got a strange message when
> stopping loncontrol on that machine as well:
> 
> Closing firewall access on port 5663.
> iptables: Bad rule (does a matching rule exist in that chain?)
> Error closing port.
> Closing firewall access on port 8080.
> iptables: Bad rule (does a matching rule exist in that chain?)
> Error closing port.

You'll get this if you do stop twice in a row, (because the firewall
already has those ports closed)

-- 
guy at albertelli.com  LON-CAPA Developer  0-7-2-9-