The Samba-Bugzilla – Bug 6548
Could not init smbd messaging context
Last modified: 2009-07-14 03:46:29 UTC
smbd will not start.
When trying to start, the following errors are logged:
Jul 12 15:23:04 localhost smbd: [2009/07/12 15:23:04, 0] lib/messages_local.c:messaging_tdb_init(96)
Jul 12 15:23:04 localhost smbd: ERROR: Failed to initialise messages database: No such file or directory
Jul 12 15:23:04 localhost smbd: [2009/07/12 15:23:04, 0] lib/messages.c:messaging_init(204)
Jul 12 15:23:04 localhost smbd: messaging_tdb_init failed: NT_STATUS_OBJECT_NAME_NOT_FOUND
Jul 12 15:23:04 localhost smbd: [2009/07/12 15:23:04, 0] smbd/server.c:smbd_messaging_context(101)
Jul 12 15:23:04 localhost smbd: Could not init smbd messaging context.
When running with -d 10 the following, additional information is recovered:
tdb(unnamed): tdb_open_ex: could not open file file:///var/lib/samba/messages.tdb: No such file or directory
ERROR: Failed to initialise messages database: No such file or directory
messaging_tdb_init failed: NT_STATUS_OBJECT_NAME_NOT_FOUND
Could not init smbd messaging context.
The file /var/lib/samba/messages.tdb did not originally exist, but making /var/lib/samba/ world writable did not help, nor did making the file, and making it world writable.
Files were installed from yum on Fedora 11.
Do you have SELinux installed? If yes, try to deactivate it. Else, please upload the output of
strace smbd -d 0 -i
Created attachment 4412 [details]
Looking through the strace, this may be useful to note.
# ls /usr/share/locale/en/LC_MESSAGES/
libsmbios-2.2.mo man sos.mo xmms.mo
Oh, and SELinux is disabled.
# find /usr/share/locale/en* -name \*libc.mo
Wait a second -- do you have "file:///" somewhere in your smb.conf??
Please post your smb.conf.
Created attachment 4413 [details]
It appears I do have that -- if that is wrong, this may be a Fedora 11/KDE issue, as, other than a single modification with KDE's wizard to add a share, this is a stock smb.conf
Please remove all file:// prefixes from your smb.conf and test again. If that does not help, please re-open this bug.
For example, the line with "pid directory" should look like
pid directory = /var/run
The others must be set equivalently.
That did it.
Now to figure out why that happened.
just do everything you did in the last couple of days once again (don't forget the coffee breaks etc.) and watch when your smb.conf changes. :-)