Re: [DNG] OpenPGP key for Devuan Release ISOs?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, There is no 'correct' location, you need a proper chain of trust in order to really verify the signature... You can try keyserver.ubuntu.com; looks like keys.gnupg.net is overloaded/offline... With best regards, b. On Fri, 2022-02-25 at 20:06 +0200, Lars Noodén via Dng wrote: > I see that the ISO images are signed. I've tried to fetch the signing > key[1] again, > > $ gpg --keyserver keys.gnupg.net \ > --recv-key E032601B7CA10BC3EA53FA81BB23C00C61FC752C > > $ gpg --keyserver keys.gnupg.net \ > --recv-key BB23C00C61FC752C > > $ gpg --keyserver keys.gnupg.net \ > --search-keys BB23C00C61FC752C > > but get an error instead with each of the above methods: > > gpg: keyserver receive failed: Server indicated a failure > > What is the current / correct location to find the public key to check > the releases with? > > /Lars > > [1] https://www.devuan.org/os/keyring > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmIZio4ACgkQE2VyCRPS 8i3efQ/7B3w1zC3R2V9O/v8Tg0Wv7QgmCdSR5wb3anlyXnNO9t2gbg35SiwUZv/G yyUEKkKQOByBfzn+zHL1qg2/turA8F6Ugajt19z1EFAYBymaZ+0tVhPlKOnXhD5J prqBzArjeyJuyxIgK5gH5g9xqe6WPCRAdJfb8CAOwFNPE5zfrZw1xDD6KWaoZcPr Kbt00+Dw7mxuIEomq416p+VVnnVlx5Bhg8QRk6FdrvcZK11+Ij1X4cErKLAtUKWG YyRfZDU0hTsugaEBQbshAOtkK7e9aVxVtkQrvTf5m9eziKyRB5Ob9qyIK2Us91Md V8jvR8AgWc7Ma8ipouykWe4wasjij37Jwj1IAHNGLuRFStrIArdcjzALIBy0iNSV 3mi+j8HXc+l5vnEr35bfgmU3oAlrkCOzwYRZWKeegqYUDdtr/7zWOChrdcHSkUuj ML8Gig+lGb0DyhfyXEnelhGXrYORq/tqNRk/g+Ioo2CXdzF83H6VPFVmQtHMEBZd KEt6KdaXYQRjWCIk2VQX5mjCDlTyD3JqyCLVn3rtEE9XymQDQ4NRSEcbIzA3K58c o74ji0s8BAd/VfCh8q3JLr96wqbZpoqPudhyQephyME731YAAuW8r2CUAZrAozOe iTBORDyDkJMJ+ppnpSxa+5/kK7tHf7lJsW5EzLlryi0PyAraXs0= =wgFA -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lvm2 depends on systemd
Hi, Maybe I have omitted to share more details - I am building the plain upstream lvm and do not create a package (no patches involved). Also I may be missing what are you trying to do, in case you share a repo, I may be able to help with that... With best regards, b. On Tue, 2022-02-22 at 08:40 +0100, aitor wrote: > > > It doesn't build successfully without disabling lvmlockd. > I rectify: without modifying the quilt patch applied by debian. > > llvm2-lockd is present in my packaging. > > Aitor. > > > Enviado con Aqua Mail para Android > https://www.mobisystems.com/aqua-mail > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng signature.asc Description: This is a digitally signed message part ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lvm2 depends on systemd
Hi, Add --disable-notify-dbus - in my case it looks like to be properly set by the autodetection and it worked. BTW lvm version 2.03.15 and I got a successful sd free build... With best regards, b. On Sat, 2022-02-19 at 22:18 +0100, aitor wrote: > Hi Boian, > On 19/2/22 0:22, Boian Bonev wrote: > What about: > ./configure --disable-systemd-journal --disable-udev-systemd-background-jobs > Thanks for your suggestion, but I run into the same error: > notify/lvmnotify.c:22:10: fatal error: systemd/sd-bus.h: No existe el fichero > o el directorio > 22 | #include > | ^~ > compilation terminated. > Cheers, > Aitor. > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng signature.asc Description: This is a digitally signed message part ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] lvm2 depends on systemd
Hi, What about: ./configure --disable-systemd-journal --disable-udev-systemd-background-jobs On Thu, 2022-02-17 at 23:31 +0100, aitor wrote: > Hi, > I've noticed that the sources of lvm2 cannot be built in devuan chimaera due > to the headers: > > #include > #include > > present in files like lib/notify/lvmnotify.c or > daemons/lvlockd/lvmlockd-core.c. The unique way > I've found to by-pass them is disabling notify-bus in the config flags > defined in debian/rules. > This entails not only the removal of the package lvm2-dbusd from > debian/control -nonexistent on > beowulf-, but also the addition of a quilt patch, say devuan-changes, that > differs slightly > from the original debian-changes. Here you are my proposal for lvm2 in devuan > chimaera: > > http://packages.gnuinos.org/gnuinos/pool/main/l/lvm2/lvm2_2.03.11-2.1+gnuinos4.debian.tar.xz > Finally, I wish to mention that the installer-isos of gnuinos have been > updated today as a > key outcome of the changes made in various packages of the repository, as > well as the recent > runit scripts put in place. > > Cheers, > Aitor. > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng signature.asc Description: This is a digitally signed message part ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bug in synaptic package manager?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Wed, 2022-01-26 at 03:30 +0200, Boian Bonev wrote: > > > Hi, > > a stupid question, could the templates be added to the base-files package > > that is already forked? > > It is not stupid at all - technically that is possible because there would be > no filename conflict. But I do not think it is the proper way because that > may > create confusion and would be hard to track for anyone not knowing what was > done. BTW I have no idea about the level of pureness desired, so I can't say. It was decided to add a Devuan specific package - python-apt-common-devuan, that is already in ceres but nothing depends on it. Soon the parts in tasksel that recommend synaptic will also recommend python-apt-common-devuan, so it would get installed automatically... Please test that - it does not depend on anything, so it should be easy to install the ceres package anywhere. Updates to the stable releases are pending after more thorough testing. HTH With best regards, b. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmH6FNYACgkQE2VyCRPS 8i2zqBAAk1v4FBjdHzZOhw6vN7ygva3zuZaYf+iRbPHPcriZkVJi03TIEmZfRsrP EDGQHQKfeJHlbH27Kl8ZtwrxuIRaGbj+fTNwRG8zVQKZA2L17TWLSXJpJw5qESis /N+PzqGa0y4exMvNNqUZNQOvsqHSrAwtHqEg7fJ2Xi5fLQqC6pUWqQ/ciI+DHNcv 1pxAIN8ID66gdLieFLrZCQGzz9gUHUYLoSYTpJQ9ySbU5wBwFdoHz6ymsRTg+o/q Pf/ALKJm/FTI6xMMnLiIayyL30ZpWqJQYDrJj61NsD6yT3o5CXT3QMuVpM+tZP3P ylRr3b0LUX6LBWDp2k3iz1VyNdHLM1j+QS0wotqTIvHHjJ67p6N7nVDKvu947Yvm rCqxyeufE3lcO1NODisqEkYCWuyBvbxkzyY1Hxe+V8QRTG+3n8RLK63WB1FcE28M 1Cde0OGIz6X+QUEazGrqRMzSYff/B/2iQ0tBG09BetHuCcyj9E7FmLojNZeuIL0z NHOsflcc+kQgd9yC4kjfiFM0B0DoVlgnZ9LuZ9Haqmt0OAWamEHupkbTZ2oxIOgy rZhVkAn3+hJqmE8wIiUvsEZhdfje0R7R5Htr1GK5bGBpX38omKuITC7rJzi67EmA L4OJPChdTFFAGB53T541mcqnBb8BW6Y4HnKRaUm+fiyrhwBt0Rc= =H0PX -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bug in synaptic package manager?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 > ... > > There are two options: > > > > 1) Submit a PR to the packager/team in Debian > > 2) Fork the package for Devuan and maintain the appropriate information in > > it > > > > My opinion is that 1) is not a good option, because the mirror list is > > volatile > > information and that would require stable updates on a regular basis (and > > that > > won't easily happen in Debian) > > Hi, > a stupid question, could the templates be added to the base-files package > that is already forked? It is not stupid at all - technically that is possible because there would be no filename conflict. But I do not think it is the proper way because that may create confusion and would be hard to track for anyone not knowing what was done. BTW I have no idea about the level of pureness desired, so I can't say. With best regards, b. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmHwpDcACgkQE2VyCRPS 8i2FTQ//UadDX/oN3Hzk1x3ubS4PX87Y4gzMkKAJLu/YEMV99Zb2QJZd3vvCryMw CyJTKfIxo9LipMSQrWvHmmO8lmcgzCD8zx+I/JvlJSf57ckmGOXkM/LPhmNwwWip aDnvDuatVNcI35f6mhd45jxzuXooz8+zG3R9c8TsnTJZC1pNe9DS9ZPA2UTxNgEq V3xLVrAh/7s+HY3/cI1ui0JurPTfD8COtqbV+BPGBpanqvAu4zBV8meWunzlOti4 xT9u8H0l+9myBAnJXwTwyF2Mw50DiDk5Y6kzyIGgxO5XCkbZYFr0cgY9IJ4xhJ04 ww1KTgoYQGDn1yHTh05MJsobSNqa1uy41+LcKLNFf9ewLkMb1rIff8916mTyswUW 4sID4QDTuCpdxjV2uRwaO4eWggB5TiI7rzQ798VhxSxAN+vwZu0IOPpqhEs8LwOw 3s/RZAm6o1uFJ6n/VIHTiTLbYVjYRCF/Qu0oHtJoYAl+g0mQfGZnU/AXm0pcpSox fTf2NE+bA0qo8bY/D5CIgh9TqtqoXFY3w/0uDXsWG5dGGLDWODvYO3+3GhHYx4Fv +eHAkWRCo24XBIbupqeVtpgOz/ABX9xoiV72XgQA6f9Gba+WeVPhrHBwqWNleO/T bX0lK2EUFu4q9DGNNxAK/clT7oD9JOzckx0BTTm6Go2JTggZHxk= =F05w -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Bug in synaptic package manager?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 ... > > > apt works for me it is just the dialog to modify, add or delete > > > repositories in synaptic > > > that doesn't work as some template is missing: > > > > > > aptsources.distro.NoDistroTemplateException: Error: could not find a > > > distribution template for Devuan/chimaera > > > > > > I was wondering If we couldn't add this template to synaptic itself > > > or to software-properties-gtk package. > > > > > > Ciao, > > > Tito > > > > > > > > Tito, > > It appears that there are no devuan-specific template files for > > synaptic. Attached is my first attempt (copied from Debian template, > > and modified, but I probably got some things wrong). These two files go > > in /usr/share/python-apt/templates > > Hope this helps somewhat. > > > > Temp > > Hi, > > thanks for your effort, I was not able to find where this templates were > hidden. > Seems to work here, software-properties-gtk dialog window opens without > exception. Could this somehow be added to debian or devuan? The templates live in python-apt-common (this package is not forked in Devuan). There are two options: 1) Submit a PR to the packager/team in Debian 2) Fork the package for Devuan and maintain the appropriate information in it My opinion is that 1) is not a good option, because the mirror list is volatile information and that would require stable updates on a regular basis (and that won't easily happen in Debian) Also I have noticed that this is not existing: http://security.devuan.org/ and MatchURI: is not proper in most cases (contents of Devuan.info) I can help with packaging the forked python-apt-common but I can not help with testing because I do not use aptitude. With best regards, b. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmHwc4UACgkQE2VyCRPS 8i1OXBAAsy7yMsxzXrdHJ0BKFffzKhErDpZq5A5TqKNNwhTxWg/RqBgRAWzrNQ97 XzJbsYuztcAMeSOyt0Sv0y2StzMqopjzwa9whkEEbOTS2sr0Lz76gTM84ExL7RBH 5njGNSKT8I3bLdlXFdkVbbQj0WbSB0JRY6Y4gb2Xu80jhXuN/f5TweRghyd3izPX fhVC3SETIUBp0dZ+UKGvSIIp1QXqNWCySyzF9nhHJMhuC4A5H9qf7vfHSLEvonqo 6Je452rBE/A4teGT8Q+m28d2qbziKyKE2cdFxu0xrL/94Rdu/cSDF0LLtYpEIXmk KunoIjDBMnCyhN5Xm1z5ErlXHeJOiY4CQ+57CuSEA0V9fK+rp8mw1nvicGahbzvv f8s4pPCYi4KQOTh5/hphY+b/nCl6YLLZcdpkkt0nm1EQcGMemqJmPud6b9b5uB8M SXc0Bem2O+sQIdaMeMbckrfGkU1aq1R4/CHU5H58lxB+UDP4Y8sxOe55ggGFx37t 5rhPUf3B2nGna3YzV3/+w+qc4z1bvtEz9Kds6NNTk8tckhy2y80lemRZ994LZInE UO6WkhYeP1UmeeIBKyUjuDGEZSXqF9rAgX5OuGpzOv2H3breV1uCiT/Ek2f1F3gj m0MvqOwXH0mKvgCEmS3hQmDpWNS+wnEY5f9pq6DGMesP8O3Z/pA= =Vxpy -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Accepting changed priority for chimaera-backports- what action?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, On Sun, 2022-01-23 at 20:17 +1100, terryc wrote: > So exactly what does this message mean and exactly what do I need to do. > Previously I've just repeated the command and the nag message went > away but this time it stays. > > user@system: sudo apt-get update > Get:1 http://deb.devuan.org/merged chimaera InRelease [33.9 kB] ... > Get:10 http://deb.devuan.org/merged chimaera-updates/main amd64 > Packages [2,608 B] > Get:11 http://deb.devuan.org/merged chimaera-updates/main i386 Packages > [2,612 B] > > Reading package lists... Done > E: Repository 'http://deb.devuan.org/merged chimaera-backports InRelease' > changed > its default priority for apt_preferences(5) from 500 to 100. > N: This must be accepted explicitly before updates for this repository can be > applied. See apt-secure(8) manpage for details Not long ago the priority of chimaera-backports was decreased. The problem is that with 500 apt would automatically install everything from backports and that is not a good idea at all. Ideally one would install only what they need from backports by manual selection - it is not guaranteed that installing everything from backports over stable will result in a working package combination. Generally recent apt version warn and refuse to continue without confirmation in case some data in the repos changes. E.g. if you used stable that was beowulf and you update after stable became chimaera, you would get a similar warning. The idea is to avoid users unknowingly doing major changes... > Except man apt-secure doesn't give me anything I understand. Use "sudo apt update" and confirm on the prompt (should happen only once) or see the answer from Ralph... With best regards, b. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmHt7jgACgkQE2VyCRPS 8i32WA/+Jgk5u67CkS9S97RHmoz519bZ3PKJA4TcnEu4xPzDnjcp+4uX8w/anZEv SijonFV4IeV2OKARPTOQ1RRgiBxkWqHFz9Ok881hPsbkV8gq6SjV/7u4YiIHySoR 5Tw3KXFJuhdyg481nFds4d6bb0E8w5neZYQA36kyWJ1s3ot0Ky0K2AmObdxzW5LE zWTCKSsybU8UvnfKK1hQIydUkUgvmCBMB1ljHowps9+pjHUdKmOno4Nk/so78rP4 eVRj25f5rlPFFuyPeaswxlOzfZZixYEzg0gN/+ty3T/6RjoNSSfSAEKHUr7odqIa 8LhoClNjnbLmY4LLi5GFE8YGISIqEMjucGTL3Xw+2eLSGbB3k+4J7CpSIi0soak/ p6XSNO33zhOr+pW5VvxJerKHl/V1ox6vLx1tbL4zibcKeLzC2omH2se6XlpjRteS 5GCPY55LxxpwnJJBhFdAO+QM7FqcikOgNKRRrbU18KsFwZciS8JSm8Nrcxtt9IgJ W7L1ynvlUPpwy2lZzuJx/RXfPd39inYMWEXJnCpNdyBXN3AzD0n09nBsrpmEixeC St3Dqt5mg9DQVBeXHLX3KrY2izC6kpFwKir1iSD060DE0hflbnNZ0qMZghSUgIH2 kh81dNhxr39/kclKC/7nKSr0vGNGWOB/XgF9laRax3dG3fjbTOk= =i7QT -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Conversion from BullsEye to Devuan Fails
Hello, See my answer inline below. On Tue, 2021-12-07 at 08:05 -0600, Kent West via Dng wrote: > Hi! > > Following the instructions > at > https://www.devuan.org/os/documentation/install-guides/chimaera/bullseye-to-chimaera > > I've tried it on two VirtualBox VMs (one two different Debian host boxes - a > Dell desktop and a Dell laptop). Both VMs were minimal Debian installs. > > I commented out all the lines in /etc/apt/sources.list and added the > following as the only lines in the file: > > deb http://deb.devuan.org/merged chimaera main > deb http://deb.devuan.org/merged chimaera-updates main > deb http://deb.devuan.org/merged chimaera-security main > #deb http://deb.devuan.org/merged chimaera-backports main > > Then I ran > > # apt-get update --allow-insecure-repositories > > which generated a dozen or so warnings/errors, which I assume is normal for > the process, so I ignored them. > > Then I ran > > # apt-get install devuan-keyring --allow-unauthenticated > > which generated a warning or two in the process. But the process appeared to > complete properly. > > Then I did > > # apt-get update > > which installed a few things, and appeared to complete properly. > > Then I did > > # apt-get upgrade > > which insisted I type in the phrase, "Yes, do as I say!". This generated > warnings/errors about too many errors processing systemd. > > The next step, > > # apt-get install eudev I think that adding sysvinit-core here will make it work. I will propose changing the document to include that. Also there are several conversion scripts that do the whole thing, but I haven't tested those after bullseye was released and used these instructions instead with sysvinit-core added. As a side note I never did convert a desktop system - only servers... With best regards, b. > > installed "openntpd" and then generated a warning that there is no init > system and policy-rc.d missing. > > The next step, the command to "reboot", resulted with "-bash: reboot: command > not found". Furthermore, the "shutdown" command can not be found. The only > way I could find to reboot was to do a VM reset. > > On reboot, there were messages about recovering the journal and clearing > orphaned inodes, then: > > run-init: can't execute '/sbin/init': No such file or directory > Target filesystem doesn't have requested /sbin/init. > run-init: can't execute (/sbin/init, /etc/init/, /bin/init): No such file or > directory > /bin/sh: 0: can't access tty; job control turned off > > The next step > > # apt-get dist-upgrade > > failed, partly because the file system is mounted read-only. Although I can > remount it as read-write, whatever is broken with the system is broken, and > the rest of these instructions aren't going to work. You just run into the > next problem (non-working network). This, too, can be fixed, but then you run > into another problem. Etc. > > > TL;DR - The conversion instructions don't work with Debian Bullseye 11.1, at > least not on minimal Debian VMs using VirtualBox on Debian, for me. > > I can just wipe these two VMs and start from scratch, no problem. But thought > whoever wrote that conversion page might need to know my experience. > > > ___ > Dng mailing list > Dng@lists.dyne.org > https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng signature.asc Description: This is a digitally signed message part ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Some RAID1's inaccessible after upgrade to beowulf from ascii
Hi Hendrik, On Thu, 2021-11-11 at 18:47 -0500, Hendrik Boom wrote: > On Thu, Nov 11, 2021 at 09:00:39PM +0100, tito via Dng wrote: > > On Wed, 10 Nov 2021 18:37:24 -0500 > > Hendrik Boom wrote: ..cut.. > What puzzles me is that md1 and md2 could not proceed as refective > RAID1's, where md0, which has lacked its second drive for month, was > assembled as a defective, but active, raid. Just a hint - as seen below, there is an (S) next to sda2 and sda3 - normally that means a spare, not a member in the mirroring. A spare drive contains no data and will automatically replace a failed drive, but can not be used to reconstruct the array in degraded mode. > > > > hendrik@april:/$ cat /proc/mdstat > > > > Personalities : [raid1] [linear] [multipath] [raid0] [raid6] [raid5] > > > > [raid4] [raid10] > > > > md1 : inactive sda2[3](S) > > > > 2391296000 blocks super 1.2 > > > > > > > > md2 : inactive sda3[0](S) > > > > 1048512 blocks > > > > > > > > md0 : active raid1 sdf4[1] > > > > 706337792 blocks [2/1] [_U] > > > > > > > > unused devices: > > > > hendrik@april:/$ With best regards, b. ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Chimaera upgrade broke stunnel4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi, On Wed, 2021-10-27 at 11:39 -0400, Jeremy via Dng wrote: > I upgraded to chimaera from beowulf and rebooted. > > Since, my stunnel4 services won't run. The port establishes from the client, > but then immediately closes. > stunnel4 log prints: > /usr/bin/stunnel: error while loading shared libraries: libgssapi_krb5.so.2: > failed to map segment from shared object > > Google told me to reinstall stunnel4 and libkrb5-3. I did that-- no > difference. > > I do see /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 which is a symlink to > /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 # dpkg --search /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 libgssapi-krb5-2:amd64: /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2 > Nothing else has changed. Any hints? Reinstall libgssapi-krb5-2 instead. With best regards, b. -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmF5yRAACgkQE2VyCRPS 8i33jRAAom+CDixNiky5q9/7sumPIf7LTL3ROjskYVHcd59RGODVJiVekUzmf1ee NIEHZoBCVtLCw4tlKdXPV/olz03b/xHU7OHmmGiDtscnudyCZxx1TY0lfl55rpQa KiEGuYmy1Cr14HMSa2vV+xkaAh6KqQ0ngbdFOlMtCEogVGgA1alIkjY0+FqSGG0/ B7zxLEzeqpRe7O99sn3BYfybCU9lZ3th4iNR6gewKeqwKS9cZKfB3rN6D4Ao8o/c 19Z+hgX0SFe0iC56WZtKyDHvmlGlRaSnQ+XF3Efh9FEG7WY431mJTPXVlI22/T5K u2LYLQoK3s+5h5oN/+q+pMQBTQSNsEWWT1NscXRszn0EdAA/UL5WZ1bkFBMXuMrq YfWl7gB6CFKKzJSDP+VnoOldAqCb67WdJot4sVzcfFUX65dv3/yR3ZZ8qjlg6+tl 1EaQ94b0R49z+zM80Bh10p6P+0yy8q02v5u+MCSytqiqaIdR4Rm0iJ+ZpJc1toYp JXH/oxzqBHr1DjfY9+WF3I9Z0QV3pUztYmpVtrebe3HWRqH3HvQZ+K2iM0ilOX4f aFYJDqXyxVgI0DC4ktGkYlNDsw7dUxLpt7F4KTOU1Jvru+rNPjt7ZNFP6tlrDRFc +Yja0O8n1ROYNOhIkiVn+LnSjbeau8BxTDvSIy1FgOa8Qu8VMMg= =TMG9 -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] Is it dead yet?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hi Hendrik, It is clearly saying that is a soft lockup, if it was a hardware problem it would say hard lockup isn't it? That problem really does not indicate a hardware problem, most probably a bug in the kernel; it can also show when a kernel driver is waiting for e.g. hard drive that is slow to respond. Try upgrading to a more recent kernel (e.g. 5.10.x or 5.14.x) - maybe the problem is already fixed there? It may also be a temporary condition - a very rare edge case that made the kernel lockup, then a reboot will help to clean the state... With best regards, b. On Mon, 2021-10-25 at 20:28 -0400, Hendrik Boom via Dng wrote: > I think I may have a clue to the mysterious stoppages of my server. > I ssh'd into it today and got the following. It is time to give up on this > machine and replace it? > > -- hendrik > > > hendrik@april:~$ su - > Password: > april:~# ps | grep lighttpd > ^C^C > Message from syslogd@april at Oct 25 20:15:48 ... > kernel:[ 5700.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:16:16 ... > kernel:[ 5728.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:16:52 ... > kernel:[ 5764.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 23s! > [ps:9184] > > > Message from syslogd@april at Oct 25 20:17:20 ... > kernel:[ 5792.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:17:56 ... > kernel:[ 5828.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:18:24 ... > kernel:[ 5856.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:18:56 ... > kernel:[ 5888.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:19:24 ... > kernel:[ 5916.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:20:00 ... > kernel:[ 5952.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > > Message from syslogd@april at Oct 25 20:20:28 ... > kernel:[ 5980.156005] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [ps:9184] > -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEumC8IPN+WURNbSUAE2VyCRPS8i0FAmF36qsACgkQE2VyCRPS 8i13tA//Yc6FzSg/wMjAm1am11kLHIzp31y0v+59ZGuXtHu7h1gatrYrnRAUwnRM MlaSFkiLO0HWr03db/6GaI0IJsWUWg9hNHuWlbBiQ0fZifCU8zjLLA2nU947t25d gBFshWFVqwZJ6rEBguZFZpg9AlGe/Ppslc//ONs2C3abvLzfVn/owWbH5Mx8+O6u raqVYutH7D/qD04I3JNyPQsWURjpVxES579cI1uqG+9wZ6L946YDChH6s4B8an+u QXLZZyPm4wLapSYuxjM4Es5UmtzN9QY59UtavTnrAPqNtudyuNBPtSfzHtycQsa8 H0BgxYp2IQxwFQMzAaFTehpQ/eUTqt4DEta40LLK2GZkKs21259RTXTE8LM1Aqrn T+WsBO5yg+UoxW/mzyipk7nUwzFYA1xUjYvVKyZEXsIyufrxPCvFCuPmV28XiVPu q0x0hfp7/7vxN8khMBIOeWROM6cEC8CV9wPgVhj4Y7vmHJou7tokB/XD4ugvf5U6 Ym5c+WQjXiDXVUoYMqLZNs75N5UV3AREq52mr8aPpu6FxCUDjKEywxSBpjuQu7Ch 6u5B6BxfWw8i/nXb0lAVEYpCp0xHQcqZvVBidEnle2QQ0djV0vNaNUS6vBbsa8F2 cJSIyWcmHDRkdCv1mj7ot1OpuxUmvBFbsl1sAaFWUCfwVMqqGSE= =Bbpj -END PGP SIGNATURE- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
