Google Cloud SQL[postgres] - db=postgres,user=postgres FATAL: password authentication failed for user "postgres" - postgresql

I googled and changed my postgres password from command line, I can able to login through windows client with no issue, but when i checked the database log through stackdriver on google it shows that "password authentication failed", not sure that is happening same i have attached below.
Please let me know how to fix this on Google space.

Still not went into the root cause but after some time when i redeployed my code into google app engine it went fine. still not done from my side but no change done on the code so considering from google side something went wrong at Cloud SQL[postgres] instance which got disappear.
Thanks for all putting your effort on my question.

Related

GCP Logs Exporter is reporting error: db=postgres,user=postgres FATAL: password authentication failed for user "postgres"

I've changed postgres user password and we started getting error:
db=postgres,user=postgres FATAL: password authentication failed for user "postgres"
It happens each second.
Our log
I still can't figure it out which service tries to reach our SQL instance with this account.
I tried to set a password we only have, which could be previous one, but it didn't help us.
Did anyone faced the similar situation? Who knows how to fix it?
Thanks in advance for any assistance.
Best regards, Alexey
If your database is accessible to the internet, then people will try to log into it. That is how things are. You can't police the world.
Their attempts are failing. So you can just enjoy watching them beat their heads against a wall. If you don't like the log spam, or if you are afraid you will absent-mindedly set your password to 'b#seb#ll12' someday, you can change your firewall to block the attempts. You could probably configure logging to log ip addresses too (or, if it is already logged, then inspect that part of the log, which you don't seem to be doing now).
Change pg_hba.conf auth-method in order to request the password, when set.
https://www.postgresql.org/docs/current/auth-password.html

Google Cloud SQL setup & connecting to App Maker

I'm trying to get a Cloud SQL database connected to Google App Maker. I've followed the step by step instructions found here: https://developers.google.com/appmaker/models/cloudsql, apparently successfully (no error messages in setup.)
But, still getting the error message that it isn't set up properly, and the instance name is incorrect. :/
What. in the world.
Also, when I go back into App Maker and click on settings, I do not get a "database" option to select.
How do I proceed??
You must firs setup CloudSql instance in G-suite admin https://support.google.com/a/answer/7550053?hl=en

Bluemix Blockchain

Facing below error for quite a long time today. Is this frequent?
We are trying to run a sample app locally [connecting to bluemix blockchain]
Also tried to install/deploy directly into blockchain.
Both results in same error on login page itself. Also gets ERR 500/
Waiting on the node server to open up so we can talk to the blockchain. This app is likely still starting up. Check the server logs if this message does not go away in 1 minute.
This application cannot run without the blockchain network :(
The "starter network" blockchain has been experiencing intermittent capacity overflow issues. We currently have availability; have you tried this recently? Try again andlet us know if you get the same error. If yes, please open a support service ticket via Bluemix dashboard.
Hope this helps, and thanks for using blockchain!

dashDB Launch Server Error

I have added a dashDB to my app and restaged as required. Unfortunately, when I select the Launch button I get a Server Error 500 page. In the Details I get the following:
The website encountered an error while retrieving https://login.ng.bluemix.net/UAALoginServerWAR/oauth/authorize?response_type=code&state=c0241f7f-cf7a-4463-9c29-502c5b4f5efb&scope=openid&client_id=mccpserviceadmin&redirect_uri=https%3A%2F%2Fmccp.ng.bluemix.net%2Flogin%2Fcallback%2Fbmmccp.eyJ0eXBlIjoiY29udHJvbCIsInJlZ2lvbiI6ImlibTp5cDp1cy1zb3V0aCIsImNvbnRyb2wiOnsiY2xpZW50X2lkIjoiZHN3Y0NsaWVudCIsInNjb3BlcyI6WyJvcGVuaWQiXSwicmVkaXJlY3RfdXJpIjoiaHR0cHM6Ly9kYXNoZGItZW50cnkteXAtZGFsMDktMDcuc2VydmljZXMuZGFsLmJsdWVtaXgubmV0Ojg0NDMvY29uc29sZS9pYm1ibHUvaW5kZXhfQ3VzdG9tZXIuanNwP3NwYWNlX2lkPTcxMjQ0ZGMzLTU5YzAtNDM5Mi1hYzYzLTIyM2UxMDA4N2ZhOCZyZWdpb249dXMtc291dGgmdWFhLXJvdXRlPWJtbWNjcC5leUowZVhCbElqb2lkV0ZoTFhKdmRYUmxJaXdpY21WbmFXOXVJam9pYVdKdE9ubHdPblZ6TFhOdmRYUm9JaXdpYjNKblgyZDFhV1FpT2lJMlpHSm1OV1UxTWkweU5XVTBMVFE0T0dVdFlqSmpZaTFqWW1Oak56VmhOR1ZsTTJNaUxDSnpjR0ZqWlY5bmRXbGtJam9pTnpFeU5EUmtZek10TlRsak1DMDBNemt5TFdGak5qTXRNakl6WlRFd01EZzNabUU0SW4wLnA3Y3FiUDJoZjA2Q0lsYjdRVVRmOTV1N0ljQVExdUV1aVczWVM4ZVp4NHl5TWN2TjVZSEsxUWdCZk1URkktZEJxbTIyLUEySWlGVmY0dTY5TzhHNmhBRmx2eHY2dXBOWnhDbVZmWG9URE5TMkdOcGRqS0NFQWlOOTlDVkRuSzFxSDZrRWJvTXY2RkRoTW9vN3JFeGsxWW1ELWo1dGlJN3lobmtEV3R6QTFoWkRtZmxESXBnUFltZ1NfcjNaemljTFFNM1U1YVdCNzBGYVJtdmFlLWpLOV9aN2ZpSzNPbE1uSVBUeFk4QWdMSl9tU3hIRXh5SnBObFo4akxCX0dIQWcxZ0ctTmxYVWgxWXZhd2VEb2dfMVg0SVJZd0ZjZFk1ZzJRLVAtWnhaUzNDdGVYcHBHSTJ0RVg0VjhkbkNrVlVDYkhoNDBvc3R1TzQzTGhTY2JWWUFVUSZhdXRob3JpemF0aW9uLWVuZHBvaW50PWh0dHBzOi8vbWNjcC5uZy5ibHVlbWl4Lm5ldC9sb2dpbiZhdXRob3JpemF0aW9uLWVuZHBvaW50LXF1ZXJ5PXB1YmxpYz10cnVlIn19.N1XmBAm3ZJQExj1FD18JFLPFkECuizGJJVrT0dTrUeZPeH2gIj6nqk6tGlChoSWMHrxdhnH59d0272OkBiT-AaDasYQsGufXwZkmqSJ72fxbwLBefKgu_fgi1rxylhNM0rs5k-YNDk6SW69vwNWI-Np3ywGW8wTRHx26tXQ8_lFzeGP6K0Mke-cQT-u-HXU6c28E6R9XHGuiahRyKHV6eY_Ohvp5I_UE2E3JOUoXVpnj-F34JsmeW6mnUalmJDVJrzVfUJ0MVb9Kyej0eZDnQOV2cnm_auoTR2U_JoIoaZb6ESfoN6nt_Z7ALPZ0txXsVGyHzWf95enwVAPstfLCpw. It may be down for maintenance or configured incorrectly.
Which I can't decipher.
I read in this forum where one can login using the details from the VCAP_VARIABLES which I was able to do successfully. Interestingly I have annother app on bluemix that also has a dashdb that was accessible but now isn't.
I have dropped the dashDB a couple of times and also created it but left it unbound all for no joy.
Any thoughts will be appreciated.
It looks like a bluemix problem as the dashdb is working fine from the Launch button and I can see the data I loaded when I logged in via the vcap variables.

error opening dashDB

After I have added a service dashDB to my Bluemix application and I click on it, I got in IE11 this message:
The website declined to show this webpage
HTTP 403
When I did the same in the Google crome I got a square head which looked sad.
Does anyone know what to do?
Thank you!
There is not much information to go but I would suggest the following to narrow down the cause of the problem or resolve the issue:
- verify that service has been provisioned successfully (unless it's an existing instance that is known to work in the past)
- clear browser cache/restart to eliminate any transient issues
- BlueMix status page (https://developer.ibm.com/bluemix/support/#status) is currently reporting some authentication issues which potentially could cause problem, it should be check if the 403 error is still reported after the problem is resolved.
It might be worth to create the service with the "leave unbound" option and try to click on it. After you could bind it to your app.
You can verify if the dashDB instance is up or not by accessing the https_url from the VCAP variable associated with the dashDB instance (for e.g.: https://bluemix05.bluforcloud.com:8443) and provide your username and password (also from the VCAP variable) for that instance and see if you can log in.