I installed 5.007 and it did a reboot and displayed 5.005. I up2date again to 5.006 & 5.007 and it is back to 5.005. Hey, I like this. I never went backwards in release before.
(see posting in other thread as well - please avoid cross posting)
we had 3 reports from customers telling us thier box did not reboot after updating from 5.004 to 5.005 (kernel update) - we could not reproduce this here and 5.006 has already been released, so we decided to add a reboot and set the version back to 5.005 for those running with the old kernel.
~marcel
PS: sorry for the inconvenience... if you encounter problems when updating to 5.007, please post them here.
(see posting in other thread as well - please avoid cross posting)
we had 3 reports from customers telling us thier box did not reboot after updating from 5.004 to 5.005 (kernel update) - we could not reproduce this here and 5.006 has already been released, so we decided to add a reboot and set the version back to 5.005 for those running with the old kernel.
~marcel
PS: sorry for the inconvenience... if you encounter problems when updating to 5.007, please post them here.
We had that problem going from 5.005 to 5.006 where the box didn't restart and I had to reboot from the terminal. Now the 5.007 was applied but it put the machine into a state where the console was locked up, none of the NICs responded to pings and the only option was a hardware restart. All is OK after the restart.
I noticed similar behaviour on two firewalls after an up2date to 5.007. Restarting one firewall resulted in the problem going away for about half an hour and then recurring. As these were remote locations (and not being able to remote when the failure occurred) so I have reinstalled both firewalls with the 5.005 image (both had been 5.000 images to start) and have not deployed the 5.007 patch until I see further comment on it. The machines are at 5.006 (up2date would not work until that was on) and no further problems noticed.
i have the same Problem Update from 5.005 to 5.006 work fine. Update to 5.006 to 5.007 not because fall back to 5.005. All logs look fine no errors in the update dialogs... So now at the 06/2004 IMHO the problem is not solved (i have probe with the new download packages 5.006+5.007). So my way was: 1) An backup :-) 2) Download Image with 5.011 3) Install completly new from 5.011 image 4) restore the backup from 1) 5) Update to 5.012
The result is that all is working fine. No problems during installation. This not really an good business solution but it is working.
My Hardware: Celeron 566 384MB RAM 2x Intel Pro+ Nics 20GB IDE HDD
I hope the information is usefull because it is late, but i had have holidays..
