I see a lot of these errors in our RHEL 5.5 Linux client-side /var/log/messages logs. Our server is Solaris 10 thumper (Sunfire) for which I tuned some variables to increase the nfsd's. However, I think this error may be client-side:
We are also mounting over UDP. I've read on Google that some recommend changing this to TCP and tuning additional parameters. Some recommend simply ignoring these errors -- philosophical or lazy? I would like to figure out what the actual problem is and tune it accordingly.
We have a varying server load. However, during the day, on this isolated backend network, there is next to no server load. The backend is a point-to-point network - and unless there is some bizarre problem with the switch or some other config, I can't see how this would be happening.
Before I go tuning additional parameters, I wonder if someone here might be able to point me in the right direction.
Thanks!
Code:
Nov 18 13:28:42 ourserver last message repeated 3 times
Nov 18 13:28:44 ourserver kernel: nfs: server ourserver OK
Nov 18 13:28:44 ourserver last message repeated 3 times
Nov 18 13:28:53 ourserver kernel: nfs: server ourserver not responding, still tryingWe are also mounting over UDP. I've read on Google that some recommend changing this to TCP and tuning additional parameters. Some recommend simply ignoring these errors -- philosophical or lazy? I would like to figure out what the actual problem is and tune it accordingly.
We have a varying server load. However, during the day, on this isolated backend network, there is next to no server load. The backend is a point-to-point network - and unless there is some bizarre problem with the switch or some other config, I can't see how this would be happening.
Before I go tuning additional parameters, I wonder if someone here might be able to point me in the right direction.
Thanks!