Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-4376

New installation after 1 or 2 days alway gives DB Error 2002

Details

    • Bug
    • Resolution: Not A Bug
    • Blocker
    • None
    • CE-22.5
    • OS
    • None
    • Ubunta 20.04 with the newest proffesional version of Observium

    Description

      Our old Observium installation had crashed so I had to install a new version.

      I have tried Ubuntu 22 and 20.04 u tried debian the newest Debian and Debian 11 and i tried CENTOS. But with all the tries after a day or 2 all the installations came with the same error. DB Error 2002. We have the paid proffesional edition and i followed step by step the provided installation guides for the installation.

      Please help me to get it up and running again.

       

      Kind regards Henk-Jan

      Attachments

        Activity

          [OBS-4376] New installation after 1 or 2 days alway gives DB Error 2002
          landy Mike Stupalov added a comment -

          Literally DB error 2002 named as "Can't connect to MySQL server" and trouble exactly with connect to DB. Not with run Observium.

          landy Mike Stupalov added a comment - Literally DB error 2002 named as "Can't connect to MySQL server" and trouble exactly with connect to DB. Not with run Observium.
          landy Mike Stupalov made changes -
          Resolution New: Not A Bug [ 6 ]
          Status Original: Pending Response [ 10000 ] New: Resolved [ 5 ]
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          landy Mike Stupalov added a comment -

          You should optimize your DB.
          Move to SSD, run mysql-tune.

          Observium actively use DB, but with optimized requests..
          Your error not related with Observium code or bugs, but with mysql server optimization.

          landy Mike Stupalov added a comment - You should optimize your DB. Move to SSD, run mysql-tune. Observium actively use DB, but with optimized requests.. Your error not related with Observium code or bugs, but with mysql server optimization.
          landy Mike Stupalov made changes -
          Status Original: Pending Response [ 10000 ] New: In Review [ 10101 ]
          dghjfsg Henk-Jan Dennenberg added a comment -

          We are monitoring our network and servers, it are about 120 devices.

          Observium is running virtual on a hyper-v cluster.

          Has 2 processors, 4GB ram, 80GB of storage and is configured with 4 NIC's.

           

          dghjfsg Henk-Jan Dennenberg added a comment - We are monitoring our network and servers, it are about 120 devices. Observium is running virtual on a hyper-v cluster. Has 2 processors, 4GB ram, 80GB of storage and is configured with 4 NIC's.  
          landy Mike Stupalov made changes -
          Status Original: In Review [ 10101 ] New: Pending Response [ 10000 ]
          adama Adam Armstrong added a comment -

          Hi Henk-Jan. 

          Jira is a bug tracker, and not a good place for support requests.

          I'm not really sure what might cause this. It means your mysql server can not be contacted, most likely because it's been killed by the system or crashed.

          You can check syslog/dmesg for the system killing processes, or the mysql log to see if it killed itself.

          I've only ever seen or heard of this happen frequently on one other system, and that's our demo system. Its a very small install so it doesn't make a lot of sense.

          How much RAM does the system have? Does the disk get full? How many things are you trying to monitor?

          Thanks,

          adam.

          adama Adam Armstrong added a comment - Hi Henk-Jan.  Jira is a bug tracker, and not a good place for support requests. I'm not really sure what might cause this. It means your mysql server can not be contacted, most likely because it's been killed by the system or crashed. You can check syslog/dmesg for the system killing processes, or the mysql log to see if it killed itself. I've only ever seen or heard of this happen frequently on one other system, and that's our demo system. Its a very small install so it doesn't make a lot of sense. How much RAM does the system have? Does the disk get full? How many things are you trying to monitor? Thanks, adam.
          adama Adam Armstrong made changes -
          Comment [ _*General questions and device support can be discussed in [our Discord channel, click here to join|https://discord.gg/GjpNXKWm8W].*_
          ----

          Please make and attach additional information about the device:
           * full snmp dump from device:
          {noformat}
          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
          snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk
          {noformat}
            _If device not support SNMP version 2c, replace -v2c with -v1._

           * If you have problems with discovery or poller processes, please do and attach these debugs:
          {noformat}
          ./discovery.php -d -h <device>
          ./poller.php -d -h <device>
          {noformat}
           
          * additionally attach device and/or vendor specific MIB files

          ----
          {color:#505F79}_This comment is added automatically._{color} ]
          dghjfsg Henk-Jan Dennenberg added a comment - - edited

          There hasn't been any reply on my issue. Can someone reply or contact me, so that we can resolve this issue. I have been a long time with out monitoring now.

          dghjfsg Henk-Jan Dennenberg added a comment - - edited There hasn't been any reply on my issue. Can someone reply or contact me, so that we can resolve this issue. I have been a long time with out monitoring now.

          People

            landy Mike Stupalov
            dghjfsg Henk-Jan Dennenberg
            Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: