[LON-CAPA-admin] loncontrol dies at lond

Todd Ruskell truskell at mines.edu
Mon Nov 7 00:38:33 EST 2005

Any ideas what can make the subject happen?

My library server /home filled up on us (we're still checking out the why's and
wherefore's), and connections weren't being made because the machine couldn't
write any more data.  

My clue was log entries like this:
lond.log:Sun Nov  6 21:33:43 2005 (2527): Famous last words: Sun Nov  6 21:33:43
2005: Catching exception - Sun Nov6 21:33:43 2005: <font color='red'>CRITICAL:
ABNORMAL EXIT. Child 2527 for server loncapa.Mines.EDU died through a crash
with this error msg->[write error at /home/httpd/perl/lond line 2355, <GEN261>
line 2009.

So on an emergency basis, we moved some stuff out of /home.

So now we've got 300+ MB free (not a lot, but I figured it should be enough to
get things going again) but this is what I get:

[root at loncapa loncapa-2.0.2]# /etc/init.d/loncontrol start
Opening firewall access on port 5663.
iptables: No chain/target/match by that name
Error opening port.
Opening firewall access on port 8080.
iptables: No chain/target/match by that name
Error opening port.
Starting LON-CAPA
Starting LON-CAPA client and daemon processes (please be patient)
lonsql          running
lond            [root at loncapa loncapa-2.0.2]#                                

Ignore the firewall thing.  The point is loncontrol dies at lond.  I don't see
anything interesting in the logs other than entries like this in lonnet.log:

Sun Nov  6 22:33:34 2005 (11576): User asingh at csm threw error con_lost when
checking authentication mechanism

which I expect if lond isn't doing its thing.


Thanks in advance,


Dr. Todd G. Ruskell                         Phone: 303-384-2080
Lecturer, Department of Physics             FAX:   303-273-3919
Colorado School of Mines
Golden, CO 80401

More information about the LON-CAPA-admin mailing list