Tested Zabbix agent 2.0.2 (revision 29143). HP-UX platforms:
- 11.23 Itanium
- 11.31 Itanium
Zabbix agent 1.8.15rc1 working properly on these platforms, so this looks like a regression.
On same versions (11.23, 11.31) but PA-RISC CPUs no crash is observed.
Reproducing is simple:
- get 2.0 Zabbix
- ./configure --enable-agent
- make
- ./zabbix_agentd
- observe the log file
It should contain something like:
16971:20120731:002429.392 Starting Zabbix Agent [Zabbix server]. Zabbix 2.0.2 (revision 29143).
16972:20120731:002429.393 agent #0 started [collector]
16972:20120731:002429.394 Got signal [signal:10(SIGBUS),reason:1,refaddr:c543000c]. Crashing ...
16972:20120731:002429.394 ====== Fatal information: ======
16972:20120731:002429.394 program counter not available for this architecture
16972:20120731:002429.394 === Registers: ===
16972:20120731:002429.394 register dump not available for this architecture
16972:20120731:002429.394 === Backtrace: ===
16972:20120731:002429.394 backtrace not available for this platform
16972:20120731:002429.394 === Memory map: ===
16972:20120731:002429.394 memory map not available for this platform
16972:20120731:002429.394 ================================
16971:20120731:002429.394 One child process died (PID:16972,exitcode/signal:-1). Exiting ...
16971:20120731:002431.400 Zabbix Agent stopped. Zabbix 2.0.2 (revision 29143).
- duplicates
-
ZBX-5289 2.0.1 agent on Solaris 10 throws "Got signal [signal:10(SIGBUS),reason:1,refaddr:fec0e4e4]. Crashing ..."
- Closed