Thank you!
Sorry for my frustration, but I have been wrestling with this for a
week. In that time, I have neither seen meaningful suggestions, nor
have I seen help for a few others with similar problems.
I would still like to see a list of warnings that would alert me to
pitfalls and other dan
You shouldn't have to reinstall Linux, just uninstall the old RPM, or
delete the old version which was installed from source, and install the
new version if it be from RPM or whatever. There is no way that the
manual could cover every installation medium that exists (RPM, tar, DEB,
BSD Ports tree
BUG: Telling me I "shouldn't have done" something, not even mentioned
in the manual, does not help me fix the problem.
BUG: Having to completely reinstall the operating system (Linux) in
order to repair problems with a mysql install. Or does someone
actually have any recommendations on this?
I had sent this earlier, but it got waylaid (twice). Perhaps the mail-
server was temporarily down.
Okay, I got rid of EVERYTHING (except the data, which got backed up
in douplicate), and did a fresh install from a tarball, f
I wish I could say that helped, Sean.
I still don't know if I should try a specific command to fix things,
or move/remove a specific file first, or completely reinstall Linux
and start from scratch. The last option is least desirable, as I will
have the most things to reconstruct on the system.
It sounds like the problem is that you originally installed from RPM and
later installed from source, or vice versa. RPMs often use a different
file layout than source distributions, this is one reason why I always
install software that I consider system critical from source, so that
there are no
There must be a bug here somewhere.
I have just made three attempts to reinstall mysql, one from rpm, two
from tarball. This is a Redhat6.1 system with 160meg of ram and mysql
once ran on it, until I gave it an incorrect shutdown command.
(It should not break so easily.)
User and group "mysql
Thank you.
I got /usr/local/mysql/bin/mysqld as the only return from that find
command.
I'll try again from a tarball.
On 23 Feb 2001, at 14:58, Atle Veka wrote:
>
> It might have installed it in a separate place. I believe the default
> might be /usr/local/libexec/mysqld.
>
> Do a 'find /usr
It might have installed it in a separate place. I believe the default
might be /usr/local/libexec/mysqld.
Do a 'find /usr/ -name "mysqld"' to attempt to find your binary.
I always like to install stuff by source, cuz then I can always specify
where things go :) RPM usually should work fine, but
I do believe I have a mess on my hands.
Lacking any other guidance, I tried upgrading my mysql to 3.23 with
an rpm on a Redhat Linux 6.1 system. I now have the same directory
layout for mysql as on my Redhat 7 server, except there is no daemon
to be found there. The only mysql daemon found anyw
I had shut down the mysql daemon using:
bin/mysql -u root -p[password] shutdown
Now when I attempt to restart it using:
bin/safe_mysql &
it gives me the message:
[1] 2564
The file /usr/local/mysql/libexec/mysqld doesn't exist or is not
executable
Ple
Thank you.
Re:
On 21 Feb 2001, at 16:29, Atle Veka wrote:
> where's your mysqld located?
/usr/local/mysql/bin
> just change your safe_mysql script to contain the correct location of
> your mysqld binary.
I thought that was what I was doing with "bin/safe_mysqld &" from
/usr/local/mysql/ I wo
where's your mysqld located?
just change your safe_mysql script to contain the correct location of your
mysqld binary.
also, i *think* mysqladmin -uroot -p[pass] shutdown
is the preferred shutdown mechanism, didn't even know you could do that
with mysql (client).
are you sure it's actually sto
13 matches
Mail list logo
