Well this has been a frustrating day,
Say the that the update to 4.017 was available via up2date. I first updated to 4.016 like the directions advised, and then proceeded to install the 4.017 update. Up2date warned me that the machine would be rebooted, and while the update was installing I received a connection refused error from the WebAdmin. I figured that this was normal, and continued to let the machine update(hard drive activity). After around 10-15 minutes of no HDD activity, and no WebAdmin access I rebooted the machine. Only to find:
Entering RunLevel 3
Starting IPTables.....
And, the machine continued to sit there for another 10-15 minutes. Shut down the machine, and threw our abckup firewall online. Tried to diagnose the problems, but could not, and decided to do a re-install and then mirror over from our backup file.
Re-install of 4.017 from the new ISO went fine, and after rebooting I am at the exact same place as after the 4.017 up2date. Still hanging @ IPTables.
Astaro, it seems that quite a few people are having problems with 4.017, was any QA done for this release, or is this "normal" behavior for an "Enterprise" level product? Please advise an immediate solution to this problem, as this firewall is without the new kernel patch, currently running 4.015.
The machine specs are:
Compaq Proliant 1600R(Pentium II 400)
128 MB RAM
4.3GB SCSI
4x Netgear PCI NIC's
I would like to emphasize that a fresh install from the 4.017 ISO did nothing to solve this problem. The machine is still stuck at "Starting IP Tables".
Peter
This thread was automatically locked due to age.
