suzanlow
asked on
System log messages
Please explain what these error messages mean and what I need to do to fix them. I am on a Digital UNIX 4.0E (Compaq/Tru64) platform with three nodes in a clustered environment.
Kern.log:
Feb 17 08:19:24 medusa vmunix: NFS server: unexported fs(2908, 59487) file 1847, RFS3_FSSTAT, client address = 10.1.254.74
Mar 6 22:00:10 medusa vmunix: tu0: transmit FIFO underflow: threshold raised to: 512 bytes
Daemon.log:
Feb 16 08:45:17 medusa lockd[2583]: lockd: monitor entry not found for "appl_top", request is not monitored.
Feb 16 08:45:19 medusa last message repeated 2 times
Feb 16 08:46:30 medusa lockd[2583]: lockd: monitor entry not found for "appl_top", request is not monitored.
Thanks.
Kern.log:
Feb 17 08:19:24 medusa vmunix: NFS server: unexported fs(2908, 59487) file 1847, RFS3_FSSTAT, client address = 10.1.254.74
Mar 6 22:00:10 medusa vmunix: tu0: transmit FIFO underflow: threshold raised to: 512 bytes
Daemon.log:
Feb 16 08:45:17 medusa lockd[2583]: lockd: monitor entry not found for "appl_top", request is not monitored.
Feb 16 08:45:19 medusa last message repeated 2 times
Feb 16 08:46:30 medusa lockd[2583]: lockd: monitor entry not found for "appl_top", request is not monitored.
Thanks.
You just got this suddenly or where there any changes to your cluster configuration before the errors...?
ASKER
The only type of changes that took place was the addition of four file systems.
You can access all filessystems on every node also trough servernet? Or create files and shares from/to any node?
For this deamon you should check your config file for the appl_top entry...
Do you get warnings if you run top on seperate nodes or for the cluster?
For this deamon you should check your config file for the appl_top entry...
Do you get warnings if you run top on seperate nodes or for the cluster?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.