rrdcached error messages after reboot

  • votdev



    I still see these errors on R Pi4


    cat /etc/default/rrdcached

    # This file is auto-generated by openmediavault (https://www.openmediavault.org)

    # WARNING: Do not edit this file, your changes will get lost.

    # /etc/default file for RRD cache daemon


    # Full path to daemon

    DAEMON=/usr/bin/rrdcached


    # Optional override flush interval, in seconds.

    WRITE_TIMEOUT=900


    # Where database files are placed. If left unset, the default /tmp will

    # be used. NB: The daemon will reject a directory that has symlinks as

    # components. NB: You may want to have -B in BASE_OPTS.

    BASE_PATH=/var/lib/rrdcached/db/


    # Where journal files are placed. If left unset, journaling will

    # be disabled.

    JOURNAL_PATH=/var/lib/rrdcached/journal/


    # FHS standard placement for process ID file.

    PIDFILE=/run/rrdcached.pid


    # FHS standard placement for local control socket.

    SOCKFILE=/run/rrdcached.sock


    # Any other options not specifically supported by the script (-P, -f,

    # -F, -B).

    BASE_OPTIONS="-B -F -f 3600"



    and running omv-salt deploy run rrdcached did not help.


    Any clues?


    Thx

  • I'm having a similar set of issues with rrdcached on an OMV 5.5.16-1 (Usul) system.

    Get two emails on reboot, one that rrdached "does not exist" and isn't running, and then subsquently one that it is running moments later.

    systemctl status rrdcached informs me that the process is running fine, and in the /etc/default/rrdcahed I find everything similar to Chudak above, main thing being that everything is at /run/ and not /var/run/, I gather as previous commenters have had issues with that.

    In /var/log/syslog I find this sequence:

    monit[871]: 'rrdcached' process is not running
    monit[871]: Cannot create socket to [127.0.0.1]:25 -- Connection refused
    monit[871]: Cannot open a connection to the mailserver 127.0.0.1:25 -- Operation now in progress
    monit[871]: Mail: Delivery failed -- no mail server is available
    monit[871]: Adding event to the queue file /var/lib/monit/events/1605598308_55f4e3545770 for later delivery
    monit[871]: 'rrdcached' trying to restart
    monit[871]: 'rrdcached' start: '/bin/systemctl start rrdcached'

    I think the mail server at :25 might be unrelated, and I don't fully understand it, but I still included it in case it is pertinent.

    If anyone has any ideas how to adress this it would be great, though at this moment it seems like a minor inconvenience I guess?

  • keinhen


    Your problem is only monit which triggers to quickly .

    The following coming command will fix it.


    sudo omv-env set OMV_MONIT_DELAY_SECONDS 240

    sudo monit restart omv-engined

    sudo omv-salt stage run prepare

    sudo omv-salt stage run deploy



    next reboot, do journalctl -u monit and you see this and hopefully no emails :)


    monit[2069]: Monit will delay for 240s on first start after reboot ...


    Oli

  • I was attended to this quote following a google search for my monitoring errors on rrd cache problems following a start-up of the module. As I expected a too early check from the monitoring system following an automatic start-up for my daily back-up. I applied your solution and it resolved the issue. a delayyed start of the monitoring system module of OMV 5 solved also my issue with the daily error and restart message.


    Thanks for the solution Oli


    Kind regards hblek

Participate now!

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