• Diese Seite verwendet Cookies. Indem du diese Website weiterhin nutzt, erklärst du dich mit der Verwendung von Cookies einverstanden. Erfahre mehr

Probleme mit zwei Samba-Dateiservern im gleichen Netz

kraekers

Well-Known Member
Themenstarter #1
Moin Kollegen,

ich möchte gerne zwei Samba-Server im gleichen Netz betreiben. Die Systeme laufen auch schon sehr gut. Problem ist nur, dass einer der Rechner (Server 2) mir ewig Fehlermeldungen um die Ohren wirft. Ich habe auch schon mit den Parametern "Local Master" und "Prefered Master" auf beiden Systemen herumgespielt, leider ohne Erfolg. Clients sind Debian-Rechner. Ich zeige Euch einmal meine Configs:

Server 1

192.168.1.10
255.255.255.0
192.168.1.1

Code:
#======================= Global Settings =====================================

[global]
workgroup = HOMELOCAL
netbios name = xxx-1
realm = xxx-1.HOME.LOCAL
server string = FreeBSD Samba Server 1 HOME
security = user
usershare allow guests = No
os level = 32
local master = Yes
preferred master = Yes
domain logons = No
domain master = No
wins support = No
read raw = No
socket options = TCP_NODELAY
load printers = No
hosts allow = 192.168.1. 127.
dos charset = CP1252
unix charset = UTF-8

...
Server 2

192.168.1.11
255.255.255.0
192.168.1.1

Code:
#======================= Global Settings =====================================

[global]
workgroup = HOMELOCAL
netbios name = xxx-2
realm = xxx-2.HOME.LOCAL
server string = FreeBSD Samba Server 2 HOME
security = user
usershare allow guests = No
os level = 31
local master = No
preferred master = No
domain logons = No
domain master = No
wins support = No
read raw = No
socket options = TCP_NODELAY
load printers = No
hosts allow = 192.168.1. 127.
dos charset = CP1252
unix charset = UTF-8

...
Log nmbd Server 2

Code:
[2019/03/04 18:45:52.359744,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/03/04 18:47:19.317642,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/03/04 18:48:37.168013,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/03/04 18:49:09.872305,  0] ../source3/nmbd/nmbd_become_lmb.c:397(become_local_master_stage2)
  *****
 
  Samba name server BSD-SRV-2 is now a local master browser for workgroup HOMELOCAL on subnet 192.168.1.11
 
  *****
[2019/03/04 18:54:08.008372,  0] ../source3/nmbd/nmbd.c:58(terminate)
  Got SIGTERM: going down...
[2019/03/05 11:36:02.134613,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections
[2019/03/05 11:46:20.938773,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 11:51:22.212519,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 11:56:23.885837,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:01:23.548494,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:06:32.383454,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:11:35.695660,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:21:45.375640,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:26:48.103389,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:31:51.041526,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:41:54.019382,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:46:57.051208,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 12:51:53.959405,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 13:02:07.905164,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 13:07:12.567194,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 13:12:16.082418,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.
[2019/03/05 13:22:32.802170,  0] ../source3/nmbd/nmbd_namequery.c:109(query_name_response)
  query_name_response: Multiple (2) responses received for a query on subnet 192.168.1.11 for name HOMELOCAL<1d>.
  This response was from IP 192.168.1.10, reporting an IP address of 192.168.1.10.

...
Log smbd Server 2

Code:
[2019/03/04 18:45:53.354773,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/04 18:47:19.318761,  0] ../lib/util/fault.c:79(fault_report)
  ===============================================================
[2019/03/04 18:47:19.318880,  0] ../lib/util/fault.c:80(fault_report)
  INTERNAL ERROR: Signal 11 in pid 970 (4.8.7)
  Please read the Trouble-Shooting section of the Samba HOWTO
[2019/03/04 18:47:19.318987,  0] ../lib/util/fault.c:82(fault_report)
  ===============================================================
[2019/03/04 18:47:19.319045,  0] ../source3/lib/util.c:815(smb_panic_s3)
  PANIC (pid 970): internal error
[2019/03/04 18:47:19.360364,  0] ../lib/util/fault.c:261(log_stack_trace)
  BACKTRACE: 6 stack frames:
   #0 0x801117c88 <log_stack_trace+0x28> at /usr/local/lib/samba4/libsamba-util.so.0
   #1 0x8017fe272 <smb_panic_s3+0x52> at /usr/local/lib/samba4/libsmbconf.so.0
   #2 0x801117a87 <smb_panic+0x17> at /usr/local/lib/samba4/libsamba-util.so.0
   #3 0x801117e3a <log_stack_trace+0x1da> at /usr/local/lib/samba4/libsamba-util.so.0
   #4 0x801117a69 <fault_setup+0x59> at /usr/local/lib/samba4/libsamba-util.so.0
   #5 0x80108d4b6 <_pthread_sigmask+0x536> at /lib/libthr.so.3
[2019/03/04 18:47:19.360653,  0] ../source3/lib/dumpcore.c:310(dump_core)
  unable to change to %N.core
  refusing to dump core
[2019/03/04 18:48:38.238125,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/05 11:36:03.279751,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/06 06:43:38.412904,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 06:11:34.679712,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 06:20:29.229734,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 06:24:59.238083,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 17:04:23.579692,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 17:08:32.146571,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 18:55:26.354731,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 19:23:38.613039,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 19:27:56.138099,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 19:37:40.246403,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/07 20:01:43.471378,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/08 05:42:23.579682,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve connections
[2019/03/08 05:44:43.229727,  0] ../lib/util/become_daemon.c:138(daemon_ready)
  daemon_ready: STATUS=daemon 'smbd' finished starting up and ready to serve Connections
Als ich nur einen Server hatte gab es diese Probleme nicht, es ist mir bewusst, dass der zweite Server dem ersten "hereingrätscht", aber mir
ist nicht klar wie ich dies abstelle.

Über einen Tipp würde ich mich freuen und vielen Dank für die Mühe im Vorwege.

Beste Grüße
kraekers
 

joergpc

Well-Known Member
#2
Hallo,
hallo wenn du server 1 auschaltest sind die meldungen noch vorhanden.

Ich würde das dann sowieso auf AD umstellen, mach die ganze Sache angenehmer in der Verwaltung.

Viele Grüße
Jörg
 

joergpc

Well-Known Member
#3
stelle mal server 1 auf "os level = 65"
Diese Angabe ist ein ganzzahliger Wert, der bestimmt, welche Chance der Samba-Server hat, um die Wahl zum Master-Browser einer Workgroup innerhalb der Broadcast-Zone zu gewinnen. Je höher der Wert ist, um so größer ist die Chance, die Wahl zu gewinnen. Ein Wert von 0 wird von jedem Windows-Rechner überboten. Windows 3.11/95/98 benutzt den Wert 1, ein NT-Server benutzt den Wert 32. Der Wert 34 würde also jeden NT-Rechner schlagen, aber selbst dann können noch verschiedene Samba-Server untereinanderausfechten, wer Master-Browser wird. Der maximale Wert ist 255.
 

kraekers

Well-Known Member
Themenstarter #4
Hallo joergpc,

vielen Dank für Deine Antwort. Da meine beiden Server in unterschiedlichen Zyklen hochgefahren werden und nicht permanent laufen,
habe ich mich damit beholfen zwei Workgroups anzulegen. So stört es mich und die Server nicht.

Beste Grüße
kraekers