Start a Conversation

Unsolved

This post is more than 5 years old

4213

April 26th, 2013 02:00

Paging turned off

Hi,

We had restarted avagent service on a linux client and since then, the paging is turned off for this client and browing is disabled.
The paging is set to automatic and IP address and port fields are not getting populated.

Found errors in avagent.log on the client:

[agentlisten(non-loopback)]  ERROR: <0001> agent_listen::body, cannot create server socket for port 28002

avagent Error <5467>: Cannot create listen port (28002) - waiting 30 minutes, possible alternate avagent running

I could see only one avagent running.

ps -ef | grep -i av

root     30650     1  0 Apr24 ?        00:00:29 /usr/local/avamar/bin/avagent.bin --bindir="/usr/local/avamar/bin" --vardir="/usr/local/avamar/var" --sysdir="/usr/local/avamar/etc" --logfile="/usr/local/avamar/var/avagent.log"

netstat shows port 28002 listening.

netstat -an | grep 28
tcp        0      0 0.0.0.0:28002           0.0.0.0:*               LISTEN

Any clues ?

11 Posts

May 6th, 2013 05:00

Anyone ?

38 Posts

August 27th, 2014 05:00

Hi,

Is your issue resolved !

Paging should be enabled

did you check ping to the backup server from the client.

please add routes if the ping is not reachable.

generally avagent processes which lock the f_cache file may terminate without releasing the lock,this causes the new process to preempt when requested for the same cache file.

try re-registering the client, this should solve your issue

October 15th, 2014 13:00

Hello, I am having the same issue with a version 7 agent on two sever 2003 machines. Meaning, that I get the same error and my client cannot start. It does not appear that there is already a service using port 28002 by running a netstat command. Verified that there are not multiple processes running. Unable to register at all because this error happens while the client is first initializing. Ping is reachable in both directions. Any advice could be helpful. Thank you.

2014/10/15-20:39:24.40100 [agentlisten(non-loopback)]  ERROR: <0001> agent_listen::body, cannot create server socket for port 28002

2014-10-15 13:39:24 avagent Error <5467>: Cannot create listen port (28002) - waiting 30 minutes, possible alternate avagent running

2014-10-15 13:39:24 avagent Info <5360>: Agent listening(loopback) on interface '127.0.0.1' address 127.0.0.1:24472 port 24472.

2014-10-15 13:39:54 avagent Warning <10506>: Default sup receive queue not created yet

2014-10-15 13:39:54 avagent Warning <8659>: No non-loopback listen port opened, continuing anyway

2014-10-15 13:39:54 avagent Info <9976>: Initializing agent settings from D:\Program Files\avs\var\agentsettings.xml

2014-10-15 13:39:54 avagent Info <6628>: Agent Update: Client ID (cid) = 0

2014-10-15 13:39:54 avagent Info <5963>: Agent will automatically re-update to the Administrator some time after 2014-10-16 13:20:54

2014-10-15 13:39:54 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:39:54 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:39:54 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:39:54 avagent Info <5321>: Unable to connect to Management Console (), sleep 42 minutes, 41 seconds before retry

2014-10-15 13:44:54 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:44:54 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:44:54 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:44:54 avagent Info <5321>: Unable to connect to Management Console (), sleep 43 minutes, 15 seconds before retry

2K Posts

October 15th, 2014 13:00

Is there further information in the avagent.log file?

October 15th, 2014 14:00

Yes, thank you for the reply. The following is the contents of this log file:

--------------------------------------------------------------------------------------------------------

-----  START avagent log 2014-10-15 13:39:24 Pacific Daylight Time  [7.0.101-61 Windows Server 2003 Standard Server Edition Service Pack 2-x86]

--------------------------------------------------------------------------------------------------------

2014/10/15-20:39:24.01099 [avagent]  Debug output redirected

2014-10-15 13:39:24 avagent Info <5008>: Logging to D:\Program Files\avs\var\avagent.log

2014/10/15-20:39:24.01099 [avagent]  Config: VARDIR=D:\Program Files\avs\var, HOMEDIR=

2014/10/15-20:39:24.01099 [avagent]  Looking for flag file "D:\Program Files\avs\var\avamar.cmd"

2014/10/15-20:39:24.01099 [avagent]  Looking for flag file "D:\Program Files\avs\var\avagent.cmd"

2014/10/15-20:39:24.01099 [avagent]  Looking for flag file "D:\Program Files\avs\var\.avagent"

2014/10/15-20:39:24.01099 [avagent]  Looking for flag file "D:\Program Files\avs\var\avagent.cfg"

2014-10-15 13:39:24 avagent Info <5702>: Command Line: avbackup --service --logfile=D:\Program Files\avs\var\avagent.log

2014-10-15 13:39:24 avagent Info <5703>: Parsed Flags: avbackup --service --logfile="D:\Program Files\avs\var\avagent.log"

2014-10-15 13:39:24 avagent Info <5210>: bindir:'D:\Program Files\avs\bin'

2014-10-15 13:39:24 avagent Info <5211>: vardir:'D:\Program Files\avs\var'

2014-10-15 13:39:24 avagent Info <5212>: sysdir:'D:\Program Files\avs\etc'

2014-10-15 13:39:24 avagent Info <5437>: hostname:'portalweb1'

2014-10-15 13:39:24 avagent Info <6986>: netbind: ''

2014-10-15 13:39:24 avagent Info <5969>: Host "portalweb1": 8 CPU, 3326 MB, running as "NT AUTHORITY\SYSTEM"

2014-10-15 13:39:24 avagent Info <6601>: Hostnamelist: portalweb1.yvmh.org,10.35.2.101,localhost,127.0.0.1

2014-10-15 13:39:24 avagent Info <7324>: Volume Type for "D:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1, Hardlinks=0

2014-10-15 13:39:24 avagent Info <5933>: Checking for plugin information files (.pin) in D:\Program Files\avs\bin

2014-10-15 13:39:24 avagent Info <5934>: Reading pin file D:\Program Files\avs\bin\update.pin

2014-10-15 13:39:24 avagent Info <7264>: Finished READING xml file - starting parse

2014-10-15 13:39:24 avagent Info <6627>: Checking version of plugin 'update', executable name 'avupdate' (mode:ctl)

2014-10-15 13:39:24 avagent Info <5936>: Plugin version 7.0.101-61 found for update plugin

2014-10-15 13:39:24 avagent Info <12489>: mess 0 '

'

2014-10-15 13:39:24 avagent Info <5934>: Reading pin file D:\Program Files\avs\bin\windows.pin

2014-10-15 13:39:24 avagent Info <7264>: Finished READING xml file - starting parse

2014-10-15 13:39:24 avagent Info <6627>: Checking version of plugin 'Windows', executable name 'avtar' (mode:ctl)

2014-10-15 13:39:24 avagent Info <5936>: Plugin version 7.0.101-61 found for Windows plugin

2014-10-15 13:39:24 avagent Info <12489>: mess 1 '

'

2014/10/15-20:39:24.40100 [agentlisten(non-loopback)]  ERROR: <0001> agent_listen::body, cannot create server socket for port 28002

2014-10-15 13:39:24 avagent Error <5467>: Cannot create listen port (28002) - waiting 30 minutes, possible alternate avagent running

2014-10-15 13:39:24 avagent Info <5360>: Agent listening(loopback) on interface '127.0.0.1' address 127.0.0.1:24472 port 24472.

2014-10-15 13:39:54 avagent Warning <10506>: Default sup receive queue not created yet

2014-10-15 13:39:54 avagent Warning <8659>: No non-loopback listen port opened, continuing anyway

2014-10-15 13:39:54 avagent Info <9976>: Initializing agent settings from D:\Program Files\avs\var\agentsettings.xml

2014-10-15 13:39:54 avagent Info <6628>: Agent Update: Client ID (cid) = 0

2014-10-15 13:39:54 avagent Info <5963>: Agent will automatically re-update to the Administrator some time after 2014-10-16 13:20:54

2014-10-15 13:39:54 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:39:54 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:39:54 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:39:54 avagent Info <5321>: Unable to connect to Management Console (), sleep 42 minutes, 41 seconds before retry

2014-10-15 13:44:54 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:44:54 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:44:54 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:44:54 avagent Info <5321>: Unable to connect to Management Console (), sleep 43 minutes, 15 seconds before retry

2014-10-15 13:49:54 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:49:54 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:49:54 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:49:54 avagent Info <5321>: Unable to connect to Management Console (), sleep 18 minutes, 43 seconds before retry

2014-10-15 13:54:55 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:54:55 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:54:55 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:54:55 avagent Info <5321>: Unable to connect to Management Console (), sleep 16 minutes, 18 seconds before retry

2014-10-15 13:59:55 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 13:59:55 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 13:59:55 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 13:59:55 avagent Info <5321>: Unable to connect to Management Console (), sleep 33 minutes, 42 seconds before retry

2014-10-15 14:04:55 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:04:55 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:04:55 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:04:55 avagent Info <5321>: Unable to connect to Management Console (), sleep 30 minutes, 20 seconds before retry

2014-10-15 14:09:24 avagent Info <5468>: Retrying create of listen port (28002)

2014/10/15-21:09:24.41300 [agentlisten(non-loopback)]  ERROR: <0001> agent_listen::body, cannot create server socket for port 28002

2014-10-15 14:09:24 avagent Error <5467>: Cannot create listen port (28002) - waiting 30 minutes, possible alternate avagent running

2014-10-15 14:09:55 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:09:55 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:09:55 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:09:55 avagent Info <5321>: Unable to connect to Management Console (), sleep 37 minutes, 11 seconds before retry

2014-10-15 14:14:56 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:14:56 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:14:56 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:14:56 avagent Info <5321>: Unable to connect to Management Console (), sleep 15 minutes, 42 seconds before retry

2014-10-15 14:19:56 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:19:56 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:19:56 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:19:56 avagent Info <5321>: Unable to connect to Management Console (), sleep 23 minutes, 50 seconds before retry

2014-10-15 14:24:56 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:24:56 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:24:56 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:24:56 avagent Info <5321>: Unable to connect to Management Console (), sleep 40 minutes, 30 seconds before retry

2014-10-15 14:29:56 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:29:56 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:29:56 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:29:56 avagent Info <5321>: Unable to connect to Management Console (), sleep 38 minutes, 30 seconds before retry

2014-10-15 14:34:56 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:34:56 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:34:56 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:34:56 avagent Info <5321>: Unable to connect to Management Console (), sleep 16 minutes, 29 seconds before retry

2014-10-15 14:39:24 avagent Info <5468>: Retrying create of listen port (28002)

2014/10/15-21:39:24.42400 [agentlisten(non-loopback)]  ERROR: <0001> agent_listen::body, cannot create server socket for port 28002

2014-10-15 14:39:24 avagent Error <5467>: Cannot create listen port (28002) - waiting 30 minutes, possible alternate avagent running

2014-10-15 14:39:57 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 14:39:57 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 14:39:57 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 14:39:57 avagent Info <5321>: Unable to connect to Management Console (), sleep 42 minutes, 38 seconds before retry

October 15th, 2014 15:00

Thanks for the reply.

I wondered about the permission problem, earlier I tried running the service as a administrator user with the same result.

I ran your netstat command and it returns no response.

I changed the listenport and received a slightly different response (pasted in below) but it still seems to error out. May just be a support call on this one. Thanks again for looking.

--------------------------------------------------------------------------------------------------------

-----  START avagent log 2014-10-15 15:38:36 Pacific Daylight Time  [7.0.101-61 Windows Server 2003 Standard Server Edition Service Pack 2-x86]

--------------------------------------------------------------------------------------------------------

2014/10/15-22:38:36.64299 [avagent]  Debug output redirected

2014-10-15 15:38:36 avagent Info <5008>: Logging to D:\Program Files\avs\var\avagent.log

2014/10/15-22:38:36.64299 [avagent]  Config: VARDIR=D:\Program Files\avs\var, HOMEDIR=

2014/10/15-22:38:36.64299 [avagent]  Looking for flag file "D:\Program Files\avs\var\avamar.cmd"

2014/10/15-22:38:36.64299 [avagent]  Looking for flag file "D:\Program Files\avs\var\avagent.cmd"

2014-10-15 15:38:36 avagent Info <5174>: - Reading D:\Program Files\avs\var\avagent.cmd

2014/10/15-22:38:36.64299 [avagent]  Looking for flag file "D:\Program Files\avs\var\.avagent"

2014/10/15-22:38:36.64299 [avagent]  Looking for flag file "D:\Program Files\avs\var\avagent.cfg"

2014-10-15 15:38:36 avagent Info <5702>: Command Line: avbackup --service --logfile=D:\Program Files\avs\var\avagent.log

2014-10-15 15:38:36 avagent Info <5703>: Parsed Flags: avbackup --acport=28777 --service --logfile="D:\Program Files\avs\var\avagent.log"

2014-10-15 15:38:36 avagent Info <5210>: bindir:'D:\Program Files\avs\bin'

2014-10-15 15:38:36 avagent Info <5211>: vardir:'D:\Program Files\avs\var'

2014-10-15 15:38:36 avagent Info <5212>: sysdir:'D:\Program Files\avs\etc'

2014-10-15 15:38:36 avagent Info <5437>: hostname:'portalweb2'

2014-10-15 15:38:36 avagent Info <6986>: netbind: ''

2014-10-15 15:38:36 avagent Info <5969>: Host "portalweb2": 8 CPU, 3326 MB, running as "NT AUTHORITY\SYSTEM"

2014-10-15 15:38:36 avagent Info <6601>: Hostnamelist: portalweb2.yvmh.org,10.35.2.102,localhost,127.0.0.1

2014-10-15 15:38:36 avagent Info <5933>: Checking for plugin information files (.pin) in D:\Program Files\avs\bin

2014-10-15 15:38:36 avagent Info <7324>: Volume Type for "D:\" is "NTFS", Supports Compression=1, Encryption=1, ACLS=1, DataStreams=1, Reparse=1, Sparse=1, Hardlinks=0

2014-10-15 15:38:36 avagent Info <5934>: Reading pin file D:\Program Files\avs\bin\update.pin

2014-10-15 15:38:36 avagent Info <7264>: Finished READING xml file - starting parse

2014-10-15 15:38:36 avagent Info <6627>: Checking version of plugin 'update', executable name 'avupdate' (mode:ctl)

2014-10-15 15:38:36 avagent Info <5936>: Plugin version 7.0.101-61 found for update plugin

2014-10-15 15:38:36 avagent Info <12489>: mess 0 '

'

2014-10-15 15:38:36 avagent Info <5934>: Reading pin file D:\Program Files\avs\bin\windows.pin

2014-10-15 15:38:36 avagent Info <7264>: Finished READING xml file - starting parse

2014-10-15 15:38:36 avagent Info <6627>: Checking version of plugin 'Windows', executable name 'avtar' (mode:ctl)

2014-10-15 15:38:37 avagent Info <5936>: Plugin version 7.0.101-61 found for Windows plugin

2014-10-15 15:38:37 avagent Info <12489>: mess 1 '

'

2014-10-15 15:38:37 avagent Info <5360>: Agent listening(loopback) on interface '127.0.0.1' address 127.0.0.1:21978 port 21978.

2014-10-15 15:38:37 avagent Info <9928>: Agent listening(non-loopback) on interface 'all' address (error):28777 port 28777.

2014-10-15 15:38:38 avagent Info <9976>: Initializing agent settings from D:\Program Files\avs\var\agentsettings.xml

2014-10-15 15:38:38 avagent Info <6628>: Agent Update: Client ID (cid) = 0

2014-10-15 15:38:38 avagent Info <5963>: Agent will automatically re-update to the Administrator some time after 2014-10-16 15:19:38

2014-10-15 15:38:38 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 15:38:38 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 15:38:38 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 15:38:38 avagent Info <5321>: Unable to connect to Management Console (), sleep 43 minutes, 58 seconds before retry

2014-10-15 15:43:38 avagent Info <5705>: Updating IP address with the MCS. local IP='10.35.2.102', registered IP='(none)', port changed:false

2014-10-15 15:43:38 avagent Info <6601>: Hostnamelist: portalweb2.yvmh.org,10.35.2.102,localhost,127.0.0.1

2014-10-15 15:43:38 avagent Info <5933>: Checking for plugin information files (.pin) in D:\Program Files\avs\var

2014-10-15 15:43:38 avagent Info <5933>: Checking for plugin information files (.pin) in D:\Program Files\avs\bin

2014-10-15 15:43:38 avagent Info <5934>: Reading pin file D:\Program Files\avs\bin\update.pin

2014-10-15 15:43:38 avagent Info <7264>: Finished READING xml file - starting parse

2014-10-15 15:43:38 avagent Info <6627>: Checking version of plugin 'update', executable name 'avupdate' (mode:ctl)

2014-10-15 15:43:38 avagent Info <5936>: Plugin version 7.0.101-61 found for update plugin

2014-10-15 15:43:38 avagent Info <12489>: mess 0 '

'

2014-10-15 15:43:38 avagent Info <5934>: Reading pin file D:\Program Files\avs\bin\windows.pin

2014-10-15 15:43:38 avagent Info <7264>: Finished READING xml file - starting parse

2014-10-15 15:43:38 avagent Info <6627>: Checking version of plugin 'Windows', executable name 'avtar' (mode:ctl)

2014-10-15 15:43:38 avagent Info <5936>: Plugin version 7.0.101-61 found for Windows plugin

2014-10-15 15:43:38 avagent Info <12489>: mess 1 '

'

2014-10-15 15:43:38 avagent Info <5470>: Updating registration information with the MCS (), paging enabled

2014-10-15 15:43:38 avagent Info <18054>: agent_commands::register_agent Registered MC address = 10.35.2.102

2014-10-15 15:43:38 avagent Error <6210>: Unable to register 'portalweb2' with MCS at :28001

2014-10-15 15:43:38 avagent Error <7500>: Registration error: NULL message received

2014-10-15 15:43:38 avagent Error <6053>: Error trying to update MCS with new ip address

2014-10-15 15:43:38 avagent Info <6626>: Agent Main: Client ID (cid) = 0

2014-10-15 15:43:38 avagent Info <5363>: Skipping registration, no MCS name

2014-10-15 15:43:38 avagent Info <5434>: MCS unknown, entering listen mode.

2014-10-15 15:43:38 avagent Info <5321>: Unable to connect to Management Console (), sleep 44 minutes, 58 seconds before retry

2K Posts

October 15th, 2014 15:00

It's possible for this issue to be caused by permissions but I don't believe that is the issue here because the log shows avagent starting under the SYSTEM account which should have all the required permissions.

The only similar issues I've found in the escalation database were caused by avagent trying to listen on port 28002 when there was already a process listening there.

What do you see if you open a command prompt as an Administrator (right-click => Run as administrator) and run the following command?

netstat -ano | findstr /c:"28002"

You should see something like this:

C:\Users\testuser>netstat -ano | findstr /c:"28002"

  TCP    0.0.0.0:28002          0.0.0.0:0              LISTENING      2072

  TCP    127.0.0.1:28002        127.0.0.1:49584        ESTABLISHED    2072

  TCP    127.0.0.1:49584        127.0.0.1:28002        ESTABLISHED    6480

If you open up Task Manager, move to the processes tab and sort by PID, you should be able to match the process id in the rightmost column of the netstat output's LISTENING line to a process name. If this process is avagent.exe, then there is already an agent running. If this is some other process, the port is already in use and one process or the other will have to move to a different port.

You can change the listen port for avagent by creating a file called avagent.cmd in the Avamar client's var directory and adding the following line (where 1234 is the port you would like avagent to listen on):

--listenport=1234

If avagent.cmd already exists, open it in an editor and add the listenport flag on its own line.

If you change the listen port for avagent, you will have to restart the Avamar Backup service and update the paging settings for the client in the Avamar Administrator GUI.

If you don't see a LISTENING line, I would recommend opening up a service request.

2K Posts

October 15th, 2014 16:00

The error messages in the most recent log you've posted show that the client doesn't know the address for the Avamar server. If you reactivate the client, that should fix the most recent issue.

2K Posts

October 16th, 2014 08:00

The avscc process that provides the system tray icon doesn't know the agent port has changed so it's not able to communicate with avagent.

You can set the port by specifying the flag --acport=1234 in avscc.cmd, then exiting and restarting the Avamar client interface. You can exit by right-clicking the Avamar icon and selecting Exit. The client interface should be in the start menu as EMC Avamar => client.

October 16th, 2014 08:00

The Avamar client hangs for a while with the status of Initializing and then eventually has a status of "No connection to agent", and so the "Activate Client" option is greyed out.

October 16th, 2014 08:00

Looks like that worked for me. Not sure why the original port would not bind to begin with, but that did the trick. Thanks for your help and the learning experience!

2K Posts

October 16th, 2014 09:00

Glad to hear you got it working! Don't forget to update the paging settings for this client in the Administrator GUI or you won't be able to browse it.

My pleasure!

No Events found!

Top