1 Reply Latest reply on Jul 14, 2015 3:38 PM by tlange

    Agents will not start on bootup

    mshubaly

      I have one Ubuntu client that will not start the McAfee agent on startup. This is the only client that I have found this issue on and I have tried reinstall and same issue.

       

      When the agents are started manually there are no issue.

       

      When started I get the one liner in syslog

      Jul 13 11:13:51 localhost Starting %s: cma

       

      After bootup there is no mention of cma in syslog and no errors in dmesg either.

       

      The OS is as follows

      Linux HOSTNAMEXXX 3.16.0-43-generic #58~14.04.1-Ubuntu SMP Mon Jun 22 10:21:20 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

       

      I have dozens of clients running the exact OS as this is a standard image.

       

      the cma file is under /etc/init.d

       

      I can manually start and stop the agents without issue. There is one error message I do get but it doesn't seem to stop the agent from starting.

       

      user:/var/log$ sudo service cma stop

      Shutting down McAfee Agent services...                     [  OK  ]
      user:/var/log$ sudo service cma start

      touch: cannot touch '/var/lock/subsys/cma': No such file or directory

      user:/var/log$ ps -ef | grep McA
      root      8169     1  2 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8175  8169  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8176  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8177  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8178  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8179  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8180  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8181  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8182  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8183  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8184  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8185  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8186  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8187  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8188  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8189  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8190  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      root      8191  8175  0 11:38 ?        00:00:00 /opt/McAfee/cma/bin/cma
      user   8193  6510  0 11:38 pts/14   00:00:00 grep --color=auto McA

       

      Any ideas where I can look to determine why the agent does not start up on bootup and only manually.