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 20512 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
    To be precise: 

    - "slow on speed" means that the web interface needs 4-5 seconds to switch to the next option.

    - The "Self monitoring deamon" protocol repeates

    2015:08:18-08:58:59 han-e7-secapp selfmonng[3951]: W triggerAction: 'cmd'
    2015:08:18-08:58:59 han-e7-secapp selfmonng[3951]: W actionCmd(+): '/etc/init.d/rrdcache restart'
    2015:08:18-08:59:00 han-e7-secapp selfmonng[3951]: W child returned status: exit='0' signal='0'
    2015:08:18-08:59:25 han-e7-secapp selfmonng[3951]: I check Failed increment rrdcache_running counter 1 - 3
    2015:08:18-08:59:30 han-e7-secapp selfmonng[3951]: I check Failed increment rrdcache_running counter 2 - 3
    2015:08:18-08:59:35 han-e7-secapp selfmonng[3951]: W check Failed increment rrdcache_running counter 3 - 3
    2015:08:18-08:59:35 han-e7-secapp selfmonng[3951]: W NOTIFYEVENT Name=rrdcache_running Level=INFO Id=192 suppressed

    - and the "System Messages" protocol tells me

    2015:08:18-09:00:02 han-e7-secapp system-reporter.pl: WARN - Error updating rrd
    2015:08:18-09:00:02 han-e7-secapp system-reporter.pl: WARN - updating rrd: connect: Connection refused
    2015:08:18-09:00:08 han-e7-secapp ips-reporter.pl: WARN - updating rrd: sending command: Broken pipe
    2015:08:18-09:00:29 han-e7-secapp postgres[3856]: [10353-1] WARNING: pgstat wait timeout
    2015:08:18-09:01:05 han-e7-secapp postgres[3856]: [10354-1] WARNING: pgstat wait timeout

    - Date and time is correct, ntp is used.

    I am diving deeper:

    - 1439323024 is 11.08.2015 / 21:57:04 
    - 1439323085 is 11.08.2015 - 21:58:05 

    How can I change the first value to the actual date?

    Christian
Reply
  • 0
    To be precise: 

    - "slow on speed" means that the web interface needs 4-5 seconds to switch to the next option.

    - The "Self monitoring deamon" protocol repeates

    2015:08:18-08:58:59 han-e7-secapp selfmonng[3951]: W triggerAction: 'cmd'
    2015:08:18-08:58:59 han-e7-secapp selfmonng[3951]: W actionCmd(+): '/etc/init.d/rrdcache restart'
    2015:08:18-08:59:00 han-e7-secapp selfmonng[3951]: W child returned status: exit='0' signal='0'
    2015:08:18-08:59:25 han-e7-secapp selfmonng[3951]: I check Failed increment rrdcache_running counter 1 - 3
    2015:08:18-08:59:30 han-e7-secapp selfmonng[3951]: I check Failed increment rrdcache_running counter 2 - 3
    2015:08:18-08:59:35 han-e7-secapp selfmonng[3951]: W check Failed increment rrdcache_running counter 3 - 3
    2015:08:18-08:59:35 han-e7-secapp selfmonng[3951]: W NOTIFYEVENT Name=rrdcache_running Level=INFO Id=192 suppressed

    - and the "System Messages" protocol tells me

    2015:08:18-09:00:02 han-e7-secapp system-reporter.pl: WARN - Error updating rrd
    2015:08:18-09:00:02 han-e7-secapp system-reporter.pl: WARN - updating rrd: connect: Connection refused
    2015:08:18-09:00:08 han-e7-secapp ips-reporter.pl: WARN - updating rrd: sending command: Broken pipe
    2015:08:18-09:00:29 han-e7-secapp postgres[3856]: [10353-1] WARNING: pgstat wait timeout
    2015:08:18-09:01:05 han-e7-secapp postgres[3856]: [10354-1] WARNING: pgstat wait timeout

    - Date and time is correct, ntp is used.

    I am diving deeper:

    - 1439323024 is 11.08.2015 / 21:57:04 
    - 1439323085 is 11.08.2015 - 21:58:05 

    How can I change the first value to the actual date?

    Christian
Children
No Data
Unfiltered HTML