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

Astaro paterns not updating?

So I just noticed that my Astaro patterns aren't updating automatically. I checked to make sure they're updating in configuration and they're set to every 15 minutes, but the number on the pattern file hasn't increased in months.. and the dashboard shows it's never checked for an update. It is on 8.102 for the version. Can anyone help??

EDIT: This is the error I get in the error logs:

2011:05:14-00:23:01 asg-fw-1 audld[29360]: Starting Up2Date Package Downloader
2011:05:14-00:23:02 asg-fw-1 audld[29360]: patch up2date possible
2011:05:14-00:23:04 asg-fw-1 audld[29360]: Could not connect to Authentication Server 175.41.132.12:443 (code=500).
2011:05:14-00:23:04 asg-fw-1 audld[29360]: Could not connect to Authentication Server 175.41.132.12:443 (code=500).
2011:05:14-00:23:04 asg-fw-1 audld[29360]: Could not connect to Authentication Server 184.72.238.199:443 (code=500).
2011:05:14-00:23:04 asg-fw-1 audld[29360]: Could not connect to Authentication Server 184.72.238.199:443 (code=500).
2011:05:14-00:23:04 asg-fw-1 audld[29360]: Could not connect to Authentication Server 79.125.21.244:443 (code=500).
2011:05:14-00:23:04 asg-fw-1 audld[29360]: Could not connect to Authentication Server 79.125.21.244:443 (code=500).
2011:05:14-00:23:04 asg-fw-1 audld[29360]: >=========================================================================
2011:05:14-00:23:04 asg-fw-1 audld[29360]: All 6 Authentication Servers failed
2011:05:14-00:23:04 asg-fw-1 audld[29360]: '175.41.132.12:443' Code: '500'
2011:05:14-00:23:04 asg-fw-1 audld[29360]: '184.72.238.199:443' Code: '500'
2011:05:14-00:23:04 asg-fw-1 audld[29360]: '79.125.21.244:443' Code: '500'
2011:05:14-00:23:04 asg-fw-1 audld[29360]:
2011:05:14-00:23:04 asg-fw-1 audld[29360]: 1. Modules::Trad_Get_Filelist::contact:1524() audld.pl
2011:05:14-00:23:04 asg-fw-1 audld[29360]: 2. main::authenticate:574() audld.pl
2011:05:14-00:23:04 asg-fw-1 audld[29360]: 3. main::run:378() audld.pl
2011:05:14-00:23:04 asg-fw-1 audld[29360]: 4. main::top-level:27() audld.pl
2011:05:14-00:23:04 asg-fw-1 audld[29360]: |=========================================================================
2011:05:14-00:23:04 asg-fw-1 audld[29360]: id="3703" severity="error" sys="system" sub="up2date" name="Authentication failed, no valid answer from Authentication Servers

This thread was automatically locked due to age.

Parents

0 Scott_Klassen over 14 years ago

There was a faulty IPS pattern last year that caused pattern updates to break. If it has been a very long time since your last pattern update, you may be experiencing this issue. Take a look at the thread: https://community.sophos.com/products/unified-threat-management/astaroorg/f/52/t/27435. Using the guidance in this thread, you can try creating the old IPS exceptions.

You can also try rebooting the Astaro just in case something is stuck.

If all else fails, you can always reinstall from the current ISO, 8.102, then restore a current config backup.

__________________
ACE v8/SCA v9.3

...still have a v5 install disk in a box somewhere.

http://xkcd.com
http://www.tedgoff.com/mb
http://www.projectcartoon.com/cartoon/1
Cancel
Vote Up 0 Vote Down

Cancel
0 caseyj1231 over 14 years ago in reply to Scott_Klassen

There was a faulty IPS pattern last year that caused pattern updates to break. If it has been a very long time since your last pattern update, you may be experiencing this issue. Take a look at the thread: http://www.astaro.org/astaro-gateway-products/hardware-installation-up2date-licensing/31686-how-force-pattern-update.html. Using the guidance in this thread, you can try creating the old IPS exceptions.

You can also try rebooting the Astaro just in case something is stuck.

If all else fails, you can always reinstall from the current ISO, 8.102, then restore a current config backup.

So I did this, 8.103, fresh install.. and still getting the same results, even with a brand new config.
Cancel
Vote Up 0 Vote Down

Cancel
0 Marcel_01 over 14 years ago in reply to caseyj1231

Hi,

your box is able to contact servers in the internet, correct? Usually, this error shows up if ASG is not able to contact any server. To verify your connection you can either try using a proxy (e.g. httpproxy) or ping the IPs listed in the log from your ASG.

Best regards,
Marcel
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Marcel_01 over 14 years ago in reply to caseyj1231

Hi,

your box is able to contact servers in the internet, correct? Usually, this error shows up if ASG is not able to contact any server. To verify your connection you can either try using a proxy (e.g. httpproxy) or ping the IPs listed in the log from your ASG.

Best regards,
Marcel
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 caseyj1231 over 14 years ago in reply to Marcel_01

Hi,

your box is able to contact servers in the internet, correct? Usually, this error shows up if ASG is not able to contact any server. To verify your connection you can either try using a proxy (e.g. httpproxy) or ping the IPs listed in the log from your ASG.

Best regards,
Marcel

Yes, I can ping all of them, and they are all accessible. I can also get to the addresses it tries to hit from my web browser and it brings up the page as well (looks like its either PHP or RSS)
Cancel
Vote Up 0 Vote Down

Cancel
0 Marcel_01 over 14 years ago in reply to caseyj1231

Hi,

so to summarize:
- Internet access is possible
- Up2Date-Servers are still not accessible

Next step: Check if requests to Up2Date-Servers are blocked by packetfilter. To do that, open packetfilter log and check for dst IPs corresponding to the Up2date servers' IPs and port 443.

Thanks,
Marcel
Cancel
Vote Up 0 Vote Down

Cancel
0 Undel over 14 years ago in reply to Marcel_01

Patterns are not being updated when Antivirus and/or IPS functionality disabled - because there is no point in updating them in such setup.
Cancel
Vote Up 0 Vote Down

Cancel