Page 1 of 1

Sharity daemon stopping

Posted: Mon Nov 08, 2010 10:49 pm
by njmeeker
Running Sharity 2.8 on Redhat linux for 5+ years now. Lately we have been getting some hangups. Not sure if it Sharity, some other network item or even hardware. Once things have gone south trying to start Sharity gives the following error message:
Internal error: Communication with UI client
ERROR Context: local machine (framework)

Doing a /etc/rc5.d/S95hsharity.init status reports that the daemon is stopped.

Trying to manually restart the daemon (/etc/rc5.d/S95sharity.init start) results in the following messages:

Starting Sharity daemon:
284.940 [0] unicode: trivialInit: using 3072 bytes for forward and 1024 bytes for reverse mapping tables
284.948 [1] ipcserver: error binding socket: [98] Address already in use
284.974 [0] unicode: init: using 40860 bytes for forward and 1024 bytes for reverse mapping tables
284.977 [0] nfs: set RX buffer to 131072 bytes
284.977 [0] nfs: set TX buffer to 131072 bytes
284.977 [1] nfs2: can't bind to preferred port 991, trying free port ([98] Address already in use)
284.977 [0] nfs3: set RX buffer to 131072 bytes
284.977 [0] nfs3: set TX buffer to 131072 bytes
284.977 [1] nfs3: can't bind to preferred port 992, trying free port ([98] Address already in use)
cat: /usr/local/sharity/var/sharity.pid: No such file or directory
0: old priority 0, new priority -5
done.

Checking the status again shows it is still stopped. The only way we've been able to rectify the situation is to reboot the linux box. After which everything is working normal. This might last a day or week or even a month. Prior to this problem we had been running for upwards of a year or more with no such issues. We have always had a stable platform and have not updated Redhat nor Sharity since they were installed (~ 2003).

Thanks and regards, Nick