SMDB doesn't start: !ERROR: Failed to initialise messages database: Invalid argument"

Discussion:

L.Willms

2011-08-08 15:02:48 UTC

what is missing?

------- from log.smdb -------------------
[2011/08/08 16:44:13, 1] lib/util_unistr.c:load_case_tables(110)
creating lame upcase table
[2011/08/08 16:44:13, 1] lib/util_unistr.c:load_case_tables(125)
creating lame lowcase table
[2011/08/08 16:44:13, 0] smbd/server.c:main(1308)
Server priority set to PRTYC_FOREGROUNDSERVER
[2011/08/08 16:44:13, 0] smbd/server.c:main(1311)
smbd version 3.3.16-eCS 1.1.0-613 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2011/08/08 16:44:14, 2] lib/util_unistr.c:init_valid_table(204)
creating default valid table
[2011/08/08 16:44:14, 0] lib/messages_local.c:messaging_tdb_init(96)
ERROR: Failed to initialise messages database: Invalid argument
[2011/08/08 16:44:14, 0] lib/messages.c:messaging_init(204)
messaging_tdb_init failed: NT_STATUS_INVALID_HANDLE
[2011/08/08 16:44:14, 0] smbd/server.c:smbd_messaging_context(101)
Could not init smbd messaging context.

------------------ end ---------------------

I'm running OS/2 4.50

Cheers,
L.W.

-----------------------------------------------------
Wenn die Milch sich in den Kaffee integriert,
dann ändert der Kaffee seine Farbe.
Falls nicht, ists kein Kaffee, sondern Altöl

L.Willms

2011-08-16 05:26:17 UTC

Permalink

is there anybody out there?

to help me, and get my SAMBA going again?

Am Mon, 8 Aug 2011 15:02:48 UTC, schrieb "L.Willms"

Post by L.Willms
what is missing?
------- from log.smdb -------------------
[2011/08/08 16:44:13, 1] lib/util_unistr.c:load_case_tables(110)
creating lame upcase table
[2011/08/08 16:44:13, 1] lib/util_unistr.c:load_case_tables(125)
creating lame lowcase table
[2011/08/08 16:44:13, 0] smbd/server.c:main(1308)
Server priority set to PRTYC_FOREGROUNDSERVER
[2011/08/08 16:44:13, 0] smbd/server.c:main(1311)
smbd version 3.3.16-eCS 1.1.0-613 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2011/08/08 16:44:14, 2] lib/util_unistr.c:init_valid_table(204)
creating default valid table
[2011/08/08 16:44:14, 0] lib/messages_local.c:messaging_tdb_init(96)
ERROR: Failed to initialise messages database: Invalid argument
[2011/08/08 16:44:14, 0] lib/messages.c:messaging_init(204)
messaging_tdb_init failed: NT_STATUS_INVALID_HANDLE
[2011/08/08 16:44:14, 0] smbd/server.c:smbd_messaging_context(101)
Could not init smbd messaging context.
------------------ end ---------------------
I'm running OS/2 4.50
Cheers,
L.W.
-----------------------------------------------------
Wenn die Milch sich in den Kaffee integriert,
dann ändert der Kaffee seine Farbe.
Falls nicht, ists kein Kaffee, sondern Altöl

Herwig Bauernfeind

2011-08-16 06:53:12 UTC

Permalink

Post by L.Willms
is there anybody out there?

Sure!

Post by L.Willms
to help me, and get my SAMBA going again?

Just for the records, did you eventually try a 3.5 build before starting
3.3.16?

I have seen messages like that here, too and I am suspecting that we
have a problem in the tdb code, however I seem to recall that it occured
with 3.5, not with 3.3. Unfortunately I don't have a proper reproduction
scenario yet.

The bad news is, that I have not found a way to recover from this -
except for a restore from a backup with a working set of tdb files.
Likely the user database is corrupted, at least it was here...

Regards,
Herwig

Post by L.Willms
Am Mon, 8 Aug 2011 15:02:48 UTC, schrieb "L.Willms"

---------------------------------------------------------------------

--
Mit freundlichen Grüßen/
With Best Regards

Herwig Bauernfeind

L.Willms

2011-08-16 07:18:04 UTC

Permalink

Am Tue, 16 Aug 2011 06:53:12 UTC, schrieb Herwig Bauernfeind

Post by Herwig Bauernfeind
Just for the records, did you eventually try a 3.5 build before starting
3.3.16?

3.5? That would be one of those in beta status, wouldn't it? No I
have not ventured into beta with SAMBA

Post by Herwig Bauernfeind
I have seen messages like that here, too and I am suspecting that we
have a problem in the tdb code, however I seem to recall that it occured
with 3.5, not with 3.3. Unfortunately I don't have a proper reproduction
scenario yet.
The bad news is, that I have not found a way to recover from this -
except for a restore from a backup with a working set of tdb files.

Sorry, but I do not have a backup... I have never really understood
what files SAMBA does keep.

Post by Herwig Bauernfeind
Likely the user database is corrupted, at least it was here...

I have now searched and found some *.tdb files. There is a
"messages.tdb" file of length zero in C:\MPTN\ETC\SAMBA\lock... where
would this "user database" be located, and what would be its name?
There is no file beginning with "user" in this "lock" directory.

Can't SAMBA create these tdb-files all from scratch? Or on
installation?

When my OS/2 box crashed, CHKDSK always recovered files as
FOUNDx.CHK, which were obviously log files or such from SAMBA, with
lots of "tdb" in its. Deleting them has never done any harm. Maybe not
the last time, after installing this 3.3.16?

I have now tried and started "Samba Gruppen- und Benutzermanagement"
(which is C:\APPS\SAMBA\SMBUSERS.EXE, I found out), and now there
exists a "messages.tdb" of 696 bytes length, but I can't log on, and I
can't view this file. Since I have switched to SAMBA from IBM PEER, I
have never logged on on the OS/2 machine, as far as I can remember.

The server does still not keep running after starting.

BTW, originally I had a domain server on Windows 2000, but that one
also had problems, so it is not working any more since several months
now. I hope that I can set it up again after returning in September.

Cheers,

Herwig Bauernfeind

2011-08-16 09:42:23 UTC

Permalink

Post by L.Willms
Am Tue, 16 Aug 2011 06:53:12 UTC, schrieb Herwig Bauernfeind

Post by Herwig Bauernfeind
Just for the records, did you eventually try a 3.5 build before starting
3.3.16?

3.5? That would be one of those in beta status, wouldn't it? No I
have not ventured into beta with SAMBA

That's bad, because that means also we have probably a the same problem
in the 3.3 code tree....

Post by L.Willms
I have now searched and found some *.tdb files. There is a
"messages.tdb" file of length zero in C:\MPTN\ETC\SAMBA\lock... where
would this "user database" be located, and what would be its name?
There is no file beginning with "user" in this "lock" directory.
Can't SAMBA create these tdb-files all from scratch? Or on
installation?

It does that for some of them. Look into the b4smb.cmd script - near the
end of the file there is a (disabled) section that removes transient tdb
files during Samba startup.
You may either enable that code or delete the files mentioned there
before you try to start Samba.

Post by L.Willms
When my OS/2 box crashed, CHKDSK always recovered files as
FOUNDx.CHK, which were obviously log files or such from SAMBA, with
lots of "tdb" in its. Deleting them has never done any harm. Maybe not
the last time, after installing this 3.3.16?

Deleting the log files never does a harm to the installtion.

Post by L.Willms
I have now tried and started "Samba Gruppen- und Benutzermanagement"
(which is C:\APPS\SAMBA\SMBUSERS.EXE, I found out), and now there
exists a "messages.tdb" of 696 bytes length, but I can't log on, and I
can't view this file. Since I have switched to SAMBA from IBM PEER, I
have never logged on on the OS/2 machine, as far as I can remember.

The users database is stored in %ETC%\samba\private\secrets.tdb and
%ETC%\samba\private\passdb.tdb. If you delete these you will loose all
your users.

Regards,
Herwig

--
Mit freundlichen Grüßen/
With Best Regards

Herwig Bauernfeind

L.Willms

2011-08-16 10:26:42 UTC

Permalink

Am Tue, 16 Aug 2011 09:42:23 UTC, schrieb Herwig Bauernfeind

Post by Herwig Bauernfeind
The users database is stored in %ETC%\samba\private\secrets.tdb and
%ETC%\samba\private\passdb.tdb. If you delete these you will loose all
your users.

I say so what. The users are only myself as user and as
administrator.

If I can make a clean start that way, It's OK with me. Maybe I
should delete all *.tdb files?

Would SAMBA then come up with a dialog to add users, or to assign a
password to the administrator? Should I keep the smbpasswd file?

BTW, other signs of sickness is that the Netdrive control program
quite often stops (without me finding a trace or reason), especially
when a program tries to access a share on another PC (with Windows),
causing this program to crash.

And the SAMBA server portion started a few days ago to cause the
whole system to crash with e.g. a Trap D.

The other solution might be trying to get back to the previous
installed version which is 3.3.15-eCS 1.1.0-565, which I had used from
July 27 to August 8. Or even one more step back.

Could it be that lack of disk space could be a cause? Free space
was very low on the boot drive (10 MB before I removed a number of
dumps and old backups; now there are 7 GB free).

Cheers,

L.Willms

2011-08-16 11:12:06 UTC

Permalink

Am Tue, 16 Aug 2011 10:26:42 UTC, schrieb "L.Willms"

Post by L.Willms
Could it be that lack of disk space could be a cause? Free space
was very low on the boot drive (10 MB before I removed a number of
dumps and old backups; now there are 7 GB free).

... but this did not change the behaviour of the sick SMDB etc

Cheers,
L.W.

Doug Bissett

2011-08-16 14:48:08 UTC

Permalink

On Tue, 16 Aug 2011 11:12:06 UTC, "L.Willms"

Post by L.Willms
Am Tue, 16 Aug 2011 10:26:42 UTC, schrieb "L.Willms"

Post by L.Willms
Could it be that lack of disk space could be a cause? Free space
was very low on the boot drive (10 MB before I removed a number of
dumps and old backups; now there are 7 GB free).

... but this did not change the behaviour of the sick SMDB etc
Cheers,
L.W.

FWIW, I finally got some time to install SAMBA to a new install of eCS
2.1. I tried to pick out the proper, latest, versions of the files
(VERY confusing). I am having a problem where SMBD starts, and stops
immediately. From what I can determine, it is upset because there is
no GUEST account (which should have been created at install time). I
cannot start "Samba Users and Groups" because SMBD isn't running (why
would that be required?), so I have no idea what it actually
configured. Looking in the file, it appears that the ROOT account is
there, but no sign of Guest.

I guess that I will need to uninstall the whole thing, and start
again, with older versions.

--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)

Neil Waldhauer

2011-08-16 15:16:12 UTC

Permalink

On Tue, 16 Aug 2011 14:48:08 +0000 (UTC), "Doug Bissett"

Post by Doug Bissett
FWIW, I finally got some time to install SAMBA to a new install of eCS
2.1. I tried to pick out the proper, latest, versions of the files
(VERY confusing). I am having a problem where SMBD starts, and stops
immediately. From what I can determine, it is upset because there is
no GUEST account (which should have been created at install time). I
cannot start "Samba Users and Groups" because SMBD isn't running (why
would that be required?), so I have no idea what it actually
configured. Looking in the file, it appears that the ROOT account is
there, but no sign of Guest.
I guess that I will need to uninstall the whole thing, and start
again, with older versions.

With my attempts at installing SAMBA (should we be saying "server"?), I've
found if the guest account is not created, I'm better off uninstalling and
trying again until the guest account is created correctly.

Further, I think perhaps with both client and server, it would be good to
clarify what kind of Windows network is being used.

1. Peer to Peer with no domain server
2. A single domain server
3. Multiple server domain
4. Active directory in compatibiltiy mode
5. Active directory

Once we understand how to install, we should try to make some notes in the Wiki.

http://svn.netlabs.org/samba/wiki

Neil

--
Neil Waldhauer, neil-+wRFRm7RS6nqlBn2x/***@public.gmane.org

Fear is the darkroom where we develop our negatives.

L.Willms

2011-08-16 15:37:54 UTC

Permalink

Am Tue, 16 Aug 2011 14:48:08 UTC, schrieb "Doug Bissett"

am having a problem where SMBD starts, and stops immediately.

This sounds like the same problem as mine.

From what I can determine, it is upset because there is
no GUEST account (which should have been created at install time).

I see a "nobody" in smbpasswd, which should play the role of
"guest", I think.

I cannot start "Samba Users and Groups" because SMBD isn't running (why
would that be required?), so I have no idea what it actually
configured. Looking in the file, it appears that the ROOT account is
there, but no sign of Guest.

In which file do you look? The same smbpasswd in private\ ?

BTW, I had installed SAMBA already last year, and installed several
times newer versions. This is my version history (grep'ed from
log.smbd)

smbd version 3.0.37-eCS 1.0.3-354 started.
smbd version 3.0.37-eCS 1.0.4-424 started.
smbd version 3.0.37-eCS 1.0.6-557 started.
smbd version 3.3.15-eCS 1.1.0-565 started.
smbd version 3.3.16-eCS 1.1.0-613 started.

My problems started a few weeks ago, I can't really no longer say if
this was already with 3.3.15 or with 3.3.16.

Cheers,
L.W.

Doug Bissett

2011-08-16 16:34:15 UTC

Permalink

On Tue, 16 Aug 2011 14:48:08 UTC, "Doug Bissett"

Post by Doug Bissett
On Tue, 16 Aug 2011 11:12:06 UTC, "L.Willms"

Post by L.Willms
Am Tue, 16 Aug 2011 10:26:42 UTC, schrieb "L.Willms"

Post by L.Willms
Could it be that lack of disk space could be a cause? Free space
was very low on the boot drive (10 MB before I removed a number of
dumps and old backups; now there are 7 GB free).

... but this did not change the behaviour of the sick SMDB etc
Cheers,
L.W.

FWIW, I finally got some time to install SAMBA to a new install of eCS
2.1. I tried to pick out the proper, latest, versions of the files
(VERY confusing). I am having a problem where SMBD starts, and stops
immediately. From what I can determine, it is upset because there is
no GUEST account (which should have been created at install time). I
cannot start "Samba Users and Groups" because SMBD isn't running (why
would that be required?), so I have no idea what it actually
configured. Looking in the file, it appears that the ROOT account is
there, but no sign of Guest.
I guess that I will need to uninstall the whole thing, and start
again, with older versions.

To follow up:
It seems that guest is there, but not obvious. What made it start
working (for me) was to overwrite a more recent version of SAMBA (from
samba-1-2-beta7.wpi) with the contents of samba-1-1-0.zip.

YMMV...

--
From the eComStation of Doug Bissett
dougb007 at telus dot net
(Please make the obvious changes, to e-mail me)

L.Willms

2011-08-17 09:56:09 UTC

Permalink

Progress! See below

Am Tue, 16 Aug 2011 10:26:42 UTC, schrieb "L.Willms"

Post by L.Willms

Post by Herwig Bauernfeind
The users database is stored in %ETC%\samba\private\secrets.tdb and
%ETC%\samba\private\passdb.tdb. If you delete these you will loose all
your users.

OK, I dared to move the whole "lock" and "private" subdirectories
from %ETC%\samba to a backup directory, recreated the empty directory
structure (without any files in it), started the server, and it works,
without stopping right away. It seems that Samba did recreate all the
TDB files from the config file.

Maybe there is some incompability in the TDB file formats between
3.3 and erlier versions?

I can now again access the files on my OS/2 box from the Windows
PCs.

Sigh!

Only the GUI "Samba Status Monitor" does not start, but only shows
an empty window titled "VX-REXX Console for Samba Status Monitor", but
not the actual monitor. The other GUI programs might show the same
behaviour, but I have not yet tested them.

Maybe there is some incompability in the TDB file formats between
3.3 and erlier versions?

Cheers,
L.W.

L.Willms

2011-08-17 10:09:13 UTC

Permalink

Am Wed, 17 Aug 2011 09:56:09 UTC, schrieb "L.Willms"

Post by L.Willms
OK, I dared to move the whole "lock" and "private" subdirectories
from %ETC%\samba to a backup directory, recreated the empty directory
structure (without any files in it), started the server, and it works,
without stopping right away. It seems that Samba did recreate all the
TDB files from the config file.

Just for the info, below I quote the lines from log.smbd showing the

Post by L.Willms
[2011/08/17 11:41:04, 1] lib/util_unistr.c:load_case_tables(110)
creating lame upcase table
[2011/08/17 11:41:04, 1] lib/util_unistr.c:load_case_tables(125)
creating lame lowcase table
[2011/08/17 11:41:05, 0] smbd/server.c:main(1308)
Server priority set to PRTYC_FOREGROUNDSERVER
[2011/08/17 11:41:05, 0] smbd/server.c:main(1311)
smbd version 3.3.16-eCS 1.1.0-613 started.
Copyright Andrew Tridgell and the Samba Team 1992-2009
[2011/08/17 11:41:05, 2] lib/util_unistr.c:init_valid_table(204)
creating default valid table
[2011/08/17 11:41:06, 2] lib/tallocmsg.c:register_msg_pool_usage(106)
Registered MSG_REQ_POOL_USAGE
[2011/08/17 11:41:06, 2] lib/dmallocmsg.c:register_dmalloc_msgs(77)
Registered MSG_REQ_DMALLOC_MARK and LOG_CHANGED

Maybe this helps the develpment and maintenance teams in some way.

Cheerio,
L.W.

L.Willms

2011-09-26 19:47:56 UTC

Permalink

Am Wed, 17 Aug 2011 10:09:13 UTC, schrieb "L.Willms"

Post by L.Willms
Am Wed, 17 Aug 2011 09:56:09 UTC, schrieb "L.Willms"

This is just a test. Please disregard.

Cheers,
L.W.