This post is more than 5 years old
38 Posts
0
15133
July 30th, 2014 23:00
CID: NO LOCATION - RECORD MAY BE CORRUPT
Hello can any one please assist me on this
avagent Error 5320- The client named: client1 is not registered as CID: NO LOCATION - RECORD MAY BE CORRUPT
2013-11-13 09:40:40 avagent Error <5320>: Received from MCS#103:The client named: client1 is not registered as CID: NO LOCATION - RECORD MAY BE CORRUPT
2013-11-13 09:40:40 avagent Error <6210>: Unable to register 'client1' with MCS at utilitynode_addr:28001
Fix:
Delete de client ID file (cid.bin), and re-register.
1 comment:
Thanks that worked for me too.
What happens exactly ?
On what base is the new CID created for the client which has already been backing up.
will the newly created CID match the existing CID records on the Grid.
or the CID on the client is got copied to what already exists on the grid.
If a new CID is created,will the avamar server run a initial full backup as it considers it as a new client
ionthegeek
2 Intern
•
2K Posts
0
August 5th, 2014 05:00
The message "Re-registration of account /path/to/client is not permitted" means that this client has already been activated to this system. If you want to re-register a client, you have to uncheck the "Activated" checkbox in the client properties, then re-activate. This is to prevent a rogue system from impersonating the client.
pawankumawat
355 Posts
0
July 31st, 2014 07:00
Hello,
Have you checked if there is no blocking on port 28001 between client and server ? It should be bidirectional opened.
Regards,
Pawan
pp082c
38 Posts
0
August 1st, 2014 00:00
28001 is the MCS port and i do not have access to that Grid.
please find the below logs and confirm if its problem with the MCS port.
2014-07-31 02:30:31 avagent Error <5320>: Received from MCS#103:The client named: Client1 is not registered as CID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2014-07-31 02:30:31 avagent Error <6210>: Unable to register 'client' with MCS at Grid:28001
2014-07-31 02:30:31 avagent Error <6163>: Registration error: MCS returned error code 103, 'The client named: client1 is not registered as CID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
2014-07-31 02:30:31 avagent Info <5321>: Unable to connect to Management Console (Grid), sleep 29 minutes, 35 seconds before retry
2014-07-31 03:00:06 avagent Info <6626>: Agent Main: Client ID (cid) = xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
2014-07-31 03:00:06 avagent Info <5470>: Updating registration information with the MCS (Grid), paging enabled
2014-07-31 03:00:06 avagent Info <6601>: Hostnamelist: client1, I.P
2014-07-31 03:00:06 avagent Info <5933>: Checking for plugin information files (.pin) in /usr/local/avamar/var
2014-07-31 03:00:06 avagent Info <5933>: Checking for plugin information files (.pin) in /usr/local/avamar/bin
2014-07-31 03:00:06 avagent Info <5934>: Reading pin file /usr/local/avamar/bin/oracle.pin
2014-07-31 03:00:06 avagent Info <7264>: Finished READING xml file - starting parse
2014-07-31 03:00:06 avagent Info <6627>: Checking version of plugin 'Oracle', executable name 'avoracle' (mode:ctl)
2014-07-31 03:00:06 avagent Info <5936>: Plugin version 6.1.101-87 found for Oracle plugin
2014-07-31 03:00:06 avagent Info <12489>: mess 0 '
how could i check if the port is bidirectional from the Grid.
seems the client initially got an acknowledgement from MCS (28001 port) as high lightened above.
pp082c
38 Posts
0
August 1st, 2014 02:00
Hello all.
Initially backups of client were failing on a /cloud/cloud_unix domain with the above mentioned logs.
Tried to re-register the client to same domain where the activation failed.
Re-registration of account /Cloud/Cloud_unix/client is not permitted' (110)
avagent.d Info: Client activation error.
But when i tried to register it and activate it the default /unix domain, it worked.
so im suspecting a CID issue b/w the client and server rather than port issue.
pawankumawat
355 Posts
0
August 1st, 2014 03:00
Hello,
Please try this KB -
https://emc--c.na5.visual.force.com/apex/KB_HowTo?id=kA0700000004KSN
Regards,
Pawan
pp082c
38 Posts
0
August 1st, 2014 03:00
Thank you,
unfortunately i do not have an account / im not authorized to that.
Can you please email me the info on poornachander90@gmail.com
pawankumawat
355 Posts
0
August 1st, 2014 06:00
Please check your email.
Regards,
Pawan
pp082c
38 Posts
0
August 3rd, 2014 18:00
hi Pawan.
Can you please post me the related stuff in that link.
i cannot access that link.
attachment would be good.
On Fri, Aug 1, 2014 at 6:34 PM, pawankumawat
ionthegeek
2 Intern
•
2K Posts
0
August 4th, 2014 16:00
I have branched this discussion into its own thread since it is unrelated to the thread where it was posted.
pp082c
38 Posts
0
August 5th, 2014 01:00
Ian can you please assist me on below.
i was able to run backups after being re-registered the client under /unix domain
Then there was a cid change under cid.bin to what exists on the avamar grid.
Enter the Avamar server domain [clients]: /Cloud/Cloud_unix
avagent.d Info: Stopping Avamar Client Agent (avagent)...
avagent.d Info: Client Agent stopped. [ OK ]
avagent Info <5008>: Logging to /usr/local/avamar/var/avagent.log
avagent Info <5174>: - Reading /usr/local/avamar/var/avagent.cmd
avagent Error <7531>: Unable to register Cloud/Cloud_unix/Client1 with Administrator Grid:28001
'* 110 * Re-registration of account /Cloud/Cloud_unix/Client1 is not permitted' (110)
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
avagent Info <5417>: daemonized as process id xxxxx
avagent.d Info: Client Agent started. [ OK ]
what could be the reason for above error.
now the client exists in both the domains,where one of them is failing.
but i want the same server to be backing up under /cloud/cloud_unix with the remaining cloud servers.
pp082c
38 Posts
0
August 5th, 2014 18:00
Thank you Ian,
This gave me a clear understanding.