I run a Pioneer-FreedomBox-HSK behind a Router (AVM Fritzbox 7390). The Pioneer is mounted and connected to a Bay-SSD. I moved the file system to the ssd as described here.
I have to HDD’s connected to the USB-Slots, which are formatted as a RAID 1 (Also described in the post linked above).
I have installed bepasty, calibre, mindlna, radicale, samba and synthing. I also run a gitea service on the box (Outside of freedombox)
I bought / ordered it on 2021-01-06
About: You are running Debian GNU/Linux 11 (bullseye) and FreedomBox version 21.7. FreedomBox is up to date.
The system ran smoothly until a couple of days before when it upgraded to bullseye. Since than the box reboots rather randomly every other day and is not reachable anymore over the network until I unplug power and power it on again.
At the moment I have no clue where to start looking. I disabled auto-update and auto-update to next stable release but to no avail. I also had issues with the syslog service not running anymore. I reinstalled and reenabled rsyslog.service again, but I have the feeling, that it misses a lot of entries, as there are huge gaps in the timestamps.
This is intentional as single log with journald is better on SD cards instead of multiple files and copies. Please use systemd-journald instead. To see the logs, run:
$ journalctl
Various units and date ranges can be filtered, see man journalctl.
My own primary FreedomBox Olimex Pioneer hardware went to twice after the upgrade. Each time it seem to have lasted around 3 days. Logs show nothing unusual, just regular messages and then suddenly nothing until next reboot.
I have now connected a USB serial console to the machine and started it. This is a good way to debug further. If there are any kernel messages such as crashes we should be able to see them on this console. If I find anything, I will post here.
I scanned through my logs and found a number of odd/ suspicious entries:
sudo journalctl -q
# The log starts on Jul 13 with a number of records, then:
# Oddly the recorded timestamp is quite different from the next one in the log
Jul 13 17:29:42 freedombox systemd-timesyncd[350]: System clock time unset or jumped backwards, restoring from recorded timestamp: Sat 2021-08-28 04:47:02 UTC
Aug 18 02:00:52 freedombox kernel: Booting Linux on physical CPU 0x0
# pam-abl started to throw errors
Aug 18 03:39:36 freedombox pam-abl[6793]: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery (-30973) while starting transaction
Aug 18 03:39:36 freedombox pam-abl[6793]: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery (-30973) while starting the transaction to record_attempt.
# Switching dates???
Aug 18 04:18:38 freedombox sshd[8401]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=78.192.6.4
Jul 13 17:29:38 freedombox systemd-timesyncd[370]: System clock time unset or jumped backwards, restoring from recorded timestamp: Wed 2021-08-18 04:18:39 UTC
Aug 18 04:18:40 freedombox sshd[8401]: Failed password for invalid user conta from 78.192.6.4 port 46970 ssh2
# A huge time gap
Aug 18 04:39:37 freedombox sshd[9527]: Disconnected from invalid user suporte 139.59.244.237 port 43338 [preauth]
Aug 18 09:00:29 freedombox systemd-timesyncd[370]: Initial synchronization to time server 144.91.116.85:123 (0.debian.pool.ntp.org).
# last log entry
Aug 18 18:38:52 freedombox gitea-zblesk[383]: 2021/08/18 18:38:52 Completed GET /user/events 200 OK in 10.600166ms
# I repowered the system
Aug 19 16:37:21 freedombox kernel: Booting Linux on physical CPU 0x0
# last log entry
Aug 19 16:38:39 freedombox syncthing[958]: [M7FML] INFO: Ready to synchronize "Default Folder" (default) (sendreceive)
# Again, I pulled the power plug and repowered
Aug 19 17:55:08 freedombox systemd-timesyncd[372]: Initial synchronization to time server 193.141.27.1:123 (0.debian.pool.ntp.org).
# Again, same scenario
Aug 20 16:54:37 freedombox sshd[19543]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=24.166.58.59
Aug 22 16:37:12 freedombox kernel: Booting Linux on physical CPU 0x0
Aug 22 16:38:27 freedombox systemd[1]: Started Session 1 of user oliver.
# time gap
Aug 22 19:24:00 freedombox systemd-timesyncd[372]: Initial synchronization to time server 144.76.59.37:123 (0.debian.pool.ntp.org).
# An error during auto update I guess
Aug 25 07:00:50 freedombox /usr/bin/plinth[11987]: Error running setup - PackageException(error_string="Error during installation", error_details="dpkg: error: dpkg frontend lock was locked by another process with pid 11372
# last log entry
Aug 26 22:37:22 freedombox sshd[23705]: Disconnected from invalid user admin 164.90.134.223 port 52398 [preauth]
# Repowering
Aug 27 09:22:20 freedombox kernel: Booting Linux on physical CPU 0x0
# last log entry
Aug 28 04:50:18 freedombox sshd[14557]: pam_unix(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=2.181.126.23
# Repowering
Aug 28 09:44:47 freedombox systemd-timesyncd[350]: Initial synchronization to time server 176.221.42.125:123 (0.debian.pool.ntp.org).
# First occurence of many pam-abl errors of the same type. Eventually I removed the complete directory in /var/lib/abl to initialize new databases, now the errors are gone
Aug 28 09:51:26 freedombox pam-abl[2473]: Resource temporarily unavailable (11) while opening the database environment
Aug 28 09:51:26 freedombox pam-abl[2473]: Resource temporarily unavailable (11) while Creating database environment.
Aug 28 09:51:26 freedombox pam-abl[2473]: The database environment could not be opened
So far, my box is running since 3 days without noticeable problems.
I think, the Pioneer board does not have a battery backed RTC clock. So, the time might jump and when the machine gets connected to the Internet, the time is set properly using the NTP protocol by systemd-timesyncd. So, this may be okay.
This is not serious. When logging into a console, pam-abl module is run by PAM. It is used to ensure that too many failures will result in an temporary ban on the user account. Since network login attempts are protected differently, this is not serious.
Adversaries on the Internet keep trying to login via SSH by trying known usernames and guessing passwords. We have fail2ban that will impose temporary bans on these attempts when certain number of attempts fail. This is not a problem unless you have week password and have not disabled password authentication yet.
Last entry but like in my case, it does not seem serious.
This can happen if FreedomBox tries a package operation when apt is busy. This is harmless as it will try again later.
My machine too is stable. Let’s keep watching. Nice work so far.
Adversaries on the Internet keep trying to login via SSH by trying known usernames and guessing passwords. We have fail2ban that will impose temporary bans on these attempts when certain number of attempts fail. This is not a problem unless you have week password and have not disabled password authentication yet.
Meanwhile I disabled password authentication, but thank you anyway for hinting.
My FreedomBox hung today. And I saw the following on the serial console. It looks like there is not enough memory for all the services I am running on my FreedomBox (I run quite a few). I will try trimming them a bit and try again.
[218575.169685] systemd[1]: Failed to start Journal Service.
[218673.885821] systemd[1]: Failed to start Journal Service.
[218768.222955] systemd[1]: Failed to start Journal Service.
[219009.404160] systemd[1]: Failed to start Journal Service.
[219113.418769] systemd[1]: Failed to start Journal Service.
[219211.965658] systemd[1]: Failed to start Journal Service.
[219491.164682] systemd[1]: Failed to start Journal Service.
[219584.282928] systemd[1]: Failed to start Journal Service.
[282024.855801] systemd[1]: Failed to start Journal Service.
[282127.806916] systemd[1]: Failed to start Journal Service.
[282329.369764] systemd[1]: Failed to start Journal Service.
[282502.910094] INFO: task systemd:1 blocked for more than 120 seconds.
[282502.917029] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[282502.925061] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[282667.948641] systemd[1]: Failed to start Journal Service.
[282793.442973] systemd[1]: Failed to start Journal Service.
[282988.381403] systemd[1]: Failed to start Journal Service.
[283333.734162] systemd[1]: Failed to start Journal Service.
[283512.250056] systemd[1]: Failed to start Journal Service.
[283590.372255] INFO: task (php):4306 blocked for more than 120 seconds.
[283590.378988] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[283590.387025] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[283590.399213] INFO: task cron:4350 blocked for more than 120 seconds.
[283590.405705] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[283590.413735] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[283590.425760] INFO: task cron:4351 blocked for more than 120 seconds.
[283590.432236] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[283590.440253] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[283952.862894] INFO: task tar:4376 blocked for more than 120 seconds.
[283952.869390] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[283952.877461] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[284073.692893] INFO: task nscd:370 blocked for more than 120 seconds.
[284073.699414] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[284073.707433] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[284073.719503] INFO: task tar:4376 blocked for more than 241 seconds.
[284073.725854] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[284073.733841] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[284276.689264] systemd[1]: Failed to start Journal Service.
[284436.186446] INFO: task cron:4460 blocked for more than 120 seconds.
[284436.193099] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[284436.201227] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[284557.027062] INFO: task btrfs-transacti:180 blocked for more than 120 seconds.
[284557.034547] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[284557.042597] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[284557.053072] INFO: task nscd:370 blocked for more than 120 seconds.
[284557.059475] Tainted: G C E 5.10.0-8-armmp-lpae #1 Debian 5.10.46-4
[284557.067516] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
[289968.573976] Out of memory: Killed process 11040 (tmux: server) total-vm:106136kB, anon-rss:103112kB, file-rss:8kB, shmem-rss:0kB, UID:10001 pgtables:232kB oom_score_adj:0
[290159.168768] systemd[1]: Failed to start Journal Service.
You can also use zram to create a compressed part in RAM which serves as swap. I had the same problem with hard freeze when ram is full and zram help a lot.
Bepasty ,Cockpit, ejabberd, jsxc, mediawiki ,minetest,mumble, Radical,Roundcube,Syncthing, and searx
Hi I do not have much knowledge
I will uninstall ejabberd, jsxc, mediawiki ,minetest,mumble, Radical,Roundcube, and then wait and see ,these are not really in use yet
sorry right now only bepasty, share, minetest searx and syncthing running. I can not switch of JSXC and Tor
Unfortunately, also here my pioneer box became unavailable again. And I have difficulties to see what’s the reason for that. Only thing, a couple of days before I added calibre to my active services:
Bepasty, Calibre, Cockpit, Roundcube, Samba, Syncthing. And gitea, which I installed separately. Quite a short list and before the dist-upgrade everything went smoothly for months.
That’s a bit frustrating. When I am home, I may restart the box but as it just happened, I was offroad for a week and soon after leaving the box became unreachable. On Sept. 21, according to journalctl, it booted six times between 6:17 and 6:25, then, 10 min later, no more log entries until I disconnected and reconnected the power 5 days later.
I can post here only 32000 characters max, so I will split my journal log in two pieces:
Sep 21 06:09:08 freedombox systemd[1]: Starting Clean php session files...
Sep 21 06:09:10 freedombox systemd[1]: phpsessionclean.service: Succeeded.
Sep 21 06:09:10 freedombox systemd[1]: Finished Clean php session files.
Sep 21 06:09:10 freedombox systemd[1]: phpsessionclean.service: Consumed 1.664s CPU time.
Sep 21 06:11:58 freedombox sshd[9374]: Received disconnect from 222.186.42.137 port 15232:11: [preauth]
Sep 21 06:11:58 freedombox sshd[9374]: Disconnected from authenticating user root 222.186.42.137 port 15232 [preauth]
Sep 21 06:12:43 freedombox sshd[9376]: error: kex_exchange_identification: Connection closed by remote host
Sep 21 06:12:43 freedombox sshd[9376]: Connection closed by 45.133.1.12 port 56368
Sep 21 06:13:27 freedombox sshd[9377]: Unable to negotiate with 45.133.1.12 port 51544: no matching key exchange method found. Their offer: diffie-hellman-group14-sha1,diffie-hellman-group-exchange-sha1,diffie-hellman-group1-sha1 [preauth]
Sep 21 06:16:29 freedombox sshd[9381]: Received disconnect from 222.187.254.41 port 38222:11: [preauth]
Sep 21 06:16:29 freedombox sshd[9381]: Disconnected from authenticating user root 222.187.254.41 port 38222 [preauth]
Sep 21 06:17:01 freedombox CRON[9384]: pam_unix(cron:session): session opened for user root(uid=0) by (uid=0)
Sep 21 06:17:01 freedombox CRON[9386]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)
Sep 21 06:17:01 freedombox CRON[9384]: pam_unix(cron:session): session closed for user root
Sep 21 06:17:27 freedombox sshd[9389]: error: kex_exchange_identification: Connection closed by remote host
Sep 21 06:17:27 freedombox sshd[9389]: Connection closed by 209.141.62.151 port 50766
-- Boot 0e3522b11fe94868a4a257728aa27a75 --
Jul 13 17:29:37 freedombox systemd-timesyncd[351]: System clock time unset or jumped backwards, restoring from recorded timestamp: Tue 2021-09-21 06:18:47 UTC
Sep 21 06:18:58 freedombox kernel: zram: Added device: zram0
Sep 21 06:18:58 freedombox kernel: zram0: detected capacity change from 0 to 488325120
Sep 21 06:18:58 freedombox kernel: Adding 476876k swap on /dev/zram0. Priority:100 extents:1 across:476876k SSFS
Sep 21 06:18:58 freedombox kernel: sun4i-drm display-engine: [drm] Cannot find any crtc or sizes
Sep 21 06:18:58 freedombox haveged[350]: haveged: ver: 1.9.14; arch: generic; vend: ; build: (gcc 10.2.1 CTV); collect: 128K
Sep 21 06:18:58 freedombox haveged[350]: haveged: cpu: (VC); data: 16K (D); inst: 16K (D); idx: 12/40; sz: 15006/57790
Sep 21 06:18:58 freedombox haveged[350]: haveged: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.9996
Sep 21 06:18:58 freedombox haveged[350]: haveged: fills: 0, generated: 0
Sep 21 06:18:47 freedombox avahi-daemon[363]: Found user 'avahi' (UID 109) and group 'avahi' (GID 115).
Sep 21 06:18:47 freedombox systemd[1]: Started Network Time Synchronization.
Sep 21 06:18:47 freedombox avahi-daemon[363]: Successfully dropped root privileges.
-- Boot e1b9af3f877f4b06893d4429080da29d --
Sep 21 06:18:58 freedombox systemd[1]: Starting Daily apt upgrade and clean activities...
-- Boot 0e3522b11fe94868a4a257728aa27a75 --
Sep 21 06:18:47 freedombox systemd[1]: Reached target System Initialization.
Sep 21 06:18:47 freedombox avahi-daemon[363]: avahi-daemon 0.8 starting up.
Sep 21 06:18:47 freedombox systemd[1]: Started Take snapper snapshot of root on boot.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring file `/etc/passwd` (1)
Sep 21 06:18:47 freedombox systemd[1]: Started Daily Cleanup of Snapper Snapshots.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring directory `/etc` (2)
Sep 21 06:18:47 freedombox systemd[1]: Started Daily Cleanup of Temporary Directories.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring file `/etc/group` (3)
Sep 21 06:18:47 freedombox systemd[1]: Reached target System Time Set.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring directory `/etc` (2)
Sep 21 06:18:47 freedombox systemd[1]: Reached target System Time Synchronized.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring file `/etc/hosts` (4)
Sep 21 06:18:47 freedombox systemd[1]: Started Daily apt download activities.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring directory `/etc` (2)
Sep 21 06:18:47 freedombox systemd[1]: apt-daily-upgrade.timer: Not using persistent file timestamp Tue 2021-09-21 06:18:58 UTC as it is in the future.
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 cmd/web.go:82:runWeb() [I] Starting Gitea on PID: 366
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 ...dules/setting/git.go:101:newGit() [I] Git Version: 2.30.2, Wire Protocol Version 2 Enabled
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 cmd/web.go:126:runWeb() [I] Global init
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 ...dules/setting/git.go:101:newGit() [I] Git Version: 2.30.2, Wire Protocol Version 2 Enabled
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 routers/init.go:134:GlobalInit() [T] AppPath: /usr/local/bin/gitea
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 routers/init.go:135:GlobalInit() [T] AppWorkPath: /var/lib/gitea
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 routers/init.go:136:GlobalInit() [T] Custom path: /var/lib/gitea/custom
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 routers/init.go:137:GlobalInit() [T] Log path: /var/log/gitea
Sep 21 06:18:58 freedombox gitea-zblesk[366]: 2021/09/21 06:18:53 routers/init.go:49:checkRunMode() [I] Run Mode: Prod
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring file `/etc/resolv.conf` (5)
Sep 21 06:18:47 freedombox systemd[1]: Started Daily apt upgrade and clean activities.
Sep 21 06:18:47 freedombox nscd[371]: 371 monitoring directory `/etc` (2)
Sep 21 06:18:47 freedombox systemd[1]: Started Run certbot twice daily.
Sep 21 06:18:48 freedombox nscd[371]: 371 monitoring file `/etc/services` (6)
Sep 21 06:18:47 freedombox systemd[1]: Started Periodic ext4 Online Metadata Check for All Filesystems.
Sep 21 06:18:48 freedombox nscd[371]: 371 monitoring directory `/etc` (2)
Sep 21 06:18:47 freedombox systemd[1]: Started Daily exim4-base housekeeping.
Sep 21 06:18:48 freedombox nscd[371]: 371 disabled inotify-based monitoring for file `/etc/netgroup': No such file or directory
Sep 21 06:18:47 freedombox systemd[1]: Started Daily rotation of log files.
Sep 21 06:18:58 freedombox zramswap[399]: <13>Sep 21 06:18:49 root: Starting Zram
Sep 21 06:18:48 freedombox nscd[371]: 371 stat failed for file `/etc/netgroup'; will try again later: No such file or directory
Sep 21 06:18:47 freedombox systemd[1]: Started Daily man-db regeneration.
Sep 21 06:18:58 freedombox zramswap[418]: Setting up swapspace version 1, size = 465.7 MiB (488321024 bytes)
Sep 21 06:18:58 freedombox zramswap[418]: no label, UUID=828bd963-94ab-4bfb-a9cd-be150d230b72
Sep 21 06:18:49 freedombox rsyslogd[370]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd. [v8.2102.0]
Sep 21 06:18:47 freedombox systemd[1]: Started Clean PHP session files every 30 mins.
Sep 21 06:18:49 freedombox rsyslogd[370]: [origin software="rsyslogd" swVersion="8.2102.0" x-pid="370" x-info="https://www.rsyslog.com"] start
Sep 21 06:18:47 freedombox systemd[1]: Started Timeline of Snapper Snapshots.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Successfully called chroot().
Sep 21 06:18:47 freedombox systemd[1]: Listening on Avahi mDNS/DNS-SD Stack Activation Socket.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Successfully dropped remaining capabilities.
Sep 21 06:18:47 freedombox systemd[1]: Starting Cockpit Web Service Socket.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Loading service file /services/domain.service.
Sep 21 06:18:47 freedombox systemd[1]: Listening on D-Bus System Message Bus Socket.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Loading service file /services/freedombox.service.
Sep 21 06:18:47 freedombox systemd[1]: Listening on Cockpit Web Service Socket.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Loading service file /services/sftp-ssh.service.
Sep 21 06:18:47 freedombox systemd[1]: Reached target Sockets.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Loading service file /services/ssh.service.
Sep 21 06:18:47 freedombox systemd[1]: Reached target Basic System.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Loading service file /services/xmpp-server.service.
Sep 21 06:18:47 freedombox systemd[1]: Starting Avahi mDNS/DNS-SD Stack...
Sep 21 06:18:49 freedombox dbus-daemon[364]: [system] Activating systemd to hand-off: service name='org.opensuse.Snapper' unit='snapperd.service' requested by ':1.2' (uid=0 pid=372 comm="/usr/bin/snapper --config root create --cleanup-al")
Sep 21 06:18:47 freedombox systemd[1]: Started D-Bus System Message Bus.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Joining mDNS multicast group on interface lo.IPv6 with address ::1.
Sep 21 06:18:47 freedombox systemd[1]: Starting Remove Stale Online ext4 Metadata Check Snapshots...
Sep 21 06:18:49 freedombox avahi-daemon[363]: New relevant interface lo.IPv6 for mDNS.
Sep 21 06:18:47 freedombox systemd[1]: Condition check resulted in getty on tty2-tty6 if dbus and logind are not available being skipped.
Sep 21 06:18:49 freedombox avahi-daemon[363]: Joining mDNS multicast group on interface lo.IPv4 with address 127.0.0.1.
Sep 21 06:18:47 freedombox systemd[1]: Started Gitea service.
Sep 21 06:18:49 freedombox avahi-daemon[363]: New relevant interface lo.IPv4 for mDNS.
Sep 21 06:18:47 freedombox systemd[1]: Starting Name Service Cache Daemon...
Sep 21 06:18:49 freedombox avahi-daemon[363]: Network interface enumeration completed.
Sep 21 06:18:47 freedombox systemd[1]: Starting Authorization Manager...
Sep 21 06:18:49 freedombox avahi-daemon[363]: Registering new address record for ::1 on lo.*.
Sep 21 06:18:47 freedombox systemd[1]: Starting System Logging Service...
Sep 21 06:18:49 freedombox avahi-daemon[363]: Registering new address record for 127.0.0.1 on lo.IPv4.
Sep 21 06:18:47 freedombox systemd[1]: Starting Take snapper snapshot of root on boot...
Sep 21 06:18:49 freedombox polkitd[369]: started daemon version 0.105 using authority implementation `local' version `0.105'
Sep 21 06:18:49 freedombox systemd[1]: Starting User Login Management...
Sep 21 06:18:49 freedombox dbus-daemon[364]: [system] Successfully activated service 'org.freedesktop.systemd1'
Sep 21 06:18:49 freedombox systemd[1]: Starting Disk Manager...
Sep 21 06:18:49 freedombox root[399]: Starting Zram
Sep 21 06:18:49 freedombox systemd[1]: Starting WPA supplicant...
Sep 21 06:18:49 freedombox wpa_supplicant[396]: Successfully initialized wpa_supplicant
Sep 21 06:18:49 freedombox systemd[1]: Starting Linux zramswap setup...
Sep 21 06:18:50 freedombox dbus-daemon[364]: [system] Successfully activated service 'org.opensuse.Snapper'
Sep 21 06:18:49 freedombox systemd[1]: Started System Logging Service.
Sep 21 06:18:50 freedombox avahi-daemon[363]: Server startup complete. Host name is freedombox.local. Local service cookie is 2915011619.
Sep 21 06:18:49 freedombox systemd[1]: Started Name Service Cache Daemon.
Sep 21 06:18:51 freedombox avahi-daemon[363]: Service "freedombox" (/services/xmpp-server.service) successfully established.
Sep 21 06:18:49 freedombox systemd[1]: Started Avahi mDNS/DNS-SD Stack.
Sep 21 06:18:51 freedombox avahi-daemon[363]: Service "freedombox" (/services/ssh.service) successfully established.
Sep 21 06:18:49 freedombox systemd[1]: Started Authorization Manager.
Sep 21 06:18:51 freedombox avahi-daemon[363]: Service "freedombox SFTP server" (/services/sftp-ssh.service) successfully established.
Sep 21 06:18:49 freedombox systemd[1]: Starting Modem Manager...
Sep 21 06:18:51 freedombox avahi-daemon[363]: Service "freedombox" (/services/freedombox.service) successfully established.
Sep 21 06:18:49 freedombox systemd[1]: Starting firewalld - dynamic firewall daemon...
Sep 21 06:18:51 freedombox avahi-daemon[363]: Service "freedombox" (/services/domain.service) successfully established.
Sep 21 06:18:49 freedombox systemd[1]: Starting DBus interface for snapper...
Sep 21 06:18:51 freedombox ModemManager[401]: <info> ModemManager (version 1.14.12) starting in system bus...
Sep 21 06:18:49 freedombox systemd[1]: Started WPA supplicant.
Sep 21 06:18:55 freedombox ModemManager[401]: <info> [base-manager] couldn't check support for device '/sys/devices/platform/soc/1c50000.ethernet': not supported by any plugin
Sep 21 06:18:49 freedombox udisksd[395]: udisks daemon version 2.9.2 starting
Sep 21 06:18:50 freedombox systemd[1]: Started DBus interface for snapper.
Sep 21 06:18:50 freedombox systemd[1]: Finished Linux zramswap setup.
Sep 21 06:18:51 freedombox systemd-logind[391]: New seat seat0.
Sep 21 06:18:51 freedombox systemd-logind[391]: Watching system buttons on /dev/input/event0 (axp20x-pek)
Sep 21 06:18:51 freedombox systemd[1]: Started User Login Management.
Sep 21 06:18:52 freedombox systemd[1]: Started Modem Manager.
Sep 21 06:18:52 freedombox udisksd[395]: Error performing housekeeping for drive /org/freedesktop/UDisks2/drives/Hitachi_HDS721010CLA330_JP2911N1068PRV: Error updating SMART data: sk_disk_smart_read_data: Operation not supported (udisks-error-quark, 0)
Sep 21 06:18:52 freedombox systemd[1]: Started Disk Manager.
Sep 21 06:18:52 freedombox udisksd[395]: Cleaning up mount point /media/root/Nas (device 8:16 is not mounted)
Sep 21 06:18:52 freedombox udisksd[395]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Sep 21 06:18:53 freedombox systemd[1]: e2scrub_reap.service: Succeeded.
Sep 21 06:18:53 freedombox systemd[1]: Finished Remove Stale Online ext4 Metadata Check Snapshots.
Sep 21 06:18:58 freedombox systemd[1]: snapper-boot.service: Succeeded.
Sep 21 06:18:58 freedombox systemd[1]: Finished Take snapper snapshot of root on boot.
Sep 21 06:19:00 freedombox kernel: vcc3v0: disabling
Sep 21 06:19:00 freedombox kernel: vcc5v0: disabling
Sep 21 06:19:00 freedombox kernel: usb0-vbus: disabling
Sep 21 06:19:00 freedombox kernel: vddio-csi0: disabling
Sep 21 06:19:00 freedombox kernel: vddio-csi1: disabling
Sep 21 06:19:02 freedombox systemd[1]: Started firewalld - dynamic firewall daemon.
Sep 21 06:19:02 freedombox systemd[1]: Reached target Network (Pre).
Sep 21 06:19:02 freedombox systemd[1]: Starting Network Manager...
Sep 21 06:19:02 freedombox systemd[1]: Starting Raise network interfaces...
-- Boot e1b9af3f877f4b06893d4429080da29d --
Sep 21 06:19:03 freedombox systemd[1]: apt-daily-upgrade.service: Succeeded.
Sep 21 06:19:03 freedombox systemd[1]: Finished Daily apt upgrade and clean activities.
Sep 21 06:19:03 freedombox systemd[1]: apt-daily-upgrade.service: Consumed 3.975s CPU time.
In all of the hangs so far, we haven’t seen any sign of something wrong with kernel (in the form panic message notices on the console) or with applications (except for out-of-memory on two occasions). This leads me to believe this could be kernel+hardware related.
2 days ago, I installed the matrix synapse chat server.
Today, my system booted 4 times (according to journalctl --boot … – comments) from 12:19 'til 12:28 for no apparent reasons, than half an hour later no more entries in journal until I repowered the box at around 18:00
Again, no conspicuous messages …
So my feeling is, the less services, the more stable the system runs, which makes it quite useless
It’s not the case. I tried with only Matrix and WireGuard running, and it’s the same. Hanging every second day. It’s very frustrating. I can’t believe that there is no solution for that problem yet. After all, that’s the pioneer edition, it’s kind a symbol of the system, and it’s not working. I think I waited enough for some solution. I’m wandering to go back to previous actually stable release (buster) or to get another hardware (e.g. Raspberry Pi)…or just go to another server OS (e.g. OMV).
after 7 days