[LON-CAPA-admin] problem updating to 1.3.3

[Nathan Schoenack]

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.  Then the killall
commands cleaned em up.  Just my guess.

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.

But, then I just started loncontrol and it seemed fine.

Opening firewall access on port 5663.
Opening firewall access on port 8080.
Starting LON-CAPA
Starting LON-CAPA client and daemon processes (please be patient)
lonsql     started
lond       started
lonc       new started
lonhttpd   started

Then I restarted httpd and everything seems to work find with the access
server.

Nathan
-----Original Message-----
From: lon-capa-admin-admin at mail.lon-capa.org
[mailto:lon-capa-admin-admin at mail.lon-capa.org]On Behalf Of Guy
Albertelli II
Sent: Monday, March 28, 2005 12:32 PM
To: lon-capa-admin at mail.lon-capa.org
Subject: Re: [LON-CAPA-admin] problem updating to 1.3.3


Hi Nathan,

> >How about
> >/etc/init.d/loncontrol stop
> >killall lond
> >killall -9 lond
> >killall loncnew
> >killall -9 loncnew
> >rm /home/httpd/perl/logs/lond.pid
> >rm /home/httpd/perl/logs/lonc.pid
> >/etc/init.d/loncontrol start
>
> Bingo!  That worked, Guy.  Thanks!

Hrrm, Any guesses as to which one of those specifically fixed it?

--
guy at albertelli.com  LON-CAPA Developer  0-7-2-9-
_______________________________________________
LON-CAPA-admin mailing list
LON-CAPA-admin at mail.lon-capa.org
http://mail.lon-capa.org/mailman/listinfo/lon-capa-admin