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

Failure in uptodate: can't connect to database

I've reveived 24 errors today regarding failure to connect and authentication errors and others.  There appears to be no notification on this site regarding any availability problems.

Errors include:

#353 - Virus Pattern Up2Date failed: No Up2Date Server(s) available
#354 -  Intrusion Protection Pattern Up2Date failed: No Up2Date Server available
#355 -  Pattern Up2Date: Netselect call for Up2Date Servers not possible
#356 - Pattern Up2Date failed: Authentication error. Trying another Authentication Server

Are others having this problem?

This thread was automatically locked due to age.

0 Simon Shaw over 20 years ago

Yup, me too. version 6.001

Pattern Up2Date failed: Message received from Server:
Mysql: No connection to database
Trying another Authentication Server...
Cancel
Vote Up 0 Vote Down

Cancel
0 Xeno over 20 years ago in reply to Simon Shaw

Maybe one of Astaro's up2date server crashed. Could you please post the IP of the up2date server? Can be found in the up2date status window.

Xeno
Cancel
Vote Up 0 Vote Down

Cancel
0 doug_p over 20 years ago in reply to Xeno

I got "Authentication error. Trying another Authentication Server " messages for both Pattern and System Up2Date a couple times on the 13th. It succeeded after a few retries though. No problems since then.
Cancel
Vote Up 0 Vote Down

Cancel
0 Xeno over 20 years ago in reply to doug_p

It was a problem in the datebase of one of the up2date servers. Fixed now.

Xeno
Cancel
Vote Up 0 Vote Down

Cancel