Bug 6548 - Could not init smbd messaging context
Summary: Could not init smbd messaging context
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.3
Classification: Unclassified
Component: File services (show other bugs)
Version: 3.3.2
Hardware: x64 Linux
: P3 critical
Target Milestone: ---
Assignee: Volker Lendecke
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-12 15:28 UTC by Jeff Chapin
Modified: 2009-07-14 03:46 UTC (History)
0 users

See Also:


Attachments
Requested strace (31.05 KB, text/plain)
2009-07-13 06:06 UTC, Jeff Chapin
no flags Details
smb.conf (9.21 KB, application/octet-stream)
2009-07-13 06:46 UTC, Jeff Chapin
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Chapin 2009-07-12 15:28:17 UTC
smbd will not start. 

When trying to start, the following errors are logged:

Jul 12 15:23:04 localhost smbd[10474]: [2009/07/12 15:23:04,  0] lib/messages_local.c:messaging_tdb_init(96)
Jul 12 15:23:04 localhost smbd[10474]:   ERROR: Failed to initialise messages database: No such file or directory
Jul 12 15:23:04 localhost smbd[10474]: [2009/07/12 15:23:04,  0] lib/messages.c:messaging_init(204)
Jul 12 15:23:04 localhost smbd[10474]:   messaging_tdb_init failed: NT_STATUS_OBJECT_NAME_NOT_FOUND
Jul 12 15:23:04 localhost smbd[10474]: [2009/07/12 15:23:04,  0] smbd/server.c:smbd_messaging_context(101)
Jul 12 15:23:04 localhost smbd[10474]:   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.
Comment 1 Volker Lendecke 2009-07-13 00:16:36 UTC
Do you have SELinux installed? If yes, try to deactivate it. Else, please upload the output of 

strace smbd -d 0 -i

Thanks,

Volker
Comment 2 Jeff Chapin 2009-07-13 06:06:30 UTC
Created attachment 4412 [details]
Requested strace
Comment 3 Jeff Chapin 2009-07-13 06:09:06 UTC
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
Comment 4 Jeff Chapin 2009-07-13 06:09:40 UTC
Oh, and SELinux is disabled.
Comment 5 Jeff Chapin 2009-07-13 06:16:50 UTC
# find /usr/share/locale/en* -name \*libc.mo
/usr/share/locale/en_GB/LC_MESSAGES/libc.mo
Comment 6 Volker Lendecke 2009-07-13 06:26:38 UTC
Wait a second -- do you have "file:///" somewhere in your smb.conf??

Please post your smb.conf.

Thanks,

Volker
Comment 7 Jeff Chapin 2009-07-13 06:46:30 UTC
Created attachment 4413 [details]
smb.conf
Comment 8 Jeff Chapin 2009-07-13 07:00:12 UTC
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
Comment 9 Volker Lendecke 2009-07-13 07:41:29 UTC
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.

Volker
Comment 10 Jeff Chapin 2009-07-13 18:11:29 UTC
That did it.

Now to figure out why that happened.
Comment 11 Björn Jacke 2009-07-14 03:46:29 UTC
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. :-)