We have a lot of [2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355) Trying to delay for oplocks twice in the logs. Do they harm in general? And only in one single case I got this, don't know if I ever will get it reproduced, so maybe not related and happened by accident: Samba version 3.0.21a PID Username Group Machine ------------------------------------------------------ 8231 testuser users ws24(192.168.1.24) 8673 testuser users ws24(192.168.1.24) 3822 testuser users ws24(192.168.1.24) Service pid machine Connected at -------------------------------------------- IPC$ 3822 ws24 Wed Jan 4 17:33:14 2006 IPC$ 8231 ws24 Wed Jan 4 17:35:02 2006 testuser 3822 ws24 Wed Jan 4 07:50:41 2006 Projects 8673 ws24 Wed Jan 4 18:44:40 2006 3822 DENY_WRITE 0x2019f RDWR NONE outlook/rsc.pst Wed Jan 4 17:20:40 2006 8673 DENY_NONE 0x20089 RDONLY NONE outlook/rsc.pst Wed Jan 4 18:49:38 2006 Windows complained about "Cannot access rcs.pst, in use by another process".
Sorry, the second problem "just" seems to be related to an offline printer: #0 0x00002aaaab3e76d4 in waitpid () from /lib64/tls/libc.so.6 #1 0x00000000005963c0 in smbrun () #2 0x000000000058a8e1 in print_run_command () #3 0x000000000058accf in generic_job_submit () #4 0x00000000005bbb20 in print_job_end () #5 0x00000000004f5f9a in _spoolss_enddocprinter_internal () #6 0x00000000004f073a in api_spoolss_enddocprinter () #7 0x000000000051eaf1 in api_rpcTNP () #8 0x000000000051ee75 in api_pipe_request () #9 0x000000000051b975 in write_to_internal_pipe () #10 0x00000000004510f1 in api_fd_reply () #11 0x0000000000451b70 in reply_trans () #12 0x0000000000497128 in switch_message () #13 0x00000000004973e9 in process_smb () #14 0x000000000049810f in smbd_process () #15 0x000000000060f1ff in main () After the job was printed some hours later all went fine. -------------------------------------------- We have a lot of [2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355) Trying to delay for oplocks twice in the logs. Do they harm in general? And only in one single case I got this, don't know if I ever will get it reproduced, so maybe not related and happened by accident: Samba version 3.0.21a PID Username Group Machine ------------------------------------------------------ 8231 testuser users ws24(192.168.1.24) 8673 testuser users ws24(192.168.1.24) 3822 testuser users ws24(192.168.1.24) Service pid machine Connected at -------------------------------------------- IPC$ 3822 ws24 Wed Jan 4 17:33:14 2006 IPC$ 8231 ws24 Wed Jan 4 17:35:02 2006 testuser 3822 ws24 Wed Jan 4 07:50:41 2006 Projects 8673 ws24 Wed Jan 4 18:44:40 2006 3822 DENY_WRITE 0x2019f RDWR NONE outlook/rsc.pst Wed Jan 4 17:20:40 2006 8673 DENY_NONE 0x20089 RDONLY NONE outlook/rsc.pst Wed Jan 4 18:49:38 2006 Windows complained about "Cannot access rcs.pst, in use by another process".
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Beschorner Daniel wrote:> We have a lot of > > [2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355) > Trying to delay for oplocks twiceWhat Samba version? If it's 3.0.21, please test 3.0.21a cheers, jerry ====================================================================Alleviating the pain of Windows(tm) ------- http://www.samba.org Centeris ----------- http://www.centeris.com "There's an anonymous coward in all of us." --anonymous -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFDvChtIR7qMdg1EfYRAkBcAKDix3deAgKIS/U0xOpRr/sMh/jAHgCg3/t8 KJmwZlKLCxfObYI/hFa0FOw=zAdB -----END PGP SIGNATURE-----
# grep "version" < Posting Samba version 3.0.21a :-)> What Samba version? If it's 3.0.21, please test 3.0.21a
The question is whether blocking is well defined in this case (because lpd hangs) or if it is an error that the file serving/locking services of the smbd process hang altogether. My print section looks like this: printing = lprng print command = lpr -r -P'%p' %s lpq command = lpq -P'%p' lprm command = lprm -P'%p' %j lppause command = lpc hold '%p' %j lpresume command = lpc release '%p' %j queuepause command = lpc stop '%p' queueresume command = lpc start '%p' use client driver = No default devmode = No force printername = No It's a Linux x64 system with lprng printing. -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Beschorner Daniel wrote:> > Sorry, the second problem "just" seems to be related to an offlineprinter:> > #0 0x00002aaaab3e76d4 in waitpid () from /lib64/tls/libc.so.6 > #1 0x00000000005963c0 in smbrun () > #2 0x000000000058a8e1 in print_run_command () > #3 0x000000000058accf in generic_job_submit () > #4 0x00000000005bbb20 in print_job_end () > #5 0x00000000004f5f9a in _spoolss_enddocprinter_internal () > #6 0x00000000004f073a in api_spoolss_enddocprinter () > #7 0x000000000051eaf1 in api_rpcTNP () > #8 0x000000000051ee75 in api_pipe_request () > #9 0x000000000051b975 in write_to_internal_pipe () > #10 0x00000000004510f1 in api_fd_reply () > #11 0x0000000000451b70 in reply_trans () > #12 0x0000000000497128 in switch_message () > #13 0x00000000004973e9 in process_smb () > #14 0x000000000049810f in smbd_process () > #15 0x000000000060f1ff in main () > > After the job was printed some hours later all went fine.Please give me some more details on the server OS and the outout from 'testparm -v'