I just updated our 425 appliance from 7.011 to 7.1 and now we are having authentication issues. Always being prompted for authentication and then we get an authentication failed message. Not going well here! I'd love some help if someone has an idea.
last week we have updated our ASG HA from v 7.011 to 7.100/101.
After click on update the slave node goes to status Up2Date in the High-Availability screen. I am logged in over ssh to the slave node and see no Up2Date process was running no tar gzip was running on the node after pressing the up2date button no information on the up2date log. There are 9 zombie processes and th load was by 6!. I have reboot the slave and wait. After Slave are up he has allegedly version 7.100. ??
After the slave was up the up2date process are truly running on the master. I think The result ist old slave node was not updated to 7.100 the old master has the update. In this constellation no service was running correctly VPN/Firewall/Proxy all unusable. Switching to the old master and all was working.
I have reinstalled the slave and rejoin the HA - all OK.
Just did our second attempt to upgrade our ASG220. Once again it has caused issues. It looks like it only got to 7.100-581 and now the web admin doesn't work. Everything appears to be working still, but I don't have any visability to fix anything. I'm waiting on tech support for help getting it running again. attempting to restart the httpd from console fails.
Our setup is really quite simple so not sure what the catch is.
Hopefully I don't need to make any changes right away.
Just did our second attempt to upgrade our ASG220. Once again it has caused issues. It looks like it only got to 7.100-581 and now the web admin doesn't work. Everything appears to be working still, but I don't have any visability to fix anything. I'm waiting on tech support for help getting it running again. attempting to restart the httpd from console fails.
Our setup is really quite simple so not sure what the catch is.
Hopefully I don't need to make any changes right away.
Appears that the system was missing the webadmin certificate information. By adding the certificate back in the httpd webadmin process starts correctly now.