Antwort: [Samba] Locking problems with upgrade from 2.0.7 to 2.2.3a

[Derivas, Eduardo V]

Hi,
	I have been having the same problem when I upgraded from 2.0.7 to
2.2.3a. I worked great for the first 16 users, but after that it gave me the
same errors and nobody else could get in. Please let me know if the
recommended parameters help.

Eduardo

-----Original Message-----
From: thomas_tiedtke at de.schindler.com
[mailto:thomas_tiedtke at de.schindler.com]
Sent: Wednesday, March 06, 2002 8:36 AM
To: Jan Mostert
Cc: samba at lists.samba.org
Subject: Antwort: [Samba] Locking problems with upgrade from 2.0.7 to
2.2.3a


Hi,

disable the parameter 

posix locking = no       (if no nfs access possible, or set this in the 
share section without nfs access -- this eats the file locks)
kernel oplocks = no    (not possible on HP/UX 10.20)
use mmap= no             (not possible on HP/UX 10.20)

... in the global section.

It maybe helps!

Regards, Thomas



Gesendet von:   samba-admin at lists.samba.org
An:     <samba at lists.samba.org>
Kopie:  "Jan Mostert" <J.Mostert at GeoDelft.nl> 
Thema:  [Samba] Locking problems with upgrade from 2.0.7 to 2.2.3a



Hello,
 
Last weekend we tried to upgrade our Samba servers  from 2.0.7 to 2.2.3a. 
This resulted in a small disaster. We did not change the  smb.conf file, 
but after one hour users had problems with their Samba share. The  log 
file contained many of the following messages:
 
[2002/03/01 08:41:01, 0]  printing/nt_printing.c:nt_printing_init(246)
  nt_printing_init: Failed  to open nt drivers database 
/opt/samba/var/locks/ntdrivers.tdb (No locks  available)
[2002/03/01 08:41:01, 0]  printing/nt_printing.c:nt_printing_init(253)
  nt_printing_init: Failed  to open nt printers database 
/opt/samba/var/locks/ntprinters.tdb (No locks  available)
[2002/03/01 08:41:05, 1]  smbd/service.c:make_connection(615)
  dg-sv21 (145.3.1.64) connect to  service kff as user kff (uid=14480, 
gid=905) (pid 9531)
[2002/03/01 08:41:12,  1] smbd/service.c:close_cnum(655)
  dg-sv20 (145.3.1.63) closed  connection to service logging
[2002/03/01 08:41:12, 1]  smbd/service.c:close_cnum(655)
  dg-sv20 (145.3.1.63) closed connection  to service logging
[2002/03/01 08:41:12, 1]  smbd/service.c:close_cnum(655)
  dg-sv20 (145.3.1.63) closed connection  to service dfe
[2002/03/01 08:41:12, 0]  printing/nt_printing.c:nt_printing_init(260)
  nt_printing_init: Failed  to open nt forms database 
/opt/samba/var/locks/ntforms.tdb (No locks  available)
[2002/03/01 08:41:12, 0]  printing/nt_printing.c:nt_printing_init(260)
  nt_printing_init: Failed  to open nt forms database 
/opt/samba/var/locks/ntforms.tdb (No locks  available)
[2002/03/01 08:41:15, 0]  printing/nt_printing.c:nt_printing_init(260)
  nt_printing_init: Failed  to open nt forms database 
/opt/samba/var/locks/ntforms.tdb (No locks  available)
[2002/03/01 08:41:15, 0]  printing/nt_printing.c:nt_printing_init(260)
  nt_printing_init: Failed  to open nt forms database 
/opt/samba/var/locks/ntforms.tdb (No locks  available)
[2002/03/01 08:41:19, 0]  printing/nt_printing.c:nt_printing_init(260)
  nt_printing_init: Failed  to open nt forms database 
/opt/samba/var/locks/ntforms.tdb (No locks  available)
[2002/03/01 08:41:19, 0]  printing/nt_printing.c:nt_printing_init(260)
  nt_printing_init: Failed  to open nt forms database 
/opt/samba/var/locks/ntforms.tdb (No locks  available)
[2002/03/01 08:41:23, 1]  smbd/service.c:make_connection(615)
  dg-sv22 (145.3.1.65) connect to  service swi as user swi (uid=18115, 
gid=300) (pid 407)
[2002/03/01 08:41:27,  1] smbd/service.c:make_connection(615)
  dg-sv22 (145.3.1.65) connect to  service logging as user gd (uid=228, 
gid=20) (pid 407)
[2002/03/01 08:41:31,  1] smbd/service.c:make_connection(615)
  dg-sv22 (145.3.1.65) connect to  service swi as user swi (uid=18115, 
gid=300) 
 
The kernel parameter NFLOCKS of the HP-UX  10.20 machine was already 
increased in the past to 1000. With Samba 2.0.7 these  messages never 
showed up. I unsderstand something has been changed in the file  locking 
part of Samba, but how can I solve this problem?
 
Kind regards,
Jan Mostert
GeoDelft