Can't pass dependency check on RHEL 4 ES x86_64 system

Discuss installation of Scalix software

Moderators: ScalixSupport, admin

patrickmcshane
Posts: 25
Joined: Thu Mar 16, 2006 8:32 pm
Location: San Diego, CA
Contact:

Can't pass dependency check on RHEL 4 ES x86_64 system

Postby patrickmcshane » Fri Mar 17, 2006 8:59 pm

Hi again,

I have loaded every package as per Scalix 10 installation PDF file on our RHEL ES 4 x86_64 system and still cannot pass the dependency check. Please advise as to what packages still may be missing given the library dependecies listed in the "System check report:" listed below. This is a 64bit Redhat EL ES 4 environment. Any help would be appreciated .

Thanks,
Pat


System check report:

Environment check passed.
Filesystem check passed.
Network check passed.
Dependency check warning -- The following packages will be installed next to resolve conflicts:
libical
Dependency check failed -- Please resolve the following package conflicts and re-run the system checks:
libcrypto.so.4 is needed by scalix-server-10.0.0.175-1.rhel4.i386
libgssapi_krb5.so.2 is needed by scalix-server-10.0.0.175-1.rhel4.i386
libkrb5.so.3 is needed by scalix-server-10.0.0.175-1.rhel4.i386
libldap-2.2.so.7 is needed by scalix-server-10.0.0.175-1.rhel4.i386
libncurses.so.5 is needed by scalix-server-10.0.0.175-1.rhel4.i386
libsasl2.so.2 is needed by scalix-server-10.0.0.175-1.rhel4.i386
libssl.so.4 is needed by scalix-server-10.0.0.175-1.rhel4.i386
Running services check warning -- A non-Scalix LDAP service is enabled at this run level. You must disable this before trying to run Scalix server.
Running services check failed -- A non-Scalix LDAP service is already running. You must stop it before starting Scalix server.

-> Please fix the problems and press Enter to run the system checks again or press CTRL-C to quit [Run Again]:
Regards,
Pat

ScalixSupport
Scalix
Scalix
Posts: 5503
Joined: Thu Mar 25, 2004 8:15 pm

Postby ScalixSupport » Sat Mar 18, 2006 12:31 am

The message is self-explanatory. You have something listening on port 389. The command

Code: Select all

lsof -i :389
will show you what processes are doing that. As the message says, you will need to stop that process before you can proceed.

If you run the command

Code: Select all

netstat -an | grep 389
this will show you if anything is listening on any port containing 389. It may also be best to kill those processes as well.


Cheers

Dave

patrickmcshane
Posts: 25
Joined: Thu Mar 16, 2006 8:32 pm
Location: San Diego, CA
Contact:

Solved

Postby patrickmcshane » Sat Mar 18, 2006 10:24 pm

Dave,

Thanks for the response. I know I have OpenLDAP running and that will be another post as I will be using OpenLDAP for primary auth and as the central user store. Not Scalix LDAP.

I was refering to the library objects and other dependencies that were listed. As this is a 64 bit RHEL ES 4 installation, I finally had to go back and bring in all the "compat-" packages which resolved the problem (the Compat software groups). I had forgotten to uncheck and re-check the Compat group which left many of the i386 arch packages out.

Sure wish Redhat would bring YUM into the distribution!!! :D

up2date needs a a serious "up2date" :wink:

Regards,
Pat
Regards,

Pat


Return to “Installation”



Who is online

Users browsing this forum: No registered users and 3 guests