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

multiple rrdtool high (100%) cpu usage

Since 02:20 this morning 3 seperate systems I look after for friends have shown this problem.

Each is running at 100% CPU load and the FW is slow

After SSH'ing in I found that there are many (20+) instances of rrdtools running.

This problem looks identical to  rrdtool high cpu usage

I have tried what is suggested there which kills the rrdtool task but after a while the instances start again so I have commented out the lines in /etc/crontab.rrd for now

What is the permanent solution to this ?

Jeff



This thread was automatically locked due to age.
Parents
  • Hello Team,

    Good day and hope every one is well. 

    This issue seems to be due to Daylight saving change that happened. This is currently being investigated by Dev Team.

    Suggested workaround is to set TimeZone to anything other than GMT, IST (Ireland), and BST (British Summer Time) and restart the system.  If that doesn’t work, UTC should work fine, as this has no daylight savings.

    As far as we know, this should only affect UK customers.

    Many thanks for your time and patience and thank you for choosing Sophos. 

    Cheers,

    Raphael Alganes
    Community Support Engineer | Sophos Technical Support
    Sophos Support Videos Product Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.

  • Any update to resolve this issue as one of our client UTM's in HA is maxed out at 100% CPU and is a complete outage for 1000 users.  CPU has gone up since early hours of Sunday morning.  This looks to be related to this issue raised as same firmware version 9.714-4.  Already raised with Sophos support 06378016.  Told that someone from technical would ring me back in 2 hours.  This is unacceptable as we have a complete outage for this client.

  • My Timezone is set to 'Europe / London' not GMT, IST (Ireland), and BST (British Summer Time)

  • Any update to resolve this issue as one of our client UTM's in HA is maxed out at 100% CPU and is a complete outage for 1000 users.  CPU has gone up since early hours of Sunday morning.  This looks to be related to this issue raised as same firmware version 9.714-4.  Already raised with Sophos support 06378016.  Told that someone from technical would ring me back in 2 hours.  This is unacceptable as we have a complete outage for this client.

    If I were in your situation I'd have implemented the workaround which JeffreyLewcock suggested last night. This kills the rrd processes and then prevents the Cron jobs from running commenting them out. Takes two minutes [assuming you know how to use vi] and it doesn't require a reboot.

    I ssh'd in then sudo'd to root

    killall /usr/local/bin/create_rrd_graphs.plx
    killall rrdtool

    I then edited

    /etc/crontab
    /etc/crontab.rrd

    to comment out the cron entry that restarts the process

    If rrdtools has respawned you might have to re run the killall commands

    This prevents the rrdtools running however the graphing is then stopped

    Remove the commenting when you have a proper solution (and tell me !!)

    I'm suprised theres not more people having this problem TBH

Reply
  • Any update to resolve this issue as one of our client UTM's in HA is maxed out at 100% CPU and is a complete outage for 1000 users.  CPU has gone up since early hours of Sunday morning.  This looks to be related to this issue raised as same firmware version 9.714-4.  Already raised with Sophos support 06378016.  Told that someone from technical would ring me back in 2 hours.  This is unacceptable as we have a complete outage for this client.

    If I were in your situation I'd have implemented the workaround which JeffreyLewcock suggested last night. This kills the rrd processes and then prevents the Cron jobs from running commenting them out. Takes two minutes [assuming you know how to use vi] and it doesn't require a reboot.

    I ssh'd in then sudo'd to root

    killall /usr/local/bin/create_rrd_graphs.plx
    killall rrdtool

    I then edited

    /etc/crontab
    /etc/crontab.rrd

    to comment out the cron entry that restarts the process

    If rrdtools has respawned you might have to re run the killall commands

    This prevents the rrdtools running however the graphing is then stopped

    Remove the commenting when you have a proper solution (and tell me !!)

    I'm suprised theres not more people having this problem TBH

Children
No Data