This is what I got:
*Distributor ID: DebianDescription: Debian GNU/Linux
bookworm/sidRelease: n/aCodename: bookworm Static hostname:
SMBDC1 Icon name: computerOperating System: Debian GNU/Linux
bookworm/sid Kernel: Linux 5.19.14-sunxi Architecture:
armroot at SMBDC1:~# uname -iunknownroot at SMBDC1:~# uname -aLinux SMBDC1
5.19.14-sunxi #22.08.4 SMP Fri Oct 7 16:45:48 UTC 2022 armv7l GNU/Linux*
Could this not be either 32 or 64 bit?
I've looked it up and if it was, it should have been mentioned somewhere in
here... right?
Il giorno dom 16 ott 2022 alle ore 12:14 Rowland Penny via samba <
samba at lists.samba.org> ha scritto:
>
>
> On 16/10/2022 11:07, Diego Franchini wrote:
> > I tried to set up the network interfaces file and do the purge, plus
> > configured the dhclient file but didn't help.
> >
> > I tried to do a Kinit with log level 3, not sure if it logs to
> > "log.samba" but it wouldn't hurt I thought...
> >
> > the log.samba file contained the following:
> >
> > / ==============================================================>
> [2022/10/16 11:40:02.067205, 0]
> ../../lib/util/fault.c:173(smb_panic_log)
> > INTERNAL ERROR: Signal 11: Segmentation fault in pid 1405
> (4.16.5-Debian)
> > [2022/10/16 11:40:02.070874, 0]
> ../../lib/util/fault.c:177(smb_panic_log)
> > If you are running a recent Samba version, and if you think this
> > problem is not yet fixed in the latest versions, please consider
> > reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
> > <https://wiki.samba.org/index.php/Bug_Reporting>
> > [2022/10/16 11:40:02.074139, 0]
> ../../lib/util/fault.c:182(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.074600, 0]
> ../../lib/util/fault.c:183(smb_panic_log)
> > PANIC (pid 1405): Signal 11: Segmentation fault in 4.16.5-Debian
> > [2022/10/16 11:40:02.075540, 3]
> > ../../lib/ldb-samba/ldb_wrap.c:332(ldb_wrap_connect)
> > ldb_wrap open of secrets.ldb
> > [2022/10/16 11:40:02.085122, 0]
> ../../lib/util/fault.c:172(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.085180, 0]
> ../../lib/util/fault.c:287(log_stack_trace)
> > BACKTRACE: 0 stack frames:
> > [2022/10/16 11:40:02.085682, 0]
> ../../lib/util/fault.c:173(smb_panic_log)
> > INTERNAL ERROR: Signal 11: Segmentation fault in pid 1407
> (4.16.5-Debian)
> > [2022/10/16 11:40:02.085959, 0]
> ../../lib/util/fault.c:177(smb_panic_log)
> > If you are running a recent Samba version, and if you think this
> > problem is not yet fixed in the latest versions, please consider
> > reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
> > <https://wiki.samba.org/index.php/Bug_Reporting>
> > [2022/10/16 11:40:02.086173, 0]
> ../../lib/util/fault.c:182(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.086364, 0]
> ../../lib/util/fault.c:183(smb_panic_log)
> > PANIC (pid 1407): Signal 11: Segmentation fault in 4.16.5-Debian
> > [2022/10/16 11:40:02.090645, 0]
> ../../lib/util/fault.c:287(log_stack_trace)
> > BACKTRACE: 0 stack frames:
> > [2022/10/16 11:40:02.097782, 0]
> > ../../source4/samba/process_prefork.c:520(prefork_restart_fn)
> > prefork_restart_fn: Restarting [kdc] pre-fork worker(2)
> > [2022/10/16 11:40:02.154078, 0]
> > ../../source4/samba/process_prefork.c:582(prefork_child_pipe_handler)
> > prefork_child_pipe_handler: Parent 1190, Child 1407 terminated with
> > signal 6
> > [2022/10/16 11:40:02.155049, 0]
> > ../../source4/samba/process_prefork.c:443(prefork_restart)
> > prefork_restart: Restarting [kdc] pre-fork worker in (20) seconds
> > [2022/10/16 11:40:02.169793, 0]
> > ../../source4/samba/process_prefork.c:582(prefork_child_pipe_handler)
> > prefork_child_pipe_handler: Parent 1190, Child 1405 terminated with
> > signal 6
> > [2022/10/16 11:40:02.170492, 0]
> > ../../source4/samba/process_prefork.c:443(prefork_restart)
> > prefork_restart: Restarting [kdc] pre-fork worker in (20) seconds
> > [2022/10/16 11:40:02.187188, 0]
> > ../../source4/samba/process_prefork.c:520(prefork_restart_fn)
> > prefork_restart_fn: Restarting [kdc] pre-fork worker(3)
> > [2022/10/16 11:40:02.207520, 3]
> > ../../lib/ldb-samba/ldb_wrap.c:332(ldb_wrap_connect)
> > ldb_wrap open of secrets.ldb
> > [2022/10/16 11:40:02.216817, 0]
> ../../lib/util/fault.c:172(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.224321, 0]
> ../../lib/util/fault.c:173(smb_panic_log)
> > INTERNAL ERROR: Signal 11: Segmentation fault in pid 1409
> (4.16.5-Debian)
> > [2022/10/16 11:40:02.227977, 0]
> ../../lib/util/fault.c:177(smb_panic_log)
> > If you are running a recent Samba version, and if you think this
> > problem is not yet fixed in the latest versions, please consider
> > reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
> > <https://wiki.samba.org/index.php/Bug_Reporting>
> > [2022/10/16 11:40:02.229932, 0]
> ../../lib/util/fault.c:182(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.230273, 0]
> ../../lib/util/fault.c:183(smb_panic_log)
> > PANIC (pid 1409): Signal 11: Segmentation fault in 4.16.5-Debian
> > [2022/10/16 11:40:02.234426, 0]
> ../../lib/util/fault.c:287(log_stack_trace)
> > BACKTRACE: 0 stack frames:
> > [2022/10/16 11:40:02.249828, 3]
> > ../../lib/util/util_runcmd.c:319(samba_runcmd_io_handler)
> > samba_runcmd_io_handler: Child /usr/sbin/samba_dnsupdate exited 0
> > [2022/10/16 11:40:02.250186, 3]
> > ../../source4/dsdb/dns/dns_update.c:88(dnsupdate_nameupdate_done)
> > Completed DNS update check OK
> > [2022/10/16 11:40:02.275544, 0]
> > ../../source4/samba/process_prefork.c:582(prefork_child_pipe_handler)
> > prefork_child_pipe_handler: Parent 1190, Child 1409 terminated with
> > signal 6
> > [2022/10/16 11:40:02.275741, 3]
> > ../../lib/ldb-samba/ldb_wrap.c:332(ldb_wrap_connect)
> > ldb_wrap open of secrets.ldb
> > [2022/10/16 11:40:02.276240, 0]
> > ../../source4/samba/process_prefork.c:443(prefork_restart)/
> > / prefork_restart: Restarting [kdc] pre-fork worker in (20) seconds
> > [2022/10/16 11:40:02.282462, 0]
> ../../lib/util/fault.c:172(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.282992, 0]
> ../../lib/util/fault.c:173(smb_panic_log)
> > INTERNAL ERROR: Signal 11: Segmentation fault in pid 1411
> (4.16.5-Debian)
> > [2022/10/16 11:40:02.283256, 0]
> ../../lib/util/fault.c:177(smb_panic_log)
> > If you are running a recent Samba version, and if you think this
> > problem is not yet fixed in the latest versions, please consider
> > reporting this bug, see https://wiki.samba.org/index.php/Bug_Reporting
> > <https://wiki.samba.org/index.php/Bug_Reporting>
> > [2022/10/16 11:40:02.283430, 0]
> ../../lib/util/fault.c:182(smb_panic_log)
> > ==============================================================>
> [2022/10/16 11:40:02.283581, 0]
> ../../lib/util/fault.c:183(smb_panic_log)
> > PANIC (pid 1411): Signal 11: Segmentation fault in 4.16.5-Debian
> > [2022/10/16 11:40:02.287395, 0]
> ../../lib/util/fault.c:287(log_stack_trace)
> > BACKTRACE: 0 stack frames:
> > [2022/10/16 11:40:02.313787, 0]
> > ../../source4/samba/process_prefork.c:582(prefork_child_pipe_handler)
> > prefork_child_pipe_handler: Parent 1190, Child 1411 terminated with
> > signal 6
> > [2022/10/16 11:40:02.314345, 0]
> > ../../source4/samba/process_prefork.c:443(prefork_restart)
> > prefork_restart: Restarting [kdc] pre-fork worker in (20) seconds
> > [2022/10/16 11:40:06.472120, 2]
> > ../../source4/dsdb/kcc/kcc_periodic.c:808(kccsrv_samba_kcc)
> > Calling samba_kcc script/
> > /[2022/10/16 11:40:06.522245, 1]
> >
>
../../source4/dsdb/kcc/garbage_collect_tombstones.c:67(garbage_collect_tombstones_part)
> > Doing a full scan on DC=ForestDnsZones,DC=example,DC=com and
looking
> > for deleted objects
> > [2022/10/16 11:40:06.550502, 1]
> >
>
../../source4/dsdb/kcc/garbage_collect_tombstones.c:67(garbage_collect_tombstones_part)
> > Doing a full scan on DC=DomainDnsZones,DC=/ /example/ /,DC=/ /com/
> > /and looking for deleted objects
> > [2022/10/16 11:40:06.574396, 1]
> >
>
../../source4/dsdb/kcc/garbage_collect_tombstones.c:67(garbage_collect_tombstones_part)
> > Doing a full scan on CN=Configuration,DC=/ /example/ /,DC=/ /com/
> > /and looking for deleted objects
> > [2022/10/16 11:40:07.000963, 1]
> >
>
../../source4/dsdb/kcc/garbage_collect_tombstones.c:67(garbage_collect_tombstones_part)
> > Doing a full scan on DC=/ /example/ /,DC=/ /com/ /and looking for
> > deleted objects
> > [2022/10/16 11:40:08.598539, 3]
> > ../../source4/samba/process_prefork.c:386(prefork_fork_master)
> > prefork_fork_master: Forking 4 ldap worker processes
> > [2022/10/16 11:40:09.533483, 3]
> > ../../lib/util/util_runcmd.c:319(samba_runcmd_io_handler)
> > samba_runcmd_io_handler: Child /usr/sbin/samba_kcc exited 0
> > [2022/10/16 11:40:09.533951, 3]
> > ../../source4/dsdb/kcc/kcc_periodic.c:793(samba_kcc_done)
> > Completed samba_kcc OK
> > [2022/10/16 11:40:22.160959, 0]
> > ../../source4/samba/process_prefork.c:520(prefork_restart_fn)
> > prefork_restart_fn: Restarting [kdc] pre-fork worker(0)
> > [2022/10/16 11:40:22.199351, 0]
> > ../../source4/samba/process_prefork.c:520(prefork_restart_fn)
> > prefork_restart_fn: Restarting [kdc] pre-fork worker(1)
> > [2022/10/16 11:40:22.278000, 0]
> > ../../source4/samba/process_prefork.c:520(prefork_restart_fn)
> > prefork_restart_fn: Restarting [kdc] pre-fork worker(2)
> > [2022/10/16 11:40:22.290846, 3]
> > ../../lib/ldb-samba/ldb_wrap.c:332(ldb_wrap_connect)
> > ldb_wrap open of secrets.ldb
> > [2022/10/16 11:40:22.303424, 0]
> ../../lib/util/fault.c:172(smb_panic_log)
> > ===============================================================/
> >
> > Not too sure what he's lamenting, but INTERNAL ERROR doesn't
sound too
> > good... could this be related to kinit not finding any KDC?
> > I'm still unsure if it's a dns problem, or rather not getting
any reply
> > from the domain controller back for some reason?
> >
> > Like, local samba-tool commands work, i.e. '/samba-tool user
setexpiry
> > Administrator --noexpiry/' and from my understanding kinit from
the Pi
> > sends out a request that should turn back to itself through the
network,
> > and then it replies back to itself, also through the network.
> > So, in this case, what if something is preventing a reply? like an
> > internal error or some component malfunctioning, i.e. krb5-config or
> > krb5-user (it is my understanding that they are responsible for the
> > kinit command)?
> >
> > I'm still getting used to the linux environment and so I still
need
> > to get familiar with a lot of the components and how they work...
> >
>
> That all looks very familiar, are you using a 32bit OS, I got something
> very similar, if not identical, when using Samba 4.16.5 on 32bit
> Raspbian. I moved to Raspberry pi OS 64bit with 4.16.5 and this is
> working correctly for myself.
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>