BUG REPORT: Samba wount start with static IP and no printing

[rancor]

I'm using a fully patched Bubba Two where all services are turned off except Windows file share and with static IP.

With this setting I can't access the shared folders and samba is returning this error message:

[2010/04/25 16:10:53, 0] printing/print_cups.c:103(cups_connect)
Unable to connect to CUPS server localhost:631 - Connection refused

If I start "Printing" the network share works as expected and I got no further error messages. Another work around is to use DHCP at the LAN interface and if I do so I don't need to start "Printing".

The only tweak I have done is to install openvpn server

Best regards rancor

[rancor]

I was wrong in my analysis. After a reboot the system stopped working again and in /var/log/samba/log.all is this logged:

[2010/04/25 17:09:59, 0] lib/interface.c:550(load_interfaces)
WARNING: no network interfaces found
[2010/04/25 17:10:00, 0] smbd/server.c:616(open_sockets_smbd)
open_sockets_smbd: No sockets available to bind to.
[2010/04/25 17:10:00, 0] smbd/server.c:837(exit_server_common)
===============================================================
[2010/04/25 17:10:00, 0] smbd/server.c:839(exit_server_common)
Abnormal server exit: open_sockets_smbd() failed
[2010/04/25 17:10:00, 0] smbd/server.c:840(exit_server_common)
===============================================================
[2010/04/25 17:10:00, 0] lib/util.c:1584(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x40) [0x102f4a24]
#1 /usr/sbin/smbd [0x105fb530]
#2 /usr/sbin/smbd [0x105fb6d8]
#3 /usr/sbin/smbd(main+0x7a8) [0x105fbf3c]
#4 /lib/tls/libc.so.6 [0xf8f0994]
#5 /lib/tls/libc.so.6(__libc_start_main+0xb0) [0xf8f0ad0]
[2010/04/25 17:10:00, 0] lib/fault.c:321(dump_core)
dumping core in /var/log/samba/cores/smbd

I must restart samba to get it to work with /etc/init.d/samba restart

If I'm running with DHCP on LAN the system works all the time

[rancor]

I got it working by enabling all services.

By enabling all services I got a slower start up time and the interface has more time to initialize?

[wm.bubba]

I too am having the same problem, and like you, rancor, I have a static IP address with most services turned off, including printing.

I have been using /etc/init.d/samba restart to get samba up each time my BUBBA is restarted. I personally would rather do that than enabling all services, most of which I won't use.

For me, this problem started after the upgrade to 1.3.0, and hasn't been addressed in the latest version 2 upgrade.

This is the extract from my /var/log/samba/log.all :

[2010/04/26 23:37:47, 1] smbd/service.c:1047(make_connection_snum)
192.168.1.2 (192.168.1.2) connect to service home initially as user wies (uid=1001, gid=100) (pid 3401)
[2010/04/26 23:38:27, 1] smbd/service.c:1226(close_cnum)
192.168.1.2 (192.168.1.2) closed connection to service home
[2010/04/26 23:40:13, 0] lib/util_sock.c:938(open_socket_in)
bind failed on port 445 socket_addr = fe80::222:2ff:fe00:611%eth1.
Error = Cannot assign requested address
[2010/04/26 23:40:13, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Cannot assign requested address
[2010/04/26 23:40:13, 0] lib/util_sock.c:938(open_socket_in)
bind failed on port 139 socket_addr = fe80::222:2ff:fe00:611%eth1.
Error = Cannot assign requested address
[2010/04/26 23:40:13, 0] smbd/server.c:457(smbd_open_one_socket)
smbd_open_once_socket: open_socket_in: Cannot assign requested address
[2010/04/26 23:40:13, 0] smbd/server.c:616(open_sockets_smbd)
open_sockets_smbd: No sockets available to bind to.
[2010/04/26 23:40:13, 0] smbd/server.c:837(exit_server_common)
===============================================================
[2010/04/26 23:40:13, 0] smbd/server.c:839(exit_server_common)
Abnormal server exit: open_sockets_smbd() failed
[2010/04/26 23:40:13, 0] smbd/server.c:840(exit_server_common)
===============================================================
[2010/04/26 23:40:13, 0] lib/util.c:1584(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x40) [0x102f4a24]
#1 /usr/sbin/smbd [0x105fb530]
#2 /usr/sbin/smbd [0x105fb6d8]
#3 /usr/sbin/smbd(main+0x7a8) [0x105fbf3c]
#4 /lib/tls/libc.so.6 [0xf8f0994]
#5 /lib/tls/libc.so.6(__libc_start_main+0xb0) [0xf8f0ad0]
[2010/04/26 23:40:13, 0] lib/fault.c:321(dump_core)
dumping core in /var/log/samba/cores/smbd

Where do we go from here?

[kfudd]

Same problem here. Using a static IP address, samba doesn't start on boot.

[RobV]

Same with me, Samba doesn't start automatically on boot since 1.3.0.
I have Static IP on LAN, DHCP on WAN and following services enabled: Windows share, both Streaming services, and Up-/download
RobV

[nyogtha]

I have the exact same problem. My setup is identical to the last poster. (Re)starting Samba via SSH fixes it.

[Lotussteve]

Hello!

A "me too!" from here, if you need any additional infos please let me know!

(Static IP, behaviour apparent since 1.3.x, Restart via SSH fixes it, logs log similar like the ones posted above!)


HTH,

Ciao,

Steve

[wm.bubba]

Hi Guys,

Not sure how much help this is going to be, but samba now seems to be working on my BUBBA.

During the last week or so, I have shut down and restarted BUBBA a number of time, and on each occasion samba is up and running.

I did try to update several times, but each time I was told there were no updates. Perhaps something was reset as part of this update process.

Maybe Excito can shed some light on the goings on with samba?

[wm.bubba]

I believed this problem to have been fixed. However, I have now upgraded to the latest version, but I am still suffering with this SAMBA problem.

I do have a workaround, which is not ideal. Is this something that is being looked at, and how soon will a solution be forthcoming.

Thanks.

[fmvaz]

After updating to 2.0, samba did not work either. I used the /etc/init.d/samba restart command and it works again. I have static IP for Bubba, DHCP on for LAN (unlike rancor), printing is off. WAN is on DHCP.

This is the samba log, I rebooted using the GUI after the sofware update.
[2010/06/25 09:20:06, 0] smbd/server.c:837(exit_server_common)
===============================================================
[2010/06/25 09:20:06, 0] smbd/server.c:839(exit_server_common)
Abnormal server exit: open_sockets_smbd() failed
[2010/06/25 09:20:06, 0] smbd/server.c:840(exit_server_common)
===============================================================
[2010/06/25 09:20:06, 0] lib/util.c:1584(log_stack_trace)
BACKTRACE: 6 stack frames:
#0 /usr/sbin/smbd(log_stack_trace+0x40) [0x102f4a24]
#1 /usr/sbin/smbd [0x105fb530]
#2 /usr/sbin/smbd [0x105fb6d8]
#3 /usr/sbin/smbd(main+0x7a8) [0x105fbf3c]
#4 /lib/tls/libc.so.6 [0xf8f0994]
#5 /lib/tls/libc.so.6(__libc_start_main+0xb0) [0xf8f0ad0]
[2010/06/25 09:20:06, 0] lib/fault.c:321(dump_core)
dumping core in /var/log/samba/cores/smbd

After this, the first entries in the log are after manual restart of Samba as described above. It looks that it crashes after the software update and does not restart properly. The smbd directory is empy btw.

Maybe of note is that is was the first time that I used the new "restart" button of the new GUI instead of turning bubba of manually. Could this have something to do with it?

Otherwise; another user with a similar samba bug, Excito guys, maybe it is worth looking into? Windows share is a pretty important feature of Bubba

[wm.bubba]

Just to confirm my settings - I have static IP for Bubba, DHCP on for LAN , printing is off.
I don't use the WAN, and neither have I used the new "restart" button on the GUI.

I have had this issue now for the best part of 2 months, ever since the upgrade from 1.3.0 to 2.0.

I was hoping this would have been fixed in a hotfix or major upgrade, but not so.

Can we have some feedback on this, please

[Moloko]

I have also the same behavior, with the same setup as mentioned by user wm.bubba - the Samba service won't start automatically after a reboot.

I am running 2.0.4 since yesterday, hoping that it would be fixed.

I am disappointed that this is still not fixed, not to mention it's a real pain in the neck having to manually restart Samba each time Bubba for some reason reboots....


I know you guys at Excito have much to do, but could somebody take look at this issue?

[Tompa]

I too have the same problem.

Running 2.0.4

Static IP on LAN, DHCP-server on LAN enabled.
DHCP IP on WAN.

Extract from samba log:

Code: Select all

===============================================================
[2010/07/03 08:50:31, 0] smbd/server.c:839(exit_server_common)
Abnormal server exit: open_sockets_smbd() failed
[2010/07/03 08:50:31, 0] smbd/server.c:840(exit_server_common)
===============================================================

As for the others, a manual

Code: Select all

/etc/init.d/samba restart

is enough to get the service working.

/Tompa

[giorgio]

Me too.. same problem.. have to do a manual restart of samba.