AWS Glue: Can't connect to AWS Redshift

Question

Hello, I am trying to connect the AWS Glue to Redshift, but instead it is failing to connect. See the logs below for more information. I am not wiser from these logs.
```
2024-08-29T16:51:09.960Z
ERROR StatusLogger Unrecognized format specifier [d] ERROR StatusLogger Unrecognized conversion specifier [d] starting at position 16 in conversion pattern.
2024-08-29T16:51:09.961Z
ERROR StatusLogger Unrecognized format specifier [thread]
2024-08-29T16:51:09.962Z
ERROR StatusLogger Unrecognized conversion specifier [thread] starting at position 25 in conversion pattern.
2024-08-29T16:51:09.963Z
ERROR StatusLogger Unrecognized format specifier [level]
2024-08-29T16:51:09.963Z
ERROR StatusLogger Unrecognized conversion specifier [level] starting at position 35 in conversion pattern.
2024-08-29T16:51:09.964Z
ERROR StatusLogger Unrecognized format specifier [logger]
2024-08-29T16:51:09.964Z
ERROR StatusLogger Unrecognized conversion specifier [logger] starting at position 47 in conversion pattern.
2024-08-29T16:51:09.964Z
ERROR StatusLogger Unrecognized format specifier [msg]
2024-08-29T16:51:09.964Z
2024-08-29T16:51:09.964Z
ERROR StatusLogger Unrecognized conversion specifier [msg] starting at position 54 in conversion pattern.
2024-08-29T16:51:09.964Z
ERROR StatusLogger Unrecognized format specifier [n]
```

This [post](https://repost.aws/questions/QUHerZcf2eTqiDF5LpVoXhcw/while-testing-redshift-connection-from-glue-i-am-getting-below-error) suggest changing the format of the logging. We do not have any formatting changes.

pbocan · Accepted Answer

It looks like bad password was the issue.

Elena Madrazo · Answer

Hello,

Thank you very much for your question. Based on the log provided, it seems that the problem comes from the log4j configuration in Glue. The error you are getting from the logs indicate that the log4j pattern used for logging is not recognized.
To try to solve the issue, you can try the following:
* Check the Log4j Configuration: AWS Glue uses Apache Log4j for logging. Ensure that the log4j configuration file (`log4j.properties` or `log4j.xml`) is correctly configured and has a valid pattern for logging.

* Check AWS Glue Version: Ensure that you are using a compatible version of AWS Glue with the log4j configuration you have provided. Different versions of AWS Glue may use different versions of log4j, which could lead to compatibility issues with the log4j configuration.

* Update the Log4j Pattern: The log4j pattern defines the format of the log messages. The error messages suggest that the pattern used in your configuration contains invalid format specifiers

Also, AWS Glue 3.0 uses Log4j 1 for logging behavior. You can customize these behaviors with a log4j.properties file. Since AWS Glue 4.0 was released, AWS Glue ETL jobs use Log4j 2 and the logging behavior is configured with a log4j2.properties file. Hope it helps!

AWS Glue: Can't connect to AWS Redshift

Relevant content