UNSOLVED

Ix1

updated

17 years ago

I

Ix1

1 Message

0

6316

May 22nd, 2009 07:00

Solaris clients not backing up

Is there a way to restart the avamar clients on these solaris boxes? I am getting Timed out - Start, and when we try to manually backup they just sit and state Queued. Help plz
  • Zhou

    1 Rookie

    •

    53 Posts

    1574

    0

    Posted May 22nd, 2009 14:00

    1.login as root
    2. run /etc/init.d/avagent stop; /etc/init.d/avagent start
  • Randeep_Singh

    1 Rookie

    •

    74 Posts

    1574

    0

    Posted May 22nd, 2009 21:00

    Try uninstalling and install it again. Then check whether same problems persists.
  • Serg_Shu

    4 Posts

    1574

    0

    Posted July 21st, 2011 02:00

    I have same problem. How I can solve it?

  • 1574

    0

    Posted July 21st, 2011 02:00

    If a client backup is reported in the activity monitor as "Timed Out - Start" it doesn't necessarily mean that the client isn't working properly or that it needs restarting.

    The Avamar server may have been too busy servicing other client backups and didn't reach this client before its backup schedule ended.

    Make sure the backup isn't scheduled to run during the maintenance window when backup session capacity is limited to 2 per data node and check that there are enough nodes to service all clients. 

    The likelihood of seeing "Timed out - start" failures will increase if you have relatively few data nodes but have lots of clients which take a significant amount of time to perform backups (therefore hogging the limited session availability).

  • Serg_Shu

    4 Posts

    1574

    0

    Posted July 21st, 2011 05:00

    First I try to restart Solaris client (V880). In logs lot of lines end with:

    2011-07-21 15:16:05 avagent Info <7452>: Registration of client /clients/V880 with MCS avamar:28001 successful.
    2011-07-21 15:16:05 avagent Info <5928>: Registration of plugin 2001 Unix successful.
    2011-07-21 15:16:05 avagent Info <5619>: Registration of client and plugins complete.
    2011-07-21 15:16:05 avagent Info <7150>: first work request delayed for 180 seconds.

    Avamar is my backup server.

    When I start backup manualy in Solaris client log is

    2011-07-21 15:18:55 avagent Info <5962>: Wake up message received

    2011-07-21 15:18:55 avagent Info <7151>: first work request delay finished.


    2011-07-21 15:18:55 avagent Info <5964>: Requesting work from avamar

    2011-07-21 15:18:55 avagent Info <5962>: Wake up message received

    In Avamar administration on "Activity" pane this backup freeze as "Waiting-Client" on 5 min.
    In logs:
    2011-07-21 15:18:55 avagent Info <7151>: first work request delay finished.

    2011-07-21 15:18:55 avagent Info <5964>: Requesting work from avamar
    2011-07-21 15:18:55 avagent Info <5962>: Wake up message received
    2011-07-21 15:23:55 avagent Warning <6556>: TCP timeout on receive ack (seconds 300)
    2011-07-21 15:23:55 avagent Warning <5473>: Null message received from MCS
    2011-07-21 15:23:55 avagent Info <5435>: Exiting work request session
    2011-07-21 15:23:55 avagent Info <5321>: Unable to connect to Management Console (avamar), sleep 26 minutes, 42 seconds before retry
    2011-07-21 15:23:55 avagent Info <6589>: Agent Main: Client ID (cid) = 5619574b2c779978cd8b0a056f19ad730ac5091b
    2011-07-21 15:23:55 avagent Info <5470>: Updating registration information with the MCS (avamar), paging enabled
    2011-07-21 15:23:55 avagent Info <6564>: Hostnamelist: v880,m3000,loghost,m3000.latrostrans.lv,v880.lrt.lv,192.168.1.4,bge3_avamar,192.168.2.2,192.168.224.2
    2011-07-21 15:23:55 avagent Info <5933>: Checking for plugin information files (.pin) in /opt/AVMRclnt/var
    2011-07-21 15:23:55 avagent Info <5933>: Checking for plugin information files (.pin) in /opt/AVMRclnt/bin
    2011-07-21 15:23:55 avagent Info <5934>: Reading pin file /opt/AVMRclnt/bin/unix.pin
    2011-07-21 15:23:55 avagent Info <7225>: Finished READING xml file - starting parse
    2011-07-21 15:23:55 avagent Info <6590>: Checking version of plugin 'Unix', executable name 'avtar.bin' (mode:ctl)
    2011-07-21 15:23:55 avagent Info <5936>: Plugin version 5.0.106-28 found for Unix plugin
    2011-07-21 15:23:56 avagent Info <7451>: Client registration updated 5619574b2c779978cd8b0a056f19ad730ac5091b avamar(1291379152)
    2011-07-21 15:23:56 avagent Info <6573>:

    ****** Current MCS name 'avamar' ******

    2011-07-21 15:23:56 avagent Info <7452>: Registration of client /clients/V880 with MCS avamar:28001 successful.
    2011-07-21 15:23:56 avagent Info <5928>: Registration of plugin 2001 Unix successful.
    2011-07-21 15:23:56 avagent Info <5619>: Registration of client and plugins complete.

    2011-07-21 15:23:56 avagent Info <5964>: Requesting work from avamar
    2011-07-21 15:23:56 avagent Info <5264>: Workorder received: sleep
    2011-07-21 15:23:56 avagent Info <5996>: Sleeping 60 seconds
    2011-07-21 15:24:00 avagent Info <5962>: Wake up message received

    2011-07-21 15:24:00 avagent Info <5964>: Requesting work from avamar
    2011-07-21 15:24:00 avagent Error <0000>: CTL: cancel on workorder "Sun group-1311250735672" not running.

    2011-07-21 15:24:10 avagent Info <5964>: Requesting work from avamar
    2011-07-21 15:24:10 avagent Info <5264>: Workorder received: sleep
    2011-07-21 15:24:10 avagent Info <5996>: Sleeping 240 seconds
    In "Activity" this task stay in "TimedOut-Response" with status code summary:
    status_code_summary Activity failed - client was given a workorder but did not acknowledge its receipt.
    How I can localize this problem?

  • ralpmat

    1 Message

    1574

    0

    Posted March 7th, 2014 09:00

    Hi Sergey,

    we are getting exactly the same error (3 years on I know), with Avamar client 6.1.101-87 on Solaris 10. Again, agent starts, requests work, and sleeps, then the grid just changes from 'waiting on client' to 'TimedOut-Response' - the client has never started off the job.

    truss-ing the avamar client process shows a lot of ETIME error messages:

    /2: lwp_park(0x00000000, 0)     (sleeping...)
    /6: lwp_park(0xFE99BA98, 0)                     Err#62 ETIME
    /5: lwp_park(0xFEA9BAF0, 0)                     Err#62 ETIME
    /6: lwp_park(0xFE99BA98, 0)     (sleeping...)
    /5: lwp_park(0xFEA9BAF0, 0)     (sleeping...)
    /7: lwp_park(0xFE89BB70, 0)                     Err#62 ETIME
    /7: lwp_park(0xFE89BB70, 0)     (sleeping...)

    Did you ever find a resolution to this?

    Thanks,

    Matt

  • Gontse_Len

    1 Rookie

    •

    11 Posts

    1574

    0

    Posted March 28th, 2014 05:00

    Ix if the solution I have only works for Exchange DAGs. If it was Exchange DAGs you would have to restart the DAGs Service on DAG's (cluster) manager