SEO

#1 (**permalink**) 02-19-2008, 06:21 AM

in SuSE 9.0 I am getting this message
"Starting service MySQL failed"
in boot.msg

.... but it works?!

MySQL server version: 4.0.15-Max
from SuSE 9 installation

Is this just the first time it tries to load and then it suceeds later?? or
is is something related to a script that misses mysql-maxd??

the running processes are mysqld-max

Needless to say This message bothers me!

Any help explaining and getting rid of this message appreciated!

(I DID find something in the Suse KB about issue in 7.1)

RSP

#2 (**permalink**) 02-19-2008, 06:21 AM

On Fri, 9 Jan 2004, R S Prigan wrote:
> in SuSE 9.0 I am getting this message
> "Starting service MySQL failed"
> in boot.msg
> ... but it works?!
> MySQL server version: 4.0.15-Max
> from SuSE 9 installation
[...]
> Any help explaining and getting rid of this message appreciated!

yes. this problem can be easily resolved by first purchasing the
slackware installation kit from store.slackware.com and then using
that to install slackware on the machine.

--
William Hunt, Portland Oregon USA

#3 (**permalink**) 02-19-2008, 06:22 AM

William Hunt <wjh@huntbros.net> wrote in message news:<Pine.LNX.4.58.0401090439390.9957@worker.hunt bros.net>...
> On Fri, 9 Jan 2004, R S Prigan wrote:
> > in SuSE 9.0 I am getting this message
> > "Starting service MySQL failed"
> > in boot.msg
> > ... but it works?!
> > MySQL server version: 4.0.15-Max
> > from SuSE 9 installation
> [...]
> > Any help explaining and getting rid of this message appreciated!
>
> yes. this problem can be easily resolved by first purchasing the
> slackware installation kit from store.slackware.com and then using
> that to install slackware on the machine.

N\oOw I have Slackware 9.1 on two partiions. I installed Mysql from
the Slack disk using pkgtool. It didn't work. I followed the
directions as best I could in the INSTALL-BINARY file in
/usr/doc/mysql*
It still didn't work.
I downloaded a fresh version from mysql.org and installed it in
/usr/local instead of /usr/share. I followed all the instructions. I
can't even change the mysql user password.

On my Slack 9.1 machine Mysql won't run no matter what I do. So your
advice is bogus in my experience. I will try Pstgresql next. It may be
better. It can't be worse.

John Culleton

#4 (**permalink**) 02-19-2008, 06:22 AM

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

John Culleton <john@wexfordpress.com> is thought to have
typed the following text on 2004-01-09:

> N\oOw I have Slackware 9.1 on two partiions. I installed Mysql from
> the Slack disk using pkgtool. It didn't work. I followed the
> directions as best I could in the INSTALL-BINARY file in
> /usr/doc/mysql*
> It still didn't work.

Didn't google and deja work either?

> On my Slack 9.1 machine Mysql won't run no matter what I do. So your
> advice is bogus in my experience. I will try Pstgresql next. It may be
> better. It can't be worse.
>
I know, Slackware is know for having not-working, untested, buggy
packages. I can't argue with your choice for postgresql, but wouldn't
it be better to make that choice based on other criteria?

- --
Bartosz Oudekerk

AOLS fortune mod volume VI
Get yourself a copy at: <URL:http://www.etv.cx/~bartosz>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE//z3H256ZyNYAOpkRAonNAJ41JLNYD6XBp3I/0DiZjlSiwbU1gQCfStwH
CMAU2xbXQqDR5oI2WHkVvIE=
=aQK8
-----END PGP SIGNATURE-----

#5 (**permalink**) 02-19-2008, 06:22 AM

Bartosz Oudekerk <bartosz@see_my_gnupg-key.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1

> John Culleton <john@wexfordpress.com> is thought to have
> typed the following text on 2004-01-09:

> > N\oOw I have Slackware 9.1 on two partiions. I installed Mysql from
> > the Slack disk using pkgtool. It didn't work. I followed the
> > directions as best I could in the INSTALL-BINARY file in
> > /usr/doc/mysql*
> > It still didn't work.

> Didn't google and deja work either?

Apparently he hasn't yet tried pgp! Methinks pgp would help him
out more than google!

> > On my Slack 9.1 machine Mysql won't run no matter what I do. So your
> > advice is bogus in my experience. I will try Pstgresql next. It may be
> > better. It can't be worse.
> >
> I know, Slackware is know for having not-working, untested, buggy
> packages. I can't argue with your choice for postgresql, but wouldn't
> it be better to make that choice based on other criteria?

IOW, you have nothing to offer this man! At least I suggested he
try pgp!

Please stop posting until you have something useful to say.

BTW: Your continued use of pgp violates this ng's policy, not to
mention usenet netiquette. You are asked, yet AGAIN, to refrain
from using pgp unless necessary.

cordially, as always,

rm

#6 (**permalink**) 02-19-2008, 06:23 AM

In alt.os.linux.slackware, John Culleton dared to utter,
> On my Slack 9.1 machine Mysql won't run no matter what I do.

less /etc/rc.d/rc.mysqld

--
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5

#7 (**permalink**) 02-19-2008, 06:29 AM

Alan Hicks <1001298936@carrier.lizella.net> wrote in message news:<slrnc00pon.udr.1001298936@carrier.lizella.ne t>...
> In alt.os.linux.slackware, John Culleton dared to utter,
> > On my Slack 9.1 machine Mysql won't run no matter what I do.
>
> less /etc/rc.d/rc.mysqld

ah, yes. I chmod -R mysql.mysql /var/lib/mysql and magically things
began to work. thanks for the pointer.

John c.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

SEO

SuSE 9 "Starting service MySQLfailed" ... but it works?!