You might be on to something. I've had no success upgrading to v7.100 and my homegrown firewall uses two "Intel Corporation 82557/8/9 [Ethernet Pro 100]" NICs (1).
I'll try another rebuild in a day or two and post the results.
BillK
1. Taken from Astaro's v7.011's Network >> Interfaces >> Hardware tab.
That's how the Astaro describes the Intel NICs in this particular box. Bear in mind, the one that was misbehaving did start working after we changed the cable, but the problem was clearly tied to the update, as it worked fine for 3 months before this. I have gotten a response from Astaro concerning this case, and they are quite interested, and have also acknowledged that many drivers were updated with the new release.. .I guess we're just finding some of the hidden issues. Billk, I'd be interested to see if crossover cables / manual speed / duplex settings / or different NICs in the same box fix your problems.
CTO, Convergent Information Security Solutions, LLC
Advice given as posted on this forum does not construe a support relationship or other relationship with Convergent Information Security Solutions, LLC or its subsidiaries. Use the advice given at your own risk.
Just updated to 7.100 this evening on our production 220 v1.
The install itself went smoothly if slow. Appeared to hang on the install of the Kernel package at 85%. I was patient and after about 10 minutes, it continued on with the ramaining packages rather quickly. Total time was around 20-25 minutes including reboot.
After re-entering WebAdmin, I flipped around a little bit, noticing that my list of sites to block in the http proxy had been successfully carried over to the new block list. Went to rejoin to our domain. In previous versions I had to use the single name for the domain, which would not work with 7.100 (tried both lower and upper case). Using the FQDN (e.g. domain.com) did work though, which wouldn't work in previous versions.
Logged onto a random workstation to check http connectivity, which worked just fine.
__________________ ACE v8/SCA v9.3
...still have a v5 install disk in a box somewhere.
I upgraded from 7.011 to 7.100 and I didn't encounter any problems so far. Machine: Dell PE2650, Dual Xeon, 2Gig RAM, Perc3, 2 x SCSI-HDD as RAID1, Intel Pro1000 Dual-Port NIC
I have gotten a response from Astaro concerning this case, and they are quite interested, and have also acknowledged that many drivers were updated with the new release.. .I guess we're just finding some of the hidden issues. Billk, I'd be interested to see if crossover cables / manual speed / duplex settings / or different NICs in the same box fix your problems.
Any news from Astaro as to when a fix will be available? I reviewed the 7.101 upgrade notes but saw nothing that specifically addresses this issue.
I was up to my eyeballs with Christmas programs this weekend, but will try next week to see if a crossover cable or different NICs make a difference.
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.
