Troubleshooting after dist-upgrade to Buster

Help with issues regarding installation of Debian

Troubleshooting after dist-upgrade to Buster

Postby fred44nl » 2019-07-17 07:20

while running Stretch, I never really had any troubles.
now after a dist-upgrade to Buster, my machine sometimes becomes unresponsive.
I cannot say, what is showing on the screen, as my machine runs headless.
this morning, again, the only communication was with Ping.
no SSH, no RDP, no web-gui of Deluged nor Sabnzbdplus.

where do I begin to look at ??
which logfiles are most relevant ??
sudo dmesg doesn't look any different than before.

edit:
I looked at /var/log/syslog and found this:
Code: Select all
Jul 17 00:00:05 Debian systemd[1]: logrotate.service: Succeeded.
Jul 17 00:00:05 Debian systemd[1]: Started Rotate log files.
Jul 17 00:00:05 Debian systemd[1]: man-db.service: Succeeded.
Jul 17 00:00:05 Debian systemd[1]: Started Daily man-db regeneration.
Jul 17 00:14:48 Debian systemd[1]: Started Deluge Bittorrent Client Daemon.
Jul 17 00:17:01 Debian CRON[23275]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 17 01:17:01 Debian CRON[23315]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 17 02:17:01 Debian CRON[23348]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Jul 17 09:56:27 Debian systemd[1]: Starting Flush Journal to Persistent Storage...
Jul 17 09:56:27 Debian kernel: [    0.000000] Linux version 4.19.0-5-amd64 (debian-kernel@lists.debian.org) (gcc version 8.3.0 (Debian 8.3.0-7)) #1 SMP Debian 4.19.37-5 (2019-06-19)
Jul 17 09:56:27 Debian systemd[1]: Started udev Kernel Device Manager.
Jul 17 09:56:27 Debian kernel: [    0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-4.19.0-5-amd64 root=UUID=c13aae11-e70b-4c32-95d4-887063631a09 ro quiet
Jul 17 09:56:27 Debian systemd[1]: Started Flush Journal to Persistent Storage.


does this mean that nothing elase has happened after Jun 17 02:17:01 ??
Debian 10 - Buster on Compulab Fitlet2
User avatar
fred44nl
 
Posts: 203
Joined: 2018-07-14 08:54

Re: Troubleshooting after dist-upgrade to Buster

Postby ruwolf » 2019-07-17 07:44

In my opinion, it needs not to mean it. It depends on the core of problem.
Maybe syslog daemon has stopped, too or its messages were not written to disk..
User avatar
ruwolf
 
Posts: 429
Joined: 2008-02-18 05:04
Location: Slovakia, Banovce nad Bebravou, Matice slovenskej 1260/4-7

Re: Troubleshooting after dist-upgrade to Buster

Postby fred44nl » 2019-07-17 08:18

ruwolf wrote:In my opinion, it needs not to mean it. It depends on the core of problem.
Maybe syslog daemon has stopped, too or its messages were not written to disk..


thanks
should there have been something on a screen, provided it was connected ??
Debian 10 - Buster on Compulab Fitlet2
User avatar
fred44nl
 
Posts: 203
Joined: 2018-07-14 08:54

Re: Troubleshooting after dist-upgrade to Buster

Postby fred44nl » 2019-07-17 09:46

what about this, that comes from /var/log/syslog:

Code: Select all
Jul 17 12:09:28 Debian systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
Jul 17 12:09:28 Debian systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
Jul 17 12:09:29 Debian systemd[1]: Reloading.


how can I update the unit file ??

edit:
I have the same thing with xrdp
however, when I stop the service xrdp, the folder /run/xrdp disappears
but when I stop the services smbd, nmbd and samba, the folder /run/samba remains in place.
can I simply remove /run/samba and its contents ??
I assume, that it will be recreated, when I restart those service.
Debian 10 - Buster on Compulab Fitlet2
User avatar
fred44nl
 
Posts: 203
Joined: 2018-07-14 08:54

Re: Troubleshooting after dist-upgrade to Buster

Postby ruwolf » 2019-07-17 12:40

Yes, you can erase items in /run directory:
Filesystem Hierarchy Standard: /run : Run-time variable data wrote:This directory contains system information data describing the system since it was booted. Files under this directory must be cleared (removed or truncated as appropriate) at the beginning of the boot process.
User avatar
ruwolf
 
Posts: 429
Joined: 2008-02-18 05:04
Location: Slovakia, Banovce nad Bebravou, Matice slovenskej 1260/4-7

Re: Troubleshooting after dist-upgrade to Buster

Postby reinob » 2019-07-17 17:57

fred44nl wrote:what about this, that comes from /var/log/syslog:

Code: Select all
Jul 17 12:09:28 Debian systemd[1]: /lib/systemd/system/smbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/smbd.pid → /run/samba/smbd.pid; please update the unit file accordingly.
Jul 17 12:09:28 Debian systemd[1]: /lib/systemd/system/nmbd.service:9: PIDFile= references path below legacy directory /var/run/, updating /var/run/samba/nmbd.pid → /run/samba/nmbd.pid; please update the unit file accordingly.
Jul 17 12:09:29 Debian systemd[1]: Reloading.


how can I update the unit file ??

edit:
I have the same thing with xrdp
however, when I stop the service xrdp, the folder /run/xrdp disappears
but when I stop the services smbd, nmbd and samba, the folder /run/samba remains in place.
can I simply remove /run/samba and its contents ??
I assume, that it will be recreated, when I restart those service.


Just leave that alone. It's only a warning from systemd. At some point the unit files will be updated and you will not see those warnings again. Don't play with /run and /var/run, as it's not causing any real problem.
reinob
 
Posts: 899
Joined: 2014-06-30 11:42

Re: Troubleshooting after dist-upgrade to Buster

Postby fred44nl » 2019-07-17 21:15

my machine is Compulab Fitlet2

Code: Select all
inxi -F
gives the following

System: Host: Debian Kernel: 4.19.0-5-amd64 x86_64 bits: 64 Console: tty 0 Distro: Debian GNU/Linux 10 (buster)
Machine: Type: Desktop Mobo: Compulab model: fitlet2 v: 1.1 serial: <root required> UEFI: American Megatrends
v: FLT2.MBM2.0.40.01.00 date: 07/05/2018
CPU: Topology: Quad Core model: Intel Celeron J3455 bits: 64 type: MCP L2 cache: 1024 KiB
Speed: 899 MHz min/max: 800/2300 MHz Core speeds (MHz): 1: 899 2: 899 3: 899 4: 898
Graphics: Device-1: Intel driver: i915 v: kernel
Display: tty server: X.org 1.20.4 driver: intel tty: 127x40
Message: Unable to show advanced data. Required tool glxinfo missing.
Audio: Device-1: Intel Atom/Celeron/Pentium Processor N4200/N3350/E3900 Series Audio Cluster driver: snd_hda_intel
Sound Server: ALSA v: k4.19.0-5-amd64
Network: Device-1: Intel Wireless 8260 driver: N/A
Device-2: Intel I211 Gigabit Network driver: igb
IF: enp2s0 state: down mac: 00:01:c0:20:75:6d
Device-3: Intel I211 Gigabit Network driver: igb
IF-ID-1: eno1 state: up speed: 1000 Mbps duplex: full mac: 00:01:c0:20:75:6e
Drives: Local Storage: total: 990.51 GiB used: 525.41 GiB (53.0%)
ID-1: /dev/sda model: NT-64 size: 59.00 GiB
ID-2: /dev/sdb type: USB vendor: Toshiba model: MQ01UBD100 size: 931.51 GiB
Partition: ID-1: / size: 53.56 GiB used: 2.56 GiB (4.8%) fs: ext4 dev: /dev/sda2
ID-2: swap-1 size: 3.83 GiB used: 5.8 MiB (0.1%) fs: swap dev: /dev/sda3
Sensors: System Temperatures: cpu: 36.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info: Processes: 157 Uptime: 7h 54m Memory: 3.68 GiB used: 1014.5 MiB (26.9%) Init: systemd runlevel: 5 Shell: bash
inxi: 3.0.32


on the forum of Fitlet it is mentioned that I am not the only one, with problems after upgrading from Debian 9 to Debian 10
as others have experienced, the machine runs fine with Debian 9
so, is there an easy way to revert to Stretch ??
I do have an rsync-backup on my external usbhdd and my data is on this external usbhdd.
or would it best to simply reinstall Debian 9.9, from which I have downloaded the iso-file
Debian 10 - Buster on Compulab Fitlet2
User avatar
fred44nl
 
Posts: 203
Joined: 2018-07-14 08:54

Re: Troubleshooting after dist-upgrade to Buster

Postby fred44nl » 2019-07-19 07:45

yesterday I purged apparmor
and I added this parameter to /etc/default/grub: "libata.force=1.5G"
so far so good.
Debian 10 - Buster on Compulab Fitlet2
User avatar
fred44nl
 
Posts: 203
Joined: 2018-07-14 08:54


Return to Installation

Who is online

Users browsing this forum: No registered users and 9 guests

fashionable