informations about boot sequence (Re: F15 - mysql start problem)

Tom Lane tgl at redhat.com
Mon May 9 18:30:07 UTC 2011


=?ISO-8859-2?Q?Micha=B3_Piotrowski?= <mkkp4x4 at gmail.com> writes:
> 2011/5/9 Tom Lane <tgl at redhat.com>:
>> I'd be interested to know whether the OP was using a vanilla my.cnf or
>> something custom, and exactly what failure mode he saw.

> In my case

> [mysqld]
> datadir=/home/data/mysql
> socket=/var/lib/mysql/mysql.sock
> user=mysql
> # Disabling symbolic-links is recommended to prevent assorted security risks
> symbolic-links=0
> bind-address = 192.168.101.200

Ah, I'll bet this bind-address setting is what's doing it --- if that
address weren't configured yet, it'd be unsurprising that mysqld would
fail to start.  (The comparable case I tested in postgresql was to set
listen_addresses = 'full.name.of.host', which failed due to DNS not
working yet.  But now that I look at this example, I bet setting
listen_addresses to a numeric IP would have the same issue as your
mysql example.)

Thanks for the followup.

			regards, tom lane


More information about the devel mailing list