Having Trouble with autoamtic update

[noimad1]

After running the automatic update, it says it is going to update some plesk module or something like that. However, it says there are 0 packages that need to be updated. But then it tries to run the up2date anyways.

Then it fails right away with this error:

An error has occurred:
exceptions.ValueError
See /var/log/up2date for more information
ERROR: The up2date utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

Here is what my /var/log/up2date log looks like:

[Tue Jul 17 18:46:52 2007] up2date File "/usr/sbin/up2date-nox", line 1288, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date-nox", line 806, in main
fullUpdate, dryRun=options.dry_run))
File "/usr/sbin/up2date-nox", line 1126, in batchRun
batch.init()
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 65, in init
self.__findPackagesToUpdate()
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 101, in __findPackagesToUpdate
plist.addGlobs(self.listOfGlobs)
File "/usr/share/rhn/up2date_client/packageList.py", line 161, in addGlobs
availList = rhnPackageInfo.getAvailablePackageList()
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 235, in getAvailablePackageList
package_list = availablePackageList(
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 169, in availablePackageList
progressCallback = progressCallback)
File "/usr/share/rhn/up2date_client/rpcServer.py", line 236, in doCall
ret = apply(method, args, kwargs)
File "/usr/share/rhn/up2date_client/repoDirector.py", line 22, in listPackages
return self.handlers[channel['type']].listPackages(channel, msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/rpmSource.py", line 229, in listPackages
msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/repoBackends/yumRepo.py", line 191, in listPackages
channelTimeStamp = time.strptime(oldVersion,"%Y%m%d%H%M%S")
File "/usr/lib/python2.3/_strptime.py", line 424, in strptime
raise ValueError("time data did not match format: data=%s fmt=%s" %

Now I can't figure out why it is doing this. If it says there are 0 packages that need to be updated, then why is it trying to update? Can I skip this somehow and go straight to the version 3.0 to 4.0 upgrade?

 

[caustic]

i'm no sure if this is sitebuilder, plesk or up2date problem. What OS do you run? What repository do you use to upgrade?

 

[noimad1]

Well it really seems like an up2date error, since that's the stage it fails on.

I'm running red hat enterprise 4.

I don't know what you mean by repository, could you be more specific on how I would check which I'm using?

Or are you referring to which file I am using to do the automatic update? I just downloaded the i386 Red hat 4 version from the sitebuilder download section?

 

[caustic]

I don't know what you mean by repository, could you be more specific on how I would check which I'm using?

what is in /etc/sysconfig/rhn/sources?

Did you get any other errors during the upgrade (e.g. unresolved dependencies, package conflicts, etc)?

 

[noimad1]

Originally posted by caustic
what is in /etc/sysconfig/rhn/sources?

Did you get any other errors during the upgrade (e.g. unresolved dependencies, package conflicts, etc)?

Here is what is in that file:

### This describes the various package repositories (repos) that up2date will
### query for packages. It currently supports apt-rpm, yum, and "dir" repos.

### Format is one repository (repo) entry per line, # starts comments, the
### first word on each line is the type of repo.

### The default RHN (using "default" as the url means use the one in the
### up2date config file). This is required.
up2date default

### Note: when a channel label is required for the non up2date repos,
### the label is solely used as an internal identifier and is not
### based on the url or any other info from the repos.

### An apt style repo (the example is arjan's 2.6 kernel repo).
### The format is:
### type channel-label service:server path repo name
#apt arjan-2.6-kernel-i386 http://people.redhat.com ~arjanv/2.5/ kernel

### Note: for apt repos, there can be multiple repo names specified (space
### seperated).

### A yum style repo. The format is:
### type channel-label url
#yum fedora-core-development http://download.fedora.redhat.com/pub/fedora/linux/core/development/$ARCH/

### A local directory full of packages (a "dir" repo). For example:
#dir my-favorite-rpms /var/spool/RPMS/

# Multiple versions of all repos except "up2date" can be used. Dependencies
# can be resolved "cross-repo" if need be.

# Atomic
yum atomic http://3es.atomicrocketturtle.com/atomic/art/4ES/
# Atomic App Vault
yum atomic-app-vault http://3es.atomicrocketturtle.com/atomic/app-vault/

# SW-Soft PSA 8.0
yum psa-8.0 http://3es.atomicrocketturtle.com/atomic/psa-8.0/4ES/

And the original error was all I seemed to get. It just failed during that upgrade right away when it got to that "up2date" part.

This what I don't understand. Here is what the update program says:

Preparing Your System for Product Installation
===============================================================================

There are 0 packages required for Plesk to function properly, which
were not found in your system.

There are 0 packages that need to be upgraded
in order to install the product.

Then I go to the next part, and it says

Plesk and operating system packages will be downloaded and saved to the
directory '/root/swsoft'.

Required disk space: 0.00 Mb.

Available disk space: 45094.89 Mb.

And then that's when I get the first error:

An error has occurred:
exceptions.ValueError
See /var/log/up2date for more information
ERROR: The up2date utility failed to install the required packages.
Attention! Your software might be inoperable.
Please, contact product technical support.

What I don't understand is if there are 0 packages to download and install, why is it still running the up2date?


This is the automatic update file I'm using:

psa_installer_v3.2.0_build070626.19_os_RedHat_el4_i386

 

[caustic]

What I don't understand is if there are 0 packages to download and install, why is it still running the up2date?

Autoinstaller is unable to calculate the number of packages it will upgrade so it just outputs 0 and lets up2date do the actual upgrade.

And then that's when I get the first error
seems the me like an up2date problem.

you can try the following:
1) add these lines to /etc/sysconfig/rhn/sources

yum sitebuilder-dist [url]http://autoinstall.plesk.com/SiteBuilder/SiteBuilder_4.0.0/dist-rpm-RedHat-el4-i386/[/url]
yum sitebuilder-update [url]http://autoinstall.plesk.com/SiteBuilder/SiteBuilder_4.0.0/update-rpm-RedHat-el4-i386/[/url]
yum sitebuilder-thirdparty [url]http://autoinstall.plesk.com/SiteBuilder/SiteBuilder_4.0.0/thirdparty-rpm-RedHat-el4-i386/[/url]

2) run

up2date-nox -nosig -dry-run sitebuilder sitebuilder-core sitebuilder-selinux

and see what happens (this command will not actually upgrade anything due to dry-run)

 

[noimad1]

I tried to run the command:

up2date-nox -nosig -dry-run sitebuilder sitebuilder-core sitebuilder-selinux

after adding that info, but it says:

/usr/sbin/up2date-nox: error: no such option: -n


Did I mistype something there?

 

[noimad1]

Sorry to bump this, but I really need to get this thing upgraded....


Thanks,
Damion

 

[caustic]

after adding that info, but it says:

/usr/sbin/up2date-nox: error: no such option: -n

Did I mistype something there?
Nope, I did. There should be two dashes before both nosig and dry-run

Sorry to bump this, but I really need to get this thing upgraded....
Then you should contact swsoft support, because I still have no idea what's wrong and figuring it out from up2date errors may take a long while.

 

[noimad1]

Thanks for the reply. The main reason I don't want to contact swsoft is because I can't afford to pay them to look at this.

I really thought this was going to be an easy upgrade. After trying everything you mentioned, I still seem to be getting an error. Looks like maybe the same error as before:

[Tue Jul 24 17:52:37 2007] up2date File "/usr/sbin/up2date-nox", line 1288, in ?
sys.exit(main() or 0)
File "/usr/sbin/up2date-nox", line 806, in main
fullUpdate, dryRun=options.dry_run))
File "/usr/sbin/up2date-nox", line 1126, in batchRun
batch.init()
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 65, in init
self.__findPackagesToUpdate()
File "/usr/share/rhn/up2date_client/up2dateBatch.py", line 101, in __findPackagesToUpdate
plist.addGlobs(self.listOfGlobs)
File "/usr/share/rhn/up2date_client/packageList.py", line 161, in addGlobs
availList = rhnPackageInfo.getAvailablePackageList()
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 235, in getAvailablePackageList
package_list = availablePackageList(
File "/usr/share/rhn/up2date_client/rhnPackageInfo.py", line 169, in availablePackageList
progressCallback = progressCallback)
File "/usr/share/rhn/up2date_client/rpcServer.py", line 236, in doCall
ret = apply(method, args, kwargs)
File "/usr/share/rhn/up2date_client/repoDirector.py", line 22, in listPackages
return self.handlers[channel['type']].listPackages(channel, msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/rpmSource.py", line 229, in listPackages
msgCallback, progressCallback)
File "/usr/share/rhn/up2date_client/repoBackends/yumRepo.py", line 191, in listPackages
channelTimeStamp = time.strptime(oldVersion,"%Y%m%d%H%M%S")
File "/usr/lib/python2.3/_strptime.py", line 424, in strptime
raise ValueError("time data did not match format: data=%s fmt=%s" %

That is from the up2date log.


Is there anyway to make the auto-installer for sitebuilder skip the up2date program and just upgrade the sitebuilder?

 

[caustic]

this is clearly an up2date issue.

Is there anyway to make the auto-installer for sitebuilder skip the up2date program and just upgrade the sitebuilder?
Try temporary removing /etc/sysconfig/rhn/systemid or/and /etc/sysconfig/rhn/up2date and then running autoinstaller.

 

[noimad1]

Wow, that actually worked.

Thank you so much. I was finally able to get the sitebuilder upgraded to version 4.0.

I appreciate your help. Now I just hope that skipping the up2date doesn't kill something on the sitebuilder itself...lol