Daniel Müller
2023-Sep-12 06:56 UTC
[Samba] WG: Update to samba 4.19 Aduc no longer working No login
This is realy urgent. Wachting the behaviour of samba 4.19. It is filling tmpfs
/run/lock/samba until 100%:
Dateisystem Gr??e Benutzt Verf. Verw% Eingeh?ngt auf
udev 63G 0 63G 0% /dev
tmpfs 13G 2,4M 13G 1% /run
/dev/mapper/dommaster--vg-root 3,6T 17G 3,4T 1% /
tmpfs 63G 2,5M 63G 1% /dev/shm
tmpfs 5,0M 4,7M 324K 94% /run/lock <---
samba is filling
/dev/sda2 471M 150M 297M 34% /boot
/dev/sdb1 11T 3,4G 11T 1% /f2
/dev/sda1 511M 3,5M 508M 1% /boot/efi
tmpfs 13G 84K 13G 1% /run/user/116
tmpfs 13G 56K 13G 1% /run/user/1000
After a restart of samba service:
Dateisystem Gr??e Benutzt Verf. Verw% Eingeh?ngt auf
udev 63G 0 63G 0% /dev
tmpfs 13G 2,4M 13G 1% /run
/dev/mapper/dommaster--vg-root 3,6T 17G 3,4T 1% /
tmpfs 63G 4,1M 63G 1% /dev/shm
tmpfs 5,0M 3,4M 1,7M 68% /run/lock <--
restarting samba set it back to work!
/dev/sda2 471M 150M 297M 34% /boot
/dev/sdb1 11T 3,4G 11T 1% /f2
/dev/sda1 511M 3,5M 508M 1% /boot/efi
tmpfs 13G 84K 13G 1% /run/user/116
tmpfs 13G 56K 13G 1% /run/user/1000
And then no logon or whatever is possible. I need to restart samba services
before it has reached the 100 % peak
to set /run/lock/samba back to work.
How can I manage that? This was not the behaviour in former versions of samba.
Greetings
Daniel
-----Urspr?ngliche Nachricht-----
Von: Mueller via samba [mailto:samba at lists.samba.org]
Gesendet: Montag, 11. September 2023 12:38
An: samba samba <samba at lists.samba.org>
Betreff: [Samba] WG: Update to samba 4.19 Aduc no longer working No login
Wichtigkeit: Hoch
I examined a bit closer. And samba writes to /run/lock/samba:
drwxrwxrwt 5 root root 120 5. Dez 2022 ..
-rw-r--r-- 1 root root 441608 11. Sep 09:58 brlock.tdb
-rw-r--r-- 1 root root 16384 8. Sep 10:54 epmdb.tdb
-rw-r--r-- 1 root root 626688 11. Sep 09:58 gencache.tdb
-rw-r--r-- 1 root root 471040 11. Sep 12:11 leases.tdb
-rw-r--r-- 1 root root 495616 11. Sep 10:00 locking.tdb
drwxr-xr-x 2 root root 720 11. Sep 12:21 msg.lock
-rw-rw---- 1 root root 8192 11. Sep 09:58 names.tdb
-rw-r--r-- 1 root root 696 22. Aug 12:39 printer_list.tdb
-rw-r--r-- 1 root root 16384 11. Sep 10:00 smbd_cleanupd.tdb
-rw------- 1 root root 36864 11. Sep 10:00 smbXsrv_client_global.tdb
-rw------- 1 root root 479232 11. Sep 12:11 smbXsrv_open_global.tdb
-rw------- 1 root root 622592 11. Sep 12:21 smbXsrv_session_global.tdb
-rw------- 1 root root 458752 11. Sep 11:32 smbXsrv_tcon_global.tdb
-rw------- 1 root root 24576 11. Sep 09:58 smbXsrv_version_global.tdb
So my tmpfs in this case is:
tmpfs 5,0M 3,7M 1,4M 74% /run/lock <--------
I found a log entry "NT_STATUS_DISK_FULL" :
[2023/09/07 14:39:43.758129, 0] ../../source3/smbd/server.c:1746(main)
smbd version 4.19.0 started.
Copyright Andrew Tridgell and the Samba Team 1992-2023
[2023/09/08 12:42:13.198122, 0] ../../source3/lib/util.c:484(reinit_after_fork)
messaging_reinit() failed: NT_STATUS_DISK_FULL
[2023/09/08 12:42:13.200547, 0] ../../source3/lib/util.c:484(reinit_after_fork)
messaging_reinit() failed: NT_STATUS_DISK_FULL
[2023/09/08 12:42:13.364187, 0]
../../source3/smbd/server.c:1024(smbd_accept_connection)
reinit_after_fork() failed
[2023/09/08 12:42:13.364246, 0] ../../lib/util/fault.c:178(smb_panic_log)
==============================================================[2023/09/08
12:42:13.364259, 0] ../../lib/util/fault.c:179(smb_panic_log)
INTERNAL ERROR: reinit_after_fork() failed in smbd () () pid 2722082 (4.19.0)
[2023/09/08 12:42:13.364271, 0] ../../lib/util/fault.c:186(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
[2023/09/08 12:42:13.364282, 0] ../../lib/util/fault.c:191(smb_panic_log)
==============================================================[2023/09/08
12:42:13.364293, 0] ../../lib/util/fault.c:192(smb_panic_log)
PANIC (pid 2722082): reinit_after_fork() failed in 4.19.0
[2023/09/08 12:42:13.364703, 0] ../../lib/util/fault.c:303(log_stack_trace)
Could it be samba filled up the tmpfs? So the smbXsrv could not be changed and
written anymore?
Can I stop samba and remove this tdbs?
Greetings
Daniel
-----Urspr?ngliche Nachricht-----
Von: Mueller [mailto:mueller at tplk.loc]
Gesendet: Montag, 11. September 2023 09:49
An: samba samba (samba at lists.samba.org) <samba at lists.samba.org>
Betreff: WG: Update to samba 4.19 Aduc no longer working No login
Wichtigkeit: Hoch
The errors:
Sep 11 09:43:47 dom2 smbd[2387364]: [2023/09/11 09:43:47.463712, 0]
../../source3/smbd/smbXsrv_session.c:1897(smbXsrv_session_logoff)
Sep 11 09:43:47 dom2 smbd[2387364]: smbXsrv_session_logoff:
smbXsrv_session_logoff(0xac9aefbb): failed to delete global key
'AC9AEFBB': NT_S>
Sep 11 09:43:47 dom2 smbd[2387364]: [2023/09/11 09:43:47.496734, 0]
../../source3/smbd/smb2_pipes.c:48(open_np_file)
Sep 11 09:43:47 dom2 smbd[2387364]: file_new failed: NT_STATUS_NOT_FOUND
Sep 11 09:43:47 dom2 smbd[2387364]: [2023/09/11 09:43:47.497793, 0]
../../source3/smbd/smb2_pipes.c:48(open_np_file)
Sep 11 09:43:47 dom2 smbd[2387364]: file_new failed: NT_STATUS_NOT_FOUND
Sep 11 09:44:17 dom2 smbd[2387371]: [2023/09/11 09:44:17.800919, 0]
../../source3/smbd/smbXsrv_session.c:1494(smbXsrv_session_update)
Sep 11 09:44:17 dom2 smbd[2387371]: smbXsrv_session_update:
smbXsrv_session_update: global_id (0x5934baf0) store failed -
NT_STATUS_NOT_FOUND
Sep 11 09:44:17 dom2 smbd[2387371]: [2023/09/11 09:44:17.802044, 0]
../../source3/smbd/smbXsrv_session.c:1897(smbXsrv_session_logoff)
Sep 11 09:44:17 dom2 smbd[2387371]: smbXsrv_session_logoff:
smbXsrv_session_logoff(0x5934baf0): failed to delete global key
'5934BAF0': NT_S>
-----Urspr?ngliche Nachricht-----
Von: Mueller [mailto:mueller at tplk.loc]
Gesendet: Montag, 11. September 2023 09:19
An: samba samba (samba at lists.samba.org) <samba at lists.samba.org>
Betreff: Update to samba 4.19 Aduc no longer working No login
Wichtigkeit: Hoch
Dear all,
after updating to samba 4.19 I cannot use ADUC anymore:
Error Trust levels between the domain could not be established because of no
domain server.
On restarting samba on the server:
service samba status
? samba.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba.service; enabled; vendor preset:
enabled)
Active: failed (Result: exit-code) since Mon 2023-09-11 08:58:38 CEST; 8min
ago
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Process: 2758367 ExecStart=/usr/sbin/samba --foreground --no-process-group
$SAMBAOPTIONS (code=exited, status=1/FAILURE)
Main PID: 2758367 (code=exited, status=1/FAILURE)
Status: "samba: ready to serve connections..."
CPU: 816ms
Sep 11 08:58:38 dommaster samba[2758391]: [2023/09/11 08:58:38.358549, 0]
../../source4/samba/process_prefork.c:498(prefork_restart)
Sep 11 08:58:38 dommaster samba[2758391]: prefork_restart: Restarting [kdc]
pre-fork worker in (10) seconds
Sep 11 08:58:38 dommaster samba[2758367]: [2023/09/11 08:58:38.358975, 0]
../../source4/samba/process_prefork.c:637(prefork_child_pipe_handler)
Sep 11 08:58:38 dommaster samba[2758367]: prefork_child_pipe_handler: Parent
2758367, Child 2758412 terminated with signal 6
Sep 11 08:58:38 dommaster samba[2758367]: [2023/09/11 08:58:38.359033, 0]
../../source4/samba/process_prefork.c:498(prefork_restart)
Sep 11 08:58:38 dommaster samba[2758367]: prefork_restart: Restarting
[winbindd] pre-fork master in (10) seconds
Sep 11 08:58:38 dommaster samba[2758367]: [2023/09/11 08:58:38.359386, 0]
../../source4/samba/server.c:403(samba_terminate)
Sep 11 08:58:38 dommaster samba[2758367]: samba_terminate: samba_terminate of
samba 2758367: smbd child process exited
Sep 11 08:58:38 dommaster systemd[1]: samba.service: Main process exited,
code=exited, status=1/FAILURE Sep 11 08:58:38 dommaster systemd[1]:
samba.service: Failed with result 'exit-code'.
What I did after upgrading:
I set ad dc functional level = 2016 in smb.conf I did, samba-tool domain
schemaupgrade --schema=2019 samba-tool domain functionalprep
--function-level=2016 samba-tool domain level raise --domain-level=2016
--forest-level=2016
All was working over the weekend but suddenly crashes. Even the Emailserver
cannot authenticate against the domain.
Kinit not possible:
kinit administrator at TLK.LOC
kinit: f?r Realm ?TLK.LOC? kann nicht KDC kontaktiert werden bei Anf?ngliche
Anmeldedaten werden geholt.
How can I fix this quickly!?
Greetings
Daniel
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Michael Tokarev
2023-Sep-12 07:08 UTC
[Samba] WG: Update to samba 4.19 Aduc no longer working No login
12.09.2023 09:56, Daniel M?ller via samba:> This is realy urgent. Wachting the behaviour of samba 4.19. It is filling tmpfs /run/lock/samba until 100%: > Dateisystem Gr??e Benutzt Verf. Verw% Eingeh?ngt auf > udev 63G 0 63G 0% /dev > tmpfs 13G 2,4M 13G 1% /run > /dev/mapper/dommaster--vg-root 3,6T 17G 3,4T 1% / > tmpfs 63G 2,5M 63G 1% /dev/shm > tmpfs 5,0M 4,7M 324K 94% /run/lock <--- samba is fillingI guess it's pointless to reply, since seemengly Daniel is using this mailing list as a write-only media. But for others it might be helpful. Here, depending on the load of servers, I see /run/samba directory sizes (here it is configured to use /run/samba instead of /run/lock) ranging from 8M to 50M. None of servers fits into 5M. FWIW. /mjt