Jump to content

vfrolov

Members
  • Posts

    15
  • Joined

  • Last visited

Everything posted by vfrolov

  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 26 /var/log/kern.log (deleted) in:imuxso 1051 1811 syslog 9w REG 254,0 44234481 22 /var/log/auth.log (deleted) in:imklog 1051 1812 syslog 7w REG 254,0 18268 29 /var/log/syslog (deleted) in:imklog 1051 1812 syslog 8w REG 254,0 0 26 /var/log/kern.log (deleted) in:imklog 1051 1812 syslog 9w REG 254,0 44234481 22 /var/log/auth.log (deleted) rs:main 1051 1813 syslog 7w REG 254,0 18268 29 /var/log/syslog (deleted) rs:main 1051 1813 syslog 8w REG 254,0 0 26 /var/log/kern.log (deleted) rs:main 1051 1813 syslog 9w REG 254,0 44234481 22 /var/log/auth.log (deleted) .... Perhaps, truncating the logs not syncronizeded properly with rsyslogd ... File i removed not from this list. restarting rsyslogd service solved the problem
  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 121,1M 4K 78B 12K 4 [SWAP] /dev/zram2 lzo 121,1M 4K 78B 12K 4 [SWAP] /dev/zram1 lzo 121,1M 4K 78B 12K 4 [SWAP] /dev/zram0 50M 43,8M 7,8M 8,7M 4 /var/log root@hms:/var# df /var/log Filesystem 1K-blocks Used Available Use% Mounted on /dev/zram0 49584 44780 1220 98% /var/log root@hms:/var# du -k /var/log 12 /var/log/motion 4 /var/log/samba/cores/winbindd 4 /var/log/samba/cores/smbd 4 /var/log/samba/cores/nmbd 16 /var/log/samba/cores 28 /var/log/samba 4 /var/log/apache2 4 /var/log/apt 4 /var/log/unattended-upgrades 56 /var/log
  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 packages containing the word "systemd" in the name >>: you may use the command "apt list *systemd*" instead of apt list | grep systemd grep "\[" --- selects only packages containing special labels, for example, "[installed]" in my case the output was: 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 [установлен] [установлен] == [installed] it shows that I'm interested in 4 packages: libpam-systemd, libsystemd0, systemd, systemd-sysv, - these are all of the seme version - very good! The seccond task is performed by the command: apt list -a systemd in my case the output was: systemd/xenial-security,xenial-updates,xenial-security,xenial-updates,now 229-4ubuntu21.9 armhf [установлен] systemd/xenial,xenial 229-4ubuntu4 armhf I assumed that the previous version was "229-4ubuntu4" The third task is performed by the command: apt-get install libpam-systemd=229-4ubuntu4 libsystemd0=229-4ubuntu4 systemd=229-4ubuntu4 systemd-sysv=229-4ubuntu4 Do not forget to pray hard during the third step! Good luck :-))
  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-security,xenial-updates,now 229-4ubuntu21.9 armhf [установлен] systemd/xenial,xenial 229-4ubuntu4 armhf # apt-get install libpam-systemd=229-4ubuntu4 libsystemd0=229-4ubuntu4 systemd=229-4ubuntu4 systemd-sysv=229-4ubuntu4
  13. does anyone tried to downgrade systemd-related packages
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines