I am trying to install Samba on RedHat9 so that I can share files with a Windows XP machine on a LAN. The install fails:

# rpm -Uvh samba*
error: Failed dependencies:
libcrypto.so.2 is needed by samba-2.2.7-5.8.0
libssl.so.2 is needed by samba-2.2.7-5.8.0
libcrypto.so.2 is needed by samba-common-2.2.7-5.8.0
libssl.so.2 is needed by samba-common-2.2.7-5.8.0
libcrypto.so.2 is needed by samba-swat-2.2.7-5.8.0
libssl.so.2 is needed by samba-swat-2.2.7-5.8.0

Here is what I have tried, without success:

1) Use rpm to install the older version of openssl in addition to the current one:

# rpm -Uvh openssl-0.9.6b-33.i686.rpm openssl-0.9.7a-5.i686.rpm
warning: package openssl = 0.9.6b-33 was already added, replacing with openssl <= 0.9.7a-5
Preparing... ########################################### [100%]
package openssl-0.9.7a-5 is already installed

2) Create the two needed files as symbolic links. Created in both /lib and /usr/lib since the "real" file was in both places.

# ln -s /lib/libcrypto.so.0.9.7a /lib/libcrypto.so.2
# ln -s /lib/libssl.so.0.9.7a /lib/libssl.so.2
# ln -s /usr//lib/libcrypto.so.0.9.7a /usr/lib/libcrypto.so.2
# ln -s /usr/lib/libssl.so.0.9.7a /usr/lib/libssl.so.2

# ll /usr/lib/libssl.so.2 /usr/lib/libcrypto.so.2
lrwxrwxrwx 1 root root 28 May 15 18:03 /usr/lib/libcrypto.so.2 -> /usr/lib/libcrypto.so.0.9.7a
lrwxrwxrwx 1 root root 25 May 15 18:03 /usr/lib/libssl.so.2 -> /usr/lib/libssl.so.0.9.7a
# ll /lib/libssl.so.2 /lib/libcrypto.so.2
lrwxrwxrwx 1 root root 19 May 15 18:03 /lib/libcrypto.so.2 -> libcrypto.so.0.9.7a
lrwxrwxrwx 1 root root 16 May 15 18:03 /lib/libssl.so.2 -> libssl.so.0.9.7a


After doing these steps, I get the same error trying to install samba. How the heck do I get these two files? Why don't the symbolic links work?

David

First, the link don't work since rpm does not check if the file exist on the system. It uses a database to log what as been installed on the system.

I have three idea that could help you:

1-
Try to run rpm with the consistency switch (don't remember what it). This switch will check the rmp database and see if it is corupted. Try to reinstall afterward.

2-
What if you try to install the RPM without the dependency.

3-
What if you try to uninstall the problematic packages and reinstall them. (I know looks a bit like a windows approch but it would make sure you have not acidently deleted some files of the package)

I can confirm that the symbolic links don't work. I managed to extract the two files I needed, copy them to the /usr/lib and /lib directories, and update the symbolic links. No go. The files are there and the symbolic links are there, but rpm insists it knows better.

1) # rpm --rebuilddb -v
error: db4 error(16) from dbenv->remove: Device or resource busy

Do I need to specify the --dbpath or --root options? They are listed as optional, and I'd expect the defaults to be correct.

2) Do you mean --force? I tried that. I get the same messages with or without --force.

3) I tried uninstalling openssl, but I got a bazillion errors about other packages being dependent on things I was uninstalling. I did not try forcing it, but that might be what I try next.

David

I got it to install using --nodeps to get rpm to igore the dependencies. Normally this might not work, but the files are there, it's just the rpm database that doesn't KNOW the files are there. At least, that is what I believe to be true at this time.

I can get into SWAT. I don't know what to DO with it, but that's a different story, and a different thread.

David

Just to make sure, did you run the rpm --rebuilddb -v
command as root?

As for the --dbpath it should not be needed. I'm usure as to what the --root does.

The error from --rebuilddb suggest your rpm database is corupted AND someone is stuck in it. You could do two things:

- run ps -A to see if the is an rpm process running. if there is, kill it ( kill -9 $pid) (where $pid is the number next to the rpm line fom ps -A)
After that retry --rebuilddb

- If it still does not work. Reboot in single user mode. From there, run the rebuilddb.

I was logged in as root, or rather "super usered" to root. I logged out and back in and the "lock" went away.

I wish I had seen your post before I did that. It would have given me more understanding of what was going on than the band-aid of logging out or rebooting. Rebooting is a habit I've picked up from Windows. :-)

David