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 when running Up2Date for IPS

Just updated to V5.005 ... I tried to run an Up2Date for the Intrusion Protection Patterns ... This is what I see in my window:

Up2Date Service
Fri May 7 10:19:27 CDT 2004

000 Pattern Up2Date: Started Pattern Up2Date
001 Checking following Pattern Types:
002 Intrusion Protection Pattern
004 Could not register Astaro::logging:callerName() at /PerlApp/Modules/ulog.pm line 54.
Done

Anyone else get this message?

This thread was automatically locked due to age.

Parents

0 Markus Hennig over 21 years ago

Hi MrJ412,

thx for the report.
We found some rare conditions were this happens...
We will prepare a Up2Date package to fix this - sorry for the circumstances
Cancel
Vote Up 0 Vote Down

Cancel
0 MrJ412 over 21 years ago in reply to Markus Hennig

That was a quick reply :-)

I was waiting for the GA release to try out the Intrusion Protection, so this isn't really affecting me yet, but I just wanted to post a message and let you know. Great to know that you are aware and working on a fix.
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to notoriousiroc

notoriousiroc is totally correct. v5.005 had an issue with ips up2dates.

you will need to do a manual update and install through webadmin
Cancel
Vote Up 0 Vote Down

Cancel
0 NilsKoch over 21 years ago in reply to Mike_H

Hi,

I get the same error when trying to do an up2date...

Could not register Astaro::logging:callerName() at /PerlApp/Modules/ulog.pm line

Have installed 5.006, but nothing changed...

Apart from that, if I activate the transparent POP3 proxy, no POP3-server can't be reached... and virus protection fpr web isn't working.. ;-(((

Best regards,

nkoch
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to NilsKoch

have you restarted ur astaro box since the manual update to 5.006? if u have not please try it and repost exact error message. copy and paste will be great
Cancel
Vote Up 0 Vote Down

Cancel
0 NilsKoch over 21 years ago in reply to Mike_H

Hi,

have restartet the system a few times after the 5.006-update but no change, when I start up2date this error occurs:

"Up2Date Service
Sun May 9 15:22:09 CEST 2004

000 System Up2Date: Started System Up2Date
001 Running Version: 5.006
002 Checking Authentication Servers ...
003 1 Authentication Server: 212.126.210.201
004 2 Authentication Server: 216.167.31.83
005 Use of uninitialized value in exists at /PerlApp/Astaro/logging.pm line 357.
006 Could not register Astaro::logging:callerName() at /PerlApp/Modules/ulog.pm line 54.
Done"

Apart from that I had to switch off the SurfProtection and POP3-Proxy because some strange errors occur:
- some pages were not visisble
- no mailserver could be reached via POP3
[...]

Hmm...

Best regards,
nkoch
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to NilsKoch

have you tried reinstalling the 5.006 file manually
Cancel
Vote Up 0 Vote Down

Cancel
0 NilsKoch over 21 years ago in reply to Mike_H

Where can I get it from?
Cancel
Vote Up 0 Vote Down

Cancel
0 Mike_H over 21 years ago in reply to NilsKoch

ftp://ftp.astaro.com/pub/Astaro_Security_Linux/up2date/v5.0/
Cancel
Vote Up 0 Vote Down

Cancel
0 NilsKoch over 21 years ago in reply to Mike_H

Thanx! I will try this from home, can't upload this sized update over the internet on my ASL @home...
Cancel
Vote Up 0 Vote Down

Cancel
0 NilsKoch over 21 years ago in reply to Mike_H

I got the update but I can't install it over, because the version 5.006 is installed already. Is there a possibility to "force" the update progress to install the 5.006 again?
Cancel
Vote Up 0 Vote Down

Cancel
0 NilsKoch over 21 years ago in reply to NilsKoch

Have edited /etc/version to 5.005 manually, and updated the system with 5.006... now everything seems to be fine!! ;-)

Best regards,
Nils
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 NilsKoch over 21 years ago in reply to NilsKoch

Have edited /etc/version to 5.005 manually, and updated the system with 5.006... now everything seems to be fine!! ;-)

Best regards,
Nils
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data