hcimonitord Virtual Memory too full error

Clovertech Forums Read Only Archives Cloverleaf General hcimonitord Virtual Memory too full error

  • Creator
    Topic
  • #52496
    Elden Jahnke
    Participant

      Hello

      We are attempting a fresh install but getting the following error when trying to startup the engine

      ************************************

      Command Issued:    hcisitectl

      Command status:     0

      Lockmgr    is NOT running

      hcimonitord is NOT running

      ************************************

      Command Issued:    hcisitectl -S

      Command status:     0

      Starting lm_ip

      Starting hcimonitord

      Lockmgr    is running on pid 27215

      hcimonitord is NOT running

      Virtual memory is too full; must be less than nan

      hcimonitord failed to execute properly

      We are running on a RHEL5 virtual machine with 2Gb of RAM and 4 Gb of swap

      Our kernel parameters seem to satisfy your requirements according to your guide

      [root@ontempd0aav002 site1]# more /proc/sys/kernel/shmmax

      68719476736

      [root@ontempd0aav002 site1]# more /proc/sys/kernel/sem

      250     32000   100     256

      [root@ontempd0aav002 site1]# more /proc/sys/fs/file-max

      193458

      [root@ontempd0aav002 site1]#

      no logfile is produced inside /opt/app/quovadx/qdx5.4.1/integrator/site1/exec/hcimonitord/

    Viewing 2 reply threads
    • Author
      Replies
      • #74466
        Ron Ridley
        Participant

          What is the output of either ‘free’ or ‘vmstat’?

        • #74467
          Elden Jahnke
          Participant

            here is the output

            [root@ontempd0aav002 ~]# free

                        total       used       free     shared    buffers     cached

            Mem:       1992888    1201432     791456          0     275172     761804

            -/+ buffers/cache:     164456    1828432

            Swap:      4192956          0    4192956

            [root@ontempd0aav002 ~]# vmstat

            procs


            memory


            —swap–


            io—- –system–


            cpu


            r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st

            0  0      0 791448 275184 761804    0    0     1     3    4   47  0  0 100  0  0

            [root@ontempd0aav002 ~]#

            on another note, it seems the integrator comes with it’s own TOP binary inside the /bin directory. Here is the output that command produces. Notice that the Memory information is blank. Perhaps that’s causing the issue?

            were running Linux ontempd0aav002.mgt.ont.srv 2.6.18-238.9.1.el5 #1 SMP Fri Mar 18 12:42:39 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux

            CPUs:  2; last pid: 10324;  load averages:  0.00,  0.00,  0.00                                                             09:36:26

            107 processes: 1 running, 106 sleeping

            CPU states:  0.0% user,  0.0% nice,  0.0% system,  100% idle

            Memory:

             PID USERNAME PRI NICE  SIZE   RES STATE   TIME   WCPU    CPU COMMAND

            6492 hci       24    0  233M   27M sleep   1:21  0.00%  0.00% java

            2816 root      15    0   17M 1284K sleep   0:09  0.00%  0.00% vmware-guestd

               2 root     -100   -5    0K    0K sleep   0:00  0.00%  0.00% migration/0

            3835 avahi     15    0   23M 1364K sleep   0:00  0.00%  0.00% avahi-daemon

            3580 haldaemo  16    0   31M 4584K sleep   0:00  0.00%  0.00% hald

               1 root      15    0   10M  636K sleep   0:00  0.00%  0.00% init

               4 root     -100   -5    0K    0K sleep   0:00  0.00%  0.00% migration/1

            2096 root      10   -5    0K    0K sleep   0:00  0.00%  0.00% kjournald

          • #74468
            Elden Jahnke
            Participant

              I believe “nan” stands for a generic error for “Not a Number”

              So perhaps the top command having memory information blanked is causing that generic error

          Viewing 2 reply threads
          • The forum ‘General’ is closed to new topics and replies.