[DNG] Upgrade from buster to beowulf, runlevels are goofed
Hi Now I upgraded my other notebook from buster to beowulf. No more debian systems chez moi. I followed the advice from the website. However, the upgrades of the notebooks were not smooth. On the 2nd NB when I started the system after the dist-upgrade, it went straight into the Xserver. Only the xserver keyboard driver was lost in the process of upgrading. Only the power button on the NB could save, no, delete the situation. After changing /etc/rc2.d/S04lightdm to /etc/rc2.d/_S04lightdm I could safely boot and do the missing work. In the times of SuSE 7.0 to 7.3 I used runlevels to control a server with attached thin clients. The users on the system got a wall message and had to save their work. After a few minutes the runlevel was reduced from 5 to 3. This stopped the x client on the server, while maintaining the network connection. A backup was made, and when finished, the runlevel was increased to 5 and the thin clients (with a blank screen) obtained their login screen automagically again. It was extremely simple to accomplish. Since the times of SuSE7.3, after with I switched to debian in 2003, I did not observe the sysvinit/runlevels, there was no need to, until I obtained the systemd message: A service required was not available at start. Now I find that the runlevels are identical from 2 to 5 as opposed to the old times, when they were substantially differentiated. (root only, +local multi-user, +network, +Xserver) Is this a heritage of the debian distribution crippled by the poeystemd? Can I obtain a devuan different more clever system with update-rc.d ? https://debianforum.de/forum/viewtopic.php?t=173006 https://de.wikipedia.org/wiki/Runlevel#Beispiel_Linux https://en.wikipedia.org/wiki/Runlevel#Linux_Standard_Base_specification devuan (beowulf standard installation with some cruft maybe) as I have it on my notebooks does not conform to the LSB. Before filing a bug, I ask for the opinion here in the forum. -- mit freundlichen Grüßen with the beste regards cordialement Erich |\/|inderlei|\| -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] unsigned kernels - strange behaviour
Hi
tonight my ansible stopped execution with the message
TASK [Reboot the box if kernel updated]
fatal: [*$Hostname*]: FAILED! => {"changed": false, "elapsed": 0, "msg": "Running reboot with
local connection would reboot the control node.", "rebooted": false}
Now there are no new kernels to install, because the system is up to date.
Last kernel install was Feb 7 06:49
/ ls -tlah vmlinuz*
lrwxrwxrwx 1 root root 28 Feb 7 06:49 vmlinuz -> boot/vmlinuz-4.19.0-14-amd64
lrwxrwxrwx 1 root root 28 Feb 7 06:49 vmlinuz.old ->
boot/vmlinuz-4.19.0-13-amd64
/boot # ls -tlah vmlinuz*
-rw-r--r-- 1 root root 5.1M Jan 30 10:35 vmlinuz-4.19.0-14-amd64
-rw-r--r-- 1 root root 5.1M Nov 28 08:47 vmlinuz-4.19.0-13-amd64
looking at the kernels I find this
dpkg -l 'linux-image-*-unsigned'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++----=
un linux-image-4.19.0-13-amd64-unsigned (no
description available)
un linux-image-4.19.0-14-amd64-unsigned (no
description available)
aptitude shows
Actions Undo Package Resolver Search Options Views Help
C-T: Menu ?: Help q: Quit u: Update g: Preview/Download/Install/Remove Pkgs
aptitude 0.8.11 @ hostname
--\ Not Installed Packages (7)
...
--\ kernel Kernel and kernel modules (6)
--\ main The main Debian archive (6)
p linux-image-4.19.0-13-amd64-unsigned
4.19.160-2
p linux-image-4.19.0-13-cloud-amd64-unsigned
4.19.160-2
p linux-image-4.19.0-13-rt-amd64-unsigned
4.19.160-2
p linux-image-4.19.0-14-amd64-unsigned
4.19.171-2
p linux-image-4.19.0-14-cloud-amd64-unsigned
4.19.171-2
p linux-image-4.19.0-14-rt-amd64-unsigned
4.19.171-2
┌─┐
│Really quit
Aptitude?│
│ [ Yes ][ No ]
│
└─┘
These packages are not installed on your computer.
This group contains 7 packages.
What are these unsigned packages for ?
Why does the system want install some unknown kernels as the actual signed
package is already installed ?
Three month ago I had a strange collapse of my debian,
as the directory /usr was empty over night.
System was unusable and I made a fresh install of devuan instad of debian.
I planned this anyhow.
Is there something spooky going on ?
Is something compromised on this system ?
--
mit freundlichen Grüßen
with the best(e) regards
cordialement
Erich |\/|inderlei|\|
___
Dng mailing list
Dng@lists.dyne.org
https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] /etc/debian_version
Hi all currently I operate one server with devuan beowulf and 2 Notebooks with debian buster. Migration is pending to devuan, as soon as a necessity arises, e.g. buster is becoming oldstable. Off Topic : the necessity has arisen now, as systemd produces huge logfiles, 0,9 GByte in 10 hours worth of log, thens hold only last 10 hours due to space limitations (keeps 10% free). These json-logs are a mess, except for illiterates. I Noted that /etc/debian_version on the debian driven notebooks is at 10.7 , but on the devuan server it is still at 10.0 There are a number of files which contain info about the actual status of the installation but the info in debian-basefiles, is misleading, as the system is uptodate otherwise. Debian : lsb_release -a Distributor ID: Debian Description:Debian GNU/Linux 10 (buster) Release:10 Codename: buster cat /etc/debian_version 10.7 aptitude show base-files Package: base-files Version: 10.3+deb10u7 Essential: yes State: installed ... Description: Debian base system miscellaneous files ... devuan : lsb_release -a No LSB modules are available. Distributor ID: Debian Description:Devuan GNU/Linux 3 (beowulf) Release:3 Codename: beowulf cat /etc/debian_version 10.0 While the system is up to date, debian_version is misleading. This is more a bug than a feature. It takes some digging to see that. The referencing to debian is not consistent. Better the file /etc/debian_version is missing @devuan than it is wrong. Change log for base-files package in Debian base-files (10.3+deb10u7) buster; urgency=medium * Change /etc/debian_version to 10.7, for Debian 10.7 point release. -- Santiago Vila Sun, 22 Nov 2020 13:37:00 +0100 base-files (10.3+deb10u6) buster; urgency=medium * Change /etc/debian_version to 10.6, for Debian 10.6 point release. -- Santiago Vila Sat, 19 Sep 2020 23:39:00 +0200 Change log for base-files package in Devuan Änderungen #21 (20.04.2020 16:24:04) Release beowulf: remove ceres from /etc/devuan_version. — leepen / detail d/control: add myself to uploaders. — leepen / detail Changelog for version 10.3+devuan3.4. — leepen / detail #20 (28.03.2020 13:43:48) Revert to ID=devuan in /etc/os-release (Closes: #411). — leepen / detail Changelog for version 11+devuan2. — leepen / detail #19 (23.02.2020 15:22:12) Add Debian as parent in origins/devuan. — parazyd / detail -- mit freundlichen Grüßen with the beste regards cordialement Erich |\/|inderlei|\| -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] monit logwatch fail2ban
Hi after the purge - install of fail2ban and logwatch yesterday logwatch reported today that fail2ban made a new database for the activities. So reportung works again ootb. Thank you for mental sparring -- mit freundlichen Grüßen with the beste regards cordialement Erich |\/|inderlei|\| ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
Re: [DNG] monit logwatch fail2ban
Hi all Hi Ludovic I found that monit is a backports package, not in standard install both for debian and devuan a case of PEBKAC Thanks Dimitris the command line logwatch yields a more detailed output than the cron.daily I did that now purging + reinstalling both logwatch and fail2ban added nextcloud.conf entries again were they were. reversed changed cron.daily/00_logwatch diff /var/backups/rsnapshot/alpha.0/localhost/etc/cron.daily/00logwatch /etc/cron.daily/00logwatch 5a6,8 # clean up rm -rf /tmp/logwatch.* 7c10 < /usr/sbin/logwatch --output mail --- /usr/sbin/logwatch --mailto erich.minderl...@posteo.de right side ist active now. lets see, what tomorrows cronjob will show Thanks everybody Am 26.01.21 um 06:24 schrieb dng-requ...@lists.dyne.org: Send Dng mailing list submissions to Today's Topics: 1. Re: AppArmor and TorBrowser (Dimitris) 2. Re: monit logwatch fail2ban (Dimitris) 3. Re: Request for assistance (o1bigtenor) 4. Re: Request for assistance (o1bigtenor) 5. Re: Request for assistance (Ralph Ronnquist) 6. librewolf (Simon Walter) -- Message: 2 ... i don't use monit, just fail2ban and logwatch in some machines. never had any issues with it.. neither in debian nor devuan machines . usually set it up and forget about it.. still works though.. check that `Service = All` and also what service exclusions exist in either /etc/logwatch/logwatch.conf or /usr/share/logwatch/default.conf/logwatch.conf could also run manually, to check, eg : # logwatch --detail Med --range Yesterday --mailto your@email i'm guessing fail2ban is installed ok ( :D) if nothing works, maybe purging + reinstalling logwatch could help.. 2c, -- End of Dng Digest, Vol 76, Issue 23 *** -- mit freundlichen Grüßen with the beste regards cordialement Erich |\/|inderlei|\| -- -Stuttgart 21- : Ein weiterer Schritt zur Erhöhung der CO2 Emissionen Mit 5 bis 10 MRD € wird der öffentliche Nahverkehr in Baden-Württemberg halbiert. Die Deutsche Bahn "erhöht" die Abfertigungskapazität von jetzt 800 auf dann maximal 430 Züge pro Tag und mischt Verkehre verschiedener Geschwindigkeit auf den gleichen Gleisen. der S21 Krimi: geht nur alles schief, was vorhergesagt wurde, oder noch mehr ? Update : mindestens alles geht schief https://www.golem.de/1103/81972.html https://fahrradzukunft.de/25/motorisierte-gewalt/ 2022 feiern wir 100 Jahre Kopfbahnhof Stuttgart !! Ich freue mich drauf ! - Friedrichstrasse 30 77948 Friesenheim (Baden) Tel +49 (0) 7821 328 99 47 Mob +49 (0) 176 54 33 94 01 ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
[DNG] monit logwatch fail2ban
Hi I have migrated a small home server from debian buster to devuan beowulf. It was a new install, but I compared/copied /etc and copied the server /var/www It was rather flawless. However before the package monit was used as intermediate function beween fail2ban and logwatch. This is not part of the devuan packages. Now I miss the section fail2ban in the logwatch daily mail Is there an adapted solution to this ? -- mit freundlichen Grüßen with the beste regards cordialement Erich |\/|inderlei|\| -- ___ Dng mailing list Dng@lists.dyne.org https://mailinglists.dyne.org/cgi-bin/mailman/listinfo/dng
