What can I do to get Samba to autostart on booting?
The sticky at the top of this section indicates that it is applicable for 12.1 and not for 12.2 so I have not tried that.
I am running 12.2 x 64 KDE.
I have installed jdmcdaniel3’s Swat script. This is a screen shot of the status after booting:
I can start it manually using Swap tool but only if I choose ‘restart’ and then ‘start’. Choosing only ‘start’ will not start it.
After some period of time, it stops again. I have not tracked that period, it seems to run at least an hour before stopping.
I am running Suse inside a private addr. network and all samba connections are on the same subnet. Suse connects to the internet via a different computer serving as NAT & Gateway.
Runlevel services has SMB & NMB set for levels 3 & 5 and displays them as Enabled.
Here are the results of service nmb status; service smb status
nmb.service - LSB: Samba NetBIOS naming service over IP
Loaded: loaded (/etc/init.d/nmb)
Active: active (running) (Result: exit-code) since Sun, 25 Nov 2012 18:53:29 -0800; 1h 21min ago
Process: 3546 ExecReload=/etc/init.d/nmb reload (code=exited, status=3/NOTIMPLEMENTED)
Process: 3519 ExecStart=/etc/init.d/nmb start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/nmb.service
└ 3529 /usr/sbin/nmbd -D -s /etc/samba/smb.conf
smb.service - LSB: Samba SMB/CIFS file and print server
Loaded: loaded (/etc/init.d/smb)
Active: active (running) since Sun, 25 Nov 2012 18:53:23 -0800; 1h 21min ago
Process: 3554 ExecReload=/etc/init.d/smb reload (code=exited, status=0/SUCCESS)
Process: 1880 ExecStart=/etc/init.d/smb start (code=exited, status=0/SUCCESS)
CGroup: name=systemd:/system/smb.service
├ 1989 /usr/sbin/smbd -D -s /etc/samba/smb.conf
└ 2525 /usr/sbin/smbd -D -s /etc/samba/smb.conf
The firewall returns FW_CONFIGURATIONS_EXT=“netbios-server samba-client samba-server”
and I don’t think the FW is an issue since I can start manually and it runs for some time before stopping itself.
The process monitor & top both show 2 smbd processes running.
On 11/25/2012 10:56 PM, 6520302 wrote:
>
> What can I do to get Samba to autostart on booting?
> The sticky at the top of this section indicates that it is applicable
> for 12.1 and not for 12.2 so I have not tried that.
> I am running 12.2 x 64 KDE.
> I have installed jdmcdaniel3’s Swat script. This is a screen shot of
> the status after booting:
>
> ‘SUSE Paste’ (http://paste.opensuse.org/38215781)
>
> I can start it manually using Swap tool but only if I choose ‘restart’
> and then ‘start’. Choosing only ‘start’ will not start it.
> After some period of time, it stops again. I have not tracked that
> period, it seems to run at least an hour before stopping.
>
> I am running Suse inside a private addr. network and all samba
> connections are on the same subnet. Suse connects to the internet via a
> different computer serving as NAT & Gateway.
>
> Runlevel services has SMB & NMB set for levels 3 & 5 and displays them
> as Enabled.
>
> Here are the results of service nmb status; service smb status
>
>
> Code:
> --------------------
> nmb.service - LSB: Samba NetBIOS naming service over IP
> Loaded: loaded (/etc/init.d/nmb)
> Active: active (running) (Result: exit-code) since Sun, 25 Nov 2012 18:53:29 -0800; 1h 21min ago
> Process: 3546 ExecReload=/etc/init.d/nmb reload (code=exited, status=3/NOTIMPLEMENTED)
> Process: 3519 ExecStart=/etc/init.d/nmb start (code=exited, status=0/SUCCESS)
> CGroup: name=systemd:/system/nmb.service
> └ 3529 /usr/sbin/nmbd -D -s /etc/samba/smb.conf
>
> smb.service - LSB: Samba SMB/CIFS file and print server
> Loaded: loaded (/etc/init.d/smb)
> Active: active (running) since Sun, 25 Nov 2012 18:53:23 -0800; 1h 21min ago
> Process: 3554 ExecReload=/etc/init.d/smb reload (code=exited, status=0/SUCCESS)
> Process: 1880 ExecStart=/etc/init.d/smb start (code=exited, status=0/SUCCESS)
> CGroup: name=systemd:/system/smb.service
> ├ 1989 /usr/sbin/smbd -D -s /etc/samba/smb.conf
> └ 2525 /usr/sbin/smbd -D -s /etc/samba/smb.conf
>
> --------------------
>
>
> The firewall returns FW_CONFIGURATIONS_EXT=“netbios-server samba-client
> samba-server”
> and I don’t think the FW is an issue since I can start manually and it
> runs for some time before stopping itself.
>
> The process monitor & top both show 2 smbd processes running.
>
> Thanks, Jon
>
>
Jon;
Is there anything in /var/log/samba/log.[n,s]mbd that might give a hint to why
smbd and nmbd are halting?
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
Is there anything in /var/log/samba/log.[n,s]mbd that might give a hint to why
smbd and nmbd are halting?
No, there isn’t anything but I’ll keep checking those logs. It doesn’t arbitrarily quit every time but it seems to quit often.
What is particularly annoying is that each bootup is not the same. This morning when I booted Samba started just fine.
I read some email, checked some web sites, updated some apps and shutdown.
Later I booted and Samba did not start but the processes were running. I had to do a smb ‘restart’ in Swat to get it going.
At other times I have issues with gapcmon (ups monitor) that is in the system tray not loading on boot. But other things I have in the sys tray are there so I can’t understand why these few things are different between bootups.
Guess I’ll have to keep watching this and take lots of notes.
On 11/26/2012 4:16 PM, 6520302 wrote:
>
>> Is there anything in /var/log/samba/log.[n,s]mbd that might give a hint
>> to why
>> smbd and nmbd are halting?
>
> No, there isn’t anything but I’ll keep checking those logs. It doesn’t
> arbitrarily quit every time but it seems to quit often.
>
> What is particularly annoying is that each bootup is not the same.
> This morning when I booted Samba started just fine.
> I read some email, checked some web sites, updated some apps and
> shutdown.
>
> Later I booted and Samba did not start but the processes were running.
> I had to do a smb ‘restart’ in Swat to get it going.
>
> At other times I have issues with gapcmon (ups monitor) that is in the
> system tray not loading on boot. But other things I have in the sys
> tray are there so I can’t understand why these few things are different
> between bootups.
>
> Guess I’ll have to keep watching this and take lots of notes.
>
> Jon
>
>
Jon;
You might try disabling AppArmor; YaST>Novell AppArmor>AppArmor Control Panel.
I don’t really think AppArmor is the problem, since if it were the effect on
smbd should be immediate and occur every time. At least disabling AppArmor will
eliminate one possibility.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
On 11/26/2012 7:03 PM, PV wrote:
> On 11/26/2012 4:16 PM, 6520302 wrote:
<snip>
>
> You might try disabling AppArmor; YaST>Novell AppArmor>AppArmor Control Panel. I
> don’t really think AppArmor is the problem, since if it were the effect on smbd
> should be immediate and occur every time. At least disabling AppArmor will
> eliminate one possibility.
>
>
Edit:
Is this a fresh install? Did you check the media? Have you checked
/var/log/messages ?
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
I just wanted to let you know that on one PC I have seen the same behavior, even as two others PC I work with have no such issue. All PC’s use openSUSE 12.2, but oddly the one PC with the issue is also running the nVIDIA proprietary video driver while the others are not. Since I can cause it to start and only restart when testing out new kernels, it is only a problem when you restart your PC. Should I determine what is wrong, I shall let you know, but no idea what might keep smbd from starting every time.
On 11/26/2012 9:06 PM, jdmcdaniel3 wrote:
>
> 6520302;2506758 Wrote:
>> No, there isn’t anything but I’ll keep checking those logs. It doesn’t
>> arbitrarily quit every time but it seems to quit often.
>>
>> What is particularly annoying is that each bootup is not the same.
>> This morning when I booted Samba started just fine.
>> I read some email, checked some web sites, updated some apps and
>> shutdown.
>>
<snip>
>> Guess I’ll have to keep watching this and take lots of notes.
>>
>> Jon
>
> I just wanted to let you know that on one PC I have seen the same
> behavior, even as two others PC I work with have no such issue. All
> PC’s use openSUSE 12.2, but oddly the one PC with the issue is also
> running the nVIDIA proprietary video driver while the others are not.
> Since I can cause it to start and only restart when testing out new
> kernels, it is only a problem when you restart your PC. Should I
> determine what is wrong, I shall let you know, but no idea what might
> keep smbd from starting every time.
>
> Thank You,
>
>
James & Jon;
You should be able to test if the nVIDIA driver is the cause for [s,n]mbd not
starting by booting into runlevel 3 a few times.
–
P.V.
“We’re all in this together, I’m pulling for you” Red Green
Hello,
I have the same behaviour and hope someone will find the solution. I also have a Radeon card (HD4850), so I don’t think the Nvidia drivers are to blame.
Romain
.