Ad Widget

Collapse

Can't allocate shared memory for collector

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • HEMA1
    Member
    • Jun 2008
    • 33

    #1

    Can't allocate shared memory for collector

    I have just downloaded the zabbix_agents_1.4.6.solaris8.sparc.tar and deployed it to a
    5.8 sparc together with the “/etc/zabbix/zabbix_agentd.conf” the problem is: when I try to start
    The agent i get (in zabbix_agentd.log):

    1731:20081114:153504 zabbix_agentd started. ZABBIX 1.4.6.
    1731:20081114:153504 Can't allocate shared memory for collector. [Invalid argument]

    When I run ipcs I can see that:
    s 4 0x7a0f8c13 --ra-ra-ra- 1001 zabbix
    s 786437 0x7a0f848a --ra-ra-ra- zabbix zabbix


    any suggestions?


    TNX
    Hema1
  • mister
    Junior Member
    • Mar 2008
    • 7

    #2
    Answered in this thread: http://www.zabbix.com/forum/showthread.php?t=7348

    The default shared memory limit on solaris 8 (and before) was extremely small by today's standards. You need to adjust it up by adding options your /etc/system file and rebooting.

    set shmsys:shminfo_shmmax=2147483648
    set shmsys:shminfo_shmseg=20

    You can pick another value for your shared mem max. My example is relatively huge at like 2GB (it was database server).

    You could go with something smaller if you want, but a large value doesn't really matter - it's just a limit and other factors almost always limit any issues before solaris would ever actually care about that limit.

    Comment

    • HEMA1
      Member
      • Jun 2008
      • 33

      #3
      shmsys

      Tnx fore the reply, do you know how much shared memory zabbix agent 1.4.* and 1.6.*demands.
      TNX
      Hema1

      Comment

      • mister
        Junior Member
        • Mar 2008
        • 7

        #4
        Last message in the other thread. Looks like 2MB.

        Old Sol 8 default is (was?) 1 MB.

        But as mentioned, its very unlikely to be a issue setting it much higher. A few of my old sol8 systems have a setting higher than the physical ram to avoid requiring a reboot to up the setting at some point. It's never been a problem.

        Comment

        • mister
          Junior Member
          • Mar 2008
          • 7

          #5
          Hmm.

          You probably don't need the "shmsys:shminfo_shmseg" setting either. That was just tied in with the DB requirements on my system.

          Comment

          Working...