This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Up2Date prefetch failes in certain time window

Hi,

since round about 1 week or so we have the error "Up2Date prefetch failed: All 4 Authentication Servers failed" on all our SGs always in the time window 1:10 AM to 1:25 AM (UTC+1). They are all running 9.505 (update to 9.506 is scheduled) on different sites with different internet connections.

This is the relevant logfile passage:

2018:01:12-01:10:01 proxy2 audld[47377]: Starting Up2Date Package Downloader
2018:01:12-01:10:02 proxy2 audld[47377]: patch up2date possible
2018:01:12-01:10:33 proxy2 audld[47377]: Could not connect to Server 79.125.21.244 (status=500 Can't connect to 79.125.21.244:443 (timeout)).
2018:01:12-01:11:03 proxy2 audld[47377]: Could not connect to Server 107.21.214.248 (status=500 Can't connect to 107.21.214.248:443 (timeout)).
2018:01:12-01:11:33 proxy2 audld[47377]: Could not connect to Server 54.214.16.252 (status=500 Can't connect to 54.214.16.252:443 (timeout)).
2018:01:12-01:11:36 proxy2 audld[47377]: Could not connect to Server 175.41.132.12 (status=500 Internal Server Error).
2018:01:12-01:11:52 proxy2 audld[47377]: Could not connect to Authentication Server 79.125.21.244 (code=500 500 Internal Server Error).
2018:01:12-01:11:56 proxy2 audld[47377]: Could not connect to Authentication Server 107.21.214.248 (code=500 500 Internal Server Error).
2018:01:12-01:11:58 proxy2 audld[47377]: Could not connect to Authentication Server 54.214.16.252 (code=500 500 Internal Server Error).
2018:01:12-01:12:00 proxy2 audld[47377]: Could not connect to Authentication Server 175.41.132.12 (code=500 500 Internal Server Error).
2018:01:12-01:12:00 proxy2 audld[47377]: >=========================================================================
2018:01:12-01:12:00 proxy2 audld[47377]: All 4 Authentication Servers failed
2018:01:12-01:12:00 proxy2 audld[47377]:
2018:01:12-01:12:00 proxy2 audld[47377]:  1. Modules::Logging::msg:46() /</sbin/audld.plx>Modules/Logging.pm
2018:01:12-01:12:00 proxy2 audld[47377]:  2. Modules::Audld::Authentication::_handle_failure:235() /</sbin/audld.plx>Modules/Audld/Authentication.pm
2018:01:12-01:12:00 proxy2 audld[47377]:  3. Modules::Audld::Authentication::start:66() /</sbin/audld.plx>Modules/Audld/Authentication.pm
2018:01:12-01:12:00 proxy2 audld[47377]:  4. main::main:174() audld.pl
2018:01:12-01:12:00 proxy2 audld[47377]:  5. main::top-level:40() audld.pl
2018:01:12-01:12:00 proxy2 audld[47377]: [CRIT-310] Up2Date prefetch failed
2018:01:12-01:12:00 proxy2 audld[47377]: |=========================================================================
2018:01:12-01:12:00 proxy2 audld[47377]: id="3703" severity="error" sys="system" sub="up2date" name="Authentication failed, no valid answer from Authentication Servers"
2018:01:12-01:12:00 proxy2 audld[47377]:
2018:01:12-01:12:00 proxy2 audld[47377]:  1. Modules::Logging::alf:100() /</sbin/audld.plx>Modules/Logging.pm
2018:01:12-01:12:00 proxy2 audld[47377]:  2. Modules::Audld::Authentication::start:70() /</sbin/audld.plx>Modules/Audld/Authentication.pm
2018:01:12-01:12:00 proxy2 audld[47377]:  3. main::main:174() audld.pl
2018:01:12-01:12:00 proxy2 audld[47377]:  4. main::top-level:40() audld.pl
2018:01:12-01:25:02 proxy2 audld[48088]: no HA system or cluster node
2018:01:12-01:25:02 proxy2 audld[48088]: Starting Up2Date Package Downloader
2018:01:12-01:25:03 proxy2 audld[48088]: patch up2date possible
2018:01:12-01:25:11 proxy2 audld[48088]: Could not connect to Server 79.125.21.244 (status=500 Internal Server Error).
2018:01:12-01:25:31 proxy2 audld[48088]: found previous authentication failure, sending INFO-310
2018:01:12-01:25:31 proxy2 audld[48088]: [INFO-310] Up2Date prefetch is working again
2018:01:12-01:25:31 proxy2 audld[48088]: id="3701" severity="info" sys="system" sub="up2date" name="Authentication successful"
2018:01:12-01:25:32 proxy2 audld[48088]: id="3707" severity="info" sys="system" sub="up2date" name="Successfully synchronized fileset" status="success" action="download" package="sys"

 

Does anyone know something about this behaviour? It doesn't seem to be critcal but somewhat annoying...

Regards Marco



This thread was automatically locked due to age.
Parents Reply Children
No Data