I used to have a similar issue when I would run MySQL 3.23.x under RedHat
when I used an LDAP server to house my user account information instead of
the standard flat-file /etc files.
To track it down try strace-ing the mysqld and seeing if it's segfaulting
and where it is. That's what was happening to me. The way I addressed
this particular issue was by editing the safe_mysqld script to manually
run the mysqld server process as the mysql user using the su -c syntax.
--Jason
On Wed, 6 Aug 2003, downtime null wrote:
> zap reset it, but it's still not really starting. if i run
> '/etc/init.d/mysql start', there is no mysql process started. there
> aren't even any new entries in any log files that i can see from
> trying to start it.
>
> is anyone else having a similar problem?
>
> On Wed, Aug 06, 2003 at 11:24:18PM -0400, gabriel wrote:
> > On August 6, 2003 11:20 pm, downtime null wrote:
> > > when i recently ran 'emerge -U world', mysql was upgraded to 4.0 which
> > > i'm happy about. the only problem is that it won't start and it won't
> > > stop. when i run '/etc/init.d/mysql start' it says that it's already
> > > running, but when i run '/etc/init.d/mysql stop' it says '[!!]'. and
> > > there is never any mysqld running at any time during that process. i
> > > don't know what happened. i don't know if it ever worked since i
> > > upgraded. i would suspect that it didn't.
> >
> > try:
> >
> > # /etc/init.d/mysql zap
> > # /etc/init.d/mysql start
> >
> > "zap" should reset the daemon to appear stopped.
> >
> >
> > --
> > we live as though the world is as it should be
> > to show it what it can be
> > - angel, angel "deep down"
> >
> >
> > --
> > [EMAIL PROTECTED] mailing list
> >
>
> --
> [EMAIL PROTECTED] mailing list
>
>
--
Jason A. Pfeil 811 Harbor Winds Dr.
Jacksonville, FL 32225
jason=at=jasonpfeil.com.NOSPAM
--
[EMAIL PROTECTED] mailing list
