Avamar: Replikering starter ikke, fordi Avagent er nede

Replikering kører ikke eller får status "Venter-klient".

Replikering starter ikke, forbliver i venteklientstatus på grund af avagenten er nede.

1. Log på Avamar Utility Node som administrator.

2. Løft til rod.

3. Tjek avagent Status med følgende Systemctl eller service Kommando:

root@avamar:~/#: systemctl status avagent
● avagent.service - Avamar Unix backup/restore agent (avagent)
   Loaded: loaded (/usr/lib/systemd/system/avagent.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2024-04-25 11:21:42 CDT; 3 weeks 3 days ago
 Main PID: 1998 (avagent.bin)
    Tasks: 9
   CGroup: /system.slice/avagent.service
           └─1998 /usr/local/avamar/bin/avagent.bin --bindir="/usr/local/avamar/bin" --vardir="/usr/local/avamar/var/client" --sysdir="/usr/local/avamar/etc/client" --logfile="/usr/local/...

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

root@avamar:~/#: service avagent status
* avagent.service - Avamar Unix backup/restore agent (avagent)
   Loaded: loaded (/usr/lib/systemd/system/avagent.service; enabled; vendor preset: disabled)
   Active: active (running) since Thu 2024-04-25 11:21:42 CDT; 3 weeks 3 days ago
 Main PID: 1998 (avagent.bin)
    Tasks: 9
   CGroup: /system.slice/avagent.service
           `-1998 /usr/local/avamar/bin/avagent.bin --bindir="/usr/local/avamar/bin" --vardir="/usr/local/avamar/var/client" --sysdir="/usr/local/avamar/etc/client" --logfile="/usr/local/avamar/var/client/avagent.log"

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Hvis ikonet avagent kører, men stadig viser status for ventende klient, så er der en mislykket avagent.

Meddelelsen /usr/local/avamar/var/client/avagent.log skal kontrolleres for at bekræfte:

root@avamar:~/usr/local/avamar/var/client#: tail avagent.log
2015/01/21-20:29:48.89689 [agent_main]  | 0000002a95678790
2015/01/21-20:29:48.89689 [agent_main]  | 0000002a9649329d
2015/01/21-20:29:48.89690 [agent_main]  | 0000002a96494a9e
2015/01/21-20:29:48.89691 [agent_main]  | 0000002a95676f61
2015/01/21-20:29:48.89692 [agent_main]  | 0000000000578201
2015/01/21-20:29:48.89692 [agent_main]  | 0000002a95672317
2015/01/21-20:29:48.89693 [agent_main]  | 0000002a9652f263
2015/01/21-20:29:48.89694 [agent_main]  ERROR: <0316> handlefatal exiting thread pid=17536, sig=6
2015-01-21 15:29:48 avagent Error <5891>: handlefatal: exiting thread pid=17536, sig=6
2015-01-21 15:29:48 avagent Info <5321>: Unable to connect to Management Console (avamar), sleep 38 minutes, 54 seconds before retry

Meddelelsen avagent er nede, eller den reagerede ikke og er nede. 

Hvis loggen viser, at avagent Hvis du ikke har reageret, eller hvis du ikke er blevet kontaktet i et stykke tid, skal du genstarte AVAGENT ved hjælp af en af de metoder, der er beskrevet nedenfor:

root@avamar:~/#: service avagent restart
avagent Info: Stopping Avamar Client Agent (avagent)...
avagent Info: Client Agent stopped.
avagent Info <5008>: Logging to /usr/local/avamar/var/client/avagent.log
avagent Info <5417>: daemonized as process id 41734
avagent Info: Client Agent started.

root@avamar:~/#: systemctl restart avagent

Vent i 180 sekunder (3 minutter), til næste job afhentes.

Hvis avagent Starter korrekt, ændres replikeringsjobbet for ventende klient til statussen "kører".