Trouble starting samba server

I have an old desktop running OpenSuse 11.4, and I’ve recently installed samba. I can’t seem to get the smb daemon or the samba server to start.

adam@linux-hihn:~> sudo /sbin/service smb stop
root's password:
Shutting down Samba SMB daemon  Warning: daemon not running.                            done
adam@linux-hihn:~> sudo /sbin/service smb start
Starting Samba SMB daemon                                                               done
adam@linux-hihn:~> sudo /sbin/service smb status
Checking for Samba SMB daemon 
adam@linux-hihn:~> 


After reading though some of the information on here I went into the Novell AppArmor control center and set the services to “compain” instead of enforce.

What else is wrong?

I’ve done some other configuring of Samba in Yast. Do I need to type in the NetBios name?

I was also able to view the status page in SWAT. It says the nmbd is running, but smbd is not running, nor is winbind. I guess pretty much the same information I got from the command line.

Any help is appreciated. I’ve been tying to get samba working on this box for days now.

On 12/15/2012 06:56 PM, treeup wrote:
> I have an old desktop running OpenSuse 11.4

-=WELCOME=- new poster!!

i can’t help with samba but i can inform you that openSUSE 11.4 is past
its end of life (cite: http://en.opensuse.org/Lifetime, no
longer receiving security patches through normal means. It therefore
should not be exposed to untrusted networks unless it incorporates
Evergreen, http://tinyurl.com/4aflkpy

there are some samba experts here, one often here has some web pages on
the subject which you will probably find very helpful
http://www.swerdna.net.au/


dd

On 12/15/2012 11:56 AM, treeup wrote:
>
> I have an old desktop running OpenSuse 11.4, and I’ve recently installed
> samba. I can’t seem to get the smb daemon or the samba server to start.
>
>
> Code:
> --------------------
> adam@linux-hihn:~> sudo /sbin/service smb stop
> root’s password:
> Shutting down Samba SMB daemon Warning: daemon not running. done
> adam@linux-hihn:~> sudo /sbin/service smb start
> Starting Samba SMB daemon done
> adam@linux-hihn:~> sudo /sbin/service smb status
> Checking for Samba SMB daemon
> adam@linux-hihn:~>
>
>
> --------------------
>
>
> After reading though some of the information on here I went into the
> Novell AppArmor control center and set the services to “compain”
> instead of enforce.
>
> What else is wrong?
>
> I’ve done some other configuring of Samba in Yast. Do I need to type
> in the NetBios name?
>
> I was also able to view the status page in SWAT. It says the nmbd is
> running, but smbd is not running, nor is winbind. I guess pretty much
> the same information I got from the command line.
>
> Any help is appreciated. I’ve been tying to get samba working on this
> box for days now.
>
>
treeup;

Do you have smb set to start at boot?

YaST > system > System Services (Runlevel). Make sure nmb and smb are set to
start at boot. There is no need for winbind unless you have a trust relation
with a Windows Domain. If smb is already set to start at boot, try to start smb
with:


su -
rcsmb start

Then immediately check /var/log/messages and /var/log/samba/log.smbd.


su -
tail -n30 /var/log/messages
tail  /var/log/samba/log.smbd

Is there any hint why smbd fails to start?


P.V.
“We’re all in this together, I’m pulling for you” Red Green

I believe that I have samba set to start at boot. I checked in Yast -> System -> System Service (Runlevel) and smb and nmb are enabled. I don’t know if that starts it on boot or not.

Anyway, here are the results from the other commands.

tail /var/log/

adam@linux-hihn:~> su
Password: 
linux-hihn:/home/adam # rcsmb start
Starting Samba SMB daemon                                                               done
linux-hihn:/home/adam # tail -n30 /var/log/messages
Dec 15 13:09:37 linux-hihn dhclient: XMT: Solicit on eth0, interval 114760ms.
Dec 15 13:11:32 linux-hihn dhclient: XMT: Solicit on eth0, interval 110340ms.
Dec 15 13:13:23 linux-hihn dhclient: XMT: Solicit on eth0, interval 119730ms.
Dec 15 13:14:23 linux-hihn smartd[4133]: Device: /dev/sda [SAT], 10 Currently unreadable (pending) sectors
Dec 15 13:14:23 linux-hihn smartd[4133]: Device: /dev/sda [SAT], 10 Offline uncorrectable sectors
Dec 15 13:15:22 linux-hihn dhclient: XMT: Solicit on eth0, interval 122830ms.
Dec 15 13:17:25 linux-hihn dhclient: XMT: Solicit on eth0, interval 130020ms.
Dec 15 13:19:36 linux-hihn dhclient: XMT: Solicit on eth0, interval 131190ms.
Dec 15 13:21:47 linux-hihn dhclient: XMT: Solicit on eth0, interval 128930ms.
Dec 15 13:23:56 linux-hihn dhclient: XMT: Solicit on eth0, interval 119850ms.
Dec 15 13:25:56 linux-hihn dhclient: XMT: Solicit on eth0, interval 125610ms.
Dec 15 13:28:01 linux-hihn dhclient: XMT: Solicit on eth0, interval 108720ms.
Dec 15 13:29:50 linux-hihn dhclient: XMT: Solicit on eth0, interval 116250ms.
Dec 15 13:31:46 linux-hihn dhclient: XMT: Solicit on eth0, interval 111920ms.
Dec 15 13:33:38 linux-hihn dhclient: XMT: Solicit on eth0, interval 128300ms.
Dec 15 13:35:47 linux-hihn dhclient: XMT: Solicit on eth0, interval 129220ms.
Dec 15 13:37:56 linux-hihn dhclient: XMT: Solicit on eth0, interval 110740ms.
Dec 15 13:39:47 linux-hihn dhclient: XMT: Solicit on eth0, interval 108170ms.
Dec 15 13:41:35 linux-hihn dhclient: XMT: Solicit on eth0, interval 110660ms.
Dec 15 13:43:26 linux-hihn dhclient: XMT: Solicit on eth0, interval 123250ms.
Dec 15 13:44:23 linux-hihn smartd[4133]: Device: /dev/sda [SAT], 10 Currently unreadable (pending) sectors
Dec 15 13:44:23 linux-hihn smartd[4133]: Device: /dev/sda [SAT], 10 Offline uncorrectable sectors
Dec 15 13:44:23 linux-hihn smartd[4133]: Device: /dev/sda [SAT], SMART Usage Attribute: 194 Temperature_Celsius changed from 19 to 21
Dec 15 13:45:29 linux-hihn dhclient: XMT: Solicit on eth0, interval 123330ms.
Dec 15 13:47:33 linux-hihn dhclient: XMT: Solicit on eth0, interval 131920ms.
Dec 15 13:49:45 linux-hihn dhclient: XMT: Solicit on eth0, interval 115410ms.
Dec 15 13:51:12 linux-hihn su: (to root) adam on /dev/pts/2
Dec 15 13:51:19 linux-hihn smbd[12155]: [2012/12/15 13:51:19.455754,  0] param/loadparm.c:7209(service_ok)
Dec 15 13:51:19 linux-hihn smbd[12155]:   WARNING: No path in service netlogon - making it unavailable!
Dec 15 13:51:40 linux-hihn dhclient: XMT: Solicit on eth0, interval 112250ms.

and tail /var/log/samba/log.smbd

linux-hihn:/home/adam # tail /var/log/samba/log.smbd
  Copyright Andrew Tridgell and the Samba Team 1992-2011
[2012/12/15 11:37:25.990192,  0] param/loadparm.c:7209(service_ok)
  WARNING: No path in service netlogon - making it unavailable!
/usr/sbin/smbd: symbol lookup error: /usr/sbin/smbd: undefined symbol: wbcSidsToUnixIds
[2012/12/15 13:51:19,  0] smbd/server.c:1050(main)
  smbd version 3.6.3-115.1-2797-SUSE-SL11.4-i386 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2011
[2012/12/15 13:51:19.455754,  0] param/loadparm.c:7209(service_ok)
  WARNING: No path in service netlogon - making it unavailable!
/usr/sbin/smbd: symbol lookup error: /usr/sbin/smbd: undefined symbol: wbcSidsToUnixIds


On 12/15/2012 2:06 PM, treeup wrote:
>
> I believe that I have samba set to start at boot. I checked in Yast →
> System → System Service (Runlevel) and smb and nmb are enabled. I
> don’t know if that starts it on boot or not.
>
> Anyway, here are the results from the other commands.
>
> tail /var/log/
>
> Code:
> --------------------
> adam@linux-hihn:~> su
> Password:
> linux-hihn:/home/adam # rcsmb start
> Starting Samba SMB daemon done
> linux-hihn:/home/adam # tail -n30 /var/log/messages
<snip>
> Dec 15 13:51:12 linux-hihn su: (to root) adam on /dev/pts/2
> Dec 15 13:51:19 linux-hihn smbd[12155]: [2012/12/15 13:51:19.455754, 0] param/loadparm.c:7209(service_ok)
> Dec 15 13:51:19 linux-hihn smbd[12155]: WARNING: No path in service netlogon - making it unavailable!
> Dec 15 13:51:40 linux-hihn dhclient: XMT: Solicit on eth0, interval 112250ms.
>
> --------------------
>
>
> and tail /var/log/samba/log.smbd
>
>
> Code:
> --------------------
> linux-hihn:/home/adam # tail /var/log/samba/log.smbd
> Copyright Andrew Tridgell and the Samba Team 1992-2011
> [2012/12/15 11:37:25.990192, 0] param/loadparm.c:7209(service_ok)
> WARNING: No path in service netlogon - making it unavailable!
> /usr/sbin/smbd: symbol lookup error: /usr/sbin/smbd: undefined symbol: wbcSidsToUnixIds
> [2012/12/15 13:51:19, 0] smbd/server.c:1050(main)
> smbd version 3.6.3-115.1-2797-SUSE-SL11.4-i386 started.
> Copyright Andrew Tridgell and the Samba Team 1992-2011
> [2012/12/15 13:51:19.455754, 0] param/loadparm.c:7209(service_ok)
> WARNING: No path in service netlogon - making it unavailable!
> /usr/sbin/smbd: symbol lookup error: /usr/sbin/smbd: undefined symbol: wbcSidsToUnixIds
>
>
> --------------------
>
>
treeup;

Try updating Samba to the most current available release (3.6.10). It is still
in the Opensuse repositories. Are you using local authorization for Samba (i.e.
Not a Network authorization)? Make sure you get the latest libraries as well.
YaST should take care of that for you. If no joy please post the contents of
/etc/samba/smb.conf.


cat /etc/samba/smb.conf

There was a Bugzilla report on wbcSidsToUnixIDs, but the Samba Bugzilla site
down for the weekend. I think the newest version should take care of this.
Unless you have a PDC, I would not worry about the “netlogon” share. But it
would be wise to remove that share from your smb.conf.


P.V.
“We’re all in this together, I’m pulling for you” Red Green

Which repository would Samba 3.6.10 be in?

My current repositories are openSUSE-11.4 Debug, Update Debug, Non-Oss, Oss, Source and Update. I just added the contrib repository, but I don’t see the latest Samba in Yast. (Sorry for the poorly readable list, but I wasn’t able to copy and past my repository list from yast, so I had to type.)

This desktop computer seems to have some trouble running this OS, so I’m considering installing a lightweight linux distro. At this point, OpenSUSE 11.4 is out of date anyway. But if I find the right repository, I might give Samba 3.6.10 at try first.:slight_smile:

On 12/17/2012 7:56 AM, treeup wrote:
>
> Which repository would Samba 3.6.10 be in?
>
> My current repositories are openSUSE-11.4 Debug, Update Debug, Non-Oss,
> Oss, Source and Update. I just added the contrib repository, but I
> don’t see the latest Samba in Yast. (Sorry for the poorly readable
> list, but I wasn’t able to copy and past my repository list from yast,
> so I had to type.)
>
> This desktop computer seems to have some trouble running this OS, so
> I’m considering installing a lightweight linux distro. At this point,
> OpenSUSE 11.4 is out of date anyway. But if I find the right
> repository, I might give Samba 3.6.10 at try first.:slight_smile:
>
>
treeup;

They are here:

http://download.opensuse.org/repositories/network:/samba:/STABLE/openSUSE_11.4/

Be sure to set YaST to view versions.


P.V.
“We’re all in this together, I’m pulling for you” Red Green

Got it! Samba server is started! Thank you for the help.

I seem to have a new problem now. I can no longer access my samba share on my other computer (ADAM-DELL16). It seems like samba works on the computer that I boot first, and the computer that I boot up second doesn’t work. The hostname appears in the samba shares in dolphin, but the share folder isn’t there, and it doesn’t prompt me for a login. Here is the result of smbclient -NL followed by the IP address of the samba share on the other computer.

linux-hihn:/home/adam # smbclient -NL 192.168.15.100
Anonymous login successful
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.11]

        Sharename       Type      Comment
        ---------       ----      -------
        print$          Disk      
        ADAMS_FILES     Disk      
        IPC$            IPC       IPC Service (Samba 3.5.11)
        PSC-1600-series Printer   HP PSC 1600 series
Anonymous login successful
Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.5.11]

        Server               Comment
        ---------            -------
        ADAM-DELL16          Samba 3.5.11
        LINUX-HIHN           Samba 3.6.10-146.1-2889-SUSE-SL11.4-i386

        Workgroup            Master
        ---------            -------
        WORKGROUP            LINUX-HIHN


I was able to access the share on ADAM-DELL16 before I got samba server working on LINUX_HIHN.

On 12/17/2012 9:46 PM, treeup wrote:
>
> Got it! Samba server is started! Thank you for the help.
>
> I seem to have a new problem now. I can no longer access my samba
> share on my other computer (ADAM-DELL16). It seems like samba works on
> the computer that I boot first, and the computer that I boot up second
> doesn’t work. The hostname appears in the samba shares in dolphin, but
> the share folder isn’t there, and it doesn’t prompt me for a login.
> Here is the result of smbclient -NL followed by the IP address of the
> samba share on the other computer.
>
<snip>
>
>
> I was able to access the share on ADAM-DELL16 before I got samba server
> working on LINUX_HIHN.
>
>
treeup;

This may be a master browser problem. Can you please post the [global] section
of /etc/samba/smb.conf from both machines (LINUX_HIHN & ADM-DELL16).


su -
cat /etc/samba/smb.conf

There are some other possibilities as well, thus I need to see both smb.conf(s).


P.V.
“We’re all in this together, I’m pulling for you” Red Green

Actually, I discovered that I can access the share on ADAM-DELL16 if I type the IP address into dolphin. It then brings up the login dialogue and I can get in. The problem is that I can’t access it by browsing to it. It searches until it times out.

Here is the global section of smb.conf on LINUX-HIHN

[global]
        workgroup = WORKGROUP
        passdb backend = tdbsam
        printing = cups
        printcap name = cups
        printcap cache time = 750
        cups options = raw
        map to guest = Bad User
        include = /etc/samba/dhcp.conf
        logon path = \\%L\profiles\.msprofile
        logon home = \\%L\%U\.9xprofile
        logon drive = P:
        usershare allow guests = Yes
        add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
        domain logons = No
        domain master = No
        security = user
        usershare max shares = 100
        wins support = No
        netbios name = linux-hihn
        wins server = 


and here is the global section from ADAM-DELL16

[global]
    ; General server settings
    netbios name = adam-Dell16
    workgroup = WORKGROUP
    socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192

    passdb backend = tdbsam
    security = user
    null passwords = true
    username map = /etc/samba/smbusers
    name resolve order = wins lmhosts hosts bcast

# WINS SETTING
# NEVER set "wins support = yes" on more than one machine in your network
# "wins support = yes" and the "wins server xxx.xxx.xxx.xxx" option are mutually exclusive; you cannot simultaneously offer Samba as the WINS server and point to another system as the server

    wins support = no
# or (not both)
#   wins server xxx.xxx.xxx.xxx

    printing = CUPS
    printcap name = CUPS

    syslog = 1
    syslog only = yes

; NOTE: If you need access to the user home directories uncomment the
; lines below and adjust the settings to your hearts content.


and here is the share, ADAMS_FILES, on ADAM-DELL16

[ADAMS_FILES]
    path = /home/adam
    browseable = yes
    read only = no
    guest ok = no
    create mask = 0644
    directory mask = 0755
    force user = adam
    force group = adamadam@adam-Dell16:~$ 


On 12/18/2012 10:06 AM, treeup wrote:
>
> Actually, I discovered that I can access the share on ADAM-DELL16 if I
> type the IP address into dolphin. It then brings up the login dialogue
> and I can get in. The problem is that I can’t access it by browsing to
> it. It searches until it times out.
>
> Here is the global section of smb.conf on LINUX-HIHN
>
>
> Code:
> --------------------
> [global]
<snip>
>
> --------------------
>
> and here is the global section from ADAM-DELL16
>
> Code:
> --------------------
> [global]
<snip>
> socket options = TCP_NODELAY IPTOS_LOWDELAY SO_KEEPALIVE SO_RCVBUF=8192 SO_SNDBUF=8192
<snip>
> name resolve order = wins lmhosts hosts bcast
>
<snip>
>
> --------------------
>
>
> and here is the share, ADAMS_FILES, on ADAM-DELL16
>
> Code:
> --------------------
> [ADAMS_FILES]
> path = /home/adam
> browseable = yes
> read only = no
> guest ok = no
> create mask = 0644
> directory mask = 0755
> force user = adam
> force group = adamadam@adam-Dell16:~$
>
>
> --------------------
>
treeup;

As you do not have a wins server you should change the parameter “name resolve
order”. Change it in the smb.conf on ADAN-DELL16 and add it to the smb.conf on
LINUX-HIHN, so they both read:


name resolve order = bcast host lmhosts wins

This will force both computers to try broad casts (bcast) first for name
resolution. As you have it set up, name resolution would have died before ever
trying bcast, which is the only method that will work with your current setup.
Make sure nmb (nmbd) is set to start on boot for both machines and is allowed
through the firewall. On Opensuse it is the “netbios server” You can configure
the firewall through YaST. Broadcasts are the native Windows method of name
resolution and work well with Samba. (FYI you could setup the lmhosts or host
files if you really wanted; but that’s hard to maintain.)

As an aside, the “socket options” parameter has not been needed for a long time.
A modern Kernel will do a much better job tuning the interface than you will
ever do manually. Also, I assume that adamadam is a local group on adam-Dell16.
You should only need “force group = adamadam”.


P.V.
“We’re all in this together, I’m pulling for you” Red Green

Works! I tried putting bcast first in the name resolve order a few days ago actually, but when it didn’t work, I reverted to my backed up smb.conf.

Thanks for the note regarding saying that I don’t need

    force user = adam

This computer’s main purpose is to back up my files, and I would like to create a samba user on ADAM-DELL16 that does not have write access. I would hate to make an error someday and write over all of my updated files with my old backups.

On 12/18/2012 1:06 PM, treeup wrote:
>
> Works! I tried putting bcast first in the name resolve order a few days
> ago actually, but when it didn’t work, I reverted to my backed up
> smb.conf.

> Thanks for the note regarding saying that I don’t need
>
> Code:
> --------------------
> force user = adam
> --------------------
>
>
> This computer’s main purpose is to back up my files, and I would like
> to create a samba user on ADAM-DELL16 that does not have write access.
> I would hate to make an error someday and write over all of my updated
> files with my old backups.

treeup;

It was the syntax of your “force group” parameter, not “force user” that I
questioned. The force user or force group parameters only determine ownership
of files, not who can or can not write to the share. You might want to look at
the “write list” parameter to control writes and/or use Linux permissions. Take
a look at “man smb.conf” for a full writeup of the possible parameters in
smb.conf and what each one does.

The last part of this howto has a number of examples of various permissions on
Samba shares you may find helpful:

http://opensuse.swerdna.org/susesambaserver.html

P.V.
“We’re all in this together, I’m pulling for you” Red Green