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

7.300 upgrade problem

Hi All,

I have an ASG 220 appliance running on 7.202 and want to upgrade to 7.300.

Originally I was going to put the 7.300 RC version on and in preparation I manually uploaded 7.260, 7.280 and 7.290 up2dates. For some reason, the up2dates would not apply from webadmin and I never got around to fixing.

Since then, 7.300 has been released. So I've copied this up2date to the box but still cannot get it to update.

If I run auisys.plx --rpmargs --force, it complains that it needs 7.250 to update to 7.260 but I cannot find this on the up2date sites.

I've since tried removing all of the interim packages and cleaning out the /var/up2date/sys-install folder but still get the exact same error.

Where am I going wrong?

Regards,
Stuart

This thread was automatically locked due to age.

Parents

0 andreas over 17 years ago

I've since tried removing all of the interim packages and cleaning out the /var/up2date/sys-install folder but still get the exact same error.

You need to clean out the /var/up2date/sys/ directory. The sys-install only contains temporary data related to the up2date packages.

Cheers,
andreas
Cancel
Vote Up 0 Vote Down

Cancel
0 Stupots over 17 years ago in reply to andreas

Hi guys,

Thanks for the replies...

Are you still running 7.202?  If so, have you retried running from webadmin in the past couple of days?  I have seen a couple of systems which have updated to 7.300 from the GUI when they gave similar incremental upgrade errors from the shell.

I tried it from webadmin on Friday just before I posted my message.

You need to clean out the /var/up2date/sys/ directory. The sys-install only contains temporary data related to the up2date packages.

Sorry, didn't make my message very clear.  I removed all of the 7.2x packages out of the sys folder leaving just the 7.300 file and cleaned out the sys-install folder.

I've now cleaned out both folders entirely and I'll let the box download everything again.  Will let you know how goes.

Regards,
Stuart
Cancel
Vote Up 0 Vote Down

Cancel
0 Stupots over 17 years ago in reply to Stupots

Hi Again,

Ok, the server has download all the packages - if I try to update from within webamin nothing appears to happen and I get the following in the up2date log.  Any help appreciated!

Regards,
Stuart

===

2008:09:01-10:40:09 (none) auisys[9567]: Installing up2date package file '/var/up2date//sys/u2d-sys-7.260.tgz.gpg'
2008:09:01-10:40:09 (none) auisys[9567]: Verifying up2date package signature
2008:09:01-10:40:30 (none) auisys[9567]: Unpacking installation instructions
2008:09:01-10:40:42 (none) auisys[9567]: >=========================================================================
2008:09:01-10:40:42 (none) auisys[9567]: id="371J" severity="error" sys="system" sub="up2date" name="Fatal: Version conflict: required version: 7.250  current version: 7.202" status="failed" action="install" package="sys"
2008:09:01-10:40:42 (none) auisys[9567]:
2008:09:01-10:40:42 (none) auisys[9567]:  1. main::alf:72() auisys.pl
2008:09:01-10:40:42 (none) auisys[9567]:  2. main:[:P]erform_work:945() auisys.pl
2008:09:01-10:40:42 (none) auisys[9567]:  3. main::auisys_prepare_and_work:519() auisys.pl
2008:09:01-10:40:42 (none) auisys[9567]:  4. main::top-level:34() auisys.pl
Cancel
Vote Up 0 Vote Down

Cancel
0 andreas over 17 years ago in reply to Stupots
It looks like the downloader contacts the wrong server. If you have a regular 7.202, you should have the official servers in the up2date server list, which would offer you the official 7.300 package that can be applied on 7.202. If you contact the beta server instead you'll be offered the beta branch packages, which need the 7.250 package to be manually installed before that. Now the question is why you have the wrong server list - did you try to install the 7.250 up2date package, but an error occurred?

Anyway, to contact the official up2date servers, please check your server list in /etc/up2date/authservers.ini. This file should contain at least the following servers:

[Server_1]
Host = v7up2date1.astaro.com
Ip   = 213.198.93.249
Port = 443
[Server_2]
Host = v7up2date2.astaro.com
Ip   = 69.10.147.76
Port = 443
[Server_3]
Host = v7up2date3.astaro.com
Ip   = 213.144.15.5
Port = 443
[Server_4]
Host = v7up2date4.astaro.com
Ip   = 128.242.114.243
Port = 443
[Server_5]
Host = v7up2date5.astaro.com
Ip   = 128.121.10.115
Port = 443
[Server_6]
Host = v7up2date6.astaro.com
Ip   = 218.213.238.229
Port = 443

This file is used as input for a process which sorts them according to proximity and reachability. To  trigger this manually, do (as root):
/usr/local/bin/netselector.plx --infile /etc/up2date/authservers.ini --outfile /etc/up2date/servers.sorted

Afterwards, the downloader should automatically fetch the correct up2date package for you. Take note that if you tried to install the 7.250 before the installation might not work without the '--rpmargs --force' switch.

Cheers,
andreas
Cancel
Vote Up 0 Vote Down

Cancel
0 Stupots over 17 years ago in reply to andreas

Hi Andreas,

It looks like the downloader contacts the wrong server. If you have a regular 7.202, you should have the official servers in the up2date server list, which would offer you the official 7.300 package that can be applied on 7.202. If you contact the beta server instead you'll be offered the beta branch packages, which need the 7.250 package to be manually installed before that. Now the question is why you have the wrong server list - did you try to install the 7.250 up2date package, but an error occurred?

Yes, we originally intended to upgrade this server to the RC version of 7.300 and had problems.  In the mean time, 7.300 was properly released so we were intending to go straight to this version instead.

Anyway, to contact the official up2date servers, please check your server list in /etc/up2date/authservers.ini. This file should contain at least the following servers:

You were spot on, the only entry in the list was for the beta update server.

This file is used as input for a process which sorts them according to proximity and reachability. To  trigger this manually, do (as root):
/usr/local/bin/netselector.plx --infile /etc/up2date/authservers.ini --outfile /etc/up2date/servers.sorted

I managed to do this but had problems which I thought I'd raise publicly in case it is a bug/design feature.  This problem ASG is on a secondary network that runs within our corporate LAN/WAN.  It does not have direct access to the internet - instead it gets its updates via another ASG that deals with our normal internet traffic (configured as a parent proxy in the up2date panel on webadmin).

When you run ths netselector.plx file, it is unable to resolve any addresses and the servers.sorted file only ended up containing the beta update server.  I got around this by temporarily configuring it to use the primary ASG for DNS resolution whilst running netselector.plx so that it could populate servers.sorted.

Afterwards, the downloader should automatically fetch the correct up2date package for you. Take note that if you tried to install the 7.250 before the installation might not work without the '--rpmargs --force' switch.

Yes, it returned an RPM error which was resolved with the switches above [:)]  One more ASG upgraded to 7.300.

Many thanks for your help.

Regards,
Stuart
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 Stupots over 17 years ago in reply to andreas

Hi Andreas,

It looks like the downloader contacts the wrong server. If you have a regular 7.202, you should have the official servers in the up2date server list, which would offer you the official 7.300 package that can be applied on 7.202. If you contact the beta server instead you'll be offered the beta branch packages, which need the 7.250 package to be manually installed before that. Now the question is why you have the wrong server list - did you try to install the 7.250 up2date package, but an error occurred?

Yes, we originally intended to upgrade this server to the RC version of 7.300 and had problems.  In the mean time, 7.300 was properly released so we were intending to go straight to this version instead.

Anyway, to contact the official up2date servers, please check your server list in /etc/up2date/authservers.ini. This file should contain at least the following servers:

You were spot on, the only entry in the list was for the beta update server.

This file is used as input for a process which sorts them according to proximity and reachability. To  trigger this manually, do (as root):
/usr/local/bin/netselector.plx --infile /etc/up2date/authservers.ini --outfile /etc/up2date/servers.sorted

I managed to do this but had problems which I thought I'd raise publicly in case it is a bug/design feature.  This problem ASG is on a secondary network that runs within our corporate LAN/WAN.  It does not have direct access to the internet - instead it gets its updates via another ASG that deals with our normal internet traffic (configured as a parent proxy in the up2date panel on webadmin).

When you run ths netselector.plx file, it is unable to resolve any addresses and the servers.sorted file only ended up containing the beta update server.  I got around this by temporarily configuring it to use the primary ASG for DNS resolution whilst running netselector.plx so that it could populate servers.sorted.

Afterwards, the downloader should automatically fetch the correct up2date package for you. Take note that if you tried to install the 7.250 before the installation might not work without the '--rpmargs --force' switch.

Yes, it returned an RPM error which was resolved with the switches above [:)]  One more ASG upgraded to 7.300.

Many thanks for your help.

Regards,
Stuart
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data