Bug #43381 agent --agent-run-os-tests crashes on Linux-x86-64 (Segmentation fault)

• Submitted: 4 Mar 2009 16:10
• Modified: 6 Mar 2009 16:00
• Reporter: Carsten Segieth
• Status: Closed
• Category: MySQL Enterprise Monitor: Agent
• Severity: S2 (Serious)
• Version: 2.0.5.7148
• OS: Linux (x86_64)
• Assigned to: Jan Kneschke
• CPU Architecture: Any

[4 Mar 2009 16:10] Carsten Segieth

Description:
calling the agent with "--agent-run-os-tests" it crashes on (at least) two Linux x86-64 boxes:

(qa-merlin)
2009-03-04 16:39:42: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192, Invalid argument (22). Current limit still 1024.
sigar-test-all.c.124 (test_sigar_pid_get):
  pid = 5188
sigar-test-all.c.106 (test_sigar_mem_get):
...cut...
sigar-test-all.c.427 (test_sigar_file_system_list_get): (items = 13)
[0]
  fs.dirname = /
  fs.devname = /dev/mapper/vg00-root
  fs.typename = local
  fs.sys-type-name = ext3
  fs.type = 2
  fsusage.total = 15481840
  fsusage.free = 14116140
  fsusage.used = 1365700
  fsusage.avail = 13329708
  fsusage.files = 1966080
  fsusage.use_percent = 0.100000
[0]
  diskusage.reads = 315302
  diskusage.writes = 6318240
  diskusage.write_bytes = 25879511040
  diskusage.read_bytes = 6561092608
  diskusage.queue = 47457530080206
Segmentation fault

On a different box no output is shown, just the "Segmentation fault".

How to repeat:
.../bin/mysql-monitor-agent --agent-run-os-tests

[5 Mar 2009 7:40] Carsten Segieth

verified on all x86-64 test boxes: blade01, blade08, blade09, blade10, qa-merlin, rh-x86-64, vm-rhas-x86-64-a

[5 Mar 2009 13:23] Jan Kneschke

Pushed and committed yesterday to both trees

revno: 1222
committer: [e-mail]
branch nick: trunk
timestamp: Wed 2009-03-04 21:08:43 +0100
message:
  include the return-code in the error-msg if one of the sigar-functions fails
  
    * fixed some warnings along the way

------------------------------------------------------------
revno: 1230
committer: [e-mail]
branch nick: rel-2.0
timestamp: Wed 2009-03-04 21:19:51 +0100
message:
  include the return-code in the error-msg if one of the sigar-functions fails
  
    * fixed some warnings along the way

[5 Mar 2009 14:15] Carsten Segieth

verified fixed in build 2.0.5.7150

[6 Mar 2009 16:00] Tony Bedford

An entry was added to the 2.0.5 changelog:

Calling the Agent with the option --agent-run-os-tests resulted in a crash. This happened on Linux x86-64 systems. The resultant stack trace was:

(qa-merlin)
2009-03-04 16:39:42: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192,
Invalid argument (22). Current limit still 1024.
sigar-test-all.c.124 (test_sigar_pid_get):
  pid = 5188
sigar-test-all.c.106 (test_sigar_mem_get):
...cut...
sigar-test-all.c.427 (test_sigar_file_system_list_get): (items = 13)
[0]
  fs.dirname = /
  fs.devname = /dev/mapper/vg00-root
  fs.typename = local
  fs.sys-type-name = ext3
  fs.type = 2
  fsusage.total = 15481840
  fsusage.free = 14116140
  fsusage.used = 1365700
  fsusage.avail = 13329708
  fsusage.files = 1966080
  fsusage.use_percent = 0.100000
[0]
  diskusage.reads = 315302
  diskusage.writes = 6318240
  diskusage.write_bytes = 25879511040
  diskusage.read_bytes = 6561092608
  diskusage.queue = 47457530080206
Segmentation fault

On some systems no output was shown, other than the message “Segmentation fault”.

[2 Jun 2009 14:22] Angelina Elliott

is version 2.0.5 out yet ?