Missing syslog in 7.3.0-5

    Quote from ryecoaaron

    There are other ways to set journalctl settings other than what is in that one file. I recommend using chatgpt to figure out why it is doing this. It would take me too much back and forth. And patience.

    I've tried from the beginning asking chatgpt

    it is suggesting problem is related to flash memory plugin (forlder2ram -syncall script) because of this script is always procees before rotation is done:

    • Official Post
    Quote from wojciszpl

    it is suggesting problem is related to flash memory plugin (forlder2ram -syncall script) because of this script is always procees before rotation is done:

    Do you turn your system off on a schedule or multiple times a day? The folder2ram script does rotate the systemd logs when it is run to avoid losing the logs. The script is run on every shutdown.

    omv 7.5.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.3.2 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    No, system is uptime for many days.

    But I found somewhere in this forum years ago suggestion to make -syncall command via cron every few hours, just for safe - is this not a good idea? is this can have influence on this problem?

    • Official Post
    Quote from wojciszpl

    But I found somewhere in this forum years ago suggestion to make -syncall command via cron every few hours, just for safe - is this not a good idea? is this can have influence on this problem?

    For people who don't want to lose their logs and don't have reliable power, I have suggested scheduling the syncall command. This command is still safe but it will rotate the logs which will make the logs not visible in the OMV log viewer.

    omv 7.5.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.3.2 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    • Official Post
    Quote from wojciszpl

    so this is the reason of my problem?

    Maybe.

    Quote from wojciszpl

    with this plugin each sync will rotate logs and make it invisible in gui?

    For syslog, yes. For other logs, it will depend on their logrotate config. https://github.com/bobafetthot…kage/sbin/folder2ram#L628


    Quote from wojciszpl

    So it means also that with this plugin all logs will disappear after each reboot?

    Not necessarily. See above. If you have a better way to protect media from excessive writes and not lose logs (not referring to the log viewer), I would be interested.

    omv 7.5.0-1 sandworm | 64 bit | 6.11 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.15 | compose 7.3.2 | cputemp 7.0.2 | mergerfs 7.0.5 | scripts 7.0.9


    omv-extras.org plugins source code and issue tracker - github - changelogs


    Please try ctrl-shift-R and read this before posting a question.

    Please put your OMV system details in your signature.
    Please don't PM for support... Too many PMs!

    Don't get me wrong - I don't judge anybody, just asking to better understand the process. I just didn't know that syncing command is making logs invisible in OMV GUI or Cockpit.

    When I removed from my cron schedule for -syncall it looks problem is solved.

    What is curious, now even after reboot I'm not loosing logs from - totatally don't understand why but happy with this :)

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login