Avamar: Replikering starter ikke på grunn av at Avagent er nede

Replikering kjører ikke eller går inn i statusen "Ventende klient".

Replikering starter ikke, blir værende i ventende klient-status på grunn av at proagenten er nede.

1. Logg på Avamar Utility Node som administrator.

2. Løft til rot.

3. Sjekk ikonet avagent Status med følgende Systemctl eller service Kommandoen:

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 avagent kjører, men fremdeles viser status for den ventende klienten, da er en mislykket avagent.

Meldingen /usr/local/avamar/var/client/avagent.log Må kontrolleres for å bekrefte:

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

Meldingen avagent er nede, eller den reagerte ikke og er nede. 

Hvis loggen viser at avagent Fordi AG-en ikke har reagert eller ikke har blitt kontaktet på en stund, starter du AVAGENS-agenten på nytt ved hjelp av en av metodene 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 neste jobb blir hentet.

Hvis avagent Starter uten problemer, endres replikeringsjobben for ventende klient til statusen "kjører".