-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi, I have a SAMBA PDC for a WinXP LAN, it works fine, but two of the
workstations don’t close the process that I can see with the command
smbstatus -b for the users, and then they can’t login again until I kill
the process. Any suggestion about it?
System: openSUSE 11.1 x86_64 2.6.27.45-0.1-default
SAMBA: 3.2.7-11.4.1-2210-SUSE-CODE11
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkuotB0ACgkQJQ+0ABWtaVnFIgCgxahlTwpzArXVNZ++ONPsJqzz
3h8An1jsk/z9TsP8jQVGTst2PAAaFLL7
=1yze
-----END PGP SIGNATURE-----
On Tue March 23 2010 07:27 am, VampirD wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi, I have a SAMBA PDC for a WinXP LAN, it works fine, but two of the
> workstations don’t close the process that I can see with the command
> smbstatus -b for the users, and then they can’t login again until I kill
> the process. Any suggestion about it?
>
> System: openSUSE 11.1 x86_64 2.6.27.45-0.1-default
> SAMBA: 3.2.7-11.4.1-2210-SUSE-CODE11
>
> - –
> VampirD
>
> Microsoft Windows is like air conditioning
> Stops working when you open a window.
VampirD;
To help you debug this, add the following to the global section
of /etc/samba/smb.conf.
log level = 3
log file = /var/log/samba/logsmbd.%m
Of course logsmbd.m% could be <anyname>.%m.
This gives you more detailed logs and you can view the messages for each
client individually in /var/log/samba/logsmbd.<machine name>. This will let
you isolate the information for the two troublesome clients. You might find
the problem immediately with this. If you are still having problems it
would help if you posted the contents of your /etc/samba/smb.conf and the
logs for a failing client.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
On Tue March 23 2010 06:06 pm, PV wrote:
> On Tue March 23 2010 07:27 am, VampirD wrote:
>
<snip>
VampirD;
I should have added this to the last post. Check your cables and switches.
If only two clients are effected this is likely something unique to those two
machines. Also verify that the users are properly closing down Windows. If
the power were cut to the machines or the network disconnected before logging
off or shutting down, then Samba would have no good way to know the machines
disconnected.
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
OK, I’ll try it and post the result
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkuqDU8ACgkQJQ+0ABWtaVnqzgCeOtYtWpjeN7sk7bWbasz5Ze2o
Sp0AnRaizU2YC2JtoQX4pSkajyWXe/K0
=tAJ5
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Damn, it still happens, here I post the smb.conf file
----------------------smb.conf-----------------------------------------------
smb.conf is the main Samba configuration file. You find a full commented
version at /usr/share/doc/packages/samba/examples/smb.conf.SUSE if the
samba-doc package is installed.
Date: 2009-06-24
[global]
workgroup = IIMPI
domain master = Yes
netbios name = Fenix
#server string = Samba
map to guest = Bad User
username map = /etc/samba/smbusers
add machine script = /usr/sbin/useradd -c Machine -d
/var/lib/nobody -s /bin/false %m$
logon drive = Z:
logon path = \%N\profiles$%U
logon home = \Fenix%U
template homedir = /var/lib/samba/netlogon/Default User
domain logons = Yes
os level = 255
preferred master = Yes
#ldap ssl = start tls
#ldap timeout = 5
usershare allow guests = Yes
usershare max shares = 100
admin users = admin
local master = Yes
security = user
time server = yes
#log file = /var/log/samba/samba.log
max log size = 5000
debug uid = Yes
wins support = Yes
name resolve order = wins lmhosts hosts
log level = 3
log file = /var/log/samba/logsmbd.%m
hide dot files = yes
[homes]
comment = Home Directories
valid users = %S
read only = No
inherit acls = Yes
browseable = No
hide dot files = yes
[users]
comment = Home Directories
path = /home
read only = No
inherit acls = Yes
browseable = No
[netlogon]
comment = Network Logon Service
path = /var/lib/samba/netlogon
write list = root
read only = yes
[profiles$]
comment = Network Profiles Service
path = /home/samba/
read only = No
inherit acls = Yes
the log is a big file so I put it here:
http://www.fing.edu.uy/~jmadera/logsmbd.tar.gz
VampirD
No in elenath hîlar nan hâd gîn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkuqyagACgkQJQ+0ABWtaVlWwACfSU+ZAxgo1WVb6K1EZIW42cnC
dFQAmQHvy4vO5t9O/lZgnoBD771DRMbJ
=n1rD
-----END PGP SIGNATURE-----
On Wed March 24 2010 09:25 pm, VampirD wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Damn, it still happens, here I post the smb.conf file
>
> -
<snip>
>
> the log is a big file so I put it here:
> http://www.fing.edu.uy/~jmadera/logsmbd.tar.gz
>
>
> - –
> VampirD
> No in elenath hîlar nan hâd gîn
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.12 (GNU/Linux)
> Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
>
> iEYEARECAAYFAkuqyagACgkQJQ+0ABWtaVlWwACfSU+ZAxgo1WVb6K1EZIW42cnC
> dFQAmQHvy4vO5t9O/lZgnoBD771DRMbJ
> =n1rD
> -----END PGP SIGNATURE-----
VampirD;
I did not spot anything in your smb.conf to explain this. I did notice from
your log file that most of the users seemed to fail authentication and are
being logged in as the guest user. Can you verify that all the entries in
the log come from client “muaddib”? The log file you posted runs for over 11
hours (10:16 to 21:13). It would be much easier to debug if you could
replicate the problem over a much shorter period of time. What happens if
you restart the client, log in to the domain, then log off in a very short
period of time. Does the process still continue to run? You stated that the
problem is for two clients. Is this 2 per 2, 2 per 20 or 2 per 500? Does
the problem exist for a single user or multiple users? What flavor of
windows are the offending clients i.e. XP,VISTA,Seven,NT,98?
One other thing I noticed that the users neither connected to nor close the
connection to profiles. Is there any indication that the user(s) are getting
a temporary profile? Are they configured for local profiles?
Can you try to isolate this down a bit, to a single user over a short period
of time and post the log?
–
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> I did not spot anything in your smb.conf to explain this. I did notice from
> your log file that most of the users seemed to fail authentication and are
> being logged in as the guest user. Can you verify that all the entries in
> the log come from client “muaddib”? The log file you posted runs for over 11
> hours (10:16 to 21:13). It would be much easier to debug if you could
> replicate the problem over a much shorter period of time. What happens if
> you restart the client, log in to the domain, then log off in a very short
> period of time. Does the process still continue to run? You stated that the
> problem is for two clients. Is this 2 per 2, 2 per 20 or 2 per 500? Does
> the problem exist for a single user or multiple users? What flavor of
> windows are the offending clients i.e. XP,VISTA,Seven,NT,98?
The problem is on 2 clients XP SP2 x86 on a LAN with 24 clients and I
noticed that two of the users that failed to log in are from another sub
LAN from the institute
> One other thing I noticed that the users neither connected to nor close the
> connection to profiles. Is there any indication that the user(s) are getting
> a temporary profile? Are they configured for local profiles?
They’re configured to use roaming profiles, but maybe the cache profile
still exist because they reset the pc twice
> Can you try to isolate this down a bit, to a single user over a short period
> of time and post the log?
I’ll do it
VampirD
No in elenath hîlar nan hâd gîn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkurLTgACgkQJQ+0ABWtaVlinwCfXWdPB/liXdhZlRJVnyqugLKm
ADcAn3Qmgtz9K/O+HOQsud+O1O7Mnnsy
=rdXZ
-----END PGP SIGNATURE-----
Some reports have been made about latest samba updates. These users state that rolling back to the openSUSE 11.2 distribution versions solved matters.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, I put here: www.fing.edu.uy/~jmadera/ghanima.tar.gz a shotest
one, and having closed the session and with another user using the PC I
still have the process
Fenix:/var/log/samba # smbstatus -b
Registered MSG_REQ_POOL_USAGE
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
lp_load_ex: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file “/etc/samba/smb.conf”
Processing section “[global]”
Processing section “[homes]”
Processing section “[users]”
Processing section “[netlogon]”
Processing section “[profiles$]”
Samba version 3.2.7-11.4.1-2210-SUSE-CODE11
PID Username Group Machine
11607 jmadera users ghanima (::ffff:164.73.33.180)
Fenix:/var/log/samba #
another question: what are the logsmbd.__ffff_xxx.xx.xx.xxx log
generated for each machine?, I have the logsmbd.machineName and
logsmbd.__ffff_MachineIP
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkurWXsACgkQJQ+0ABWtaVk/fgCfQD/NX0o37mkTYnfY9iC4y697
RJcAn3uaY+Iw1gO4tQjAY/tpBLKUYYFH
=KSHg
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
You suggest to upgrade SAMBA to the openSUSE 11.2 version? but, it will
work fine on openSUSE 11.1?
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkurXUYACgkQJQ+0ABWtaVm3KACdHTnggkU55CLgOccQAV6Co/MF
/rsAnjvJJHh8Dsf7Com76wUUgaTag80M
=pqyf
-----END PGP SIGNATURE-----
No, sorry, that was not my intention. For you it should be 11.1
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
ok ok, I can try it
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAkurZzIACgkQJQ+0ABWtaVm82QCeM2L3OEJPp643R+UoHQmJqXlK
a2cAnjjCnHpuO7Ucj2w0kvdBOsKSpD1u
=sNXB
-----END PGP SIGNATURE-----
On Thu March 25 2010 07:37 am, VampirD wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Well, I put here: www.fing.edu.uy/~jmadera/ghanima.tar.gz a shotest
> one, and having closed the session and with another user using the PC I
> still have the process
>
> Fenix:/var/log/samba # smbstatus -b
> Registered MSG_REQ_POOL_USAGE
> Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED
> lp_load_ex: refreshing parameters
> Initialising global parameters
> params.c:pm_process() - Processing configuration file “/etc/samba/smb.conf”
> Processing section “[global]”
> Processing section “[homes]”
> Processing section “[users]”
> Processing section “[netlogon]”
> Processing section “[profiles$]”
>
> Samba version 3.2.7-11.4.1-2210-SUSE-CODE11
> PID Username Group Machine
> - -------------------------------------------------------------------
> 11607 jmadera users ghanima (::ffff:164.73.33.180)
> Fenix:/var/log/samba #
>
> another question: what are the logsmbd.__ffff_xxx.xx.xx.xxx log
> generated for each machine?, I have the logsmbd.machineName and
> logsmbd.__ffff_MachineIP
> - –
> VampirD
>
> Microsoft Windows is like air conditioning
> Stops working when you open a window.
<snip>
VampirD;
Sorry it took me so long to get back to you. After reading your last log I
found that jmadera connected to the profiles share 5 times and for the first
three times closed the connection about 10 seconds later. But the last 2
(PID 11607) at 9:10:43 and 9:11:32 do not seem to have a paired close.
jespas connected twice with two paired closes.
It looks to me like jmadera never quite finished the logout. Since less than
10% of the clients have this problem, it is most likely a problem with the
client or the network connection (cables, switches etc.) Rather than kill the
process on the server have you tried restarting Windows? It’s possible that
if the Windows machine shuts down it will finish the logout.
The problem that knurpht referred to seems to affect the ability of Linux
users to connect to shares on a Windows machine.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Well, I’ll change the switch and see what happen with a new one, and
you’re right, restarting the client also works
VampirD
Microsoft Windows is like air conditioning
Stops working when you open a window.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org/
iEYEARECAAYFAku7RXMACgkQJQ+0ABWtaVlUigCffX/wGJw3SAjt4z4C/QRjkBWJ
N14AnR87hEHO83W25JGO8roBD2xrybnt
=5Etw
-----END PGP SIGNATURE-----
I’ve been running into a similar issue, and posted about it a while back. I’ve changed the logging level per your suggestion and hope that will shed some insight into what is going on. While I’m not positive it only applies to windows 7, I speculate that during the Windows 7 backup process it opens a new smbd to serve it.
The link to my old thread.
If it is of any help. I can provide any additional information if anyone thinks they can help me troubleshoot this. During setting up windows 7 backup it will not let me use a drive letter already bound (ie: Z to a samba share, it wants \samba-server\samba-share with credentials). I’d assume that would work well as it is requiring credentials, but who knows. At any rate, the backups have occurred similar to last week and now I have 1010.0 load average.
17:36:59 up 5 days, 13:00, 5 users, load average: 1010.01, 1010.01, 1010.00
IE: all smbd agents, can’t kill them they are all blocked:
shane 11846 0.0 0.0 81076 2964 ? D Apr06 0:00 /usr/sbin/smbd
-D -s /etc/samba/smb.conf
The only way to get rid of the samba processes (that I have found) is to reboot the machine without properly shutting it down. I can still talk to it, and even put it in single user mode, but kill -9, killall -9, pkill -9, none of those work.
ShaneR;
I replied to your original thread.
P. V.
“We’re all in this together, I’m pulling for you.” Red Green