Got a different error later on, after a soft restart..
from the client showing the node is not available, server not started..
looking at the dpnctl.status
msc & backup schedular are showing down, on restart ...
Startup Failed: Closing all connections to database. Server already started on port: 7778
Finding what is keeping the connection open, lsof -nP | grep 7778
Kill - HUP 13967..
restarted the service and access was restored.
looks like the old process was still hanging onto the port, so new one could not bind/start.
The second error above looks like a false positive,
The Administrator Server data is normally saved or flushed hourly for disaster recovery purposes.One of these hourly flushes did not occur as scheduled.
Acknowledged the error and the flushing process began..
DDave447
26 Posts
0
May 15th, 2018 01:00
update -
similar but didnt fix my problem - Avamar Administrator Client Error
Got a different error later on, after a soft restart..
from the client showing the node is not available, server not started..
looking at the dpnctl.status
msc & backup schedular are showing down, on restart ...
Startup Failed: Closing all connections to database. Server already started on port: 7778
Finding what is keeping the connection open, lsof -nP | grep 7778
Kill - HUP 13967..
restarted the service and access was restored.
looks like the old process was still hanging onto the port, so new one could not bind/start.
The second error above looks like a false positive,
The Administrator Server data is normally saved or flushed hourly for disaster recovery purposes.One of these hourly flushes did not occur as scheduled.
Acknowledged the error and the flushing process began..
D