Unable to see CIF connections from a shell

Status
Not open for further replies.

billm

Dabbler
Joined
Jun 23, 2011
Messages
23
when I run "smbstatus" from the shell, I get the error
locking.tdb not initialised.

If I restart smbd and nmbd from the web admin or from the shell, the locking.tdb file is created in /var/db/samba and smbstatus works again.

I'm running FreeNAS-8.2.0-BETA2-x64 (r10638). I upgraded from FreeNAS-8.0.4-RELEASE-x64.GUI_Upgrade and before that FreeNAS-8.0.4-BETA2-x64.GUI_Upgrade.

Everything else seems to work fine. But I would like to fix this problem short of a fresh install.

Log files follow.

log.smbd:

[2012/03/14 11:20:55, 0] smbd/server.c:1051(main)
smbd version 3.6.3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2012/03/14 11:20:55.399084, 0] smbd/server.c:1107(main)
standard input is not a socket, assuming -D option
[2012/03/14 11:20:55.505437, 1] smbd/files.c:204(file_init)
file_init: Information only: requested 16384 open files, 11075 are available.
[2012/03/14 11:28:16, 0] smbd/server.c:1051(main)
smbd version 3.6.3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2012/03/14 11:28:16.071092, 0] smbd/server.c:1107(main)
standard input is not a socket, assuming -D option
[2012/03/14 11:28:16.090055, 1] smbd/files.c:204(file_init)
file_init: Information only: requested 16384 open files, 11075 are available.
[2012/03/14 11:31:36.110881, 1] smbd/service.c:1081(make_connection_snum)
the-86 (192.168.3.86) connect to service data initially as user billm (uid=1001, gid=0) (pid 3107)

log.nmbd:


[2012/03/14 11:21:01, 0] nmbd/nmbd.c:860(main)
nmbd version 3.6.3 started.
Copyright Andrew Tridgell and the Samba Team 1992-2011
[2012/03/14 11:21:01, 0] nmbd/nmbd.c:888(main)
standard input is not a socket, assuming -D option
[2012/03/14 11:21:25, 0] nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
*****

Samba name server BILLNAS is now a local master browser for workgroup HOME on subnet 192.168.1.36

*****
 

willy.tenner

Cadet
Joined
Apr 17, 2012
Messages
2
I got the same issue since upgrading from FreeNAS-8.0.4-RELEASE-x64 to FreeNAS-8.0.4-RELEASE-p1-x64.

Had to stop and restart smbd manually after each reboot of the server. I wrote a script for automatic shutdown of my home server which needs the correct output from smbstatus. For now it's worthless for me and I must shutdown the server by hand.

What happened between FreeNAS-8.0.4-RELEASE and FreeNAS-8.0.4-RELEASE-p1 ???
 

willy.tenner

Cadet
Joined
Apr 17, 2012
Messages
2
@protosd: You think the issue is caused by the samba 3.6.4 upgrade? I already searched the web for any problems with this version but found nothing. Yesterday I opened a trouble ticket @ support.freenas.org.

Kind regards,
Willy
 

ProtoSD

MVP
Joined
Jul 1, 2011
Messages
3,348
Hi Willy,

Maybe not so much specifically with Samba itself, but something with the way it was integrated into FreeNAS. It's probably a simple syntax error or small change in logic where samba gets started. Tickets are a good way to alert the developers who are familiar enough with the code to know where to check for possible problems. Right now they're working pretty hard to get 8.2 out and something simple could have easily been overlooked. Thanks for opening a ticket, it's helpful to everyone!
 
Status
Not open for further replies.
Top