minor feedback on install.sh errors

6 posts / 0 new
Last post
#1 Mon, 10/01/2007 - 08:09
maxslug

minor feedback on install.sh errors

centos 5.0, fresh out of the box, Xen instance.
[code:1]

add this to the [main] section of /etc/yum.conf if you are on an x86_64 box exclude=*.i386 *.i586 *.i686 vi /etc/yum.conf

yum update yum install perl yum install wget yum install slocate yum install tar wget http://software.virtualmin.com/gpl/scripts/install.sh chmod +x install.sh ./install.sh [/code:1]

Above works great!

Here is the error message I was getting before I added slocate, included here for googlers of the future.

[code:1] Checking for curl or wget...found /usr/bin/wget -nv Checking for perl...found /usr/bin/perl 23:05:11 URL:http://software.virtualmin.com/lib/spinner [182/182] -> "spinner" [1] Loading log4sh logging library... 23:05:11 URL:http://software.virtualmin.com/lib/log4sh [21395/21395] -> "log4sh" [1] INFO - Started installation log in virtualmin-install.log INFO - Checking for fully qualified hostname... INFO - Hostname OK: fully qualified as borkborkbork INFO - Installing serial number and license key into /etc/virtualmin-license INFO - Loading OS selection library... 23:05:12 URL:http://software.virtualmin.com/lib/oschooser.pl [4448/4448] -> "oschooser.pl" [1] INFO - Download of http://software.virtualmin.com/lib/oschooser.pl Succeeded. INFO - Loading OS list... 23:05:12 URL:http://software.virtualmin.com/lib/os_list.txt [3473/3473] -> "os_list.txt" [1] INFO - Download of http://software.virtualmin.com/lib/os_list.txt Succeeded. INFO - Operating system name: CentOS Linux INFO - Operating system version: 5 INFO - Installing virtualmin-release package for CentOS Linux 5... INFO - Disabling SELinux during installation... /usr/sbin/setenforce: SELinux is disabled INFO - setenforce 0 failed: 1 error: /usr/share/rhn/RPM-GPG-KEY: import read failed(-1). 23:05:13 URL:http://software.virtualmin.com/gpl/rhel/5/x86_64/virtualmin-release-late... [10572/10572] -> "virtualmin-release-latest.noarch.rpm" [1] INFO - Download of http://software.virtualmin.com/gpl/rhel/5/x86_64/virtualmin-release-late... Succeeded. warning: virtualmin-release-latest.noarch.rpm: Header V3 DSA signature: NOKEY, key ID a0bdbcf9 Running updatedb so locate works...this will take a little while. /var/tmp/rpm-tmp.19722: line 12: updatedb: command not found Attempting to import various system RPM-GPG-KEY files...Errors may occur, if you've already imported them. It is safe to ignore these errors. /var/tmp/rpm-tmp.19722: line 39: locate: command not found INFO - Succeeded.

[/code:1]

EDIT2: Tar was needed by webmin but not installed, added it byhand to the pre-install process, also added blurb from below about x86_64

-m

Post edited by: maxslug, at: 2007/10/01 08:31<br><br>Post edited by: maxslug, at: 2007/10/01 09:20

Mon, 10/01/2007 - 08:13
maxslug

Oops, problems...

[code:1]
Transaction Check Error:
file /usr/share/man/man1/asn1parse.1ssl.gz from install of openssl-0.9.8b-8.3.el5 conflicts with file from package openssl-0.9.8b-8.3.el5
file /usr/share/man/man1/nseq.1ssl.gz from install of openssl-0.9.8b-8.3.el5 conflicts with file from package openssl-0.9.8b-8.3.el5
file /usr/share/man/man1/ocsp.1ssl.gz from install of openssl-0.9.8b-8.3.el5 conflicts with file from package openssl-0.9.8b-8.3.el5
file /usr/share/man/man1/smime.1ssl.gz from install of openssl-0.9.8b-8.3.el5 conflicts with file from package openssl-0.9.8b-8.3.el5
[/code:1]

EDIT: This seems to be a case of this bug : <a href='http://bugs.centos.org/view.php?id=1356' target='_blank'>http://bugs.centos.org/view.php?id=1356</a>
&quot;0001356: Yum installs i386 and x86_64 packages&quot; . I am indeed installing on an x86_64 platform.

Still trying to figure out how to fix the install process.
-m&lt;br&gt;&lt;br&gt;Post edited by: maxslug, at: 2007/10/01 08:40

Mon, 10/01/2007 - 08:42 (Reply to #2)
Joe
Joe's picture

Me neither. There's a bug in the CentOS bug tracker about it, but they don't seem to think it's a problem. I'm not sure <i>how</i> they can think that it's not a problem, but they do.

It comes from the fact that there is a 32 bit and a 64 bit version of openssl, and they have some of the same files. They should be installable simultaneously, since the only reason you'd need a 32 bit build is for compatibility with oddball binary only software--which means you'd want the 64 bit package, too, for all of the other stuff that isn't a binary only build.

Frankly, I don't know what to do about it. If the CentOS folks don't want to believe it's a problem, there's not a lot I can do to convince them it is. (And if we replaced their packages, it would introduce some new issues.)

In the short-term, you can workaround it by removing &quot;openssl&quot; from the rhdeps variable in install.sh. It's safe to do so, since you obviously already have openssl installed. (Note that if you didn't have openssl installed, this error wouldn't occur.)

--

Check out the forum guidelines!

Mon, 10/01/2007 - 08:52 (Reply to #3)
maxslug

Thanks for the fast reply. I removed all occurances of 'openssl' from install.sh and I still get the same dependency failure. I'm guessing that it's still checking this dependency from another related package?

Package management is never fun :-)

-m

Mon, 10/01/2007 - 08:57 (Reply to #4)
maxslug

OK, I got around it using the suggested (albeit kludge-tastic) line in my yum.conf :

[code:1]
[main]
exclude=*.i386 *.i586 *.i686
[/code:1]

It's now on to installing the virtualmin-base package with a couple warnings which i'm ignoring.

[code:1]
|warning: perl-IO-Socket-INET6-2.51-2.fc6: Header V3 DSA signature: NOKEY, key ID e8562897

...
-warning: cyrus-sasl-plain-2.1.22-4: Header V3 DSA signature: NOKEY, key ID e8562897
|chcon: can't apply partial context to unlabeled file /usr/share/awstats/wwwroot/cgi-bin
chcon: can't apply partial context to unlabeled file /var/lib/awstats
/sh: /usr/lib/sasl2/smtpd.conf: No such file or directory
sh: /usr/lib/sasl2/smtpd.conf: No such file or directory
[/code:1]

-m

Mon, 10/01/2007 - 09:31 (Reply to #5)
maxslug

Success! Now on to the normal installation procedures. Man, even w/ some small snafus, that was only 2 hours start to finish. you guys rock.

Topic locked