Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

karthikravada31

2 Posts

2597

November 24th, 2014 22:00

Client activation error

Hello All,

when activating a client to appropriate AVAMAR grid we are seeing below error when doing it. can some have a look at this and guide me in getting rid of this error....Need to know actually what this error mean

Error: [/usr/local/avamar/var/avagent.cmd] Invalid flag: "--bigdirgroup"

avagent Error <5062>: [/usr/local/avamar/var/avagent.cmd] Invalid flag: "--bigdirgroup"

avagent.d Info: Client activation error.                   [FAILED]

avagent Info <5008>: Logging to /usr/local/avamar/var/avagent.log

avagent Info <5174>: - Reading /usr/local/avamar/var/avagent.cmd

Error: [/usr/local/avamar/var/avagent.cmd] Invalid flag: "--bigdirgroup"

avagent Error <5062>: [/usr/local/avamar/var/avagent.cmd] Invalid flag: "--bigdirgroup"

avagent.d Info: Could not start client agent.              [FAILED]

tats

--bigdirgroup=400000

--filecachemax=1536

--comstats

ionthegeek

2 Intern

 • 

2K Posts

November 26th, 2014 06:00

  1. None of the flags you've specified here belong in avagent.cmd.
  2. The bigdirgroup flag is deprecated and does nothing.
  3. The maximum size of the monolithic file cache is 1408, making the filecachemax flag listed here do nothing.
  4. The comstats flag will balloon the size of your logs and provide very little information that is useful to an end user -- they may even fill up your disk.

Remove the avagent.cmd file from this client and try the activation again. Please don't add flags in your Avamar environment unless you know exactly what they do.

karthikravada31

2 Posts

November 26th, 2014 18:00

Thanks to Ian Anderson fix.

mhelal_mds

5 Posts

April 8th, 2017 05:00

Hi

i am having a big issue, i woundered if you could help.

i have HQ with AV/DD acting as the target of replication for many single nodes.

one single node crashed and we did re-kick started the node and installed the same avamar version.

now we are trying to configure the replication again but we can not as the system says authentication failure.

can you hep in maing the target forget about the old configuration for the node before we re-kick start.

Was this post helpful?

View All

No Events found!

Top