Ad Widget

Collapse

Error message after upgrade 1.6.1 to 1.6.2 in Agent

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • mlange
    Member
    • Sep 2008
    • 78

    #1

    Error message after upgrade 1.6.1 to 1.6.2 in Agent

    zabbix_agentd.log:

    25917:20090120:110610 Can't open jason object
    25917:20090120:110810 Can't open jason object
    25917:20090120:111010 Can't open jason object
    25917:20090120:111210 Can't open jason object
    25917:20090120:111410 Can't open jason object
    25917:20090120:111610 Can't open jason object
    25917:20090120:111810 Can't open jason object
    25917:20090120:112010 Can't open jason object
    25917:20090120:112210 Can't open jason object
    25917:20090120:112410 Can't open jason object
  • NomenNescio
    Member
    • Jan 2009
    • 70

    #2
    I'm getting this error too.

    I'm running zabbix on Ubuntu in vmware, I currently have 3 virtual machines, 1 zabbix server and 3 agents.

    two of my agents are getting this "can't open jason object" error in their logs but one of my agents, the one which is running on the same machine the zabbix server & LAMP is running isn't getting any errors.

    Both the server and agents are 1.6.2

    hope it helps.
    Last edited by NomenNescio; 21-01-2009, 18:14.

    Comment

    • ataylo13
      Senior Member
      • Feb 2007
      • 122

      #3
      I am getting the same error. The host giving me the error is on a proxy server. The proxy is version 1.6.2 and I have tried the 1.6.1 agent and the 1.6.2 agent. I am only getting the jason errors on active checks. The normal zabbix agent checks are working correctly.
      Version : 1.8.8
      Current Configuration 1 Master and 3 Child Nodes

      Comment

      • MrKen
        Senior Member
        • Oct 2008
        • 652

        #4
        Just upgraded from 1.6.1 to 1.6.2 today and getting the same error message re: jason.

        I did /etc/init.d/zabbix_agentd stop
        then ps -ef | grep zabbix and noticed that the agent had not stopped!

        I then killed the process and restarted the agent. Everything started running fine and no more jason error messages.

        MrKen
        Disclaimer: All of the above is pure speculation.

        Comment

        • ataylo13
          Senior Member
          • Feb 2007
          • 122

          #5
          I verified that the agent was stopped and restarted. I am still seeing the error on active checks through a proxy. I am not seeing on active checks that are connecting directly to the master node.
          Version : 1.8.8
          Current Configuration 1 Master and 3 Child Nodes

          Comment

          • NomenNescio
            Member
            • Jan 2009
            • 70

            #6
            I think I got it, you have to uncomment Serverport in your agents config file, and set it to the port the server is using. Don't forget to make sure that that port is open on the server.

            Comment

            • ataylo13
              Senior Member
              • Feb 2007
              • 122

              #7
              disregard previous posts of mine. The more I dug into I was have dns issues. All is well.
              Version : 1.8.8
              Current Configuration 1 Master and 3 Child Nodes

              Comment

              • Alexei
                Founder, CEO
                Zabbix Certified Trainer
                Zabbix Certified SpecialistZabbix Certified Professional
                • Sep 2004
                • 5654

                #8
                Originally posted by mlange
                25917:20090120:110610 Can't open jason object
                The warning is slightly misleading. It happens when the agent tries to receive list of active checks from Zabbix server, but the server does not have the host in the database. Check if Hostname is correct in zabbix_agentd.conf.

                You may ignore this message.
                Alexei Vladishev
                Creator of Zabbix, Product manager
                New York | Tokyo | Riga
                My Twitter

                Comment

                • zabbix_es
                  Senior Member
                  • Apr 2007
                  • 153

                  #9
                  [zabbix-1.6.2] problem with active checks and jason error.

                  Hello:
                  My environment was a zabbix server and local agent with version 1.6.1 and four agents with version 1.6 (no upgraded because issue related to character ',' in UserParameter).
                  All hosts working properly.
                  Afther upgrade zabbix server and local agent to 1.6.2, appears this error message in server log:
                  Send list of active checks to [192.168.1.20] failed: host [myhost.mydomain.com] not found.
                  and in agent's log of related host:
                  Can`t open jason object.
                  Nevertheless, If I ping myhost.mydomain.com it responds without problems, so DNS is OK. An hostname is properly configured in zabbix_agentd.conf.
                  I tried to upgrade agent from 1.6 to 1.6.2 and this issue persists.
                  Now I have downgrade agent to 1.6 and issue remains but other three agents work fine. It happens only with one of four agentes.

                  Comment

                  • oneye
                    Junior Member
                    • May 2008
                    • 27

                    #10
                    i have similar problems...

                    Comment

                    • Alexei
                      Founder, CEO
                      Zabbix Certified Trainer
                      Zabbix Certified SpecialistZabbix Certified Professional
                      • Sep 2004
                      • 5654

                      #11
                      Just configure Hostname in zabbix_agentd.conf to match host name defined in ZABBIX front-end to make the warning disappear.
                      Alexei Vladishev
                      Creator of Zabbix, Product manager
                      New York | Tokyo | Riga
                      My Twitter

                      Comment

                      • zabbix_es
                        Senior Member
                        • Apr 2007
                        • 153

                        #12
                        [zabbix-1.6.2] problem with active checks and jason error.

                        I have confirmed that hostname in configuration of zabbix_agent match hostname (DNS) configured in zabbix_server and, in configuration of hosts in server, also is check that server must poll to agents throught DNS instead of IP address.

                        Furthermore, I din't change any connections or DNS parameters during upgrade and before the upgrade all worked properly.

                        Comment

                        • MrKen
                          Senior Member
                          • Oct 2008
                          • 652

                          #13
                          As Alexei pointed out, above, it has nothing to do with DNS name.

                          On you Configuration --> Hosts page, the first three columns are: Name; DNS; IP.

                          What you need is Name! Then restart your agentd.

                          MrKen
                          Disclaimer: All of the above is pure speculation.

                          Comment

                          • zabbix_es
                            Senior Member
                            • Apr 2007
                            • 153

                            #14
                            [zabbix-1.6.2] problem with active checks and jason error.



                            I had as Name "myhost" and as DNS "myhost.mydom1.mydom2.mydom3".
                            Afther, put in Name same value I was in DNS it works fine.

                            Thank you MrKen!.

                            But, I disagree with this behaviour because I think that Name could be diferent of DNS hostname.
                            I suposse that is a change included in revision 1.6.2.
                            Furthermore, I don't undestand why rest of agents (four of five) continuing working fine without changes.

                            Comment

                            • zabbix_es
                              Senior Member
                              • Apr 2007
                              • 153

                              #15
                              I answer my self:
                              Instead of putting "myhost.mydom1.mydom2.mydom3" in both fields ("Name" in front-end and "HostName" in agent), in my case, I have changed both to myhost and their also works fine.
                              I have checked rest of hosts and they have also this configuration so this was the reason because they didn't have any warnings.

                              Comment

                              Working...