Topic: update not installing

[gixmo]

I've just been trying to install the available updates through the server-manager.
I get these messages :

Loading "fastestmirror" plugin
Loading "smeserver" plugin
Setting up Update Process
Setting up repositories
Loading mirror speeds from cached hostfile
Reading repository metadata in from local files
Excluding Packages from CentOS - os
Finished
Excluding Packages from CentOS - updates
Finished
Resolving Dependencies
--> Populating transaction set with selected packages. Please wait.
---> Package yum.noarch 0:2.4.3-3.el4.centos set to be updated
---> Package audit.i386 0:1.0.15-3.EL4 set to be updated
---> Package libstdc++.i386 0:3.4.6-8 set to be updated
---> Package dosfstools.i386 0:2.8-18 set to be updated
---> Package unzip.i386 0:5.51-9.EL4.5 set to be updated
---> Package php-mysql.i386 0:4.3.9-3.22.5 set to be updated
---> Package procps.i386 0:3.2.3-8.6 set to be updated
---> Package mutt.i386 5:1.4.1-12.el4 set to be updated
---> Package net-snmp-utils.i386 0:5.1.2-11.EL4.10 set to be updated
---> Package net-tools.i386 0:1.60-37.EL4.9 set to be updated
---> Package xorg-x11-libs.i386 0:6.8.2-1.EL.18 set to be updated
---> Package rpm.i386 0:4.3.3-22_nonptl set to be updated
---> Package lvm2.i386 0:2.02.21-5.el4 set to be updated
---> Package rpm-build.i386 0:4.3.3-22_nonptl set to be updated
---> Package iputils.i386 0:20020927-19.EL4.5 set to be updated
---> Package openldap.i386 0:2.2.13-7.4E set to be updated
---> Package kernel-utils.i386 1:2.4-13.1.99 set to be updated
---> Package libxml2.i386 0:2.6.16-10 set to be updated
---> Package dbus.i386 0:0.22-12.EL.9 set to be updated
---> Package words.noarch 0:3.0-3.2 set to be updated
---> Package pciutils.i386 0:2.1.99.test8-3.4 set to be updated
---> Package gd.i386 0:2.0.28-5.4E set to be updated
---> Package elfutils.i386 0:0.97.1-4 set to be updated
---> Package netpbm-progs.i386 0:10.25-2.EL4.6 set to be updated
---> Package openssh-clients.i386 0:3.9p1-8.RHEL4.20 set to be updated
---> Package postgresql-libs.i386 0:7.4.17-1.RHEL4.1 set to be updated
---> Package mod_ssl.i386 1:2.0.52-32.ent.centos4 set to be updated
---> Package usermode.i386 0:1.74-2 set to be updated
---> Package device-mapper.i386 0:1.02.17-3.el4 set to be updated
---> Package php-domxml.i386 0:4.3.9-3.22.5 set to be updated
---> Package libattr.i386 0:2.4.16-3.1.el4 set to be updated
---> Package dmraid.i386 0:1.0.0.rc14-5_RHEL4_U5 set to be updated
---> Package util-linux.i386 0:2.12a-16.EL4.25 set to be updated
---> Package dhcp.i386 7:3.0.1-59.EL4 set to be updated
---> Package rpmdb-CentOS.i386 2:4.5-0.20070506 set to be updated
---> Package openldap-servers.i386 0:2.2.13-7.4E set to be updated
---> Package rpm-python.i386 0:4.3.3-22_nonptl set to be updated
---> Package net-snmp-libs.i386 0:5.1.2-11.EL4.10 set to be updated
---> Package cracklib.i386 0:2.8.9-1.3 set to be updated
---> Package strace.i386 0:4.5.15-1.el4.1 set to be updated
---> Package rhpl.i386 0:0.148.5-1 set to be updated
---> Package hwdata.noarch 0:0.146.28.EL-1 set to be updated
---> Package cpio.i386 0:2.5-13.RHEL4 set to be updated
---> Package php.i386 0:4.3.9-3.22.5 set to be updated
---> Package python-sqlite.i386 0:1.1.7-1.2.1 set to be updated
---> Package openssl.i686 0:0.9.7a-43.16 set to be updated
---> Package ntp.i386 0:4.2.0.a.20040617-6.el4 set to be updated
---> Package kudzu.i386 0:1.1.95.22-1 set to be updated
---> Package httpd.i386 0:2.0.52-32.ent.centos4 set to be updated
---> Package samba.i386 0:3.0.10-1.4E.12.2 set to be updated
---> Package cracklib-dicts.i386 0:2.8.9-1.3 set to be updated
---> Package comps.i386 2:4.5CENTOS-0.20070506 set to be updated
---> Package glibc-common.i386 0:2.3.4-2.36 set to be updated
---> Package iproute.i386 0:2.6.9-3.EL4.7 set to be updated
---> Package grep.i386 0:2.5.1-32.3 set to be updated
---> Package curl.i386 0:7.12.1-11.el4 set to be updated
---> Package python.i386 0:2.3.4-14.4 set to be updated
---> Package enscript.i386 0:1.6.1-33.el4 set to be updated
---> Package squid.i386 7:2.5.STABLE14-1.4E set to be updated
---> Package php-mbstring.i386 0:4.3.9-3.22.5 set to be updated
---> Package SysVinit.i386 0:2.85-34.4 set to be updated
--->Error: Missing Dependency: initscripts >= 7.93.26.EL-1 is needed by package httpd
 Package quota.i386 1:3.12-6.el4 set to be updated
---> Package audit-libs.i386 0:1.0.15-3.EL4 set to be updated
---> Package php-imap.i386 0:4.3.9-3.22.5 set to be updated
---> Package php-gd.i386 0:4.3.9-3.22.5 set to be updated
---> Package popt.i386 0:1.9.1-22_nonptl set to be updated
---> Package python-elementtree.i386 0:1.2.6-5.el4.centos set to be updated
---> Package sqlite.i386 0:3.3.6-2 set to be updated
---> Package freeradius.i386 0:1.0.1-3.RHEL4.5 set to be updated
---> Package samba-client.i386 0:3.0.10-1.4E.12.2 set to be updated
---> Package netpbm.i386 0:10.25-2.EL4.6 set to be updated
---> Package cups-libs.i386 1:1.1.22-0.rc1.9.20 set to be updated
---> Package attr.i386 0:2.4.16-3.1.el4 set to be updated
---> Package hal.i386 0:0.4.2-6.EL4 set to be updated
---> Package sysstat.i386 0:5.0.5-14.rhel4 set to be updated
---> Package coreutils.i386 0:5.2.1-31.6 set to be updated
---> Package net-snmp.i386 0:5.1.2-11.EL4.10 set to be updated
---> Package dhclient.i386 7:3.0.1-59.EL4 set to be updated
---> Package glibc.i686 0:2.3.4-2.36 set to be updated
---> Package httpd-suexec.i386 0:2.0.52-32.ent.centos4 set to be updated
---> Package pam.i386 0:0.77-66.21 set to be updated
---> Package dbus-glib.i386 0:0.22-12.EL.9 set to be updated
---> Package e2fsprogs.i386 0:1.35-12.5.el4 set to be updated
---> Package gamin.i386 0:0.1.7-1.2.EL4 set to be updated
---> Package openssh.i386 0:3.9p1-8.RHEL4.20 set to be updated
---> Package xorg-x11-Mesa-libGL.i386 0:6.8.2-1.EL.18 set to be updated
---> Package samba-common.i386 0:3.0.10-1.4E.12.2 set to be updated
---> Package libxml2-python.i386 0:2.6.16-10 set to be updated
---> Package centos-release.i386 6:4-4.3 set to be updated
---> Package hotplug.i386 3:2004_04_01-7.8 set to be updated
---> Package rpm-libs.i386 0:4.3.3-22_nonptl set to be updated
---> Package krb5-libs.i386 0:1.3.4-47 set to be updated
---> Package php-pear.i386 0:4.3.9-3.22.5 set to be updated
---> Package binutils.i386 0:2.15.92.0.2-22 set to be updated
---> Package elfutils-libelf.i386 0:0.97.1-4 set to be updated
---> Package ImageMagick.i386 0:6.0.7.1-17 set to be updated
---> Package module-init-tools.i386 0:3.1-0.pre5.3.4 set to be updated
---> Package grub.i386 0:0.95-3.8 set to be updated
---> Package ftp.i386 0:0.17-23.EL4 set to be updated
---> Package libselinux.i386 0:1.19.1-7.3 set to be updated
---> Package openssh-server.i386 0:3.9p1-8.RHEL4.20 set to be updated
---> Package libacl.i386 0:2.2.23-5.3.el4 set to be updated
---> Package sed.i386 0:4.1.2-6.el4 set to be updated
---> Package shadow-utils.i386 2:4.0.3-61.RHEL4 set to be updated
---> Package libgcc.i386 0:3.4.6-8 set to be updated
---> Package php-ldap.i386 0:4.3.9-3.22.5 set to be updated
--> Running transaction check
--> Processing Dependency: initscripts >= 7.93.26.EL-1 for package: httpd
--> Finished Dependency Resolution
yum update ImageMagick.i386 SysVinit.i386 attr.i386 audit-libs.i386 audit.i386 binutils.i386 centos-release.i386 comps.i386 coreutils.i386 cpio.i386 cracklib-dicts.i386 cracklib.i386 cups-libs.i386 curl.i386 dbus-glib.i386 dbus.i386 device-mapper.i386 dhclient.i386 dhcp.i386 dmraid.i386 dosfstools.i386 e2fsprogs.i386 elfutils-libelf.i386 elfutils.i386 enscript.i386 freeradius.i386 ftp.i386 gamin.i386 gd.i386 glibc-common.i386 glibc.i686 grep.i386 grub.i386 hal.i386 hotplug.i386 httpd-suexec.i386 httpd.i386 hwdata.noarch iproute.i386 iputils.i386 kernel-utils.i386 krb5-libs.i386 kudzu.i386 libacl.i386 libattr.i386 libgcc.i386 libselinux.i386 libstdc++.i386 libxml2-python.i386 libxml2.i386 lvm2.i386 mod_ssl.i386 module-init-tools.i386 mutt.i386 net-snmp-libs.i386 net-snmp-utils.i386 net-snmp.i386 net-tools.i386 netpbm-progs.i386 netpbm.i386 ntp.i386 openldap-servers.i386 openldap.i386 openssh-clients.i386 openssh-server.i386 openssh.i386 openssl.i686 pam.i386 pciutils.i386 php-domxml.i386 php-gd.i386 php-imap.i386 php-ldap.i386 php-mbstring.i386 php-mysql.i386 php-pear.i386 php.i386 popt.i386 postgresql-libs.i386 procps.i386 python-elementtree.i386 python-sqlite.i386 python.i386 quota.i386 rhpl.i386 rpm-build.i386 rpm-libs.i386 rpm-python.i386 rpm.i386 rpmdb-CentOS.i386 samba-client.i386 samba-common.i386 samba.i386 sed.i386 shadow-utils.i386 sqlite.i386 squid.i386 strace.i386 sysstat.i386 unzip.i386 usermode.i386 util-linux.i386 words.noarch xorg-x11-Mesa-libGL.i386 xorg-x11-libs.i386 yum.noarch failed: 256

The updates are not installed. Does anyone have usefull tips?

[termico]

I've the same problem.

[mudra]

I too have the same problem.

[MarkR]

Me too....

Code: [Select]

Error: Missing Dependency: initscripts >= 7.93.26.EL-1 is needed by package httpd


[socate]

also here...

[Cygnus600]

Me also...

[cactus]

Me too....

Code: [Select]

Error: Missing Dependency: initscripts >= 7.93.26.EL-1 is needed by package httpd


Please follow up in  bug 3002.

[lucho115]

i have the same problem, and the bug 3002 have no solution yet

[cbacani]

The latest error message resulted in this output.


--> Finished Dependency Resolution
Error: Missing Dependency: initscripts >= 7.93.26.EL-1 is needed by package httpd


Anybody else?

[compdoc]

hmm. This might not be related, but before things started working, I added a contrib from dungog, and added their server to my yum repository with this command:

db yum_repositories set dungog repository \
BaseURL http://sme.dungog.net/packages/smeserver/7.0/i386/dungog/ \
EnableGroups yes \
GPGCheck no \
Name 'SME Server 7 - dungog' \
Visible yes \
status enabled

I dont know if that fixed the problem, or if its just a coincidence (probably the latter), but yum update worked after I did that...

Adding their repository is outlined here: http://www.dungog.net/sme/repo.php

[bpivk]

Read the bugtracker. There are a lot of people with this problem (myself included). We reported the bug and are patiently waiting for the solution.

[compdoc]

It's nothing to do with the dungog yum repo - its just working now on it's own. I just updated two of my customer's SME servers with no problems...

[CharlieBrady]

also here...

Can none of you read? What does "Don't report problems here" mean to you? Did you not see it - despite the large red letters?

[compdoc]

Well, the problem is, the bugtracker isnt a forum. It's not read by nearly as many people. It's not nearly as easy to use. It doesnt contain nearly as much information.

And with a name like 'bug tracker' one would think its for tracking bugs, and not for problems that wouldnt be considered a bug, but could be, for example, a individual server's hardware defect.

Why have these forums at all? What are they for if not for people to discuss problems? Why not just take them down if you dont want anyone to use them?

[petero]

I agree. I think this is a good place for starting discussion on a problem which isn't obviously a bug. If it then turns out to be a bug it can be moved to the bug tracker.

Often a problem is due to a lack of knowledge or a particular set-up quirk rather than a bug and that is more easily resolved here.

If you would like to switch us to the bug tracker for a problem it would be helpful to post a link to the entry so that people are easily re-directed.

Thanks,

[pfloor]

Well, the problem is, the bugtracker isnt a forum. It's not read by nearly as many people. It's not nearly as easy to use. It doesnt contain nearly as much information.

You are somewhat mistaken.  The forums contain some good information along with a lot of theories, guesses, possibilities and a huge amount of misinformation.

The bug tracker contains factual and accurate information from those that develop this software.

And with a name like 'bug tracker' one would think its for tracking bugs, and not for problems that wouldnt be considered a bug, but could be, for example, a individual server's hardware defect.

Dozens of users experiencing the same problem is a bug.  Bugs don't get fixed in the forums, they get tracked and fixed in the bug tracker.

Why have these forums at all? What are they for if not for people to discuss problems? Why not just take them down if you dont want anyone to use them?

The forums are fine to discuss configuration, setup, etc questions but when dozens of users are experiencing a bug as obvious as this one, take it to the bug tracker and let the experts fix it.  Discussing it here in the forums won't fix anything.

I agree. I think this is a good place for starting discussion on a problem which isn't obviously a bug. If it then turns out to be a bug it can be moved to the bug tracker.

If this isn't an obvious bug, I can't imagine what it could be.  It was moved to the bug tracker and fixed.  Continuing to try to fix it in the forums is just a waste of time.

If you would like to switch us to the bug tracker for a problem it would be helpful to post a link to the entry so that people are easily re-directed.

This I agree with you 100% and cactus posted the bug number for everyone to follow up.  This thread should have been closed right then and there but people just kept posting to this thread.  The bug was reported at 02:15, analyzed, tracked, fixed, update pushed to the mirrors at around 16:00 and the bug was closed at 17:58.

As you suggest, a link to the bug was posted and all discussion should have moved there, so why are you still here? The bug was fixed 3 hours before you posted.  If you would have clicked the link to the bug and followed it, you would have known that.

[p-jones]

If this isn't an obvious bug, I can't imagine what it could be.

Paul, with respect, try to imagine this situation as being an individual server that has screwed up for whatever reason - a previous power outage & dirty shutdown, an incompatible contrib, old and unreliable hardware, whatever.

Many people on this forum, and I include myself here, just dont have the greater depth of knowledge to differentiate between a bug and an individual server problem and its not till after posting in the forum, and hopefully recieving some mentoring, does it become obvious it needs to be escalated to the bug tracker.

Furthermore, SME is tauted as being a stable reliable and production version compilation so it is not unreasonable (in my opinion) to expect that a bug is not on the top of ones problem solving list. (This is not a criticism, simply a comment)

There are many posts in these forums that could be classed as "dipstick post"  but to the poster, they are very real issues. Sure they are usually borne from a lack of knowledge/understanding not a bug yet quick as a flash, they are pushed over to the bugtracker.

Personally, I think the bug tracker is as friendly as a boa constrictor and I would suspect that to a newbie, who is struggling with the basics of SME, it just scares them off totally.

Having said this, I do see where the "go to the bug tracker" comment is coming from. Once again, I make these comments with respect.

P

[cool34000]

It's getting hot in here!

Thanks to the devteam for fixing this bug so quickly. I guess that's all we should say!

[bpivk]

Well i agree with paul. If 20 users post that they have the same problem that it's a bug. (And for the record... only 4 users reported it to the bugtracker).