• Content Count

  • Joined

  • Last visited

About vfrolov

  • Rank

Recent Profile Visitors

496 profile views
  1. Got it. Looks like a bug lsof | grep /var/log ...... rsyslogd 1051 syslog 7w REG 254,0 18268 29 /var/log/syslog (deleted) rsyslogd 1051 syslog 8w REG 254,0 0 26 /var/log/kern.log (deleted) rsyslogd 1051 syslog 9w REG 254,0 44234481 22 /var/log/auth.log (deleted) in:imuxso 1051 1811 syslog 7w REG 254,0 18268 29 /var/log/syslog (deleted) in:imuxso 1051 1811 syslog 8w REG 254,0 0
  2. Hello! How could it be? zram is full, but /var/log is empty. I think this happened when once the log was full and I deleted a large file. How to fix it without rebooting? ======================================================================================== root@hms:/var# uname -a Linux hms 4.19.20-sunxi #5.75 SMP Sat Feb 9 19:02:47 CET 2019 armv7l armv7l armv7l GNU/Linux root@hms:/var# zramctl NAME ALGORITHM DISKSIZE DATA COMPR TOTAL STREAMS MOUNTPOINT /dev/zram4 lzo 121,1M 4K 78B 12K 4 [SWAP] /dev/zram3 lzo
  3. all this is very encouraging. but how can a mere mortal get these sweeties
  4. today after upgrading systemd package to the version "229-4ubuntu21.15" (on 32-bit armbian) sshd and some other system services are not started again. after downgrade systemd package to version "229-4ubuntu21.11" everything is workig
  5. I Confirm. systemd 229-4ubuntu21.10 works again. Darkness Falls.
  6. could anyone confirm that mew version of SYSTEMD (229-4ubuntu21.10) works well ??
  7. thank you. please tell us, what board & OS version/release have you got
  8. have you done upgrade after fresh install? what version of systemd is installed now? apt list systemd thank you
  9. 1. Use XRDP or HDMI monitor, as well as the USB keyboard and mouse 2. launch the terminal window using the mouse, or the keyboard by pressing Control+Alt+T 3. Execute commands: sudo mkdir /var/run/sshd sudo service sshd start But the problem is much wider than what you have had encountered with
  10. hi, smuschevich. sorry for inconvenience. The basic idea is simple: return the package that worked before the updates 1. we need to find out which packages from the "SYSTEMD" family are currently installed on the computer 2. what was the previous version(s) that worked, unlike the new one 3. and finally, install packages of the correct version The first task is performed by the command: apt list | grep systemd | grep "\[" where: apt list --- gives the full list of packages of your distribution grep systemd --- selects only package
  11. motion, apache, sshd, openvpn, fail2ban, apcupsd, smbd/nmbd, screen - everything is fine
  12. did it! # apt list | grep systemd |grep "[" libpam-systemd/xenial-security,xenial-updates,xenial-security,xenial-updates,now 229-4ubuntu21.9 armhf [установлен] libsystemd0/xenial-security,xenial-updates,xenial-security,xenial-updates,now 229-4ubuntu21.9 armhf [установлен] systemd/xenial-security,xenial-updates,xenial-security,xenial-updates,now 229-4ubuntu21.9 armhf [установлен] systemd-sysv/xenial-security,xenial-updates,xenial-security,xenial-updates,now 229-4ubuntu21.9 armhf [установлен] # apt list -a systemd systemd/xenial-security,xenial-updates,xenial-