2011/5/9 Tom Lane <tgl@xxxxxxxxxx>:
> Reindl Harald <h.reindl@xxxxxxxxxxxxx> writes:
>> Am 09.05.2011 19:09, schrieb Michał Piotrowski:
>>> W dniu 9 maja 2011 18:10 użytkownik Michal Schmidt
>>> <mschmidt@xxxxxxxxxx> napisał:
>>>> Are you sure that none of these services can deal with the network
>>>> connection coming up later?
>
>>> I don't know. It appears that MySQL can't deal with that
>
>> i wonder that mysqld should need network in every case since most setups out there using
>> only sockets for mysql-connections and it is a valid use-case having mysql on machines
>> without any network
>
> I did some quick tests and it seemed that the plain-vanilla
> configuration of both postgres and mysql would start all right in F15.
> However, it's definitely possible to configure postgres in a way that
> requires it to do DNS lookups at startup, and I verified that that will
> fail in the current state of F15. I'm less familiar with all of mysql's
> options but I wouldn't be surprised if there's comparable issues there.
>
> 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
init_connect='SET collation_connection = utf8_general_ci'
init_connect='SET NAMES utf8'
character-set-server = utf8
collation-server = utf8_general_ci
[mysql]
default-character-set=utf8
[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid
MySQL exited with code 1
mysqld.service - SYSV: MySQL database server.
Loaded: loaded (/etc/rc.d/init.d/mysqld)
Active: failed since Mon, 09 May 2011 08:15:44 +0200; 4min 32s ago
Process: 549 ExecStart=/etc/rc.d/init.d/mysqld start
(code=exited, status=1/FAILURE)
CGroup: name=systemd:/system/mysqld.service
Here is a fragment from log
110509 8:15:41 [Note] Plugin 'FEDERATED' is disabled.
110509 8:15:41 InnoDB: The InnoDB memory heap is disabled
110509 8:15:41 InnoDB: Mutexes and rw_locks use GCC atomic builtins
110509 8:15:41 InnoDB: Compressed tables use zlib 1.2.5
110509 8:15:41 InnoDB: Using Linux native AIO
110509 8:15:41 InnoDB: Initializing buffer pool, size = 128.0M
110509 8:15:41 InnoDB: Completed initialization of buffer pool
110509 8:15:41 InnoDB: highest supported file format is Barracuda.
110509 8:15:42 InnoDB: Waiting for the background threads to start
110509 8:15:43 InnoDB: 1.1.5 started; log sequence number 48965389142
110509 8:15:43 [ERROR] Can't start server: Bind on TCP/IP port:
Cannot assign requested address
110509 8:15:43 [ERROR] Do you already have another mysqld server
running on port: 3306 ?
110509 8:15:43 [ERROR] Aborting
110509 8:15:43 InnoDB: Starting shutdown...
110509 8:15:44 InnoDB: Shutdown completed; log sequence number 48965389142
110509 8:15:44 [Note] /usr/libexec/mysqld: Shutdown complete
>
> regards, tom lane
>
> --
> devel mailing list
> devel@xxxxxxxxxxxxxxxxxxxxxxx
> https://admin.fedoraproject.org/mailman/listinfo/devel
>
--
Best regards,
Michal
http://eventhorizon.pl/
--
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
