[CLUE-Tech] installing mysql on Redhat 8.0

[Ed Young]

locate yields no occurrence of the libmysqlclient.so.10 and neither does
find!

I ran rpm -qli mysql and it returned with a bunch of files in locations that
do not exist on this system. Does it query some database that may or may not
reflect the reality of this system?

I  tried to remove the mysql package and got  dependency errors from
mysql-server and perl-DBD-MySQL. When I tried to rpm -e mysql-server the rpm
call never returned. ctrl-c does nothing to stop it.

At this point I'm guessing the rpm "database" system is corrupted (Berkely
DB?).

For the record, this is a system that has been unadulterated by the
installation of any packages other than from the initial install and from
up2date and most recently the mysql packages in question that I downloaded
from the Redhat site. I've until recently only used to surf the web, and
perform the up2date processes that Redhat graciously alerts me to do.

I can't conclude anything now except that the package management is whacked
on this system, despite the little check mark in the toolbar assuring me I'm
"up2date".

Is this someone's way of telling me to go back to Debian?



>
> > I'm trying to get MySQLAdmin and mysql-server installed on a redhat 8
> > system but am having installation problems. It seems that the install is
> > broken, and many mysql files are missing, or I haven't set mysql up
> > correctly.
> ...
> > [root at gerakina MySQL]# /usr/bin/mysqladmin
> > /usr/bin/mysqladmin: error while loading shared libraries:
> > libmysqlclient.so.10: cannot open shared object file: No such file or
> > directory.
> >
> > The above shared library doesn't exist on my system and there isn't
> > even a /usr/lib/mysql directory...
>
> Sounds like a broken install. I don't use up2date, so I can't even guess
> how that might happen. Does up2date save any log information you can look
> through?
>
> I'd use the locate command to see if the library is anywhere on the
> system. That might be nothing more than just curiosity though, unless
> you're OK with running using wherever things wound up. I wouldn't go for
> that myself, because it might cause problems later on, when a newer
> version installs in the standard location. I doubt the files went to some
> other directory though, although I think it's possible to do that with rpm
> (using --prefix and/or --relocate), but why would up2date do that?
>
> I guess what I'd try would be to uninstall it using 'rpm -e {package
> names}' and then reinstall, but again using 'rpm -i' instead of up2date.
>
> jed
>
> -- 
> I wouldn't even think about bribing a rottweiler with a steak that
> didn't weigh more than I do. -- Jason Earl
> _______________________________________________
> CLUE-Tech mailing list
> CLUE-Tech at clue.denver.co.us
> http://clue.denver.co.us/mailman/listinfo/clue-tech