Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 12 replies
  • Subscribers 2 subscribers
  • Views 2346 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

[8.202] Strange CPU-peaks in the last 2 weeks (postgres)

Copyright
Hello

As you can see in the attached screenshots, our ASG320 [8.202] shows strange CPU-peaks every 15 mins which last 2 mins each time and are caused by postgres.

This behaviour began about 2 weeks ago and increased the CPU-usage from under 50% to over 75%.

I opened an ticket at Astaro (premium support) but they didn't find anything in the last 3 days.

Does someone know these symptoms and can tell me how to fix it ?

Node1 is slave at the time of the screenshot, node2 is master (3rd screenshot)


This thread was automatically locked due to age.
Parents
  • 0
    Is there anything unusual in the Selfmonitoring or System messages log?  Do all of the graphs in Reporting look like the relevant PostgreSQL databases are OK?

    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
    Selfmonitoring log seems clean:

    2011:11:09-08:08:43 astaro-1 selfmonng[5939]: T Loading Selfmonitoring Checks complete new=0 failed=0 retained=66 dropped=0
    2011:11:09-08:08:43 astaro-1 selfmonng[5939]: T read config file '/etc/selfmonng.conf'
    2011:11:09-13:21:11 astaro-2 selfmonng[5956]: I reloading all checks
    2011:11:09-13:21:12 astaro-2 selfmonng[5956]: W Duplicate check name 'snort_inline_running' detected
    2011:11:09-13:21:12 astaro-2 selfmonng[5956]: T Loading Selfmonitoring Checks complete new=1 failed=0 retained=65 dropped=1
    2011:11:09-13:21:12 astaro-2 selfmonng[5956]: T read config file '/etc/selfmonng.conf'
    2011:11:09-13:21:14 astaro-1 selfmonng[5939]: I reloading all checks
    2011:11:09-13:21:14 astaro-1 selfmonng[5939]: W Duplicate check name 'snort_inline_running' detected
    2011:11:09-13:21:14 astaro-1 selfmonng[5939]: T Loading Selfmonitoring Checks complete new=1 failed=0 retained=65 dropped=1
    2011:11:09-13:21:14 astaro-1 selfmonng[5939]: T read config file '/etc/selfmonng.conf'
    ---

    System messages log:
    2011:11:09-16:36:40 astaro-1 syslog-ng[8079]: Syslog connection failed; fd='124', server='AF_INET(127.0.0.1:10100)', error='Connection refused (111)', time_reopen='60'
    2011:11:09-16:37:01 astaro-2 /usr/sbin/cron[7916]: (root) CMD ((date;uptime;free -m;ps auxf;netstat -natup;cat /proc/slabinfo) >> /var/log/meminfo.log)
    2011:11:09-16:37:40 astaro-1 syslog-ng[8079]: Syslog connection failed; fd='124', server='AF_INET(127.0.0.1:10100)', error='Connection refused (111)', time_reopen='60'

    All reports on our ASG320 look fine, I can't find any issues
  • 0 in reply to Copyright
    Could the logging to the Astaro logging cloud cause this issue ? As I can see, we sent 2.4 million log lines to the Astaro logging cloud at 6th of november 2011
Reply Children
No Data
Cookie Information Banner