Samba service doesn't start automatically

Bug #480152 reported by Michał Gołębiowski-Owczarek
34
This bug affects 7 people
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: samba

I always have to manually trigger:
$ sudo /etc/init.d/samba restart
Otherwise, my shares are not visible in the network.

ProblemType: Bug
Architecture: amd64
Date: Tue Nov 10 18:36:17 2009
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: wl
Package: samba 2:3.4.0-3ubuntu5
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: samba
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
Michał Gołębiowski-Owczarek (mgol) wrote :
Revision history for this message
Thierry Carrez (ttx) wrote :

Please give more information on your setup. It probably tries to start and fail for a reason. Is there anything in the logs (/var/log/samba/) when it fails to start at boot ? What is your networking setup ? Wireless, fixed ? Is it configured through networkmanager or /etc/network/interfaces ?

Changed in samba (Ubuntu):
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Chuck Short (zulcss) wrote :

Hi,

Please attach your /var/log/samba/log.smbd.

Thanks
chuck

Changed in samba (Ubuntu):
importance: Medium → Low
Revision history for this message
Michał Gołębiowski-Owczarek (mgol) wrote :

Sorry for the delay.First samba restart raises an error:
$ sudo service samba restart
 * Stopping Samba daemons
start-stop-daemon: warning: failed to kill 1839: No such process
                                                                                                                     [OK]
 * Starting Samba daemons [OK]

The second restart works fine:
$ sudo service samba restart
 * Stopping Samba daemons [ OK ]
 * Starting Samba daemons [ OK ]

After that, I looked at a requested file, here it is:
$ cat /var/log/samba/log.smbd
[2009/11/16 02:58:58, 0] lib/util_sock.c:1468(get_peer_addr_internal)
  getpeername failed. Error was Transport endpoint is not connected
[2009/11/17 07:39:38, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/11/17 07:39:39, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/11/17 07:39:39, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/11/17 07:39:42, 0] smbd/server.c:1068(main)
  smbd version 3.4.0 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2009/11/17 07:39:42, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use
[2009/11/17 07:39:42, 0] smbd/server.c:456(smbd_open_one_socket)
  smbd_open_once_socket: open_socket_in: Address already in use

Revision history for this message
Michał Gołębiowski-Owczarek (mgol) wrote :

To make logs more understandable - both samba restarts were run at 7:39, one after another.

Chuck Short (zulcss)
Changed in samba (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Michał Gołębiowski-Owczarek (mgol) wrote :

It's been a month since last activity appeared on this bug report. Any chances of fixing it?

Revision history for this message
ethanay (ethan-y-us) wrote :

this affects my parent's laptop, but not mine -- nearly identical, up-to-date installs of 9.10

on the plus side, i have used it as an opportunity to teach my mom how to use some terminal commands :D

Revision history for this message
HStoic (reddishegret) wrote :

This bug affects one Karmic machine but not another Karmic machine on our network. No obvious differences (to me) between the two -- they run similar apps -- although the afflicted machine often runs a VirtualBox guest WinXP virtual machine. I'd be glad to run diagnostics if someone can suggest what to do.

Revision history for this message
Michał Gołębiowski-Owczarek (mgol) wrote :

I also run VirtualBox Windows XP guest. But how could it affect samba processes? It seems unbelievable...

Revision history for this message
HStoic (reddishegret) wrote :

Michael, you're right, it's too unbelievable. I just noticed that after the most recent reboot, Samba also did not restart on the other Karmic machine (no VirtualBox). OTOH, Samba did successfully restart after the most recent reboot of the machine that runs VirtualBox.

So my experience can be summarized as: *Sometimes* Samba fails to restart after rebooting Karmic, on both Karmic machines here. AFAIK VirtualBox is a red herring.

Another thought, FWIW: Both these Karmics were upgraded from Jaunty; neither is a clean Karmic install.

Revision history for this message
Thierry Carrez (ttx) wrote :

Probably a duplicate of bug 462169.
A fixed samba was released Saturday to karmic-updates. Please confirm that it fixes the issue.

Changed in samba (Ubuntu):
importance: Low → Medium
status: Confirmed → Incomplete
Revision history for this message
Michał Gołębiowski-Owczarek (mgol) wrote :

I can't reproduce it any more. Seems to be fixed.

Revision history for this message
Chuck Short (zulcss) wrote :

Thanks for the info.

Regards
chuck

Changed in samba (Ubuntu):
status: Incomplete → Fix Released
Revision history for this message
HStoic (reddishegret) wrote :

Looking good. Both my Karmic machines have been automatically restarting Samba after reboots. Thanks for the fix.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.