Ad Widget

Collapse

Zabbix server restarted due to housekeeping

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • SysFiller
    Junior Member
    • Jul 2013
    • 6

    #1

    Zabbix server restarted due to housekeeping

    Hello everyone,
    I get the alarm "Zabbix server has just been restarted" very often, and it seems like it happens when executing the housekeeping process. Is this normal or something should be configured in some specific way? Currently housekeeping executes every hour.

    Thank you
    Alessio
  • tchjts1
    Senior Member
    • May 2008
    • 1605

    #2
    No, that is not normal. Take a look on your Zabbix server and see if there is any further related messages in zabbix_server.log

    Comment

    • SysFiller
      Junior Member
      • Jul 2013
      • 6

      #3
      Thank you for reply. I can't see anything strange, just the housekeeping process.

      Code:
      18807:20130730:075751.033 executing housekeeper
       18807:20130730:075813.552 housekeeper deleted: 134285 records from history and trends, 0 records of deleted items, 0 events, 0 alerts, 0 sessions
       18807:20130730:085814.039 executing housekeeper
       18807:20130730:085833.897 housekeeper deleted: 134380 records from history and trends, 0 records of deleted items, 0 events, 0 alerts, 0 sessions
       18807:20130730:095834.374 executing housekeeper
       18807:20130730:095855.123 housekeeper deleted: 134163 records from history and trends, 0 records of deleted items, 0 events, 0 alerts, 0 sessions
      I attach you my zabbix_server.conf:

      Code:
      LogFile=/var/log/zabbix/zabbix_server.log
      LogFileSize=0
      DebugLevel=3
      PidFile=/var/run/zabbix/zabbix_server.pid
      DBName=zabbix
      DBUser=zabbix
      DBPassword=<mypassword>
      DBSocket=/var/lib/mysql/mysql.sock
      StartPollers=6
      StartIPMIPollers=1
      StartPollersUnreachable=5
      StartTrappers=10
      StartHTTPPollers=1
      AlertScriptsPath=/var/lib/zabbixsrv/alertscripts
      ExternalScripts=/var/lib/zabbixsrv/externalscripts
      FpingLocation=/usr/sbin/fping
      Thank you,
      Alessio

      Comment

      • trikke76
        Member
        Zabbix Certified Trainer

        • Apr 2013
        • 42

        #4
        Sounds more like an non zabbix issue to me


        maybe hardware ( defect disks ? )

        or database corruption ?

        Comment

        • SysFiller
          Junior Member
          • Jul 2013
          • 6

          #5
          Hello everyone! We solved the issue. It was related to the server CPU utilization.
          We solved increasing the number of pre-forked discoverers (which defaults to 1) by setting:

          Code:
          StartDiscoverers=3
          Thank you!
          Alessio

          Comment

          • SysFiller
            Junior Member
            • Jul 2013
            • 6

            #6
            Hello,
            just to point out: I still have this issue! I though it was solved, but I keep receiving emails with

            Code:
            PROBLEM: Zabbix server has just been restarted
            Anyway the item values in the email are:


            Code:
            Trigger: monitor has just been restarted
            Trigger status: PROBLEM
            Trigger severity: Information
            Trigger URL: 
            
            Item values:
            
            1. System uptime (monitor:system.uptime): 7 days, 11:39:43
            2. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
            3. *UNKNOWN* (*UNKNOWN*:*UNKNOWN*): *UNKNOWN*
            Thank you
            Alessio

            Comment

            • tchjts1
              Senior Member
              • May 2008
              • 1605

              #7
              So is the server actually rebooting, or are you saying these are false alerts?

              Comment

              • SysFiller
                Junior Member
                • Jul 2013
                • 6

                #8
                Thank you for your reply, as you can see from the post is a false alarm. The uptime value is correct, but alerts are still sent.

                Alessio

                Comment

                Working...