All Questions

Content language: English

Sort by most recent

Browse through the questions and answers listed below or filter and sort to narrow down your results.

PostgreSQL Connection to RDS from external server - Connection errors but works from other sources

I have a Lambda Python function connecting via psycopg2 to a PostgreSQL db instance running RDS. The Lambda connects absolutely fine (Lambda and RDS both in EU-West-2 region) I can also connect to the PostgreSQL via PgAdmin4 from a local development system and other developers can also access from other locations/IPs via PGAdmin with no problem. I can also connect a simple psycopg2 connect and query script from my local desktop here. Therefore I know RDS is accepting and responding to externally-sourced psycopg2 connections and queries. HOWEVER, when I upload the same simple connect script to my web server (OVH - based in France if of any relevance), running equivalent Python and psycopg2 etc., the connection fails with the standard psycopg2 error response from the Python: `Error raised: connection to server at "xxxxxxxx.yyyyyyyyyy.eu-west-2.rds.amazonaws.com" (ppp.qqq.rrr.ssss), port 5432 failed: Connection refused Is the server running on that host and accepting TCP/IP connections?` I've tweaked the Security Group settings to permit anything from anywhere etc and still no joy. PostgreSQL in the RDS seems to have listening on * which seems necessary to permit connections under certain circumstances. What is the subtlety in the differing sources that means such a connection from the OVH web server won't work; I can't find anything in the docs that seems to link to this issue and there's nothing obvious mis-configured on the server-side.. Any responses gratefully received.
0
answers
0
votes
8
views
asked 18 hours ago

RDS "Failed to start" when i changed the parameter group

with the default parameter group, there is no problem to pause and start RDS but with the custom parameter group, i face "Failed to start" error everytime i pause and start RDS after the "Failed to start" error, RDS backup and reboot the database automatically, and it works fine at the end. - i've changed the parameter group from "default.mysql8.0" to the custom parameter group - i haven't changed any parameters of the new parameter group, every parameters is same with the default parameter group this is the log of the lastest pause and start, i have no idea what is the problem, thanks for the any advice `2022-12-03T16:31:42.090150Z 0 [Warning] [MY-011068] [Server] The syntax 'log_s lave_updates' is deprecated and will be removed in a future release. Please use log_replica_updates instead. 2022-12-03T16:31:42.090159Z 0 [Warning] [MY-011069] [Server] The syntax '--m aster-info-repository' is deprecated and will be removed in a future release. 2022-12-03T16:31:42.090164Z 0 [Warning] [MY-011069] [Server] The syntax '--m aster-info-repository' is deprecated and will be removed in a future release. 2022-12-03T16:31:42.090220Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-file' is deprecated and will be removed in a future release. 2022-12-03T16:31:42.090225Z 0 [Warning] [MY-011069] [Server] The syntax '--relay-log-info-repository' is deprecated and will be removed in a future release. 2022-12-03T16:31:42.090252Z 0 [Warning] [MY-011068] [Server] The syntax 'skip_s lave_start' is deprecated and will be removed in a future release. Please use skip_replica_start instead. 2022-12-03T16:31:42.090259Z 0 [Warning] [MY-011068] [Server] The syntax 's lave_exec_mode' is deprecated and will be removed in a future release. Please use replica_exec_mode instead. 2022-12-03T16:31:42.090265Z 0 [Warning] [MY-011068] [Server] The syntax 's lave_load_tmpdir' is deprecated and will be removed in a future release. Please use replica_load_tmpdir instead. 2022-12-03T16:31:42.090437Z 0 [Warning] [MY-010101] [Server] Insecure configuration for --secure-file-priv: Location is accessible to all OS users. Consider choosing a different directory. 2022-12-03T16:31:42.090470Z 0 [Warning] [MY-010918] [Server] 'default_authentication_plugin' is deprecated and will be removed in a future release. Please use authentication_policy instead. 2022-12-03T16:31:42.090478Z 0 [System] [MY-010116] [Server] /rdsdbbin/mysql/bin/mysqld (mysqld 8.0.30) starting as process 731 2022-12-03T16:31:42.099878Z 0 [Warning] [MY-013907] [InnoDB] Deprecated configuration parameters innodb_log_file_size and/or innodb_log_files_in_group have been used to compute innodb_redo_log_capacity=268435456. Please use innodb_redo_log_capacity instead. 2022-12-03T16:31:42.101840Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2022-12-03T16:31:42.104547Z 1 [Warning] [MY-012191] [InnoDB] Scan path '/rdsdbdata/db/innodb' is ignored because it is a sub-directory of '/rdsdbdata/db/ 2022-12-03T16:31:42.513654Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 2022-12-03T16:31:42.827606Z 0 [Warning] [MY-013414] [Server] Server SSL certificate doesn't verify: unable to get issuer certificate 2022-12-03T16:31:42.827781Z 0 [System] [MY-013602] [Server] Channel mysql_main configured to support TLS. Encrypted connections are now supported for this channel. 2022-12-03T16:31:42.887455Z 0 [System] [MY-010931] [Server] /rdsdbbin/mysql/bin/mysqld: ready for connections. Version: '8.0.30' socket: '/tmp/mysql.sock' port: 3306 Source distribution. 2022-12-03T16:34:08.192155Z 11 [Warning] [MY-010055] [Server] IP address '125.178.113.15' could not be resolved: Name or service not known 2022-12-03T16:34:08.192271Z 12 [Warning] [MY-010055] [Server] IP address '125.178.113.15' could not be resolved: Name or service not known 2022-12-03T16:34:08.192151Z 10 [Warning] [MY-010055] [Server] IP address '125.178.113.15' could not be resolved: Name or service not known 2022-12-03T16:34:08.192487Z 9 [Warning] [MY-010055] [Server] IP address '125.178.113.15' could not be resolved: Name or service not known `
1
answers
0
votes
5
views
asked a day ago