Posts by prtigger1

Hi Pro's

Just a short question, because i don't remember it anymore:

I created a Btrfs Raid1 with the GUI

over my 3 identical SSDs. With which default parameters will it be created?

Is it Raid1c3 for data and metadata?

Best regards

prtigger

That's tough...

Because i can't confirm a general problem with Samba on OMV 7...

But i'm speaking only for my old hardware..

Ok, thanks..

I'll keeping my eyes on!

What i still not understand is:

What is running parallel when logrotate.service tries to startup during the first boot (reading the log i posted, status is locked)?

And why is everything fine when i shutdown the system after this and boot again??

Why should a start of logrotate.service every boot help (just more compressed files)?

Best regards

prtigger

Hi

Do you set SMB3 as minimal protocol?

That's what i set...

Best regards

prtigger

I just checked the whole output of

journalctl (3500 lines). There are no errors or warnings i had never seen before, after boot.

Only the part i described here in this case.

May be a stupid question:

What about the logs outside of the journal?

What is happening with them?

Thanks for your help

prtigger

It´s not long ago i done the commands from #6

Here the output:

root@pr-srv-01:~# du -h /var/log/journal/
142M    /var/log/journal/21bdaa7233734a9491a6b4852adf96b0
142M    /var/log/journal/
root@pr-srv-01:~# ls -ahlS /var/log
insgesamt 168K
-rw-r--r--   1 root     root            8,2K 20. Mär 16:57 dpkg.log.12.gz
drwxr-xr-x  13 root     root            4,0K 20. Mär 16:57 ..
-rw-r--r--   1 root     root            3,2K 20. Mär 17:57 dpkg.log.10.gz
-rw-rw-r--   1 root     utmp            1,5K 21. Apr 08:35 wtmp
drwxr-xr-x  14 root     root            1,3K 21. Apr 08:15 .
-rw-r--r--   1 root     root            1,2K 20. Apr 17:46 dpkg.log.1
drwxr-xr-x   2 root     root             580 20. Apr 17:49 apt
drwxr-x---   3 root     adm              540 21. Apr 08:13 samba
drwxr-xr-x   2 root     adm              520 21. Apr 08:13 nginx
-rw-r--r--   1 root     root             429 31. Mär 20:12 dpkg.log.9.gz
-rw-r--r--   1 root     root             385 13. Apr 17:57 dpkg.log.5.gz
-rw-r--r--   1 root     root             367 20. Mär 17:14 dpkg.log.11.gz
-rw-r--r--   1 root     root             367  5. Apr 07:55 dpkg.log.7.gz
drwxr-x---   2 root     adm              340 21. Apr 08:15 unattended-upgrades
-rw-r--r--   1 root     root             336  1. Apr 18:19 dpkg.log.8.gz
-rw-rw-r--   1 root     utmp             292 21. Apr 08:35 lastlog
-rw-r--r--   1 root     root             290  6. Apr 18:11 dpkg.log.6.gz
-rw-r--r--   1 root     root             273 14. Apr 20:24 dpkg.log.2.gz
-rw-r--r--   1 root     root             250 13. Apr 18:22 dpkg.log.3.gz
-rw-r--r--   1 root     root             249 13. Apr 18:17 dpkg.log.4.gz
-rw-r--r--   1 root     root             208 21. Apr 08:15 alternatives.log.1
drwxr-xr-x   3 root     root             180 17. Mär 21:09 installer
-rw-------   1 root     root             140 21. Apr 08:15 php8.2-fpm.log.6.gz
-rw-r--r--   1 root     root             138 14. Apr 21:08 alternatives.log.11.gz
-rw-r--r--   1 root     root             138 21. Apr 08:03 alternatives.log.2.gz
-rw-r--r--   1 root     root             138 20. Apr 17:50 alternatives.log.3.gz
-rw-r--r--   1 root     root             138 20. Apr 17:45 alternatives.log.4.gz
-rw-r--r--   1 root     root             138 18. Apr 16:32 alternatives.log.5.gz
-rw-r--r--   1 root     root             138 18. Apr 16:21 alternatives.log.6.gz
-rw-r--r--   1 root     root             138 17. Apr 07:23 alternatives.log.7.gz
-rw-r--r--   1 root     root             138 16. Apr 21:09 alternatives.log.8.gz
-rw-r--r--   1 root     root             138 16. Apr 21:01 alternatives.log.9.gz
-rw-r--r--   1 root     root             136 16. Apr 20:36 alternatives.log.10.gz
-rw-r--r--   1 root     root             135 14. Apr 20:48 alternatives.log.12.gz
-rw-------   1 root     root             117 21. Apr 08:13 php8.2-fpm.log.7.gz
drwxr-xr-x   2 minidlna minidlna          80 20. Mär 17:58 minidlna
-rw-------   1 root     root              76 21. Apr 08:03 php8.2-fpm.log.10.gz
-rw-------   1 root     root              76 21. Apr 08:03 php8.2-fpm.log.11.gz
-rw-------   1 root     root              76 21. Apr 08:03 php8.2-fpm.log.12.gz
-rw-------   1 root     root              76 21. Apr 08:15 php8.2-fpm.log.2.gz
-rw-------   1 root     root              76 21. Apr 08:15 php8.2-fpm.log.3.gz
-rw-------   1 root     root              76 21. Apr 08:15 php8.2-fpm.log.4.gz
-rw-------   1 root     root              76 21. Apr 08:15 php8.2-fpm.log.5.gz
-rw-------   1 root     root              76 21. Apr 08:03 php8.2-fpm.log.8.gz
-rw-------   1 root     root              76 21. Apr 08:03 php8.2-fpm.log.9.gz
drwxr-sr-x+  3 root     systemd-journal   60 17. Mär 21:11 journal
drwxr-xr-x   3 root     root              60 17. Mär 20:57 runit
drwxr-xr-x   2 root     root              60 17. Mär 20:57 salt
-rw-------   1 root     root              56 21. Apr 08:15 php8.2-fpm.log
-rw-------   1 root     root              56 21. Apr 08:15 php8.2-fpm.log.1
drwxr-x---   2 _chrony  _chrony           40 17. Mär 21:11 chrony
drwxr-xr-x   2 root     root              40 16. Dez 09:36 openmediavault
drwx------   2 root     root              40 23. Dez 14:38 private
lrwxrwxrwx   1 root     root              39 17. Mär 20:57 README -> ../../usr/share/doc/systemd/README.logs
-rw-r--r--   1 root     root               0 21. Apr 08:15 alternatives.log
-rw-r--r--   1 root     root               0 23. Dez 14:38 bootstrap.log
-rw-rw----   1 root     utmp               0 21. Apr 08:15 btmp
-rw-rw----   1 root     utmp               0 21. Apr 08:15 btmp.1
-rw-r--r--   1 root     root               0 20. Apr 17:49 dpkg.log
-rw-r--r--   1 root     root               0 23. Dez 14:38 faillog
-rw-r--r--   1 root     root               0 23. Dez 14:38 fontconfig.log
-rw-r-----   1 root     adm                0 23. Dez 14:38 monit.log
-rw-r--r--   1 root     root               0 23. Dez 14:38 tallylog
-rw-rw-r--   1 root     utmp               0 21. Apr 08:15 wtmp.1
root@pr-srv-01:~#

Hi macom

I'm not a pro... The only thing i know is, that all the logs like messages, syslog.. are concentrated in the journal, like a database... I want to cleanup this because

it's getting bigger and bigger....

You can correct me if i'm wrong.. My Linux knowledge is really old from 1991-1995 with kernel 0.99... I have to learn a lot of the actual stuff...

Best regards

prtigger

For me it's looking like a timing problem during boot...???

Quote from macom

Seems you just have to wait for the next time that logrotate is executed. As you don't run your server 24/7 you might add a scheduled job that runs at reboot and add this as command:

sleep 60 && systemctl start logrotate.service

Hi macom

I'm wondering about this, because i think this bootup fail is new with the reinstall of OMV.

Do you have a small explanation how to create such a job?

Quote from macom

Be aware that this clears up the journal, but it does not rotate the *.log files.

Is there any better way or command to get rid of all the old journal files?

Thanks for your help and best regards

prtigger

Quote from macom

How do you shutdown the server?

Hi macom

Shutdown:

'shutdown' at console or with putty... After that logout with <strg>-d... And wait for power-off...

Startup:

I switch on the power-distribution where the server power cord is plugged in....

Waiting till network light is beginning to flash (Mainboard has power good signal)...

Press power on button at the server...

Nothing special! My system is only running when i need it. The other time it is power free...

Here the actual output:

root@pr-srv-01:~# systemctl start logrotate.service

root@pr-srv-01:~# systemctl status logrotate.service

○ logrotate.service - Rotate log files

Loaded: loaded (/lib/systemd/system/logrotate.service; static)

Active: inactive (dead) since Mon 2025-04-21 11:56:09 CEST; 14s ago

TriggeredBy: ● logrotate.timer

Docs: man:logrotate(8)

man:logrotate.conf(5)

Process: 3296 ExecStart=/usr/sbin/logrotate /etc/logrotate.conf (code=exited, status=0/SUCCESS)

Main PID: 3296 (code=exited, status=0/SUCCESS)

CPU: 301ms

Apr 21 11:56:09 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

Apr 21 11:56:09 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.

Apr 21 11:56:09 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.

root@pr-srv-01:~# journalctl -u logrotate.service

Apr 21 08:03:41 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

Apr 21 08:03:42 pr-srv-01 logrotate[759]: error: state file /var/lib/logrotate/status is already locked

Apr 21 08:03:42 pr-srv-01 logrotate[759]: logrotate does not support parallel execution on the same set of logfiles.

Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

Apr 21 08:03:42 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

-- Boot 751038e34e674b07a474e75dab3bb80d --

Apr 21 11:56:09 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

Apr 21 11:56:09 pr-srv-01 systemd[1]: logrotate.service: Deactivated successfully.

Apr 21 11:56:09 pr-srv-01 systemd[1]: Finished logrotate.service - Rotate log files.

root@pr-srv-01:~#

Best regards

prtigger

Buy the way:

I can clear up journal with:

sudo journalctl --flush --rotate --vacuum-time=30s

sudo journalctl --user --flush --rotate --vacuum-time=30s

This may help for a while...

macom

Good morning

Just power up my server (Hanging on switchable powerplug! Over night system is powerfree)... The same problem:

root@pr-srv-01:~# journalctl -u logrotate.service

Apr 21 08:03:41 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

Apr 21 08:03:42 pr-srv-01 logrotate[759]: error: state file /var/lib/logrotate/status is already locked

Apr 21 08:03:42 pr-srv-01 logrotate[759]: logrotate does not support parallel execution on the same set of logfiles.

Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

Apr 21 08:03:42 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

Apr 21 08:03:42 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

root@pr-srv-01:~#

Shutdown system.., start again:

No failure again...

OMV is uptodate!

Best regards

prtigger

By the way...

If Windows is working, the problem is the FX File commander... But you can try another kernel (6.11. Proxmox or the stable Debian 6.1.133-1).. Or you try to change the filesystem... Or you try to install a backported samba, but i don't know how to configure a samba bpo...

Best regards

prtigger

In addition:

Just a cold power on of my system!

macom

Here it is:

root@pr-srv-01:~# journalctl -u logrotate.service

Apr 20 17:45:31 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

Apr 20 17:45:32 pr-srv-01 logrotate[807]: error: state file /var/lib/logrotate/status is already locked

Apr 20 17:45:32 pr-srv-01 logrotate[807]: logrotate does not support parallel execution on the same set of logfiles.

Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

Apr 20 17:45:32 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

root@pr-srv-01:~#

Best regards

prtigger

Hi

I can´t say anything to mergerFS... Hopefully ryecoaaron has an idea what can help you with your problem!

He is using mergerFS, too.

Best regards

prtigger

Hi professionals

Powering up my system is bring back a logrotate.service error... (Not the first time)...

No idea for any reason... shutting down and booting up again... Everything is fine...

....

Apr 20 17:45:31 pr-srv-01 anacron[798]: Anacron 2.3 started on 2025-04-20

Apr 20 17:45:31 pr-srv-01 systemd[1]: Started cpufrequtils.service - LSB: set CPUFreq kernel parameters.

Apr 20 17:45:31 pr-srv-01 systemd[1]: Started php8.2-fpm.service - The PHP 8.2 FastCGI Process Manager.

Apr 20 17:45:31 pr-srv-01 anacron[798]: Will run job `cron.daily' in 5 min.

Apr 20 17:45:31 pr-srv-01 anacron[798]: Jobs will be executed sequentially

Apr 20 17:45:31 pr-srv-01 systemd[1]: Starting phpsessionclean.service - Clean php session files...

Apr 20 17:45:31 pr-srv-01 systemd[1]: Starting logrotate.service - Rotate log files...

Apr 20 17:45:31 pr-srv-01 folder2ram[441]: start /var/spool

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 111.6M, max >

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 8.0M of archived journals from /var/log/journal/21bdaa723373>

Apr 20 17:45:32 pr-srv-01 logrotate[807]: error: state file /var/lib/logrotate/status is already locked

Apr 20 17:45:32 pr-srv-01 logrotate[807]: logrotate does not support parallel execution on the same set of logfiles.

Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Main process exited, code=exited, status=3/NOTIMPLEMENTED

Apr 20 17:45:32 pr-srv-01 systemd[1]: logrotate.service: Failed with result 'exit-code'.

Apr 20 17:45:32 pr-srv-01 systemd[1]: Failed to start logrotate.service - Rotate log files.

Apr 20 17:45:32 pr-srv-01 folder2ram[441]: start /var/lib/rrdcached

Apr 20 17:45:32 pr-srv-01 systemd[1]: eth-network-optimization.service: Deactivated successfully.

Apr 20 17:45:32 pr-srv-01 systemd[1]: Finished eth-network-optimization.service - Set enp2s0+enp3s0 network optimizations.

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 109.4M, max >

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 3.5M of archived journals from /var/log/journal/21bdaa723373>

Apr 20 17:45:32 pr-srv-01 systemd[1]: phpsessionclean.service: Deactivated successfully.

Apr 20 17:45:32 pr-srv-01 systemd[1]: Finished phpsessionclean.service - Clean php session files.

Apr 20 17:45:32 pr-srv-01 folder2ram[441]: start /var/lib/monit

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 105.0M, max >

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 7.1M of archived journals from /var/log/journal/21bdaa723373>

Apr 20 17:45:32 pr-srv-01 folder2ram[441]: start /var/cache/samba

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: System Journal (/var/log/journal/21bdaa7233734a9491a6b4852adf96b0) is 101.4M, max >

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Received client request to rotate journal, rotating.

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Deleted archived journal /var/log/journal/21bdaa7233734a9491a6b4852adf96b0/system@>

Apr 20 17:45:32 pr-srv-01 systemd-journald[303]: Vacuuming done, freed 3.5M of archived journals from /var/log/journal/21bdaa723373>

Apr 20 17:45:33 pr-srv-01 systemd-networkd[334]: enp2s0: Gained carrier

Apr 20 17:45:33 pr-srv-01 kernel: e1000e 0000:02:00.0 enp2s0: NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None

...

Any suggestions?

Best regards

prtigger

Hi

OMV is installing official Debian backport kernel, by default. This may be different to Ubuntu and TrueNAS kernel compilations, with different libraries and kernel components...

Available official development on kernel versions can be found here:

The Linux Kernel Archives

Best regards

prtigger

Hi

You may find the answer here:

Thread

Get rid of all backports that are installed?

Hi folks
I´ve got a clean install of OMV with default backports enabled... With stable 6.1.x kernel and backport kernel...
Is there an easy way to uninstall all packages installed from backport repository, to get back to pure stable Debian basis?
Or must i do a new installation again and disable backports before i´m doing omv-upgrade the first time?

Thanks for suggestions
and best regards
prtigger

prtigger1

Apr 13th 2025

Best regards

prtigger