Avamar: MCS-avslutningsarbeidsflyten slutter å svare under tømming av ClientRegistryService

 Oppstart av MCS mislyktes på grunn av å følge feilen:

Startup Failed: Closing all connections to database. Server already started on port: 7778 

Informasjonen i ClientRegistryService Spylingen slutter å svare når MCS slås av. Alle tjenester tømmes under MCS-avslutning, og starter med ClientRegistryService.

> 08/13-12:13:51.00900 [RMI TCP Connection(109)-10.241.180.21#904] com.avamar.asn.Node._stop
> FINE: Stopping the service container...
> 08/13-12:13:51.00902 [FlushCacheThread#1042] com.avamar.asn.service.ServiceContainerImpl$FlusherThread.run
> FINE: About to flush com.avamar.mc.cr.ClientRegistryService
> --
> 08/13-12:13:51.00993 [FlushCacheThread#1042] com.avamar.asn.service.ServiceContainerImpl$FlusherThread.run
> FINE: Done flushing com.avamar.mc.cr.ClientRegistryService in 91 ms
> ...
> ...
> FINE: About to flush com.avamar.mc.pdm.ProxyDeploymentManagerService
> 08/13-12:13:52.00031 [FlushCacheThread#1092] com.avamar.asn.service.ServiceContainerImpl$FlusherThread.run
> FINE: Done flushing com.avamar.mc.pdm.ProxyDeploymentManagerService in 0 ms

Denne loggen viser bare ClientRegistryService spyler uten å fullføre.
 

> 08/13-00:06:29.00971 [RMI TCP Connection(3663)-10.241.180.21#68659] com.avamar.asn.Node._stop
> FINE: Stopping the service container...
> 08/13-00:06:29.00972 [FlushCacheThread#68734] com.avamar.asn.service.ServiceContainerImpl$FlusherThread.run
> FINE: About to flush com.avamar.mc.cr.ClientRegistryService 

Hovedjobben med spyling ClientRegistryService er å oppdatere alle klienter fra cache til mcdb.

> 08/13-00:06:29.00972 [FlushCacheThread#68734] com.avamar.mc.cr.ClientStore.saveAll
> FINE: Start saving clients in ClientStore...
> 08/13-00:06:29.00972 [FlushCacheThread#68734] com.avamar.mc.cr.ClientStore.saveAll
> FINE: Flushing client f6a0975c4854536da1089c6800dc1212b2257a9a due to server shutdown,

Finn PID-en for "java.*mcserver"

 ps -eaf | grep "java.*mcserver"

Stopp MCS-prosessen manuelt. 

pkill -9 <PID of "java.*mcserver">

Hvis dette skjedde under oppstarten, starter du på nytt med:

dpnctl start

Det er mulig, men ikke sannsynlig, at MCS-spylingen etterlater MCS i en inkonsekvent tilstand. Slik gjenoppretter du forrige flush:

dpnctl start --force_mcs_restore

For å sikre at alt er bra og tjenester har blitt tatt opp vellykket, kan sjekke status med.

dpnctl status
Identity added: /home/admin/.ssh/admin_key (/home/admin/.ssh/admin_key)
dpnctl: INFO: gsan status: up
dpnctl: INFO: MCS status: up.
dpnctl: INFO: emt status: up.
dpnctl: INFO: Backup scheduler status: up.
dpnctl: INFO: Maintenance windows scheduler status: enabled.
dpnctl: INFO: Unattended startup status: enabled.
dpnctl: INFO: avinstaller status: up.
dpnctl: INFO: ConnectEMC status: up.
dpnctl: INFO: ddrmaint-service status: up.