• This forum has a zero tolerance policy regarding spam. If you register here to publish advertising, your user account will be deleted without further questions.

Samba startet nicht richtig

Pfiffikus

Member
Hallo Leute,

hier werkelt ein Raspberry Pi mit einem RAID 1 und dient als NAS. Ursprünglich waren die Dienste auch von unserem Windows-Rechner erreichbar, weil samba lief. Irgendwann lief es nicht mehr. Das war nicht weiter kritisch, denn das wird ja nur von der Windows-Kiste gebraucht.

Heute versuche ich, diesen Dienst wieder in Betrieb zu nehmen, doch es will mir nicht so richtig gelingen.

Code:
root@Edel-Raspi:/var/log# /etc/init.d/samba start
[....] Starting nmbd (via systemctl): nmbd.serviceJob for nmbd.service failed. See 'systemctl status nmbd.service' and 'journalctl -xn' for details.
 failed!

Wir schauen mal nach:
Code:
root@Edel-Raspi:/var/log# journalctl -xn
...
Apr 09 14:07:24 Edel-Raspi systemd[1]: Starting LSB: start Samba NetBIOS nameserver (nmbd)...
-- Subject: Unit nmbd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has begun starting up.
Apr 09 14:07:25 Edel-Raspi nmbd[13425]: Starting NetBIOS name server: nmbd failed!
Apr 09 14:07:25 Edel-Raspi systemd[1]: nmbd.service: control process exited, code=exited status=1
Apr 09 14:07:25 Edel-Raspi systemd[1]: Failed to start LSB: start Samba NetBIOS nameserver (nmbd).
-- Subject: Unit nmbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has failed.
-- 
-- The result is failed.
Apr 09 14:07:25 Edel-Raspi systemd[1]: Unit nmbd.service entered failed state.

Das fand ich nicht so aufschlussreich. Eventuell gibt es hier Anhaltspunkte für sinnvolleKorrekturen?
Code:
root@Edel-Raspi:/var/log# tail -n 30 samba/log.nmbd
[2017/04/09 12:48:07,  0] ../source3/nmbd/nmbd.c:908(main)
  nmbd version 4.2.14-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014
[2017/04/09 13:42:01,  0] ../source3/nmbd/nmbd.c:908(main)
  nmbd version 4.2.14-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014
[2017/04/09 14:07:25,  0] ../source3/nmbd/nmbd.c:908(main)
  nmbd version 4.2.14-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014
Code:
root@Edel-Raspi:/var/log# tail -n 30 samba/log.smbd 
[2017/04/08 07:17:13,  0] ../source3/smbd/server.c:1241(main)
  smbd version 4.2.14-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2014

Nein! Die Dienste sind nicht gestartet! Versteht sich von selbst, dass sich bei smb://192.168.1.56/ niemand meldet.

Hat jemand von Euch Ideen, was schief läuft?


Pfiffikus,
der von Euch gern wissen möchte, in welchen Logdateien man noch nach Hinweisen forschen könnte
 
Existiert die smb.conf in /etc/samba?

Wurden in letzter Zeit Betriebssystemupdates eingespielt?
Ggf. Samba mal auf eine andere Version downgraden?
 
Existiert die smb.conf in /etc/samba?
Ja, die gibt es. Und zwar in einer Version, mit der es mal funktioniert hat.

Existiert die smb.conf in /etc/samba?
Wurden in letzter Zeit Betriebssystemupdates eingespielt?[/QUOTE]
Klar. Apt-get update und upgrade wurden in regelmäßigen Abständen durchgeführt. Sehr wahrscheinlich waren da auch Updates für samba dabei. Aber soll dadurch die Konfiguration zerschossen worden sein?

Existiert die smb.conf in /etc/samba?
Ggf. Samba mal auf eine andere Version downgraden?[/QUOTE]
Und auch wenn es neue Versionen gibt, sollten die auch funktionieren.


Pfiffikus,
der eigentlich viel lieber nach der Stelle suchen will, an der ich diese und auch künftige Versionen zum Laufen bekommen kann
 
Ich bin es noch einmal. Auch das hilft nicht.

Code:
apt-get purge samba
Code:
apt-get autoremove

Code:
apt-get install samba


Es bleibt bei solchen Meldungen:
Code:
root@Edel-Raspi:/home/pi# journalctl -xn
Apr 12 13:40:27 Edel-Raspi systemd[1]: Starting LSB: start Samba NetBIOS nameser
-- Subject: Unit nmbd.service has begun with start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has begun starting up.
Apr 12 13:40:28 Edel-Raspi nmbd[16185]: Starting NetBIOS name server: nmbd faile
Apr 12 13:40:28 Edel-Raspi systemd[1]: nmbd.service: control process exited, cod
Apr 12 13:40:28 Edel-Raspi systemd[1]: Failed to start LSB: start Samba NetBIOS 
-- Subject: Unit nmbd.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit nmbd.service has failed.
-- 
-- The result is failed.
Apr 12 13:40:28 Edel-Raspi systemd[1]: Unit nmbd.service entered failed state.
Frustrierend! Dass es nicht läuft, weiß ich selber.


Pfiffikus,
der im Moment nicht mehr weiß, wo er noch detailliertere Fehlermeldungen erfahren könnte
 
Ich würde ja mal schauen, was testparm so ausspuckt - da dürften einige Hinweise drin sein.
 
der wahrscheinlichste Fall dürfte ein Fehler in der smb.conf sein - poste die doch mal.
Bittesehr:
Code:
#
# 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. 

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

[global]

## Browsing/Identification ###

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

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

# 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

#### 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 eth0

# 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 machine
# that connects
   log file = /var/log/samba/log.%m

# 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

# We 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 #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# 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 ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or '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

############ 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

# 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

# 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 =======================

[homes]
   comment = Home Directories
   browseable = yes

# 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 = 0770

# 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 = 0770

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

[wir]
  path = /media/nas/wir
  comment = Freigabe fuer uns
  available = yes
  browseable = yes
  guest ok = no
  writeable = yes



# 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

# 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

Ich würde ja mal schauen, was testparm so ausspuckt - da dürften einige Hinweise drin sein.
Da steht das drin:
Code:
root@Edel-Raspi:/home/pi# /etc/init.d/samba start
[....] Starting nmbd (via systemctl): nmbd.serviceJob for nmbd.service failed. See 'systemctl status nmbd.service' and 'journalctl -xn' for details.
 failed!
root@Edel-Raspi:/home/pi# testparm 
Load smb config files from /etc/samba/smb.conf
Processing section "[homes]"
Processing section "[wir]"
Loaded services file OK.
Server role: ROLE_STANDALONE

Press enter to see a dump of your service definitions

# Global parameters
[global]
	workgroup = ZUHAUSE
	server string = NAS
	server role = standalone server
	map to guest = Bad User
	obey pam restrictions = Yes
	pam password change = Yes
	passwd program = /usr/bin/passwd %u
	passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
	unix password sync = Yes
	syslog = 0
	log file = /var/log/samba/log.%m
	max log size = 1000
	dns proxy = No
	usershare allow guests = Yes
	panic action = /usr/share/samba/panic-action %d
	idmap config * : backend = tdb


[homes]
	comment = Home Directories
	valid users = %S
	read only = No
	create mask = 0770
	directory mask = 0770


[wir]
	comment = Freigabe fuer uns
	path = /media/nas/wir
	read only = No


Pfiffikus,
der in diesen Ausgaben keine Hinweise auf Fehler findet
 
Die üblichen Sachen geprüft? Steht war im normalen Syslog drin? Ich lassen rsyslog bei Fehleranalysen auch gerne mal alles komplett ungefilter in eine Datei schreiben (kann aber auch schnell unübersichtlich werden). Läuft vielleicht noch ein alter Daemon oder irgendwas anderes, was die Ports noch blockiert? Mal rebootet?
 
Die üblichen Sachen geprüft? Steht war im normalen Syslog drin?
Syslog schweigt dazu. Finde ich jetzt aber nicht so bedenklich, denn ich habe ja in der GLOBAL-Sektion der smb.conf stehen:
syslog = 0

Statt dessen wird in den Dateien log.smbd und log.nmbd protokolliert. Was drin zu finden ist: Siehe oben im Eingangsbeitrag! Sollte in der Syslog mehr aufgezeichnet werden?

Läuft vielleicht noch ein alter Daemon oder irgendwas anderes, was die Ports noch blockiert? Mal rebootet?
Ja klar. Solche Versuche waren so ziemlich die ersten Maßnahmen, die ich bei den Startversuchen unternommen habe.


Gerne hätte ich Dir aufgelistet, welche Daemons installiert sind, die den Start blockieren können. Aber:
Code:
root@Edel-Raspi:/home/pi# dpkg -l
dpkg-query: Fehler: Parsen der Datei �/var/lib/dpkg/status�, nahe Zeile 0:
 EOF nach Feldname ��


Ich finde hier keinen Verdächtigen:
Code:
root@Edel-Raspi:/home/pi# ps -axf
  PID TTY      STAT   TIME COMMAND
    2 ?        S      0:00 [kthreadd]
    3 ?        S      0:11  \_ [ksoftirqd/0]
    5 ?        S<     0:00  \_ [kworker/0:0H]
    7 ?        S      0:33  \_ [rcu_sched]
    8 ?        S      0:00  \_ [rcu_bh]
    9 ?        S      0:00  \_ [migration/0]
   10 ?        S      0:00  \_ [migration/1]
   11 ?        S      0:01  \_ [ksoftirqd/1]
   13 ?        S<     0:00  \_ [kworker/1:0H]
   14 ?        S      0:00  \_ [migration/2]
   15 ?        S      0:03  \_ [ksoftirqd/2]
   17 ?        S<     0:00  \_ [kworker/2:0H]
   18 ?        S      0:00  \_ [migration/3]
   19 ?        S      0:02  \_ [ksoftirqd/3]
   21 ?        S<     0:00  \_ [kworker/3:0H]
   22 ?        S<     0:00  \_ [khelper]
   23 ?        S      0:00  \_ [kdevtmpfs]
   24 ?        S<     0:00  \_ [netns]
   25 ?        S<     0:00  \_ [perf]
   26 ?        S      0:00  \_ [khungtaskd]
   27 ?        S<     0:00  \_ [writeback]
   28 ?        S<     0:00  \_ [crypto]
   29 ?        S<     0:00  \_ [bioset]
   30 ?        S<     0:00  \_ [kblockd]
   32 ?        S<     0:00  \_ [rpciod]
   33 ?        S      0:01  \_ [kswapd0]
   34 ?        S      0:00  \_ [fsnotify_mark]
   35 ?        S<     0:00  \_ [nfsiod]
   41 ?        S<     0:00  \_ [kthrotld]
   43 ?        S<     0:00  \_ [VCHIQ-0]
   44 ?        S<     0:00  \_ [VCHIQr-0]
   45 ?        S<     0:00  \_ [VCHIQs-0]
   46 ?        S<     0:00  \_ [iscsi_eh]
   47 ?        S<     0:00  \_ [dwc_otg]
   48 ?        S<     0:00  \_ [DWC Notificatio]
   51 ?        S      0:32  \_ [mmcqd/0]
   52 ?        S      0:00  \_ [VCHIQka-0]
   53 ?        S<     0:00  \_ [SMIO]
   54 ?        S<     0:00  \_ [deferwq]
   57 ?        S      0:29  \_ [jbd2/mmcblk0p2-]
   58 ?        S<     0:00  \_ [ext4-rsv-conver]
   59 ?        S      0:00  \_ [scsi_eh_0]
   60 ?        S<     0:00  \_ [scsi_tmf_0]
   61 ?        S      0:01  \_ [usb-storage]
   62 ?        S<     0:00  \_ [ipv6_addrconf]
   63 ?        S      0:00  \_ [scsi_eh_1]
   64 ?        S<     0:00  \_ [scsi_tmf_1]
   68 ?        S      0:01  \_ [usb-storage]
   80 ?        S<     0:00  \_ [kworker/0:1H]
  133 ?        S<     0:00  \_ [md]
  209 ?        S<     0:00  \_ [kworker/1:1H]
  407 ?        S<     0:00  \_ [cfg80211]
 1060 ?        S<     0:00  \_ [kworker/2:1H]
 3875 ?        S<     0:00  \_ [kworker/3:1H]
 4015 ?        S<     0:00  \_ [bioset]
 4016 ?        S      0:00  \_ [md0_raid1]
 4565 ?        S      0:18  \_ [kworker/0:0]
 7095 ?        S      0:00  \_ [jbd2/md0-8]
 7096 ?        S<     0:00  \_ [ext4-rsv-conver]
17048 ?        S      0:00  \_ [kworker/u8:2]
17088 ?        S      0:01  \_ [kworker/u8:1]
17204 ?        S      0:00  \_ [kworker/3:1]
17301 ?        S      0:00  \_ [kworker/1:1]
17314 ?        S      0:00  \_ [kworker/1:0]
17317 ?        S      0:00  \_ [kworker/2:2]
17321 ?        S      0:00  \_ [kworker/0:1]
17322 ?        S      0:00  \_ [kworker/2:0]
17323 ?        S      0:00  \_ [kworker/3:0]
17331 ?        S      0:00  \_ [kworker/0:2]
    1 ?        Ss     0:11 /sbin/init
  115 ?        Ss     0:00 /lib/systemd/systemd-udevd
  373 ?        Ss     0:08 avahi-daemon: running [Edel-Raspi.local]
  414 ?        S      0:00  \_ avahi-daemon: chroot helper
  376 ?        Ss     0:00 /usr/sbin/cron -f
  377 ?        Ssl    0:00 /usr/sbin/rsyslogd -n
  378 ?        Ssl    0:00 /usr/sbin/ModemManager
  383 ?        Ss     0:01 /lib/systemd/systemd-logind
  384 ?        Ss     0:01 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
  406 ?        Ss     0:00 /usr/sbin/thd --daemon --triggers /etc/triggerhappy/triggers.d/ --socket /var/run/thd.socke
  409 ?        Ss     0:02 /sbin/dhcpcd -q -b
  489 ?        Ssl    0:00 /usr/lib/policykit-1/polkitd --no-debug
  493 ?        Ss     0:00 /usr/sbin/sshd -D
 3876 ?        Ss     0:00  \_ sshd: pi [priv]     
 3891 ?        S      0:19  |   \_ sshd: pi@pts/0      
 3894 pts/0    Ss     0:00  |       \_ -bash
 3909 pts/0    S      0:00  |           \_ sudo su
 3916 pts/0    S      0:00  |               \_ su
 3925 pts/0    S      0:00  |                   \_ bash
17240 pts/0    S+     1:40  |                       \_ htop
 6974 ?        Ss     0:00  \_ sshd: ich [priv]   
 6991 ?        S      0:00  |   \_ sshd: ich@notty    
 6994 ?        Ss     0:00  |       \_ /usr/lib/openssh/sftp-server
 6995 ?        Ss     0:00  \_ sshd: ich [priv]   
 7005 ?        S      0:00  |   \_ sshd: ich@notty    
 7008 ?        Ss     0:00  |       \_ /usr/lib/openssh/sftp-server
 5329 ?        Ss     0:00  \_ sshd: pi [priv]     
 5337 ?        S      0:01      \_ sshd: pi@pts/1      
 5340 pts/1    Ss     0:00          \_ -bash
 5350 pts/1    S      0:00              \_ sudo su
 5357 pts/1    S      0:00                  \_ su
 5366 pts/1    S      0:00                      \_ bash
17337 pts/1    R+     0:00                          \_ ps -axf
  547 tty1     Ss+    0:00 /sbin/agetty --noclear tty1 linux
  549 ttyAMA0  Ss+    0:00 /sbin/agetty --keep-baud 115200 38400 9600 ttyAMA0 vt102
  562 ?        Ss     0:12 /usr/sbin/ntpd -p /var/run/ntpd.pid -g -c /var/lib/ntp/ntp.conf.dhcp -u 107:112
  600 ?        S      2:07 Xtightvnc :1 -desktop X -auth /home/pi/.Xauthority -geometry 1352x900 -depth 24 -rfbwait 12
  829 ?        S      0:00 /bin/sh /home/pi/.vnc/xstartup
  876 ?        Sl     0:00  \_ /usr/bin/lxsession -s LXDE-pi -e LXDE
  961 ?        Ss     0:00      \_ /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session x-session-manager
 1073 ?        S      0:00      \_ openbox --config-file /home/pi/.config/openbox/lxde-pi-rc.xml
 1076 ?        Sl     0:00      \_ lxpolkit
 1078 ?        Sl    11:26      \_ lxpanel --profile LXDE-pi
 1081 ?        Sl     0:00      \_ pcmanfm --desktop --profile LXDE-pi
  910 ?        Ss     0:06 /usr/sbin/apache2 -k start
 5104 ?        S      0:00  \_ /usr/sbin/apache2 -k start
 5105 ?        S      0:00  \_ /usr/sbin/apache2 -k start
 5106 ?        S      0:00  \_ /usr/sbin/apache2 -k start
 5107 ?        S      0:00  \_ /usr/sbin/apache2 -k start
 5108 ?        S      0:00  \_ /usr/sbin/apache2 -k start
17233 ?        S      0:00  \_ /usr/sbin/apache2 -k start
  914 ?        Ss     0:00 /usr/sbin/exim4 -bd -q30m
  972 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session x-session-manager
  980 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 5 --print-address 7 --session
 1023 ?        Sl     0:00 /usr/lib/gvfs/gvfsd
 1037 ?        Sl     0:00 /usr/lib/gvfs/gvfsd-fuse /home/pi/.gvfs -f -o big_writes
 1088 ?        Ss     0:00 /usr/bin/ssh-agent -s
 1142 ?        Sl     0:00 /usr/lib/gvfs/gvfs-udisks2-volume-monitor
 1158 ?        Ssl    0:01 /usr/lib/udisks2/udisksd --no-debug
 1232 ?        Sl     0:00 /usr/lib/gvfs/gvfs-goa-volume-monitor
 1247 ?        Sl     0:00 /usr/lib/gvfs/gvfs-afc-volume-monitor
 1264 ?        Sl     0:00 /usr/lib/gvfs/gvfs-gphoto2-volume-monitor
 1278 ?        Sl     0:00 /usr/lib/gvfs/gvfs-mtp-volume-monitor
 1324 ?        Ssl    0:00 /usr/lib/menu-cache/menu-cached /tmp/.menu-cached-:1-pi
 1330 ?        Sl     0:00 /usr/lib/gvfs/gvfsd-trash --spawner :1.1 /org/gtk/gvfs/exec_spaw/0
 3882 ?        Ss     0:00 /lib/systemd/systemd --user
 3887 ?        S      0:00  \_ (sd-pam)  
 4036 ?        Ss     0:00 /sbin/mdadm --monitor --scan
 6982 ?        Ss     0:00 /lib/systemd/systemd --user
 6987 ?        S      0:00  \_ (sd-pam)  
 7145 ?        S      0:00 /bin/sh /usr/bin/mysqld_safe
 7491 ?        Sl     2:17  \_ /usr/sbin/mysqld --basedir=/usr --datadir=/media/nas/Datenbanken/mysql --plugin-dir=/us
 5484 ?        Ssl    0:00 /usr/lib/packagekit/packagekitd



Pfiffikus,
der froh ist, wenigstens über sftp auf die Dateien zugreifen zu können
 
Wenn der Fehler nicht bei Samba, sondern z.B. schon bei Systemd liegt, tauchen dessen Meldungen nicht in den Samba-Logs auf, sondern im Syslog. Daher ist auch das Syslog wichtig (welches der Syslog-Daemon nach diversen Regeln auf verschiedene Dateien verteilt).
Ansonsten hilft natürlich auch, mal den Log-Level von Samba hochzusetzen: https://www.samba.org/samba/docs/using_samba/ch12.html
 
So, Ende vom Lied:

Habe eine neue SD-Karte gekauft und den Raspi völlig neu aufgesetzt. Jetzt geht auch Samba wieder.

Die beiden Festplatten, die als RAID-1 genutzt worden sind, ließen sich wunderbar wieder nachnutzen. (Nur die User und Gruppen-IDs in der /etc/passwd und /etc/group mussten so verändert werden, wie sie auf der alten SD-Karte mal waren.)

An welcher Stelle sich der Fehler verbarg, kann ich leider nicht mehr rekonstruieren.


Pfiffikus,
der so eine Austausch-Aktion ohnehin mal als Havarieübung durchziehen wollte
 
Back
Top