Wakealarm spamming error in syslog

  • Hi everyone,
    I noticed right now that the plug-in wakealarm is spamming this error in syslog:


    Code
    Sep 10 00:22:01 delibird CRON[27247]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
    Sep 10 00:23:01 delibird CRON[27284]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)
    Sep 10 00:24:01 delibird CRON[27324]: (root) CMD (   test -x /usr/sbin/wakealarm && /usr/sbin/wakealarm > /dev/null 2>&1)

    I found that there are other people with the same error in the forum, but no one answered to how avoid this problem.



    Can this be resolved with a wakealarm update? Otherwise there is some way to avoid this entry to be spammed in the syslog every minute?

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • First off, it's not an error. It's the output of a cron job that seems to be set up to run every minute.


    If you don't want cron to log at all, then modify your rsyslog.conf file to silence it there.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

  • Not every cron job is shown in OMV's scheduled commands, if that's what that screenshot is.


    Run crontab -e to see more.


    Post your /etc/rsyslog.conf.

    --
    Google is your friend and Bob's your uncle!


    OMV AMD64 7.x on headless Chenbro NR12000 1U 1x 8m Quad Core E3-1220 3.1GHz 32GB ECC RAM.

    • Offizieller Beitrag

    I don't have any job every minute

    The plugin adds it - https://github.com/OpenMediaVa…ster/etc/cron.d/wakealarm


    This is how wakealarm works.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • Thanks for the answer.
    than how can I modify my rsyslog.conf file to silence it? It's hard to find the log I'm looking for otherwise.


    Or is it possible to have wakealarm log in a different file instead of syslog?

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

    • Offizieller Beitrag

    Or is it possible to have wakealarm log in a different file instead of syslog?

    wakealarm does send its output to its own log file - link. cron is sending the log entry to syslog when it executes the wakealarm entry.

    omv 7.0.4-2 sandworm | 64 bit | 6.5 proxmox kernel

    plugins :: omvextrasorg 7.0 | kvm 7.0.10 | compose 7.1.2 | k8s 7.0-6 | cputemp 7.0 | mergerfs 7.0.3


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


    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!

  • ooops. Forgot to answer at this! Yes, I solved creating a dedicated log file for cron adding this line to /etc/rsyslog.conf :
    #
    # First some standard log files. Log by facility.
    #
    cron.* /var/log/cron.log

    Intel G4400 - Asrock H170M Pro4S - 8GB ram - Be Quiet Pure Power 11 400 CM - Nanoxia Deep Silence 4 - 6TB Seagate Ironwolf - RAIDZ1 3x10TB WD - OMV 5 - Proxmox Kernel

  • Thanks for providing the fix. Probably this behaviour should be documented.



    This is my default /etc/rsyslog.conf and the line is already here, just commented!


    EDIT: I made the change, rebooted, but wakealarm is still spamming...

    Ok, I fixed it by also adding cron to line number 5 (thanks Google...). That's how it looks now, and finally it's not spamming anymore!


    OMV BUILD - MY NAS KILLER - OMV 6.x + omvextrasorg (updated automatically every week)

    NAS Specs: Core i3-8300 - ASRock H370M-ITX/ac - 16GB RAM - Sandisk Ultra Flair 32GB (OMV), 256GB NVME SSD (Docker Apps), Several HDDs (Data) w/ SnapRAID - Fractal Design Node 304 - Be quiet! Pure Power 11 350W


    My all-in-one SnapRAID script!

    3 Mal editiert, zuletzt von auanasgheps ()

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!