Bug 3548 - Unable to open new log file
Unable to open new log file
Status: CLOSED FIXED
Product: Samba 3.0
Classification: Unclassified
Component: Config Files
3.0.21b
x86 Linux
: P3 minor
: none
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-02-23 17:19 UTC by Daniel Beschorner
Modified: 2006-08-09 03:26 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Beschorner 2006-02-23 17:19:52 UTC
For probably Samba > 3.0.14 I see this often in the logs:

[2006/01/19 12:25:13, 0] lib/debug.c:reopen_logs(597)
  Unable to open new log file /usr/local/samba/var/log.smbd: Permission denied
Comment 1 Olaf Imig 2006-04-12 03:33:12 UTC
(In reply to comment #0)
> For probably Samba > 3.0.14 I see this often in the logs:
> 
> [2006/01/19 12:25:13, 0] lib/debug.c:reopen_logs(597)
>   Unable to open new log file /usr/local/samba/var/log.smbd: Permission denied
> 
Yes, I found this bug also in Samba 3.0.22 at Solaris Sparc for the first time:
2006/04/12 10:12:04, 0] lib/debug.c:(597)
  Unable to open new log file /var/log/samba/log.smbd: Zugriff verweigert
Comment 2 Daniel Beschorner 2006-06-29 03:56:50 UTC
also in 3.0.23RC3, but seems non-fatal

[2006/06/29 08:22:50, 0] lib/debug.c:reopen_logs(625)
  Unable to open new log file /server/samba/var/log.smbd: Permission denied
[2006/06/29 08:22:50, 0] lib/smbldap.c:smbldap_open(1009)
  smbldap_open: cannot access LDAP when not root..
[2006/06/29 08:22:50, 0] lib/smbldap.c:smbldap_open(1009)
  smbldap_open: cannot access LDAP when not root..
[2006/06/29 08:22:50, 0] lib/smbldap.c:smbldap_open(1009)
  smbldap_open: cannot access LDAP when not root..
[2006/06/29 08:22:50, 1] smbd/service.c:make_connection_snum(941)
Comment 3 Volker Lendecke 2006-06-29 06:13:50 UTC
Daniel, can you reproduce the   smbldap_open: cannot access LDAP when not root.. ones? If yes, I'd like to see a debug level 10 log of that.

Volker
Comment 4 Daniel Beschorner 2006-06-30 07:24:33 UTC
I'd like to reproduce it, but it happens too sporadically and a permanent level 10 log to catch it is impossible in our production environment.

But what I can say is that it has been introduced by 3.0.23, often seen with a make_connection_snum call, but sometimes totally unrelated.

As soon as I got a hint how I can trigger it, I'll provide a level 10 log.
Comment 5 Daniel Beschorner 2006-08-09 03:21:47 UTC
I haven't seen this error yet with 3.0.23.
Also the LDAP messages may be gone.