So after trying update, reinstallation, changing to a new sdcard... I get the same errors, when starting samba with the backport version: [2022/05/16 14:34:36.466993, 0] ../../source4/samba/server.c:621(binary_smbd_main) samba version 4.16.1-Debian started. Copyright Andrew Tridgell and the Samba Team 1992-2022 [2022/05/16 14:34:36.467540, 0] ../../lib/util/become_daemon.c:150(daemon_status) daemon_status: daemon 'samba' : Starting process... [2022/05/16 14:34:37.208800, 0] ../../source4/samba/server.c:897(binary_smbd_main) binary_smbd_main: samba: using 'prefork' process model [2022/05/16 14:34:37.319717, 0] ../../source4/lib/tls/tlscert.c:67(tls_cert_generate) Attempting to autogenerate TLS self-signed keys for https for hostname 'DC03.samba.laurenz.ws' [2022/05/16 14:34:37.557399, 0] ../../lib/util/fault.c:172(smb_panic_log) ==============================================================[2022/05/16 14:34:37.557734, 0] ../../lib/util/fault.c:173(smb_panic_log) INTERNAL ERROR: Signal 11: Segmentation fault in pid 24413 (4.16.1-Debian) [2022/05/16 14:34:37.557842, 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 [2022/05/16 14:34:37.557926, 0] ../../lib/util/fault.c:182(smb_panic_log) ==============================================================[2022/05/16 14:34:37.558004, 0] ../../lib/util/fault.c:183(smb_panic_log) PANIC (pid 24413): Signal 11: Segmentation fault in 4.16.1-Debian [2022/05/16 14:34:37.558571, 0] ../../lib/util/fault.c:287(log_stack_trace) BACKTRACE: 0 stack frames: [2022/05/16 14:34:37.621827, 0] ../../lib/util/fault.c:172(smb_panic_log) ==============================================================[2022/05/16 14:34:37.624922, 0] ../../lib/util/fault.c:173(smb_panic_log) INTERNAL ERROR: Signal 11: Segmentation fault in pid 24427 (4.16.1-Debian) [2022/05/16 14:34:37.626360, 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 [2022/05/16 14:34:37.627836, 0] ../../lib/util/fault.c:182(smb_panic_log) ==============================================================[2022/05/16 14:34:37.629315, 0] ../../lib/util/fault.c:183(smb_panic_log) PANIC (pid 24427): Signal 11: Segmentation fault in 4.16.1-Debian [2022/05/16 14:34:37.631621, 0] ../../lib/util/fault.c:287(log_stack_trace) BACKTRACE: 0 stack frames: [2022/05/16 14:34:37.636204, 0] ../../source4/samba/process_prefork.c:582(prefork_child_pipe_handler) prefork_child_pipe_handler: Parent 24399, Child 24413 terminated with signal 6 [2022/05/16 14:34:37.639824, 0] ../../source4/samba/process_prefork.c:520(prefork_restart_fn) prefork_restart_fn: Restarting [kdc] pre-fork worker(0) [2022/05/16 14:34:37.657836, 0] ../../lib/util/fault.c:172(smb_panic_log)> -----Urspr?ngliche Nachricht----- > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Dirk Laurenz > via samba > Gesendet: Dienstag, 10. Mai 2022 16:13 > An: 'L.P.H. van Belle' <belle at bazuin.nl>; samba at lists.samba.org > Betreff: Re: [Samba] Broken Dependencies? > > THanks a lot from me too > > > -----Urspr?ngliche Nachricht----- > > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von L.P.H. van > > Belle via samba > > Gesendet: Dienstag, 10. Mai 2022 15:21 > > An: samba at lists.samba.org > > Cc: Dirk Laurenz <samba at laurenz.ws> > > Betreff: Re: [Samba] Broken Dependencies? > > > > Hi Dirk > > > > > If i understand your right, using backports is an alternative? > > That?s possible now, correct. > > > > Well, before Micheal, there was not debian-backports samba.. > > I wanted todo that, but that was a to big job for me. > > Micheal worked his ass of to get it this far. > > An amazing job he did, I followed all changes closely. > > Which is also why I didn?t release any 4.16.x packages yet. > > > > As soon the freeze is in for wormbook ( debian 12) we cant update > > samba anymore in debian for new stable. > > Micheal made sure at least 4.16.x gets in. > > He fixed a lot already. > > > > I will be provinding higher samba version to Debian Stable where needed. > > I will be doing the lower current versions also conform samba schedule. > > > > So thanks to all effort of him, now you can step in also on > debian-backports > > Unless, you use profiling-data or Spotlight with Gnome Tracker Backend. > > then you must use my packages. > > > > Samba on Debian got way way better thanks to Michael, and I fully rely > > on > the > > maintainers so, all he did, will get adopted in mine. > > but only as of 4.16, im not backporting all his changes.. > > way to much work. (* sorry) > > > > and please to read the change logs, before you install them. > > https://www.samba.org/samba/history/samba-4.16.0.html > > > > > > Greetz, > > > > Louis > > > > > > > -----Oorspronkelijk bericht----- > > > Van: samba Namens Dirk Laurenz via samba > > > Verzonden: dinsdag 10 mei 2022 14:32 > > > Aan: belle at samba.org; samba at lists.samba.org > > > Onderwerp: Re: [Samba] Broken Dependencies? > > > > > > If i understand your right, using backports is an alternative? > > > > > > > -----Urspr?ngliche Nachricht----- > > > > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von L. van > > > > Belle via samba > > > > Gesendet: Dienstag, 10. Mai 2022 13:36 > > > > An: samba at lists.samba.org > > > > Betreff: Re: [Samba] Broken Dependencies? > > > > > > > > Hai Dirk, > > > > > > > > Can you give me a output of both servers. > > > > dpkg -l | grep -E "samba|winbind|krb5|smbclient " > > > > > > > > I think I see where this is coming from, im already adressing this > > > > in > > > newer > > > > version. > > > > > > > > 2:4.15.7+dfsg-0.1buster1 > > > > 2:4.15.7+dfsg-0.1bullseye1 > > > > > > > > S is higher that L > > > > > > > > Quick fix, remove samba and install it again.. > > > > Just don?t use --autoremove --purge options. > > > > All data and configs will stay as is.. > > > > > > > > The new format will be for the 4.16 line. > > > > > > > > samba_4.16.1+dfsg-3nmu1~deb10+1 < not sure if i will build these. > > > > Reason for that is, there are things enabled that are not > > > > supported on > > > buster. > > > > > > > > samba_4.16.1+dfsg-3nmu1~deb11+1 > > > > samba_4.16.1+dfsg-3ubuntu0~20.04+1 < not sure if i will build > these, > > > > same reason as above but for focal. > > > > samba_4.16.1+dfsg-3ubuntu0~22.04+1 > > > > > > > > The why not, vfs_uring needs kernel 5.1+ > > > > > > > > if you want sooner to 4.16.1 > > > > https://packages.debian.org/search?suite=bullseye- > > > > backports&arch=any&searcho > > > > n=names&keywords=samba > > > > Micheal (new samba debian maintainer) provided already a backport. > > > > > > > > so what's the difference compaired to mine and the > > > > debian-backports, not much anymore. > > > > > > > > last changelog. > > > > samba (2:4.16.1+dfsg-3nmu1~deb11+1) bullseye; urgency=medium > > > > > > > > * Non-maintainer upload. > > > > * Rebuild from bullseye-backports. > > > > Please don't forget to enable Debian Backports for neededdepends> > > > * d/rules, Add profiling-data build parameter > > > > * d/control, Enabled tracker-sparql-2.0 as build depend > > > > This enables support for Spotlight with Gnome Tracker Backend. > > > > Info > > > > > > > https://wiki.samba.org/index.php/Spotlight_with_Gnome_Tracker_Backen > > > d > > > > > > > > -- Louis van Belle <louis at van-belle.nl> Mon, 09 May 2022 > > > > 10:59:16 > > > > +0200 > > > > > > > > im not done with testing them, but if all goes as expected, these > > > > will be > > > online > > > > this week. > > > > At least the debian Bullseye line, very soon now. > > > > > > > > PS. Small side note, > > > > just got a message from Michael, that the current backported samba > > > > does > > > not > > > > support SSSD yet. > > > > fix soon, see debian bug #1010801 > > > > > > > > > > > > Greetz, > > > > > > > > Louis > > > > > > > > > > > > > > > > > -----Oorspronkelijk bericht----- > > > > > Van: samba Namens Dirk Laurenz via samba > > > > > Verzonden: dinsdag 10 mei 2022 12:39 > > > > > Aan: 'sambalist' <samba at lists.samba.org> > > > > > Onderwerp: [Samba] Broken Dependencies? > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > i upgraded a raspian from buster to bullseye and changed all > > > sources.list > > > > to > > > > > bullseye. > > > > > > > > > > > > > > > > > > > > Samba want?s outdated packages? This is the contents of > van-belle.list: > > > > > > > > > > > > > > > > > > > > root at dc02:~# cat /etc/apt/sources.list.d/van-belle.list > > > > > > > > > > # AptVanBelle repo for samba. > > > > > > > > > > #deb [arch=armhf > > > > > signed-by=/usr/share/keyrings/louis-van-belle.gpg] > > > > > http://apt.van-belle.nl/debian/ buster-samba415 main > > > > > > > > > > deb [arch=armhf > > > > > signed-by=/usr/share/keyrings/louis-van-belle.gpg] > > > > > http://apt.van-belle.nl/debian/ bullseye-samba415 main > > > > > > > > > > > > > > > > > > > > So far everything went well, but apt uninstalled samba while > upgrading. > > > > > When I now want to reinstall I get this. > > > > > > > > > > > > > > > > > > > > root at dc02:~# aptitude update > > > > > > > > > > Treffer http://apt.van-belle.nl/debian buster-samba415 InRelease > > > > > > > > > > Treffer http://raspbian.raspberrypi.org/raspbian bullseye > > > > > InRelease > > > > > > > > > > Treffer http://archive.raspberrypi.org/debian bullseye InRelease > > > > > > > > > > Treffer http://apt.van-belle.nl/debian bullseye-samba415 > > > > > InRelease > > > > > > > > > > Treffer https://repo.saltproject.io/py3/debian/11/amd64/latest > > > > > bullseye InRelease > > > > > > > > > > Ign https://download.webmin.com/download/repository sarge > > > InRelease > > > > > > > > > > Treffer https://download.webmin.com/download/repository sarge > > > > > Release > > > > > > > > > > > > > > > > > > > > root at dc02:~# apt-get full-upgrade > > > > > > > > > > Paketlisten werden gelesen? Fertig > > > > > > > > > > Abh?ngigkeitsbaum wird aufgebaut? Fertig > > > > > > > > > > Statusinformationen werden eingelesen? Fertig > > > > > > > > > > Paketaktualisierung (Upgrade) wird berechnet? Fertig > > > > > > > > > > 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht > > > > aktualisiert. > > > > > > > > > > root at dc02:~# aptitude install samba > > > > > > > > > > Die folgenden NEUEN Pakete werden zus?tzlich installiert: > > > > > > > > > > acl{a} attr{a} libldb2{a} libtdb1{a} python3-cffi-backend{a} > > > > > python3- cryptography{a} python3-dnspython{a} python3- > > markdown{a} > > > > > python3- pygments{a} python3-requests-toolbelt{a} samba{b} > > > > > > > > > > samba-common{a} tdb-tools{a} > > > > > > > > > > 0 Pakete aktualisiert, 13 zus?tzlich installiert, 0 werden > > > > > entfernt und > > > 0 > > > > nicht > > > > > aktualisiert. > > > > > > > > > > 1.244 kB/2.822 kB an Archiven m?ssen heruntergeladen werden. > > > > > Nach dem Entpacken werden 24,5 MB zus?tzlich belegt sein. > > > > > > > > > > Die folgenden Pakete haben verletzte Abh?ngigkeiten: > > > > > > > > > > samba : H?ngt ab von: python3 (< 3.8) but 3.9.2-3 is installed > > > > > > > > > > H?ngt ab von: python3-samba ist aber nicht > > > > > installationsf?hig > > > > > > > > > > H?ngt ab von: samba-common-bin (> > > > > 2:4.15.7+dfsg-0.1buster1) ist > > > > aber > > > > > nicht installationsf?hig > > > > > > > > > > H?ngt ab von: libpython3.7 (>= 3.7.0) which is a > > > > > virtual > > > package > > > > and is not > > > > > provided by any available package > > > > > > > > > > > > > > > > > > > > H?ngt ab von: samba-libs (= 2:4.15.7+dfsg-0.1buster1) > > > > > ist aber > > > > nicht > > > > > installationsf?hig > > > > > > > > > > > > > > > > > > > > Why is samba requesting buster packages although I provide the > > > > > bullseye repo (samba at the moment same version) > > > > > > > > > > > > > > > > > > > > Beibehalten der folgenden Pakete in ihrer aktuellen Version: > > > > > > > > > > 1) samba [Nicht installiert] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > 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 > > > > > > > > > -- > > > 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 > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba
Here are level 10 debug logs> -----Urspr?ngliche Nachricht----- > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Dirk Laurenz > via samba > Gesendet: Montag, 16. Mai 2022 14:39 > An: 'Dirk Laurenz' <samba at laurenz.ws>; 'L.P.H. van Belle'<belle at bazuin.nl>;> samba at lists.samba.org > Betreff: Re: [Samba] Broken Dependencies? > > So after trying update, reinstallation, changing to a new sdcard... I getthe> same errors, when starting samba with the backport version: > > > [2022/05/16 14:34:36.466993, 0] > ../../source4/samba/server.c:621(binary_smbd_main) > samba version 4.16.1-Debian started. > Copyright Andrew Tridgell and the Samba Team 1992-2022 > [2022/05/16 14:34:36.467540, 0] > ../../lib/util/become_daemon.c:150(daemon_status) > daemon_status: daemon 'samba' : Starting process... > [2022/05/16 14:34:37.208800, 0] > ../../source4/samba/server.c:897(binary_smbd_main) > binary_smbd_main: samba: using 'prefork' process model > [2022/05/16 14:34:37.319717, 0] > ../../source4/lib/tls/tlscert.c:67(tls_cert_generate) > Attempting to autogenerate TLS self-signed keys for https for hostname > 'DC03.samba.laurenz.ws' > [2022/05/16 14:34:37.557399, 0] ../../lib/util/fault.c:172(smb_panic_log) > ==============================================================> [2022/05/16 14:34:37.557734, 0] ../../lib/util/fault.c:173(smb_panic_log) > INTERNAL ERROR: Signal 11: Segmentation fault in pid 24413 (4.16.1- > Debian) > [2022/05/16 14:34:37.557842, 0] ../../lib/util/fault.c:177(smb_panic_log) > If you are running a recent Samba version, and if you think this problemis> not yet fixed in the latest versions, please consider reporting this bug,see> https://wiki.samba.org/index.php/Bug_Reporting > [2022/05/16 14:34:37.557926, 0] ../../lib/util/fault.c:182(smb_panic_log) > ==============================================================> [2022/05/16 14:34:37.558004, 0] ../../lib/util/fault.c:183(smb_panic_log) > PANIC (pid 24413): Signal 11: Segmentation fault in 4.16.1-Debian > [2022/05/16 14:34:37.558571, 0]../../lib/util/fault.c:287(log_stack_trace)> BACKTRACE: 0 stack frames: > [2022/05/16 14:34:37.621827, 0] ../../lib/util/fault.c:172(smb_panic_log) > ==============================================================> [2022/05/16 14:34:37.624922, 0] ../../lib/util/fault.c:173(smb_panic_log) > INTERNAL ERROR: Signal 11: Segmentation fault in pid 24427 (4.16.1- > Debian) > [2022/05/16 14:34:37.626360, 0] ../../lib/util/fault.c:177(smb_panic_log) > If you are running a recent Samba version, and if you think this problemis> not yet fixed in the latest versions, please consider reporting this bug,see> https://wiki.samba.org/index.php/Bug_Reporting > [2022/05/16 14:34:37.627836, 0] ../../lib/util/fault.c:182(smb_panic_log) > ==============================================================> [2022/05/16 14:34:37.629315, 0] ../../lib/util/fault.c:183(smb_panic_log) > PANIC (pid 24427): Signal 11: Segmentation fault in 4.16.1-Debian > [2022/05/16 14:34:37.631621, 0]../../lib/util/fault.c:287(log_stack_trace)> BACKTRACE: 0 stack frames: > [2022/05/16 14:34:37.636204, 0] > ../../source4/samba/process_prefork.c:582(prefork_child_pipe_handler) > prefork_child_pipe_handler: Parent 24399, Child 24413 terminated with > signal 6 > [2022/05/16 14:34:37.639824, 0] > ../../source4/samba/process_prefork.c:520(prefork_restart_fn) > prefork_restart_fn: Restarting [kdc] pre-fork worker(0) > [2022/05/16 14:34:37.657836, 0] ../../lib/util/fault.c:172(smb_panic_log) > > > > > -----Urspr?ngliche Nachricht----- > > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von Dirk Laurenz > > via samba > > Gesendet: Dienstag, 10. Mai 2022 16:13 > > An: 'L.P.H. van Belle' <belle at bazuin.nl>; samba at lists.samba.org > > Betreff: Re: [Samba] Broken Dependencies? > > > > THanks a lot from me too > > > > > -----Urspr?ngliche Nachricht----- > > > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von L.P.H. van > > > Belle via samba > > > Gesendet: Dienstag, 10. Mai 2022 15:21 > > > An: samba at lists.samba.org > > > Cc: Dirk Laurenz <samba at laurenz.ws> > > > Betreff: Re: [Samba] Broken Dependencies? > > > > > > Hi Dirk > > > > > > > If i understand your right, using backports is an alternative? > > > That?s possible now, correct. > > > > > > Well, before Micheal, there was not debian-backports samba.. > > > I wanted todo that, but that was a to big job for me. > > > Micheal worked his ass of to get it this far. > > > An amazing job he did, I followed all changes closely. > > > Which is also why I didn?t release any 4.16.x packages yet. > > > > > > As soon the freeze is in for wormbook ( debian 12) we cant update > > > samba anymore in debian for new stable. > > > Micheal made sure at least 4.16.x gets in. > > > He fixed a lot already. > > > > > > I will be provinding higher samba version to Debian Stable whereneeded.> > > I will be doing the lower current versions also conform sambaschedule.> > > > > > So thanks to all effort of him, now you can step in also on > > debian-backports > > > Unless, you use profiling-data or Spotlight with Gnome TrackerBackend.> > > then you must use my packages. > > > > > > Samba on Debian got way way better thanks to Michael, and I fully > > > rely on > > the > > > maintainers so, all he did, will get adopted in mine. > > > but only as of 4.16, im not backporting all his changes.. > > > way to much work. (* sorry) > > > > > > and please to read the change logs, before you install them. > > > https://www.samba.org/samba/history/samba-4.16.0.html > > > > > > > > > Greetz, > > > > > > Louis > > > > > > > > > > -----Oorspronkelijk bericht----- > > > > Van: samba Namens Dirk Laurenz via samba > > > > Verzonden: dinsdag 10 mei 2022 14:32 > > > > Aan: belle at samba.org; samba at lists.samba.org > > > > Onderwerp: Re: [Samba] Broken Dependencies? > > > > > > > > If i understand your right, using backports is an alternative? > > > > > > > > > -----Urspr?ngliche Nachricht----- > > > > > Von: samba <samba-bounces at lists.samba.org> Im Auftrag von L. van > > > > > Belle via samba > > > > > Gesendet: Dienstag, 10. Mai 2022 13:36 > > > > > An: samba at lists.samba.org > > > > > Betreff: Re: [Samba] Broken Dependencies? > > > > > > > > > > Hai Dirk, > > > > > > > > > > Can you give me a output of both servers. > > > > > dpkg -l | grep -E "samba|winbind|krb5|smbclient " > > > > > > > > > > I think I see where this is coming from, im already adressing > > > > > this in > > > > newer > > > > > version. > > > > > > > > > > 2:4.15.7+dfsg-0.1buster1 > > > > > 2:4.15.7+dfsg-0.1bullseye1 > > > > > > > > > > S is higher that L > > > > > > > > > > Quick fix, remove samba and install it again.. > > > > > Just don?t use --autoremove --purge options. > > > > > All data and configs will stay as is.. > > > > > > > > > > The new format will be for the 4.16 line. > > > > > > > > > > samba_4.16.1+dfsg-3nmu1~deb10+1 < not sure if i will buildthese.> > > > > Reason for that is, there are things enabled that are not > > > > > supported on > > > > buster. > > > > > > > > > > samba_4.16.1+dfsg-3nmu1~deb11+1 > > > > > samba_4.16.1+dfsg-3ubuntu0~20.04+1 < not sure if i will build > > these, > > > > > same reason as above but for focal. > > > > > samba_4.16.1+dfsg-3ubuntu0~22.04+1 > > > > > > > > > > The why not, vfs_uring needs kernel 5.1+ > > > > > > > > > > if you want sooner to 4.16.1 > > > > > https://packages.debian.org/search?suite=bullseye- > > > > > backports&arch=any&searcho > > > > > n=names&keywords=samba > > > > > Micheal (new samba debian maintainer) provided already abackport.> > > > > > > > > > so what's the difference compaired to mine and the > > > > > debian-backports, not much anymore. > > > > > > > > > > last changelog. > > > > > samba (2:4.16.1+dfsg-3nmu1~deb11+1) bullseye; urgency=medium > > > > > > > > > > * Non-maintainer upload. > > > > > * Rebuild from bullseye-backports. > > > > > Please don't forget to enable Debian Backports for needed > depends > > > > > * d/rules, Add profiling-data build parameter > > > > > * d/control, Enabled tracker-sparql-2.0 as build depend > > > > > This enables support for Spotlight with Gnome Tracker Backend. > > > > > Info > > > > > > > > > https://wiki.samba.org/index.php/Spotlight_with_Gnome_Tracker_Back > > > > en > > > > d > > > > > > > > > > -- Louis van Belle <louis at van-belle.nl> Mon, 09 May 2022 > > > > > 10:59:16 > > > > > +0200 > > > > > > > > > > im not done with testing them, but if all goes as expected, > > > > > these will be > > > > online > > > > > this week. > > > > > At least the debian Bullseye line, very soon now. > > > > > > > > > > PS. Small side note, > > > > > just got a message from Michael, that the current backported > > > > > samba does > > > > not > > > > > support SSSD yet. > > > > > fix soon, see debian bug #1010801 > > > > > > > > > > > > > > > Greetz, > > > > > > > > > > Louis > > > > > > > > > > > > > > > > > > > > > -----Oorspronkelijk bericht----- > > > > > > Van: samba Namens Dirk Laurenz via samba > > > > > > Verzonden: dinsdag 10 mei 2022 12:39 > > > > > > Aan: 'sambalist' <samba at lists.samba.org> > > > > > > Onderwerp: [Samba] Broken Dependencies? > > > > > > > > > > > > Hi, > > > > > > > > > > > > > > > > > > > > > > > > i upgraded a raspian from buster to bullseye and changed all > > > > sources.list > > > > > to > > > > > > bullseye. > > > > > > > > > > > > > > > > > > > > > > > > Samba want?s outdated packages? This is the contents of > > van-belle.list: > > > > > > > > > > > > > > > > > > > > > > > > root at dc02:~# cat /etc/apt/sources.list.d/van-belle.list > > > > > > > > > > > > # AptVanBelle repo for samba. > > > > > > > > > > > > #deb [arch=armhf > > > > > > signed-by=/usr/share/keyrings/louis-van-belle.gpg] > > > > > > http://apt.van-belle.nl/debian/ buster-samba415 main > > > > > > > > > > > > deb [arch=armhf > > > > > > signed-by=/usr/share/keyrings/louis-van-belle.gpg] > > > > > > http://apt.van-belle.nl/debian/ bullseye-samba415 main > > > > > > > > > > > > > > > > > > > > > > > > So far everything went well, but apt uninstalled samba while > > upgrading. > > > > > > When I now want to reinstall I get this. > > > > > > > > > > > > > > > > > > > > > > > > root at dc02:~# aptitude update > > > > > > > > > > > > Treffer http://apt.van-belle.nl/debian buster-samba415 > > > > > > InRelease > > > > > > > > > > > > Treffer http://raspbian.raspberrypi.org/raspbian bullseye > > > > > > InRelease > > > > > > > > > > > > Treffer http://archive.raspberrypi.org/debian bullseye > > > > > > InRelease > > > > > > > > > > > > Treffer http://apt.van-belle.nl/debian bullseye-samba415 > > > > > > InRelease > > > > > > > > > > > > Treffer https://repo.saltproject.io/py3/debian/11/amd64/latest > > > > > > bullseye InRelease > > > > > > > > > > > > Ign https://download.webmin.com/download/repository sarge > > > > InRelease > > > > > > > > > > > > Treffer https://download.webmin.com/download/repository sarge > > > > > > Release > > > > > > > > > > > > > > > > > > > > > > > > root at dc02:~# apt-get full-upgrade > > > > > > > > > > > > Paketlisten werden gelesen? Fertig > > > > > > > > > > > > Abh?ngigkeitsbaum wird aufgebaut? Fertig > > > > > > > > > > > > Statusinformationen werden eingelesen? Fertig > > > > > > > > > > > > Paketaktualisierung (Upgrade) wird berechnet? Fertig > > > > > > > > > > > > 0 aktualisiert, 0 neu installiert, 0 zu entfernen und 0 nicht > > > > > aktualisiert. > > > > > > > > > > > > root at dc02:~# aptitude install samba > > > > > > > > > > > > Die folgenden NEUEN Pakete werden zus?tzlich installiert: > > > > > > > > > > > > acl{a} attr{a} libldb2{a} libtdb1{a} python3-cffi-backend{a} > > > > > > python3- cryptography{a} python3-dnspython{a} python3- > > > markdown{a} > > > > > > python3- pygments{a} python3-requests-toolbelt{a} samba{b} > > > > > > > > > > > > samba-common{a} tdb-tools{a} > > > > > > > > > > > > 0 Pakete aktualisiert, 13 zus?tzlich installiert, 0 werden > > > > > > entfernt und > > > > 0 > > > > > nicht > > > > > > aktualisiert. > > > > > > > > > > > > 1.244 kB/2.822 kB an Archiven m?ssen heruntergeladen werden. > > > > > > Nach dem Entpacken werden 24,5 MB zus?tzlich belegt sein. > > > > > > > > > > > > Die folgenden Pakete haben verletzte Abh?ngigkeiten: > > > > > > > > > > > > samba : H?ngt ab von: python3 (< 3.8) but 3.9.2-3 is installed > > > > > > > > > > > > H?ngt ab von: python3-samba ist aber nicht > > > > > > installationsf?hig > > > > > > > > > > > > H?ngt ab von: samba-common-bin (> > > > > > 2:4.15.7+dfsg-0.1buster1) ist > > > > > aber > > > > > > nicht installationsf?hig > > > > > > > > > > > > H?ngt ab von: libpython3.7 (>= 3.7.0) which is a > > > > > > virtual > > > > package > > > > > and is not > > > > > > provided by any available package > > > > > > > > > > > > > > > > > > > > > > > > H?ngt ab von: samba-libs (= 2:4.15.7+dfsg-0.1buster1) > > > > > > ist aber > > > > > nicht > > > > > > installationsf?hig > > > > > > > > > > > > > > > > > > > > > > > > Why is samba requesting buster packages although I provide the > > > > > > bullseye repo (samba at the moment same version) > > > > > > > > > > > > > > > > > > > > > > > > Beibehalten der folgenden Pakete in ihrer aktuellenVersion:> > > > > > > > > > > > 1) samba [Nicht installiert] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > 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 > > > > > > > > > > > > -- > > > > 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 > > > > > > -- > > 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
16.05.2022 15:38, Dirk Laurenz via samba wrote:> So after trying update, reinstallation, changing to a new sdcard... I get > the same errors, when starting samba with the backport version: > > > [2022/05/16 14:34:36.466993, 0] > ../../source4/samba/server.c:621(binary_smbd_main) > samba version 4.16.1-Debian started. > Copyright Andrew Tridgell and the Samba Team 1992-2022 > [2022/05/16 14:34:36.467540, 0] > ../../lib/util/become_daemon.c:150(daemon_status) > daemon_status: daemon 'samba' : Starting process... > [2022/05/16 14:34:37.208800, 0] > ../../source4/samba/server.c:897(binary_smbd_main) > binary_smbd_main: samba: using 'prefork' process model > [2022/05/16 14:34:37.319717, 0] > ../../source4/lib/tls/tlscert.c:67(tls_cert_generate) > Attempting to autogenerate TLS self-signed keys for https for hostname > 'DC03.samba.laurenz.ws' > [2022/05/16 14:34:37.557399, 0] ../../lib/util/fault.c:172(smb_panic_log) > ==============================================================> [2022/05/16 14:34:37.557734, 0] ../../lib/util/fault.c:173(smb_panic_log) > INTERNAL ERROR: Signal 11: Segmentation fault in pid 24413 (4.16.1-Debian)Lovely. I haven't seen any panics with 4.16 versions so far. But this is arm, - I never tried samba on arm either. In debian by default panic action is set to /usr/share/samba/panic-action which is a script which tries to send email with the backtrace. It is an old thing, I think it should be changed now to save the backtrace in some file instead of trying to email it. There, if there's no "mail" command installed, the script just exits with exit status 0, and it even if this command is available, there's a good chance it does not work anyway. In order to collect a useful backtrace which can be used to diagnose this, one has to install the dbgsym package for samba (and I guess samba-libs too), - see https://wiki.debian.org/HowToGetABacktrace for how to add the necessary line into your apt/sourses.list file, next install samba-dbgsym and samba-libs-dbgsym packages. And install gdb package too. After that, - it looks like you don't have a working mail command - I'd suggest you to modify the script, /usr/share/samba/panic-action (or change "panic action" parameter in smb.conf to point to the new script) which does just this: #! /bin/sh exe=$(readlink /proc/$1/exe) gdb -x /etc/samba/gdbcommands --batch $exe $1 >/var/log/samba/backtrace.$1 2>&1 (untested but should be close to what's needed). and post the contents of /var/log/backtrace.NN files here. The backtrace isn't usually large. Thanks, /mjt