Ad Widget

Collapse

Compile on Sparc / Solaris 10 - system.cpu.util not works

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • uakm2201
    Junior Member
    • Mar 2009
    • 2

    #1

    Compile on Sparc / Solaris 10 - system.cpu.util not works

    Hello all,

    I'm coming to this forum to have a little help.
    I'm actually working on a Solaris Box and I have some small problems.
    My system is a Sparc system with 4 cpus, Solaris 10.
    I'm using GNU gcc 3.4.6.
    When I compiling the agent, I have no problem, but when I try to monitor the system, the agent tell that system.cpu.util is not supported.

    So, I'm trying to investigate.

    I'm joining my config.log, because I think that it's the first point to check, but I'm not expert and can't analyze this file.

    Can someone could tell me if this log is 'normal' ?
    Attached Files
  • NomenNescio
    Member
    • Jan 2009
    • 70

    #2
    I think I've got the same problem. :-( only I'm using solaris 8

    Edit: I've discoverd that only system.cpu.util[all] works but system.cpu.util[all,,avg1] or system.cpu.util[all,,avg5] doesn't work.

    Edit: My bad, looks like average is not supported in solaris :-(
    Last edited by NomenNescio; 24-03-2009, 15:35.

    Comment

    • NOB
      Senior Member
      Zabbix Certified Specialist
      • Mar 2007
      • 469

      #3
      Originally posted by NomenNescio
      I think I've got the same problem. :-( only I'm using solaris 8

      Edit: I've discoverd that only system.cpu.util[all] works but system.cpu.util[all,,avg1] or system.cpu.util[all,,avg5] doesn't work.

      Edit: My bad, looks like average is not supported in solaris :-(
      Hi

      I have this item system.cpu.load[all,avg1]working with the Solaris 1.4.4 agent and one patch which was published in the appropriate forum (Patches).
      The patch works with 1.4.6, too.
      Replace three occurences of #ifdef HAVE_PROC_LOADAVG in src/libs/zbxsysinfo/solaris/cpu.c by #ifdef HAVE_GETLOADAVG and
      that's it.

      It should been fixed in the 1.6.x series of agents. At least the
      current nightly build looks fine.

      HTH,

      Norbert.

      Comment

      Working...