| Bug #41382 | Agent log only gives generic error when agent trying to connect via SSL | ||
|---|---|---|---|
| Submitted: | 11 Dec 2008 0:11 | Modified: | 6 Feb 2009 14:02 |
| Reporter: | Bill Weber | Email Updates: | |
| Status: | No Feedback | Impact on me: | |
| Category: | MySQL Enterprise Monitor: Agent | Severity: | S3 (Non-critical) |
| Version: | 2.0.0.7111 | OS: | Any |
| Assigned to: | Assigned Account | CPU Architecture: | Any |
[6 Jan 2009 14:02]
Kay Roepke
This seems to be a platform issue.
Running the test scenario on OS X, I get the following error message in the log:
2009-01-06 14:59:17: (critical) network-io.c:222: curl_easy_perform('https://agent:agent@127.0.0.1:18080/heartbeat';) failed: SSL connection timeout (curl-error = 'Timeout was reached' (28))
I'd need a list of platforms that do not report this kind of error (i.e. for which libcurl cannot tell us the reason).
[7 Feb 2009 0:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
Description: When trying to connect the agent to the Monitor via SSL and the Monitor has not been installed to support SSL (which is the default), the error in the agent log is : (critical) C:\cygwin\home\mysqldev\bs\merlin\agent-2.0\src\mysql-proxy-0.7.0r1122\plugins\agent\network-io.c:215: curl_easy_perform('https://agent:mysql@127.0.0.1:8443/heartbeat';) failed: couldn't connect to host (curl-error = 'Couldn't connect to server' (7), os-error = 'Unknown error' (10061)) How to repeat: - install monitor without checking the SSL support checkbox - install agent to use SSL support - start the agent and notice it doesn't connect to the dashboard - check agent log | has generic "unknown error" Suggested fix: put in more explicit "SSL" error in agent log