The semaphore timeout period has expired
When accessing samba share in Linux, I receive The semaphone timeout period has expired.
The server & connection to windows clients have been working for over 2 years.
The smb.conf does not contain "local browsermaster" statement
The smbd & nmbd services are running.
The server have been reboot
How can the values in the /proc/kernel/sem be reset? Or what is the best way to resolve?
Please advise
Elaine
The server & connection to windows clients have been working for over 2 years.
The smb.conf does not contain "local browsermaster" statement
The smbd & nmbd services are running.
The server have been reboot
How can the values in the /proc/kernel/sem be reset? Or what is the best way to resolve?
Please advise
Elaine
ASKER
Since this error occurred on Friday, Aug.19, this server has been rebooted 3 times.
The last reboot was, this morning, around 8:10 am.
If more semaphores are required, how is that changed?
What's confusing is that the semaphores are reset or cleared after rebooting then how do you set initially?
the /proc/sys/kernel/sem indicates 250 32000 32 128 (that's off the top of my head, the 3rd value may be off)
Your help is greatly appreciated.
Elaine
The last reboot was, this morning, around 8:10 am.
If more semaphores are required, how is that changed?
What's confusing is that the semaphores are reset or cleared after rebooting then how do you set initially?
the /proc/sys/kernel/sem indicates 250 32000 32 128 (that's off the top of my head, the 3rd value may be off)
Your help is greatly appreciated.
Elaine
Do you see semaphores used via ipcs -a ???
But before error occured - was server used for two years, or for at least half year or such long times ???
But before error occured - was server used for two years, or for at least half year or such long times ???
ASKER
Yes, the ipcs -a produces --- (3) entries
semid owner perms nsems
65536 apache 600 1
98305 apache 600 1
131074 apache 600 1
The ipcrm -s 131074 -- removed all entries resulting in inability to use httpd too -- after rebooting and running
ipcs -a again the same results appear.
The reference to running the server for 2 years was that it wasn't a newly installed o/s. There have been reboots during
that timeframe. This is however the first time with this perticular error.
Thanks
semid owner perms nsems
65536 apache 600 1
98305 apache 600 1
131074 apache 600 1
The ipcrm -s 131074 -- removed all entries resulting in inability to use httpd too -- after rebooting and running
ipcs -a again the same results appear.
The reference to running the server for 2 years was that it wasn't a newly installed o/s. There have been reboots during
that timeframe. This is however the first time with this perticular error.
Thanks
ASKER
If the values in the shmmax, sem are linux defaults how do I determine what values to increase them too?
cat /proc/sys/kernel/shmmax = 33554432
cat/proc/sys/kernel/sem = 250 32000 32 128
A article reference on redhat knowledgebase indicates these are default values. The version I am running has reached EOL.
Any suggestions?
cat /proc/sys/kernel/shmmax = 33554432
cat/proc/sys/kernel/sem = 250 32000 32 128
A article reference on redhat knowledgebase indicates these are default values. The version I am running has reached EOL.
Any suggestions?
Then problem does not relate to semaphores.
Another is timers - used for locks
fs.files-max I assume.
Another is timers - used for locks
fs.files-max I assume.
ASKER
Thanks for the advice.
by increasing the fs.files-max the same error is occurring.
For admin it's -semaphore timeout ... for users - it's network path not found.
The log.nmbd states find_response_record: response packet id 4502 received with no matching record.
by increasing the fs.files-max the same error is occurring.
For admin it's -semaphore timeout ... for users - it's network path not found.
The log.nmbd states find_response_record: response packet id 4502 received with no matching record.
ASKER
I found this entry in the log.nmbd
nmbd/nmbd_become_lmb.c:bec
Is it possible this is the problem?
nmbd/nmbd_become_lmb.c:bec
Is it possible this is the problem?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
how long it was up before reboot ???
maybe it needs just more semaphores or so.