pixel
17.07.02, 13:37
Hi@all,
beim durchstöber den Logfiles (/var/log/messages) sind mir einige Sachen im Umfeld vom Samba aufgefallen welche ich nicht so richtig interpretieren kann.
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/asyncdns.c:start_async_dns(148)
Jul 17 00:23:14 tux nmbd[765]: started asyncdns process 766
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_logonnames.c:add_logon_names(156)
Jul 17 00:23:14 tux nmbd[765]: add_domain_logon_names:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become logon server for workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_logonnames.c:add_logon_names(156)
Jul 17 00:23:14 tux nmbd[765]: add_domain_logon_names:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become logon server for workgroup SOFTWARESCHMIED on subnet UNICAST_SUBNET
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_win s(339)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_wins:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become domain master browser on workgroup SOFTWARESCHMIED, subnet UNICAST_SUBNET.
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_win s(354)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_wins: querying WINS server at IP 192.168.111.1 for domain master browser name S$
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(115)
Jul 17 00:23:14 tux nmbd[765]: become_logon_server_success: Samba is now a logon server for workgroup SOFTWARESCHMIED on subnet UNICAST_SUB$
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(115)
Jul 17 00:23:14 tux nmbd[765]: *****
Jul 17 00:23:14 tux nmbd[765]:
Jul 17 00:23:14 tux nmbd[765]: Samba server TUX is now a domain master browser for workgroup SOFTWARESCHMIED on subnet UNICAST_SUBNET
Jul 17 00:23:14 tux nmbd[765]:
Jul 17 00:23:14 tux nmbd[765]: *****
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bca st(291)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_bcast:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become domain master browser on workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bca st(305)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_bcast: querying subnet 192.168.111.1 for domain master browser on workgroup SOFOFTWARESCHMIED
.....
.....
dann kommen ein paar Einträge vom DHCP-Server
Jul 17 00:23:18 tux nmbd[765]: [2002/07/17 00:23:18, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(115)
Jul 17 00:23:18 tux nmbd[765]: become_logon_server_success: Samba is now a logon server for workgroup SOFTWARESCHMIED on subnet 192.168.111$
Jul 17 00:23:18 tux nmbd[765]: [2002/07/17 00:23:18, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237)
Jul 17 00:23:18 tux nmbd[765]: find_response_record: response packet id 6015 received with no matching record.
Jul 17 00:23:18 tux nmbd[765]: [2002/07/17 00:23:18, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237)
Jul 17 00:23:18 tux nmbd[765]: find_response_record: response packet id 6016 received with no matching record.
Jul 17 00:23:18 tux /etc/hotplug/net.agent[618]: No HW description found ... exiting
Jul 17 00:23:20 tux kernel: eth0: no IPv6 routers present
Jul 17 00:23:22 tux nmbd[765]: [2002/07/17 00:23:22, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(115)
Jul 17 00:23:22 tux nmbd[765]: *****
Jul 17 00:23:22 tux nmbd[765]:
Jul 17 00:23:22 tux nmbd[765]: Samba server TUX is now a domain master browser for workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:22 tux nmbd[765]:
Jul 17 00:23:22 tux nmbd[765]: *****
Jul 17 00:23:37 tux nmbd[765]: [2002/07/17 00:23:37, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404)
Jul 17 00:23:37 tux nmbd[765]: *****
Jul 17 00:23:37 tux nmbd[765]:
Jul 17 00:23:37 tux nmbd[765]: Samba name server TUX is now a local master browser for workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:37 tux nmbd[765]:
....
....
Es ist Bürobeginn, die Leute melden sich am Server an
....
....
Jul 17 08:17:38 tux smbd[1928]: [2002/07/17 08:17:38, 0] lib/util_sock.c:read_data(436)
Jul 17 08:17:38 tux smbd[1928]: read_data: read failure for 4. Error = Connection reset by peer
....
....
und dann kommen jede Menge folgende Einträge
....
Jul 17 08:24:08 tux smbd[1986]: [2002/07/17 08:24:08, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:08 tux smbd[1986]: Very strange, couldn't stat "." path=
Jul 17 08:24:08 tux smbd[1986]: [2002/07/17 08:24:08, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:08 tux smbd[1986]: Very strange, couldn't stat "." path=
Jul 17 08:24:08 tux smbd[1986]: [2002/07/17 08:24:08, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:08 tux smbd[1986]: Very strange, couldn't stat "." path=
....
diese Meldung kommt dann ununterbrochen bis:
Jul 17 08:24:12 tux smbd[1986]: [2002/07/17 08:24:12, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:12 tux smbd[1986]: Very strange, couldn't stat "." path=
und das ca. 50 mal pro Senkunde!!
Kann mir jemand auf die Sprünge helfen was er hat bzw. warum der Samba dreimal seinen Status ausgibt? Ich habe fast das Gefühl als würde dieser Mehrfach gestartet.
Gruss Pixel
beim durchstöber den Logfiles (/var/log/messages) sind mir einige Sachen im Umfeld vom Samba aufgefallen welche ich nicht so richtig interpretieren kann.
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/asyncdns.c:start_async_dns(148)
Jul 17 00:23:14 tux nmbd[765]: started asyncdns process 766
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_logonnames.c:add_logon_names(156)
Jul 17 00:23:14 tux nmbd[765]: add_domain_logon_names:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become logon server for workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_logonnames.c:add_logon_names(156)
Jul 17 00:23:14 tux nmbd[765]: add_domain_logon_names:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become logon server for workgroup SOFTWARESCHMIED on subnet UNICAST_SUBNET
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_win s(339)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_wins:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become domain master browser on workgroup SOFTWARESCHMIED, subnet UNICAST_SUBNET.
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_win s(354)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_wins: querying WINS server at IP 192.168.111.1 for domain master browser name S$
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(115)
Jul 17 00:23:14 tux nmbd[765]: become_logon_server_success: Samba is now a logon server for workgroup SOFTWARESCHMIED on subnet UNICAST_SUB$
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(115)
Jul 17 00:23:14 tux nmbd[765]: *****
Jul 17 00:23:14 tux nmbd[765]:
Jul 17 00:23:14 tux nmbd[765]: Samba server TUX is now a domain master browser for workgroup SOFTWARESCHMIED on subnet UNICAST_SUBNET
Jul 17 00:23:14 tux nmbd[765]:
Jul 17 00:23:14 tux nmbd[765]: *****
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bca st(291)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_bcast:
Jul 17 00:23:14 tux nmbd[765]: Attempting to become domain master browser on workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:14 tux nmbd[765]: [2002/07/17 00:23:14, 0] nmbd/nmbd_become_dmb.c:become_domain_master_browser_bca st(305)
Jul 17 00:23:14 tux nmbd[765]: become_domain_master_browser_bcast: querying subnet 192.168.111.1 for domain master browser on workgroup SOFOFTWARESCHMIED
.....
.....
dann kommen ein paar Einträge vom DHCP-Server
Jul 17 00:23:18 tux nmbd[765]: [2002/07/17 00:23:18, 0] nmbd/nmbd_logonnames.c:become_logon_server_success(115)
Jul 17 00:23:18 tux nmbd[765]: become_logon_server_success: Samba is now a logon server for workgroup SOFTWARESCHMIED on subnet 192.168.111$
Jul 17 00:23:18 tux nmbd[765]: [2002/07/17 00:23:18, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237)
Jul 17 00:23:18 tux nmbd[765]: find_response_record: response packet id 6015 received with no matching record.
Jul 17 00:23:18 tux nmbd[765]: [2002/07/17 00:23:18, 0] nmbd/nmbd_responserecordsdb.c:find_response_record(237)
Jul 17 00:23:18 tux nmbd[765]: find_response_record: response packet id 6016 received with no matching record.
Jul 17 00:23:18 tux /etc/hotplug/net.agent[618]: No HW description found ... exiting
Jul 17 00:23:20 tux kernel: eth0: no IPv6 routers present
Jul 17 00:23:22 tux nmbd[765]: [2002/07/17 00:23:22, 0] nmbd/nmbd_become_dmb.c:become_domain_master_stage2(115)
Jul 17 00:23:22 tux nmbd[765]: *****
Jul 17 00:23:22 tux nmbd[765]:
Jul 17 00:23:22 tux nmbd[765]: Samba server TUX is now a domain master browser for workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:22 tux nmbd[765]:
Jul 17 00:23:22 tux nmbd[765]: *****
Jul 17 00:23:37 tux nmbd[765]: [2002/07/17 00:23:37, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(404)
Jul 17 00:23:37 tux nmbd[765]: *****
Jul 17 00:23:37 tux nmbd[765]:
Jul 17 00:23:37 tux nmbd[765]: Samba name server TUX is now a local master browser for workgroup SOFTWARESCHMIED on subnet 192.168.111.1
Jul 17 00:23:37 tux nmbd[765]:
....
....
Es ist Bürobeginn, die Leute melden sich am Server an
....
....
Jul 17 08:17:38 tux smbd[1928]: [2002/07/17 08:17:38, 0] lib/util_sock.c:read_data(436)
Jul 17 08:17:38 tux smbd[1928]: read_data: read failure for 4. Error = Connection reset by peer
....
....
und dann kommen jede Menge folgende Einträge
....
Jul 17 08:24:08 tux smbd[1986]: [2002/07/17 08:24:08, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:08 tux smbd[1986]: Very strange, couldn't stat "." path=
Jul 17 08:24:08 tux smbd[1986]: [2002/07/17 08:24:08, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:08 tux smbd[1986]: Very strange, couldn't stat "." path=
Jul 17 08:24:08 tux smbd[1986]: [2002/07/17 08:24:08, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:08 tux smbd[1986]: Very strange, couldn't stat "." path=
....
diese Meldung kommt dann ununterbrochen bis:
Jul 17 08:24:12 tux smbd[1986]: [2002/07/17 08:24:12, 0] smbd/vfs.c:vfs_GetWd(747)
Jul 17 08:24:12 tux smbd[1986]: Very strange, couldn't stat "." path=
und das ca. 50 mal pro Senkunde!!
Kann mir jemand auf die Sprünge helfen was er hat bzw. warum der Samba dreimal seinen Status ausgibt? Ich habe fast das Gefühl als würde dieser Mehrfach gestartet.
Gruss Pixel