Threaded Mode | Linear Mode

PSPkiller · 07/09/2010 07:39 AM

It's worth a shot I suppose. I'm far more likely to get any attention here than somewhere like Ubuntuforums. That place is overrun be newbies meaning any threads you make are lost in the sea of noobishness.

Anyways. I've recently rebuilt and revamped my file/web/streaming music server at home. Basically it was a case of back up all files, format all hard drives, install Ubuntu on a new drive as the SMART status on the old one suggested it might die soon, blow up the new drive with a flying Leatherman, find another drive, install Ubuntu on that, get all the other drives mounted and ready, install a fudgeton of software and fiddle with configuration files and hope for the best. So far it's worked out pretty well. I have access to everything I need over FTP and HTTP. I've set up SSH and VNC for fiddling with settings and whathaveyou and I also have Jinzora installed on the HTTP webserver for the streaming of MP3's over the intertubes to wherever I may be. It's all great except for the single most important function.

I need access to my files from within my network. The natural choice for this is Samba to set up Windows shares. So, I installed it, configured it and voila. All was well until the the server was rebooted. Samba doesn't want to start up. So, I unintstalled it, cleared the configuration files and started again. Same problem again. I'm on the 3rd install now and it's annoying me now.

The log of Samba attempting to start goes as follows:

Code:

[2010/09/07 15:20:36,  0] smbd/server.c:1069(main)
  smbd version 3.4.7 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2009
[2010/09/07 15:20:37,  0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2010/09/07 15:20:37,  0] printing/print_cups.c:103(cups_connect)
  Unable to connect to CUPS server localhost:631 - Connection refused
[2010/09/07 15:20:37,  0] smbd/server.c:1115(main)
  standard input is not a socket, assuming -D option

Now, I know that CUPS is to do with printing and that Samba can be used to work as a print server as well as a file server or domain controller but the printing and domain functions are all disabled.

If you need here's my smb.conf file:

Spoiler for smb.conf:

#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
#  - When such options are commented with ";", the proposed setting
#    differs from the default Samba behaviour
#  - When commented with "#", the proposed setting is the default
#    behaviour of Samba but the option is considered important
#    enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
# A well-established practice is to name the original file
# "smb.conf.master" and create the "real" config file with
# testparm -s smb.conf.master >smb.conf
# This minimizes the size of the really used smb.conf file
# which, according to the Samba Team, impacts performance
# However, use this with caution if your smb.conf file contains nested
# "include" statements. See Debian bug #483187 for a case
# where using a master file is not a good idea.
#

#======================= Global Settings =======================

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
  server string = %h: Rob's Ultime Server of Awesomeness (Samba %v on Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
;   wins support = yes

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

# What naming service and in what order should wee use to resolve host names
# to IP addresses
;   name resolve order = lmhosts host wins bcast

#Follow symbolic links
    follow symlinks = yes
    wide links = yes
    unix extensions = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
  interfaces = 127.0.0.0/8 eth1

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
   bind interfaces only = yes

#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each user
# that connects
   log file = /var/log/samba/log.%U

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# Wee want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
;   panic action = /usr/share/samba/panic-action %d

####### Authentication #######

# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
   security = user

# You may wish to use password encryption.  See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
   encrypt passwords = true

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
;   domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g

########## Printing ##########

# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
   load printers = no

# lpr(ng) printing. You may wish to override the location of the
# printcap file
;   printing = bsd
;   printcap name = /etc/printcap

# CUPS printing.  See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
;   printing = cups
;   printcap name = cups

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
#         SO_RCVBUF=8192 SO_SNDBUF=8192
   socket options = TCP_NODELAY

# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
;   message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &

# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
#   domain master = auto

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
;   winbind enum groups = yes
;   winbind enum users = yes

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares.  This will share each
# user's home directory as \\server\username
[homes]
   comment = Home Directories. These are private.
   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
   read only = no

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.  Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# This might need tweaking when using external authentication schemes
   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes
;   share modes = no

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

;[printers]
;   comment = All Printers
;  browseable = no
;   path = /var/spool/samba
;   printable = yes
;   guest ok = no
;   read only = yes
;   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
;[print$]
;   comment = Printer Drivers
;   path = /var/lib/samba/printers
;   browseable = yes
;   read only = yes
;   guest ok = no

# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin

# A sample share for sharing your CD-ROM with others.
[cdrom]
   comment = Server's CD-ROM
   read only = yes
   locking = no
   path = /media/cdrom
   guest ok = no

# The next two parameters show how to auto-mount a CD-ROM when the
#

cdrom share is accesed. For this to work /etc/fstab must contain
#

an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
#

is mounted on /cdrom
#
   preexec = /bin/mount /cdrom
   postexec = /bin/umount /cdrom

[Shared]
        comment = Shared files. Don't put anything private here.
        create mode = 755
        path = /media/shared

browsable = yes

read only = no

guest ok = no

ZiNgA BuRgA · 07/09/2010 05:31 PM

Have never used Samba, but does the same thing happen if you try to start the service manually?

PSPkiller · 07/09/2010 06:11 PM

Nope. It starts successfully if I kick it up the donkey with some "sudo /etc/init.d/smbd start".

I've done a bit of reading and I think I may have found what's going wrong but not how to solve it. Apparently there's a bug in Samba and a few other servers of that ilk that stop them from starting up successfuly on bootup. You can start them manually once the system is fully up and running but not at bootup. Now, my immediate thoughts after that were to write a shell script that runs the command to manually start Samba then set that script to run automatically once my user account auto logs on. (Another problem. I can't get VNC to work at the logon screen so its just setup to auto logon as me. Not exactly safe but it's all I can do.) The problem with this approach however is that sudo is needed to start Samba. You can't put sudo in a shell script that's meant to run without any user intervention because it has to ask for a passoword. I tried it but it didn't work.

Oh well.

ZiNgA BuRgA · 07/09/2010 06:16 PM

Can't you just login to root?
It's not like security is much of an issue...

Otherwise, have an external shell script, and chmod it to SUID (chmod 4755 myscript.sh) and chown to root.

PSPkiller · 07/09/2010 06:32 PM

It's not the script itself that needs permission. It's the command that it runs. As for auto logging in as root it would be a last resort. At the moment security isn't an issue but it might be soon. I'm moving to Uni in 2 weeks and i don't know what kind of people I'll be living with. If I can find a way of locking the screen as soon as it logs on then I'll consider it.

ZiNgA BuRgA · 07/09/2010 06:54 PM

(07/09/2010 06:32 PM)PSPkiller Wrote: It's not the script itself that needs permission. It's the command that it runs.

I meant to create a separate script which runs the command. The script can then be SUID to root, which, in effect, is an automatic sudo.

PSPkiller · 09/09/2010 04:27 PM

Well I finally got it sorted. In the end I added myself to the sudoers file so that the script would run without needing a password. Thanks for your help Zinga.

Threaded Mode \| Linear Mode Anybody here know anything about setting up a Samba server on Linux?
Author	Message