Troubleshooting

If installation of the ClouSE plugin fails or the plugin fails to initialize or it goes offline when MySQL starts, the MySQL error log often contains data that can help you identify the root cause of the problem. For more information about MySQL error log please refer to the MySQL documentation.

The following table can be useful to find out a possible solution from error messages from the MySQL error log.

Error message Problem and/or solution
[ERROR] /usr/local/mysql/bin/mysqld: unknown variable
‘clouse_cloud_data_url’
Or
unknown variable ‘clouse_local_log_path’
The ClouSE plugin is not installed and MySQL does not recognize the clouse_XXX variables in the my.cnf file.
Remove (or comment out) clouse_XXX variables from the my.cnf first, restart mysql, add the variables back and install ClouSE plugin. When mysql installs a plugin, it automatically re-loads my.cnf and passes plugin-specific variables to the corresponding plugin.
ClouSE: The cloud data URL must be specified in the clouse_cloud_data_url variable. The clouse_cloud_data_url variable is not specified in the [mysqld] section of the my.cnf file.
ClouSE: Invalid storage class ‘https’ in ‘https://s3.amazonaws.com/mybucket/prefix’. The clouse_cloud_data_url value has invalid format. Make sure that value starts with the ‘s3://’ prefix.
ClouSE: Bucket name is missing in cloud storage URL s3.amazonaws.com/ The clouse_cloud_data_url value has invalid format.
ClouSE: The listObjects operation for ‘mybucket’ failed.
Couldn’t connect to www.invalid-host.com:443.
Invalid host name is specified in the clouse_cloud_data_url variable or the host is currently unreachable.
ClouSE: The listObjects operation for ‘mybucket2′ failed.
The specified bucket does not exist (Code=’NoSuchBucket’, RequestId=’1234′)
Invalid bucket name is specified in the clouse_cloud_data_url variable.
ClouSE: The listObjects operation for ‘mybucket-in-west-1-region’ failed.
The bucket you are attempting to access must be addressed using the specified endpoint. Please send all future requests to this endpoint. (Code=’PermanentRedirect’, RequestId=’1234′)
Invalid end point is specified in the clouse_cloud_data_url variable. Use region-specific endpoint name. For a list of region specific endpoints please refer to http://docs.amazonwebservices.com/general/latest/gr/rande.html#s3_region.
ClouSE: The listObjects operation for ‘mybucket’ failed.
Recv failure: Connection was reset.
Or
Couldn’t connect to s3.amazonaws.com:999
Or
routines:SSL23_GET_SERVER_HELLO:unknown protocol.
Invalid port number is specified in the clouse_cloud_data_url variable or the service is currently unavailable.
ClouSE: The listObjects operation for ‘mybucket’ failed.
Could not resolve host: 127.0.0.10; Host not found.
Invalid host name is specified in the clouse_cloud_data_url variable or the host is currently unreachable.
ClouSE: The put operation for prefix/…/2A/1669CA300D2924/000000000000.dat failed.
Access Denied (Code=’AccessDenied’, RequestId=’A754895B91DAEB2C’)
The user identified by the AccessKeyId specified in the clouse_cloud_auth_key variable (the first part of the value before the ‘:’) doesn’t have full access to the S3 bucket specified in the clouse_cloud_data_url variable. Check both variables and / or S3 configuration.
ClouSE: The listObjects operation for ‘mybucket’ failed.
The AWS Access Key Id you provided does not exist in our records. (Code=’InvalidAccessKeyId’, RequestId=’1234′)
Invalid AccessKeyId is specified in the clouse_cloud_data_url variable. Verify and change the first part of the value before ‘:’ as needed.
ClouSE: The listObjects operation for ‘mybucket’ failed.
The request signature we calculated does not match the signature you provided. Check your key and signing method. (Code=’SignatureDoesNotMatch’, RequestId=’1234′)
Invalid SecretAccessKey is specified in the clouse_cloud_data_url variable. Verify and change the second part of the value after ‘:’ as needed.
Make sure that you use path-style bucket name, i.e. s3.amazonaws.com/bucket not bucket.s3.amazonaws.com.
ClouSE: The listObjects operation for ‘mybucket’ failed.
Could not resolve proxy: 127.0.0.300; Host not found.
Invalid proxy host name is specified in the clouse_cloud_proxy variable or the proxy host is currently unreachable.
ClouSE: The listObjects operation for ‘mybucket’ failed.
Couldn’t connect to s3.amazonaws.com:10.
Invalid proxy port number is specified in the clouse_cloud_proxy variable or the proxy service is currently unavailable.
ClouSE: Could not parse traceFilter. Invalid value is specified in the clouse_trace_filter variable.
ClouSE: The listObjects operation for ‘mybucket’ failed.
The difference between the request time and the current time is too large. (Code=’RequestTimeTooSkewed’, RequestId=’1234′)
The time of the machine that ClouSE runs on is different from the AWS time by more than 15 minutes. Check the machine time and update it as needed.
ClouSE: SSL certificate problem, verify that the CA cert is OK. Details:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
  • Invalid root certificate due to changes in the AWS certificate chain.
  • Set clouse_cloud_ssl_cert variable in my.cnf to point to a file containing a list of Root certificates in the PEM format.

  • https traffic is compromised.
  • Connecting to a wrong SSL server.
ClouSE: The listObjects operation for ‘mybucket’ failed.
error setting certificate verify locations:
CAfile: /tmp/cacert.pem
Invalid value is specified in the clouse_cloud_ssl_cert_file variable. Check that file exists and it’s in the correct format.
ClouSE: Log file /usr/local/mysql/data/clse_log_hdr.xnl version 1.0.5.x is not supported, supported version is 1.0.2.x. The installed ClouSE version (1.0.2.x in this example) doesn’t support the data format and cannot work with the data. Update ClouSE to a version that supports the data format (in this example that would be 1.0.5.x).
ClouSE: Local log fork 52D0B903BB65FA is outdated by cloud log fork 52D476652CF179. ClouSE detected that there is another instance of ClouSE that is writing into the same cloud storage location. There must be only one ClouSE instance writing to the same cloud storage location.

See also: