samba - Mar 2000 - cannot start samba

Hi,
I need help.
I am running Caldera eServer 2.3 and cannot start
samba.
I used webmin and a get the following error
Failed to start samba servers : /usr/sbin/nmbd failed

I also tried to start it from the command line using
samba start and it seems to be running, but I don't
think it is.
Any help is very much appriciated.
thanks

====Alexander W. Miranda
Systems Engineer

                       \\\ | ///
                       \\ ~ ~ //
                        ( @ @ )
        -------------oOOo-(_)-oOOo-------------------

__________________________________________________
Do You Yahoo!?
Talk to your friends online with Yahoo! Messenger.
http://im.yahoo.com

Hi,
I currently have an old samba 2.2.2 on my network. It's working, but
it's
quite old...
I tried version 3.0.0rc4 but it doesn't want to start. Here are the errors :

[2003/09/23 18:27:45, 8] lib/util.c:fcntl_lock(1621)
  fcntl_lock 6 13 0 1 1
[2003/09/23 18:27:45, 3] lib/util.c:fcntl_lock(1632)
  fcntl_lock: fcntl lock gave errno 22 (Invalid argument)
[2003/09/23 18:27:45, 3] lib/util.c:fcntl_lock(1651)
  fcntl_lock: lock failed at offset 0 count 1 op 13 type 1 (Invalid argument)
[2003/09/23 18:27:45, 0] lib/pidfile.c:pidfile_create(97)
  ERROR: nmbd : fcntl lock of file 
/usr/local/samba-3.0.0rc4/var/locks/nmbd.pid failed. Error was Invalid 
argument

The server is a linux 2.4.17 (i cannot change the kernel). 
Can you help me ?

-- 
Bruno PINAUD
Performanse SA

Does the /usr/local/samba-3.0.0rc4/var/locks/ directory exists? Witch
account do you use to launch you init script? in case this is not root,
does it have suffisent permission?

Also, how about starting nmbd and smbd manually, with -D option?

>yes i'm using init.d (redhat style). samba is installed in
>/usr/local/samba-3.0.0rc4/. I've got a symbolic link to /usr/local/samba
>which is used by the init.d script.
>
>Le Mercredi 24 Septembre 2003 19:22, Matias Silva a ?crit :
>> It looks like you are still trying to access the 3.0 version pid file
>>
>>  > /usr/local/samba-3.0.0rc4/var/locks/nmbd.pid failed. Error was
Invalid
>>  > argument
>>
>> How are you starting and stopping samba?  Are you using init.d?
>>
>> Matias
>>
>> Bruno Pinaud wrote:
>> > Hi,
>> > I currently have an old samba 2.2.2 on my network. It's
working, but
it's
>> > quite old...
>> > I tried version 3.0.0rc4 but it doesn't want to start. Here
are the
>> > errors :
>> >
>> > [2003/09/23 18:27:45, 8] lib/util.c:fcntl_lock(1621)
>> >   fcntl_lock 6 13 0 1 1
>> > [2003/09/23 18:27:45, 3] lib/util.c:fcntl_lock(1632)
>> >   fcntl_lock: fcntl lock gave errno 22 (Invalid argument)
>> > [2003/09/23 18:27:45, 3] lib/util.c:fcntl_lock(1651)
>> >   fcntl_lock: lock failed at offset 0 count 1 op 13 type 1
(Invalid
>> > argument) [2003/09/23 18:27:45, 0]
lib/pidfile.c:pidfile_create(97)
>> >   ERROR: nmbd : fcntl lock of file
>> > /usr/local/samba-3.0.0rc4/var/locks/nmbd.pid failed. Error was
Invalid
>> > argument
>> >
--
Vincent

>> Does the /usr/local/samba-3.0.0rc4/var/locks/ directory exists? Witch
>yes it does.
Sorry, i didn't read the code enought. The error would not be the same.
>same problem with both...
This is normal, since pid files are handle by samba itself
>Perhaps it's related to my kernel but actually samba 2.2.2 is working...
I don't think so, since the error tell us that pid files can not be locked.

>[2003/09/23 18:27:45, 8] lib/util.c:fcntl_lock(1621)
>fcntl_lock 6 13 0 1 1
>[2003/09/23 18:27:45, 3] lib/util.c:fcntl_lock(1632)
>  fcntl_lock: fcntl lock gave errno 22 (Invalid argument)
>[2003/09/23 18:27:45, 3] lib/util.c:fcntl_lock(1651)
>  fcntl_lock: lock failed at offset 0 count 1 op 13 type 1 (Invalid
  argument)
>[2003/09/23 18:27:45, 0] lib/pidfile.c:pidfile_create(97)
>  ERROR: nmbd : fcntl lock of file
>/usr/local/samba-3.0.0rc4/var/locks/nmbd.pid failed. Error was Invalid
>argument
I think the error is reported by the fcntl() system call. I don't know
about the reason. "Invalid argument" seems not to be related to a
problem
on the file system, nor the kernel ressources. However, i never saw this
error on my own servers, so this sould not be a bad argument passing to the
function.

This error thus astonishes me much and i'm also insterested by the real
reason.

--
Vincent