Ad Widget

Collapse

"program counter not available for this architecture"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • herta
    Senior Member
    • Sep 2011
    • 101

    #1

    "program counter not available for this architecture"

    I just upgraded the agent on one Solaris SPARC 10 server to zabbix 2.0.3. It won't start. Previous posts suggest this is a bug. Does anyone else have the same issue?

    You can find the full error log below.

    Kind regards,

    Herta

    15544:20121009:152808.696 Got signal [signal:15(SIGTERM),sender_pid:5094,sender_uid:0,re ason:0]. Exiting ...
    15539:20121009:152808.699 One child process died (PID:15544,exitcode/signal:-1). Exiting ...
    15541:20121009:152808.700 Got signal [signal:15(SIGTERM),sender_pid:5094,sender_uid:0,re ason:0]. Exiting ...
    15539:20121009:152808.700 Zabbix Agent stopped. Zabbix 2.0.0 (revision 27675).
    5100:20121009:152817.991 Starting Zabbix Agent [edgucapdr-global]. Zabbix 2.0.3 (revision 30485).
    5101:20121009:152817.994 agent #0 started [collector]
    5102:20121009:152817.995 agent #1 started[listener]
    5103:20121009:152817.995 agent #2 started[listener]
    5104:20121009:152817.997 agent #3 started[listener]
    5105:20121009:152817.998 agent #4 started[listener]
    5106:20121009:152817.999 agent #5 started[listener]
    5101:20121009:152818.015 Got signal [signal:10(SIGBUS),reason:1,refaddr:feb8e4e4]. Crashing ...
    5101:20121009:152818.015 ====== Fatal information: ======
    5101:20121009:152818.015 program counter not available for this architecture
    5101:20121009:152818.015 === Registers: ===
    5101:20121009:152818.016 register dump not available for this architecture
    5101:20121009:152818.016 === Backtrace: ===
    5101:20121009:152818.016 backtrace not available for this platform
    5101:20121009:152818.016 === Memory map: ===
    5101:20121009:152818.016 memory map not available for this platform
    5101:20121009:152818.016 ================================
    5100:20121009:152818.019 One child process died (PID:5101,exitcode/signal:-1). Exiting ...
    5100:20121009:152820.020 Zabbix Agent stopped. Zabbix 2.0.3 (revision 30485).
    5114:20121009:152840.678 Starting Zabbix Agent [edgucapdr-global]. Zabbix 2.0.3 (revision 30485).
    5115:20121009:152840.681 agent #0 started [collector]
    5116:20121009:152840.682 agent #1 started[listener]
    5117:20121009:152840.682 agent #2 started[listener]
    5118:20121009:152840.684 agent #3 started[listener]
    5119:20121009:152840.685 agent #4 started[listener]
    5120:20121009:152840.686 agent #5 started[listener]
    5115:20121009:152840.701 Got signal [signal:10(SIGBUS),reason:1,refaddr:feb8e4e4]. Crashing ...
    5115:20121009:152840.701 ====== Fatal information: ======
    5115:20121009:152840.702 program counter not available for this architecture
    5115:20121009:152840.702 === Registers: ===
    5115:20121009:152840.702 register dump not available for this architecture
    5115:20121009:152840.702 === Backtrace: ===
    5115:20121009:152840.702 backtrace not available for this platform
    5115:20121009:152840.702 === Memory map: ===
    5115:20121009:152840.703 memory map not available for this platform
    5115:20121009:152840.703 ================================
    5114:20121009:152840.705 One child process died (PID:5115,exitcode/signal:-1). Exiting ...
    5114:20121009:152842.705 Zabbix Agent stopped. Zabbix 2.0.3 (revision 30485)
  • markl
    Member
    Zabbix Certified Specialist
    • Apr 2008
    • 62

    #2
    Hi, I have exactly the same issue. Have you managed to get around it yet? I've had to revert back to 2.0.0 for the agent.

    Comment

    • herta
      Senior Member
      • Sep 2011
      • 101

      #3
      No, I haven't, but it's hectic at work right now, and I haven't had time to investigate further. (Should improve by the end of the month.)

      I also reverted to Solaris agent 2.0.0 for now.

      Comment

      • vtm
        Junior Member
        • Oct 2012
        • 2

        #4
        same problem
        m5000
        SunOS host 5.10 Generic_144488-09 sun4u sparc SUNW,SPARC-Enterprise

        Comment

        • tchjts1
          Senior Member
          • May 2008
          • 1605

          #5
          I can verify this same issue on Solaris10 with 2.0.3 agent.

          Code:
           19965:20121022:092855.664 Starting Zabbix Agent [xxxxxxxx]. Zabbix 2.0.3 (revision 30485).
           19966:20121022:092855.666 agent #0 started [collector]
           19968:20121022:092855.666 agent #2 started[listener]
           19967:20121022:092855.666 agent #1 started[listener]
           19969:20121022:092855.667 agent #3 started[listener]
           19970:20121022:092855.668 agent #4 started[listener]
           19972:20121022:092855.669 agent #6 started [active checks]
           19971:20121022:092855.668 agent #5 started[listener]
           19966:20121022:092855.673 Got signal [signal:10(SIGBUS),reason:1,refaddr:fed0e4e4]. Crashing ...
           19966:20121022:092855.673 ====== Fatal information: ======
           19966:20121022:092855.673 program counter not available for this architecture
           19966:20121022:092855.673 === Registers: ===
           19966:20121022:092855.673 register dump not available for this architecture
           19966:20121022:092855.673 === Backtrace: ===
           19966:20121022:092855.673 backtrace not available for this platform
           19966:20121022:092855.673 === Memory map: ===
           19966:20121022:092855.674 memory map not available for this platform
           19966:20121022:092855.674 ================================
           19965:20121022:092855.675 One child process died (PID:19966,exitcode/signal:-1). Exiting ...
           19965:20121022:092857.675 Zabbix Agent stopped. Zabbix 2.0.3 (revision 30485).
          
          SunOS 5.10 Generic_147440-19 sun4u sparc SUNW,SPARC-Enterprise

          Comment

          • tchjts1
            Senior Member
            • May 2008
            • 1605

            #6
            There is an open issue on bug tracker for this: https://support.zabbix.com/browse/ZBX-5289

            Comment

            Working...