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

Error with up2date 6.106 -> 6.2

Hi,
I've got a little problem with the update from 6.106 to 6.2. The insall starts, but after a while, a error message apears.

ainstall[5532]: System Up2Date failed: Error occured while running installer
ainstall[5532]: System Up2Date failed: Installer stopped due to internal error

After this, a rollback were done and now, I can't restart the firewall. The licening is not possible and I can't see any rules.
Btw: this system is located in swizerland and I'm sitting in Bochum, so I can't easy go to the system ^^ In Swizzerland there is no enhanced user to do anything more than switch off an on the sytem.
Pleas, some ideas to solve this problem. [:S]

Sabine

This thread was automatically locked due to age.

Parents

0 Zitronennetz over 19 years ago

Hi SabineW,

I would suggest to download the updates manually (you can download it here). After downloading check the MD5, if it looks ok, do the manual update ("Import from file").
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Zitronennetz over 19 years ago

Hi SabineW,

I would suggest to download the updates manually (you can download it here). After downloading check the MD5, if it looks ok, do the manual update ("Import from file").
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 SabineW over 19 years ago in reply to Zitronennetz

Hi,
thnx for reply! I'll try it and keep fingers cross
Cancel
Vote Up 0 Vote Down

Cancel
0 SabineW over 19 years ago in reply to SabineW

Hi,
nope, it didn't work. The sytem told me there a no licences key and if I install the key nothing happens. A manuell updat to 6.2 isn't possible, because there is no licence key... Rules are not visible ... A reboot isn't possible because nothing happens.

Q: What happens, when I switch off/on the system? Is there a chance to "rescue" the system and to update it manually?

Sabine [:S]
Cancel
Vote Up 0 Vote Down

Cancel
0 florian over 19 years ago in reply to SabineW

Hi Sabine,

did you only try a restart with the GUI or do you have the possibility to login with ssh and do a reboot?

Florian
Cancel
Vote Up 0 Vote Down

Cancel
0 SabineW over 19 years ago in reply to florian

Hi,
just restart with GUI... I've to be carefully, because there serveral kilometers between me and the system... A restart with shell isn't the problem, but after this, the system have to work - i'm remoteadmin in the moment [:(]
Cancel
Vote Up 0 Vote Down

Cancel
0 florian over 19 years ago in reply to SabineW

Hi Sabine,

have you checked all the daemons that should be running, esp. the middleware daemon?

Florian
Cancel
Vote Up 0 Vote Down

Cancel
0 SabineW over 19 years ago in reply to florian

Hi,
after some checks what's running and what's not runnig (middelware daemon doesn't) I do a system reboot (and keeps fingers cross) and it's runnig now. I'm some years older and get some gray hairs.

Sabine
Cancel
Vote Up 0 Vote Down

Cancel