Help us enhance your Sophos Community experience. Share your thoughts in our Sophos Community survey.

Thread Info
  • State Verified Answer
  • +1 person also asked this people also asked this
  • Locked Locked
  • Replies 9 replies
  • Subscribers 3 subscribers
  • Views 20509 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

[Solved]UTM problems with rrdcached since 9.315-2

cwoller
Hi. 

Since the update to 9.315-2, the UTM 320 is slow on speed and we got tons of erros from rrdcached. The "Fallback" log fills up with messages like this:

2015:08:18-08:43:44 han-e7-secapp [daemon:notice] rrdcached[10060]: queue_thread_main: rrd_update_r (/var/log/reporting/rrd/apusage_A400175F685D801.rrd) failed with status -1. (/var/log/reporting/rrd/apusage_A400175F685D801.rrd: illegal attempt to update using time 1439323024 when last update time is 1439323085 (minimum one second step))

and this

2015:08:18-08:44:19 han-e7-secapp [daemon:info] rrdcached[10124]: starting up
2015:08:18-08:44:19 han-e7-secapp [daemon:info] rrdcached[10124]: checking for journal files
2015:08:18-08:44:19 han-e7-secapp [daemon:notice] rrdcached[10124]: replaying from journal: /var/log/reporting/rrd/rrd.journal.1439316807.508822

Every hour we get emails with this subject:

[INFO-192] RRD cache daemon not running - restarted

Has anybody seen this before or has any hit to solve this? 

I tried google on this but it seams to me, that his error is a kind of special on our system.

Any hint is welcome.

Best regards, Christian


This thread was automatically locked due to age.
Parents
  • 0
    Christian, try restoring the config backup made just prior to the Up2Date.  If that doesn't help, try a reboot.  Any luck?

    Cheers - Bob
     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0 in reply to BAlfson
    Hi Bob. 

    Thanks for your reply.

    The update we did a couple of days before, was from 9.313-3 over 9.314-13 to 9.315-2. Then the error happend.

    Now, I recovered the UTM to a 9.313-3 config. After recovery, I waited for 10 minutes, watching the logs. After no changes happend (failure still existed), I rebooted the system - without any effect on the failure. 

    Do I need to make a full restore with an image or do you have any more ideas for me? :-)

    Best regards,

    Christian
Reply
  • 0 in reply to BAlfson
    Hi Bob. 

    Thanks for your reply.

    The update we did a couple of days before, was from 9.313-3 over 9.314-13 to 9.315-2. Then the error happend.

    Now, I recovered the UTM to a 9.313-3 config. After recovery, I waited for 10 minutes, watching the logs. After no changes happend (failure still existed), I rebooted the system - without any effect on the failure. 

    Do I need to make a full restore with an image or do you have any more ideas for me? :-)

    Best regards,

    Christian
Children
No Data
Unfiltered HTML