Bug 3679 - Semaphore Error when Logon Script is running
Semaphore Error when Logon Script is running
Status: NEW
Product: Samba 3.0
Classification: Unclassified
Component: File Services
3.0.21c
x86 Linux
: P3 normal
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-13 05:18 UTC by M.R.Niranjan
Modified: 2006-04-20 08:03 UTC (History)
0 users

See Also:


Attachments
Debug Level 10 Output (75.82 KB, text/plain)
2006-04-13 05:22 UTC, M.R.Niranjan
no flags Details
Debug Level 10 Output (74.51 KB, text/plain)
2006-04-13 06:07 UTC, M.R.Niranjan
no flags Details
Debug 10 Output (74.73 KB, text/plain)
2006-04-18 04:46 UTC, M.R.Niranjan
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description M.R.Niranjan 2006-04-13 05:18:49 UTC
Hi all
 
I have a samba PDC (3.0.21c with ldap backend). and another linux server used as
file server(samba 3.0.21c). . the users access the file shares using logon script 
which redirects to respective shares in file server. 
but when the logon script runs it gives the followin error

System error 121 has occurred.

The semaphore timeout period has expired.

Any ideas?
 
I have a samba 3.0.21c with ldap backend acting as a PDC , i have about 100 users connectingto my domain.i have another linux system which acts as a file server (prjsrv01) where i have declared 2 shares.projects and datalib. The users get drives mapped with the help of logon
script. so i map projects share as P: drive 
net use p: //prjsrv01/projects.
but whent the logon script runs the command. it says semaphore error.

The Domain Member Server uses lib_nss, to get user information from ldaps server

The following is the log level 10 output when the semaphore error occured. ie
the log starts when the user logs in and logon script runs.

when the semaphore error returns at windows client, at log it shows
NT_STATUS_IO_TIMEOUT




Regards
Niranjan
Comment 1 M.R.Niranjan 2006-04-13 05:22:36 UTC
Created attachment 1854 [details]
Debug Level 10 Output 

Log Level 10 ouput when the user logs on the the domain
and logon script runs. 
The log is taken from the domain member server ie my file server
the log file is generally username.machine.log. 
The ouput is attached
Comment 2 Volker Lendecke 2006-04-13 05:42:35 UTC
It looks as if the logfile has prematurely ended. Do you have other logfiles for the guest user? Can you 'su -' to the user you set in 'guest account'?

Volker
Comment 3 M.R.Niranjan 2006-04-13 06:07:21 UTC
Created attachment 1855 [details]
Debug Level 10 Output 

This is another log, the log is of user dcadmin
logged in the machine name printsrv001. 
it's not guest user. 

Regards
Niranjan
Comment 4 Volker Lendecke 2006-04-13 06:12:33 UTC
Is it possible that you have winbind running and that winbind is haning for some reason? Could you try to issue 'wbinfo -t' on the command line and report the output? Could you also try to issue 'wbinfo -a domain\\user%password' on the command line and report the output? If that gives any problems, could you please also upload the winbind log files?

Thank you,

Volker
Comment 5 M.R.Niranjan 2006-04-18 04:46:15 UTC
Created attachment 1862 [details]
Debug 10 Output
Comment 6 Volker Lendecke 2006-04-18 04:52:26 UTC
The NT_STATUS_IO_TIMEOUT comes from the communication with winbind. Could you please upload winbind logfiles from the operations that I mentioned?

Thanks,

Volker
Comment 7 Gerald (Jerry) Carter 2006-04-20 08:03:42 UTC
severity should be determined by the developers and not the reporter.