Ad Widget

Collapse

Data Lost

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • rafael
    Junior Member
    • Sep 2006
    • 11

    #1

    Data Lost

    I upgrade my server from 1.6.1 to 1.6.3. After the upgrade the system was working fine. During the weekend something happen because now all the configurations are gone (hosts, groups, items, triggers, templates) nothing is being display on the system. I then upgrade to zabbix 1.6.4 and the issue did not get resolve

    The system is running on:
    Solaris 10
    zabbix 1.6.3

    How can I recover my system?
  • philippn
    Junior Member
    • Dec 2007
    • 3

    #2
    If you have backups (I hope so), you can try to downgrade to an working version, export your settings to xml and import them into your new version.

    Maybe that works...

    Comment

    • rafael
      Junior Member
      • Sep 2006
      • 11

      #3
      I tried that already. Downgraded to 1.6.1. then back to 1.6.3 and now I'm at 1.6.4 because 1.6.3 has a lot of bugs.

      The server is configure as node #3 in a distributed node. This might be the issue. But I can not find any thread on how to upgrade all nodes.

      Comment

      • Cray
        Member
        • Mar 2009
        • 72

        #4
        I can't tell exactly what happened (DB failure, hacking trough the Zabbix Web-ui, Zabbix bug...), but it is strongly advised to backup your database(s) before doing an upgrade;

        It is also advised to put your database on another server (if you have another physical / virtual server to use).

        Anyway, I hope you will recover your data, because loosing config always sucks

        Comment

        • troffasky
          Senior Member
          • Jul 2008
          • 567

          #5
          An 'export everything to XML' option would be nice. Right now the Screens are missing, amongst other things.

          Comment

          • Cray
            Member
            • Mar 2009
            • 72

            #6
            Yep, it would be nice, but it might no be that simple (the developers have to manage all the dependencies between items / graphs / hosts before providing a fully exportable screen).

            Comment

            • troffasky
              Senior Member
              • Jul 2008
              • 567

              #7
              If it's possible to manage the dependencies between a graph, some items and the host they belong to in order to make a graph exportable, I can't see why a screen would be any harder. But then I'm not a developer so this is just idle speculation!

              Comment

              • rafael
                Junior Member
                • Sep 2006
                • 11

                #8
                I did not think a DB backup would be necessary since I was going from version 1.6.1 to 1.6.3. I did backup the DB when I upgraded from 1.4.2 to 1.6.1. That upgrade was fine.

                The only thing that changed was the frontend and the exec.

                I did the upgrade on another system and that upgrade did not have any issues. I was able to upgrade to 1.6.3 and then again to 1.6.4. But on this particular system days later I am not able to anything to display. The server logs have the following entry "Send list of active checks to [] failed: host [hostname]"

                Comment

                • jroberson
                  Senior Member
                  • May 2008
                  • 124

                  #9
                  Have you tried reloading the front-end and then going through the Administration --> Installation again? Though that might not apply, I haven't messed with any nodes yet.

                  Comment

                  • rafael
                    Junior Member
                    • Sep 2006
                    • 11

                    #10
                    Yes, it almost seems like the frontend is not connecting to DB or the DB is locking out the frontend. The only thing that is available right now are the accounts of the users I created, everything else is gone.

                    Right now I am restoring the db to another one, and pointing the frontend to that DB to see if that helps.

                    If that does not work I am going to start from scratch.

                    Comment

                    Working...