[LON-CAPA-admin] problem updating to 1.3.3

[Guy Albertelli II]

Hi Nathan,


> I've come across a problem after I upgraded to 1.3.3.  It appears that the
> loncontrol daemon isn't restarting properly after the update.  I'll stop it
> and then start it, but it doesn't give me a response that it has been
> started.
> 
> lonsql     running
> lond       [root at neptune loncapa-1.3.3]#

Nothing changed in either lond, or loncontrol in version 1.3.3

So this is a bit odd.

> It looks like it isn't restarting all of the services...any
> suggestions?

Is there anything in /home/httpd/perl/logs/lond_errors?
Did you try 
/etc/init.d/loncontrol stop
then
/etc/init.d/loncontrol start

?

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



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