^7_of_9
10-30-2003, 12:39 PM
Been using DCMonitor for a while now and not too long before the last changeover it stopped monitoring three Linux clients properly for some reason.
Until that time it always told me if the client was running (I'm assuming both these programs only look for the lock file to see if it's running). Nothing has changed whatsoever on any of the Lnux clients at all. "Voyager" is the main machine running NFS exports for the other two machines running Diskless Path from the Windows machine that is running DF and DC Monitor is \\voyager\nfs\exports\Picard\distribfold and \\voyager\nfs\exports\Kirk\distribfold and then \\voyager\DC\distribfold (The last one is the local client on that machine)
No permissions problem as I've still got full access to those directories and other shared ones on the same machine. (Using SAMBA for Windows access)
Now for some reason They report the client as always being "stopped" ... Here's the URL of the HTML pages that are updated once every 5 mins for DCMonitor and 10 minutes
DC Monitor: http://sigs.teampicard.com/DCMonitor/
DF Monitor: http://sigs.teampicard.com/DFMonitor/
You'll see that Voyager, Kirk and Picard are all either "Stalled" or "Stopped" (Don't worry about Vinculum as that's a machine that the new client always seems to crash on .. :rolleyes: ), but I know for a fact they aren't as I've turned off quiet mode on the client and see it going through the processes and everything, but still receive the output that the client isn't running. I've even gone in and run a ps -e and a top to see what was going on and no problems there either. My output is about what it should be as well.
So I'm REALLY :confused: on this one now ...
Until that time it always told me if the client was running (I'm assuming both these programs only look for the lock file to see if it's running). Nothing has changed whatsoever on any of the Lnux clients at all. "Voyager" is the main machine running NFS exports for the other two machines running Diskless Path from the Windows machine that is running DF and DC Monitor is \\voyager\nfs\exports\Picard\distribfold and \\voyager\nfs\exports\Kirk\distribfold and then \\voyager\DC\distribfold (The last one is the local client on that machine)
No permissions problem as I've still got full access to those directories and other shared ones on the same machine. (Using SAMBA for Windows access)
Now for some reason They report the client as always being "stopped" ... Here's the URL of the HTML pages that are updated once every 5 mins for DCMonitor and 10 minutes
DC Monitor: http://sigs.teampicard.com/DCMonitor/
DF Monitor: http://sigs.teampicard.com/DFMonitor/
You'll see that Voyager, Kirk and Picard are all either "Stalled" or "Stopped" (Don't worry about Vinculum as that's a machine that the new client always seems to crash on .. :rolleyes: ), but I know for a fact they aren't as I've turned off quiet mode on the client and see it going through the processes and everything, but still receive the output that the client isn't running. I've even gone in and run a ps -e and a top to see what was going on and no problems there either. My output is about what it should be as well.
So I'm REALLY :confused: on this one now ...