dsm update stuck or something?

[jumbonet]

This issue has still gone unresolved and I still haven't received any reply from it.

My dsm update keeps telling me ImageMagick and Mysql is due for an update but when I run an update it says mysql cannot be updated and after it apppears to be finished downloading. it still tells me that imagemagick needs to be updated.

Also, for the Redhat Errata section. It's stuck trying to tell me to update my xinetd package and has no effect when i run the update.

Is there a way to reset or refresh this?

[LeeJ]

Send in a support request ticket so that we can take a look.

[musictech]

Mine does the same exact thing ever since I did the urgent redhat update via command line "up2date -u" that the hosting company said we all needed to do because of a severe security hole.

Everytime I go to the DSM update page, it tells me that ImageMagick packages are available for DSM and the xinetd RedHat errata package is available. If I choose them and do the install it appears that everything goes correctly and I get a successful message, but the next time I go to update they are still there.

Everything still seems to be working fine, and I've been doing redhat updates via the command line as directed by the hosting company, so I haven't worried about it too much.

[parawing742]

Same problem here. It started happening after running up2date on my server.

[LeeJ]

Below is the version that we offer for download which is a redhat errata release.

Name : xinetd Relocations: (not relocateable)
Version : 2.3.9 Vendor: Red Hat, Inc.
Release : 0.73 Build Date: Wed 02 Oct 2002 07:32:49
AM MST
Install date: (not installed) Build Host: stripples.devel.redhat.c

Below is the version on machines that up2date has been run on.

Version : 2.3.7 Vendor: Red Hat, Inc.
Release : 4.7x Build Date: Tue 19 Nov 2002 10:00:23
AM MST
Install date: Fri 06 Dec 2002 07:30:15 PM MST Build Host: stripples.devel.r
edhat.com
Group : System Environment/Daemons Source RPM: xinetd-2.3.7-4.7x.src.rp
m

Even when trying to update via the command line you get the below output.

[root@ns1 root]# rpm -Uvh xinetd-2.3.9-0.73.i386.rpm
Preparing... ########################################### [100%]
package xinetd-2.3.7-4.7x (which is newer than xinetd-2.3.9-0.73) is already installed
[root@ns1 root]#


We will be submitting this to the rpm list to see if we can get any type of explainiation and will post in the forum once we get a reply.

[jumbonet]

What about your findings on the MySql and ImageMagick packages?

Also, if my version is newer than the one requested by up2date then why is
it stuck there on your update screen?

At least that's three people complaining about this. ;)

For a minute there i thought it was my screw up again.

[Staff]

If you look closely at Joel's post, the version we are trying to install IS newer. The one on our update servers is 2.3.9 and more some reason RPM seems to think that 2.3.7 is newer. We are investigating this issue currently.

[jumbonet]

that's exactly what i mean. i said "my version" - which is obviously from your copy.

sorry for the confusion.

[jumbonet]

If it's any worth. I don't think redhat linux reacts kindly by installing RPMs not part of their distribution. Even IF the app you're installing happens to be part of their distro but you got it from another source. e.g. If you download mysql RPM from mysql.com, (of course, we know redhat has mysql with it) up2date will complain about package dependencies and some rpms not being there even if you have complate mysql packages and dependencies.

I recently had this problem with another server i was using. I had to uninstall the one i downloaded from the official website of the app and use the one that came with redhat. otherwise up2date will error out and exit.

[Gyrbo]

From the commandline, you can add the --force flag. This will force the update, no matter what.
However, be carefull because it can break things.