On Mon, Aug 08, 2005 at 09:09:33PM -0400, Aiello, Steve (Corporate, consultant) wrote:
Anything in the /var/log/hobbit/clientdata.log file ?
Yes, lots of:
"Worker process died with exit code 132, terminating"
OK, should have checked that first, of course. The hobbitd module that processes the data from your client is crashing, which explains why you dont see any statuses on the web display.
"code 132" usually means it was killed by a signal 4, which is SIGILL. Looking at the data from your client I notice that:
[free]
total used free shared buffers cached
Mem: 239100 152428 86672 0 35020 19500
-/+ buffers/cache: 97908 141192
Swap: 0 0 0
total swap-space is 0. The client module in 4.1.1 has a bug that makes it do a divide-by-zero with those data, which could well explain this. Could you try installing the latest Hobbit snapshot on your server ? It's available from http://www.hswn.dk/beta/