Hi Guys, I have experienced an issue when the smbd stops responding, and after cannot kill the process, using SIGTERM or SIGKILL. A reboot cured the problem. I had the same problem once again a couple of days later. I realised that both times I had changed my smb.conf file directly, using vi, and shortly before the hang occured. The changes to the file were very minor, and the two were different options. Nothing appeared in the log, but my logging level is very low. Both times a reboot cured the problem. Now here is my problem - the version of samba was tested before going live, but the problem was not picked ip, but now it is in a production environment, which I cannot disrupt until the last person goes home. I guess I what I am asking is what can you guys suggest I try in the small window i have to test it, to gather enough information for you to diagnose where the problem lies, if indeed it is related to the modified smd.conf. I will turn the logging level up to 10, but will have to stop samba first, so hopefully editing the smb.conf shouldn't cause a problem then. The server is a dual Zeon with Suse 9.0 kernel 2.4.21-273-smp4g with yast updates and samba 3.0.11. BTW, what is the actually policy for samba to watch for config updates? Is there a polling interval of sorts? Thanks in advance for any help, Olly
> Hi Guys, > > I have experienced an issue when the smbd stops responding, and after cannot > kill the process, using SIGTERM or SIGKILL. A reboot cured the problem. I > had the same problem once again a couple of days later. I realised that both > times I had changed my smb.conf file directly, using vi, and shortly before > the hang occured. The changes to the file were very minor, and the two were > different options. Nothing appeared in the log, but my logging level is very > low. Both times a reboot cured the problem. > > Now here is my problem - the version of samba was tested before going live, > but the problem was not picked ip, but now it is in a production > environment, which I cannot disrupt until the last person goes home. I guess > I what I am asking is what can you guys suggest I try in the small window i > have to test it, to gather enough information for you to diagnose where the > problem lies, if indeed it is related to the modified smd.conf. I will turn > the logging level up to 10, but will have to stop samba first, so hopefully > editing the smb.conf shouldn't cause a problem then. > > The server is a dual Zeon with Suse 9.0 kernel 2.4.21-273-smp4g with yast > updates and samba 3.0.11. > > BTW, what is the actually policy for samba to watch for config updates? Is > there a polling interval of sorts? > > Thanks in advance for any help, > > Olly >I have got the sambe problems with my SuSE 9.1 and smb-3.0.11. After installing the older version (3.0.9) the problem does not appear. So I wait for a new update (3.0.12 or somehting later) :-) -- Regards, Jens Strohschnitter ------------------------------------- *!!!LINUX LINUX LINUX LINUX LINUX!!!* * http://www.jens-strohschnitter.de * ------------------------------------- Set the controls for the heart of the sun -------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 olly wrote: | Hi Guys, | | I have experienced an issue when the smbd stops | responding, and after cannot kill the process, using | SIGTERM or SIGKILL. If you can't SIGKILL, it's a kernel bug IMO. | A reboot cured the problem. I had the same problem | once again a couple of days later. I realised that both | times I had changed my smb.conf file directly, using | vi, and shortly before the hang occured. The changes to | the file were very minor, and the two were different | options. Nothing appeared in the log, but my logging | level is very low. Both times a reboot cured the problem. There changes to how we reload the printer cache between 3.0.9 and 3.0.11. I've never seen the behavior you describe but all my boxes are running 2.6 these days. | | Now here is my problem - the version of samba was | tested before going live, but the problem was not | picked ip, but now it is in a production environment, which | I cannot disrupt until the last person goes home. I guess | I what I am asking is what can you guys suggest I try | in the small window i have to test it, to gather enough | information for you to diagnose where the problem lies, if | indeed it is related to the modified smd.conf. I will turn | the logging level up to 10, but will have to stop samba | first, so hopefully editing the smb.conf shouldn't cause | a problem then. You can run smbcontrol smbd debug 10 to set the debug level. You might also want to run strace on the 'hung' process (although if it is really hung, you won't get any feedback here either). | The server is a dual Zeon with Suse 9.0 kernel 2.4.21-273-smp4g | with yast updates and samba 3.0.11. | | BTW, what is the actually policy for samba to watch for | config updates? Is there a polling interval of sorts? internal checks every 3 minutes. grep for SMBD_RELOAD_CHECK. cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCGyo6IR7qMdg1EfYRAq8YAJ9R3YoMBiVchd5+9otFBfTSdnKYOgCfdVNt ZChjVAhHuS7JGz8Vf5amX40=mId3 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jens Strohschnitter wrote: | I have got the sambe problems with my SuSE 9.1 and | smb-3.0.11. After installing the older version (3.0.9) | the problem does not appear. So I wait for a new update | (3.0.12 or somehting later) :-) where did you get the Samba packages ? or did you compile from source ? cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCGypsIR7qMdg1EfYRArqKAKDgEAmeU/1uLPNrDNZ/BKNfGuEIsgCdE9m1 PRxJzdai28x7BczhE6Uc7vE=eyLY -----END PGP SIGNATURE-----
> | I have got the sambe problems with my SuSE 9.1 and > | smb-3.0.11. After installing the older version (3.0.9) > | the problem does not appear. So I wait for a new update > | (3.0.12 or somehting later) :-) > > where did you get the Samba packages ? or did you compile > from source ?from rpmseek.de -- Regards, Jens Strohschnitter ------------------------------------- *!!!LINUX LINUX LINUX LINUX LINUX!!!* * http://www.jens-strohschnitter.de * ------------------------------------- Set the controls for the heart of the sun -------------------------------------
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jens Strohschnitter wrote: |>| I have got the sambe problems with my SuSE 9.1 and |>| smb-3.0.11. After installing the older version (3.0.9) |>| the problem does not appear. So I wait for a new update |>| (3.0.12 or somehting later) :-) |> |>where did you get the Samba packages ? or did you compile |>from source ? | | from rpmseek.de Would you mind testing the ones at http://samba.org/samba/ftp/Binary_Packages/SuSE/3.0/i386/ ? cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org GnuPG Key ----- http://www.plainjoe.org/gpg_public.asc "I never saved anything for the swim back." Ethan Hawk in Gattaca -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCGzKiIR7qMdg1EfYRAvbRAJ4g/Kar/oxhIN/MCNovP9q8R48R5QCdEzCx 7h1ZHsDj8ZSb9lT6TK8majQ=UUMf -----END PGP SIGNATURE-----