Bug #40530 | Agent cannot connect to DB with hostname=localhost | ||
---|---|---|---|
Submitted: | 5 Nov 2008 14:01 | Modified: | 21 Nov 2008 16:31 |
Reporter: | Andrii Nikitin | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
Version: | 1.x, 2.0.0.7092 | OS: | Any (UNIX) |
Assigned to: | Kay Roepke | CPU Architecture: | Any |
Tags: | kay_merlin_immediate |
[5 Nov 2008 14:01]
Andrii Nikitin
[6 Nov 2008 19:35]
Sloan Childers
Due to the overwhelming number of support cases related to this behavior we should really consider fixing it or making it easy for a customer to work around.
[12 Nov 2008 14:12]
Kay Roepke
The agent will now regard 'localhost' as '127.0.0.1', differing to mysqld's usage of localhost. A log message will be printed if this is detected: 2008-11-12 15:06:22: (message) agent-inst-config.c:153: [mysqld].hostname was 'localhost', setting to '127.0.0.1' to prevent connection over UNIX socket. If you want to connect via the socket, specify [mysqld].socket directly.
[18 Nov 2008 14:47]
Carsten Segieth
tested OK in 2.0.0.7100
[21 Nov 2008 16:31]
Tony Bedford
An entry was added to the 2.0 changelog: The Agent could not connect to a database with the hostname set to localhost. Doing so resulted in the error: (critical) the MySQL server could not be reached at socket '(null)', we will check in 10 seconds