google-cloud-sql

is it possible to access Google Cloud SQL from Google Compute Engine using the private network? It appears that Google Cloud SQL sees the public network IP for the Google Compute Engine instance. And, the web console doesn't allow entering the instance private address. No it is not possible to access Google Cloud SQL instances via a private IP address. This this page confirms this, it says Note: You must use the external (public) IP address of the GCE instance ...when configuring Authorized IP Addresses to your cloud sql instance from your GCE instance. This is now available via private

I am using GKE with istio add-on enabled. Myapp somehow gives 503 errors using when using websocket. I am starting to think that maybe the websocket is working but the database connection is not and that causes 503's, as the cloudsql-proxy logs give errors: $ kubectl logs myapp-54d6696fb4-bmp5m cloudsql-proxy 2019/01/04 21:56:47 using credential file for authentication; email=proxy-user@myproject.iam.gserviceaccount.com 2019/01/04 21:56:47 Listening on 127.0.0.1:5432 for myproject:europe-west4:mydatabase 2019/01/04 21:56:47 Ready for new connections 2019/01/04 21:56:51 New connection for

I recently upgraded a Postgres 9.6 instance to 11.1 on Google Cloud SQL. Since then I've begun to notice a large number of the following error across multiple queries: org.postgresql.util.PSQLException: ERROR: could not resize shared memory segment "/PostgreSQL.78044234" to 2097152 bytes: No space left on device From what I've read, this is probably due to changes that came in PG10, and the typical solution involves increasing the instance's shared memory. To my knowledge this isn't possible on Google Cloud SQL though. I've also tried adjusting work_mem with no positive effect. This may not

I asked this question a few weeks ago. Today I have actually written and released a standard Django application, i.e. a fully-functional relational DB-backed (and consequently fully-functional Django admin) enabled by Google CloudSQL . The only time I had to deviate from doing things the standard Django way was to send email (had to do it the GAE way). My setup is GAE 1.6.4 , Python2.7 , Django 1.3 using the following in app.yaml : libraries: - name: django version: "1.3" However I do need you to suggest clear actionable steps to improve to the response time of the initial request when cold of

I have been trying to mount SQL and a storage bucket to my docker WordPress container. It appears to succeeding in mounting SQL, but failing mounting the bucket. The instance is based of of this post . I have attached the Docker file and error below, as well as my build command. Build command: docker build -t ic/spm . Dockerfile: FROM wordpress MAINTAINER Gareth Williams <gareth@itinerateconsulting.com> # Move login creds locally ADD ./creds.json /creds.json # install sudo, wget and gcsfuse ENV GCSFUSE_REPO=gcsfuse-jessie RUN apt-get update && \ apt-get -y install sudo && \ apt-get install -y

I'm not sure what else I'm missing here, but my application is failing on start with: Message : The connection attempt failed. at org.flywaydb.core.internal.jdbc.JdbcUtils.openConnection(JdbcUtils.java:60) ~[flyway-core-5.2.4.jar!/:na] at org.flywaydb.core.internal.database.DatabaseFactory.createDatabase(DatabaseFactory.java:72) ~[flyway-core-5.2.4.jar!/:na] at org.flywaydb.core.Flyway.execute(Flyway.java:1670) ~[flyway-core-5.2.4.jar!/:na] at org.flywaydb.core.Flyway.migrate(Flyway.java:1356) ~[flyway-core-5.2.4.jar!/:na] at org.springframework.boot.autoconfigure.flyway

I am using Rails and am experiencing a connection pool error very randomly and it does not target any single endpoint specifically. I can hit endpoints about 70% of the time without getting this error. The database is PostgreSQL running on Google Cloud. Here's the main stuff of the error I'm getting: #<ActiveRecord::ConnectionNotEstablished: ActiveRecord::ConnectionNotEstablished> /usr/local/bundle/gems/activerecord-5.1.5/lib/active_record/connection_handling.rb:112:in `connection_pool' ActiveRecord::ConnectionNotEstablished (No connection pool with 'primary' found.): Gemfile: source 'https:/

I have been looking at the console’s billing as far as Cloud SQL and the VM Instance is concerned. I see that a lot of the cost comes from the idling hours of the Cloud SQL IP address. I am unsure as to where the settings are for this as i have tried to “unassign” the ip address that is associated with my Cloud SQL Instance. Are these charges static, as in am I always, no matter what, going to be charged for the ip address constantly or is there a way to turn this off when I am not using the Cloud SQL Instance? If so, how can I? You will be charged $0.01 for every hour the instance is not