[Samba] FW: Questions about Samba 4
L.P.H. van Belle
belle at bazuin.nl
Wed Aug 26 15:44:44 UTC 2015
ok, i cant make i crash. but i notice my cpu load.
17535 username 20 0 294852 13716 11520 R 100.0 1.3 280:28.70 winbindd
542 username 20 0 291040 16720 14172 R 99.6 1.6 281:45.88 winbindd
and the funny thing.. this user isnt logged in anymore since the last 6 hours.
Greetz,
Louis
>-----Oorspronkelijk bericht-----
>Van: samba [mailto:samba-bounces at lists.samba.org] Namens
>L.P.H. van Belle
>Verzonden: woensdag 26 augustus 2015 11:50
>Aan: samba at lists.samba.org
>Onderwerp: [Samba] FW: Questions about Samba 4
>
>i found the following also ..
>
>Aug 7 08:44:10 rtd-print1 autofs[15991]: Starting automount....
>Aug 7 08:48:26 rtd-print1 autofs[16291]: Stopping automount....
>Aug 7 08:48:27 rtd-print1 automount[16302]: syntax error in
>map near [ * server.internal.domain.tld: ]
>Aug 7 08:48:27 rtd-print1 autofs[16297]: Starting automount....
>Aug 7 08:48:46 rtd-print1 rpcbind: rpcbind terminating on
>signal. Restart with "rpcbind -w"
>Aug 7 08:48:46 rtd-print1 rpcbind[16334]: Stopping rpcbind daemon....
>Aug 7 08:48:46 rtd-print1 rpcbind[16339]: Starting rpcbind daemon....
>
>i had an error in my automount.
>i disabled it, for now, and.. now i recall.. this happend when
>i logged in on ssh also..
>
>i'll try to reproduce this on 4.1.17 ( my proxy ) and 4.2.3
>sernet samba my print server.
>Since the setup of these is exact the same, both debian jessie.
>i cant test it on wheezy, these are still in production.
>
>Greetz,
>
>Louis
>
>
>-----Oorspronkelijk bericht-----
>Van: L.P.H. van Belle [mailto:belle at bazuin.nl]
>Verzonden: woensdag 26 augustus 2015 11:42
>Aan: 'samba at lists.samba.org'
>Onderwerp: RE: [Samba] Questions about Samba 4
>
>Hai
>
>I just looked at the bug report.
>I can say, the error shown in comment 6, of Francois, that
>one i have also seen.
>i cant recall what i exactly did.
>i found the logs with the error, i'll put it in the bug report.
>i cant repoduce this, i upgrade to sernet samba 4.2.3.
>ow and the upgrade was because of the windows Printe managment
>tools, i showed wrong printers + drivers after a rename.
>with 4.2.3 this was gone.
>
>conf here.. and log below ..
>
>the config was unchanged.
>[global]
> workgroup = INTERNAL
> security = ADS
> realm = INTERNAL.DOMAIN.TLD
>
> netbios name = RTD-PRINT1
> domain master = no
> host msdfs = no
>
> dedicated keytab file = /etc/krb5.keytab
> kerberos method = secrets and keytab
> client signing = if_required
>
> ## map id's outside to domain to tdb files.
> idmap config *:backend = tdb
> idmap config *:range = 2000-9999
>
> ## map ids from the domain the range may not overlap !
> idmap config INTERNAL : backend = ad
> idmap config INTERNAL : schema_mode = rfc2307
> idmap config INTERNAL : range = 10000-3999999
>
> winbind nss info = rfc2307
> winbind trusted domains only = no
> winbind use default domain = yes
> winbind enum users = yes
> winbind enum groups = yes
> winbind refresh tickets = yes
> winbind offline logon = yes
>
> wins server = 192.168.0.1, 192.168.0.2
>
> usershare path =
> username map = /etc/samba/samba_usermapping
>
> # For ACL support on member file server
> vfs objects = acl_xattr
> map acl inherit = yes
> store dos attributes = yes
>
> veto files = /.bash_logout/.bash_profile/.bash_history/.bashrc/
> hide unreadable = yes
>
> ## Enabling spoolssd
> rpc_server:spoolss = external
> rpc_daemon:spoolssd = fork
>
> spoolssd:prefork_min_children = 5 # Minimum
>number of child processes
> spoolssd:prefork_max_children = 25 # Maximum
>number of child processes
> spoolssd:prefork_spawn_rate = 5 # Start (fork)
>x new childs if one connection comes in (up to prefork_max_children)
> spoolssd:prefork_max_allowed_clients = 100 # Number of
>clients, a child process should be responsible for
> spoolssd:prefork_child_min_life = 60 # Minimum
>lifetime of a child process (60 seconds
> # is the
>minimum, even a lower value has been configured)
>
>---- log...
>
>and a quick short version :
>Aug 7 08:48:46 rtd-print1 rpcbind: rpcbind terminating on
>signal. Restart with "rpcbind -w"
>Aug 7 08:48:46 rtd-print1 rpcbind[16334]: Stopping rpcbind daemon....
>Aug 7 08:48:46 rtd-print1 rpcbind[16339]: Starting rpcbind daemon....
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: STATUS=daemon
>'winbindd' finished starting up and ready to serve
>connections====================================================
>===========
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: [2015/08/07
>08:49:16.367256, 0] ../lib/util/fault.c:73(fault_report)
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: INTERNAL ERROR:
>Signal 11 in pid 13862 (4.1.17-Debian)
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: Please read the
>Trouble-Shooting section of the Samba HOWTO
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: [2015/08/07
>08:49:16.367371, 0] ../lib/util/fault.c:75(fault_report)
>Aug 7 08:49:16 rtd-print1 winbindd[13862]:
>===============================================================
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: [2015/08/07
>08:49:16.367577, 0] ../source3/lib/util.c:785(smb_panic_s3)
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: PANIC (pid
>13862): internal error
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: [2015/08/07
>08:49:16.375044, 0] ../source3/lib/util.c:896(log_stack_trace)
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: BACKTRACE: 27
>stack frames:
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #0
>/usr/lib/x86_64-linux-gnu/libsmbconf.so.0(log_stack_trace+0x1a)
> [0x7fb28c4622ca]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #1
>/usr/lib/x86_64-linux-gnu/libsmbconf.so.0(smb_panic_s3+0x20)
>[0x7fb28c4623b0]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #2
>/usr/lib/x86_64-linux-gnu/libsamba-util.so.0(smb_panic+0x2f)
>[0x7fb29078ccaf]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #3
>/usr/lib/x86_64-linux-gnu/libsamba-util.so.0(+0x1cecf) [0x7fb29078cecf]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #4
>/lib/x86_64-linux-gnu/libpthread.so.0(+0xf8d0) [0x7fb290bbc8d0]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #5
>/usr/lib/x86_64-linux-gnu/libkrb5.so.26(krb5_storage_free+0x1)
>[0x7fb28af9c2a1]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #6
>/usr/lib/x86_64-linux-gnu/libkrb5.so.26(+0x47665) [0x7fb28af81665]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #7
>/usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0x8e06) [0x7fb28cff8e06]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #8
>/usr/lib/x86_64-linux-gnu/samba/libgse.so.0(gse_krb5_get_server
>_keytab+0xeb) [0x7fb28cff932b]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #9
>/usr/lib/x86_64-linux-gnu/samba/libgse.so.0(+0xb03a) [0x7fb28cffb03a]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #10
>/usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech+0x72
>) [0x7fb28d48aab2]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #11
>/usr/lib/x86_64-linux-gnu/libgensec.so.0(gensec_start_mech_by_o
>id+0x26) [0x7fb28d48ad96]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #12
>/usr/sbin/winbindd(kerberos_return_pac+0x42c) [0x7fb291012cac]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #13
>/usr/sbin/winbindd(winbindd_dual_pam_auth+0x1150) [0x7fb2910385a0]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #14
>/usr/sbin/winbindd(+0x5fd5c) [0x7fb29104cd5c]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #15
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x92cb) [0x7fb28a4bd2cb]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #16
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x7797) [0x7fb28a4bb797]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #17
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d
>) [0x7fb28a4b7f9d]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #18
>/usr/sbin/winbindd(+0x620d8) [0x7fb29104f0d8]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #19
>/usr/sbin/winbindd(+0x627d5) [0x7fb29104f7d5]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #20
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(tevent_common_loop_imm
>ediate+0xd4) [0x7fb28a4b87c4]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #21
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x908e) [0x7fb28a4bd08e]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #22
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(+0x7797) [0x7fb28a4bb797]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #23
>/usr/lib/x86_64-linux-gnu/libtevent.so.0(_tevent_loop_once+0x8d
>) [0x7fb28a4b7f9d]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #24
>/usr/sbin/winbindd(main+0xad4) [0x7fb291012024]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #25
>/lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf5)
>[0x7fb28a12cb45]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: #26
>/usr/sbin/winbindd(+0x25699) [0x7fb291012699]
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: [2015/08/07
>08:49:16.380788, 0] ../source3/lib/dumpcore.c:312(dump_core)
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: unable to change
>to /var/log/samba/cores/winbindd
>Aug 7 08:49:16 rtd-print1 winbindd[13862]: refusing to dump core
>
>
>>-----Oorspronkelijk bericht-----
>>Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rowland Penny
>>Verzonden: woensdag 26 augustus 2015 11:05
>>Aan: samba at lists.samba.org
>>Onderwerp: Re: [Samba] Questions about Samba 4
>>
>>On 26/08/15 09:55, Felix Matouschek wrote:
>>> Hi,
>>>
>>> I can reproduce that behaviour. Our winbindd crashes as well
>>when setting that option.
>>>
>>> Greetings,
>>> Felix
>>>
>>> -----Ursprüngliche Nachricht-----
>>> Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag
>>von Jeremy Allison
>>> Gesendet: Dienstag, 25. August 2015 18:18
>>> An: Sven Schwedas
>>> Cc: samba at lists.samba.org
>>> Betreff: Re: [Samba] Questions about Samba 4
>>>
>>> On Tue, Aug 25, 2015 at 08:36:14AM +0200, Sven Schwedas wrote:
>>>> On 2015-08-24 20:55, Jeremy Allison wrote:
>>>>> On Thu, Aug 13, 2015 at 09:21:23AM +0200, Sven Schwedas wrote:
>>>>> winbindd is extremely reliable and fully supported by the Samba
>>>>> Team, please don't post FUD about Samba components. If you have
>>>>> winbindd problems, post bug reports
>>>> I did, months ago, the last bug report is still unanswered by the
>>>> Samba team and I can still reproducibly crash winbindd (and all
>>>> depending
>>>> services) trivially. Hence, no, it's not "extremely reliable", and
>>>> "full support" is not reassuring.
>>> Reproducible crashes get urgent attention. Is this something
>>that only happens on your system, or is it reproducible elsewhere ?
>>>
>>> --
>>> To unsubscribe from this list go to the following URL and read the
>>> instructions: https://lists.samba.org/mailman/options/samba
>>>
>>>
>>
>>Just what option are you setting?
>>I have seen posts saying 'winbind crashes' but nobody seems to
>>post any
>>info about what they have in smb.conf and what triggers the crash.
>>
>>Rowland
>>
>>
>>--
>>To unsubscribe from this list go to the following URL and read the
>>instructions: https://lists.samba.org/mailman/options/samba
>>
>>
>
>
>--
>To unsubscribe from this list go to the following URL and read the
>instructions: https://lists.samba.org/mailman/options/samba
>
>
More information about the samba
mailing list