smb will not start at boot

[lovswr]

Hello. I don't know if this is a samba problem or a boot problem.

I just got my printer sharing working with CUPS. I wanted to make sure that in the case of a power outage, everything would reboot & my family would still be able to print. Well everything is good to go, except I just noticed that smb always fails at boot (message scrolls by very quickly, but the red FAILED is easy to notice).


nmb starts just fine. I am using FC8 kernel 2.6.25.9-40.

[marcrblevins]

Start terminal and try:

su -
chkconfig --list | grep smb
chkconfig --list | grep nmb

If either has all set to 'off' then

chkconfig smb on
chkconfig nmb on

Can you show me the result of:

service nmb restart
service smb restart

[lovswr]

some of them were off & they still were off after I ran the chkconfig command.




[root@matrix ~]# chkconfig --list | grep smb
smb 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@matrix ~]# chkconfig --list | grep nmb
nmb 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@matrix ~]# chkconfig smb on
[root@matrix ~]# chkconfig nmb on
[root@matrix ~]# chkconfig --list | grep smb
smb 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@matrix ~]# service nmb restart
Shutting down NMB services: [ OK ]
Starting NMB services: [ OK ]
[root@matrix ~]# service smb restart
Shutting down SMB services: [ OK ]
Starting SMB services: [ OK ]
[root@matrix ~]# chkconfig --list | grep nmb
nmb 0:off 1:off 2:on 3:on 4:on 5:on 6:off

[marcrblevins]

chkconfig looks correct.

When you see those [OK] from nmb & smb, should be ready to go.
Go ahead and reboot your Linux box. Then start terminal, type:

su -
service smb status

Should say running...

[lovswr]

chkconfig looks correct.

When you see those [OK] from nmb & smb, should be ready to go.
Go ahead and reboot your Linux box. Then start terminal, type:

su -
service smb status

Should say running...

Sorry it took me so long to reply.



[root@matrix ~]# service smb status
smbd is stopped



also when the boot messages were running by, I saw FAILED in red letters next to starting SMB...

[marcrblevins]

Both stopped when trying to start it?

su -
service nmb restart
service smb restart

Both failed?

Did you use your firewall and checked samba?

su -
system-config-firewall

[lovswr]

Both stopped when trying to start it?

su -
service nmb restart
service smb restart

Both failed?

Did you use your firewall and checked samba?

su -
system-config-firewall



I don't use the software firewall at all. I use the one that is built into my Linksys router & the one inside my Bellsouth DSL Modem/router

[marcrblevins]

Ok then, try:

su -
testparm /etc/samba/smb.conf

Just to may sure smb.conf not messed up.

[lovswr]

Ok then, try:

su -
testparm /etc/samba/smb.conf

Just to may sure smb.conf not messed up.


You may be on to something here...



[root@matrix ~]# testparm /etc/samba/smb.conf
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[printers]"
Processing section "[MP830]"
Processing section "[marlene]"
Loaded services file OK.
Invalid combination of parameters for service MP830. Level II oplocks can only be set if oplocks are also set.
Server role: ROLE_STANDALONE
Press enter to see a dump of your service definitions


The real reason that I want samba to start up automatically, is in case of a power failure. I have my Canon MP830 connected to this box & thus the rest of my (windows) network via CUPS. When I got MP830 to work, it just added "printers" & MP830. I have been afraid to just delete the printers share, as everything actually does work ( & the linux printer driver is much faster than the native windows one that came with the printer!)