그룹
로그인
그룹
Google Cloud SQL discuss
대화
정보
의견 보내기
도움말
관련순 정렬
날짜순 정렬
여러 개 중 1~30개
perezsanchez
,
Eno Compton
2
22. 6. 27.
Re: Can't connect to instance because "Policy checks are unavailable"
> *
ERROR
:* (gcloud.sql.connect) UNAVAILABLE: Policy checks are unavailable. >> >> >> Here's what cloud_sql_proxy says: >> >> 2022/06
읽지 않음,
Re: Can't connect to instance because "Policy checks are unavailable"
> *
ERROR
:* (gcloud.sql.connect) UNAVAILABLE: Policy checks are unavailable. >> >> >> Here's what cloud_sql_proxy says: >> >> 2022/06
22. 6. 27.
Priya Geetha
,
loreasanchez
2
22. 6. 1.
Import of data to GCP Database is failing with error
Getting this
error
when trying to Import data to GCP Database is failing > with
error
- > > Multiple databases detected in BAK file. Only importing a single database > is
읽지 않음,
Import of data to GCP Database is failing with error
Getting this
error
when trying to Import data to GCP Database is failing > with
error
- > > Multiple databases detected in BAK file. Only importing a single database > is
22. 6. 1.
--
2
22. 5. 31.
Share Cloud SQL DB between 2 projects with app engine
connection >
error
> > *could not connect to server: Connection refused * > *Is the server running locally and accepting connections on Unix domain > socket "
읽지 않음,
Share Cloud SQL DB between 2 projects with app engine
connection >
error
> > *could not connect to server: Connection refused * > *Is the server running locally and accepting connections on Unix domain > socket "
22. 5. 31.
Robert Xu
, …
contreraspinon
4
22. 5. 16.
Recommended cloud sql postgresql client settings
describes this
error
being caused by connection timeouts , have you found better results by increasing the connection life ? On Friday, May 13, 2022 at 6:31:53 PM UTC-5 r...@transcarent
읽지 않음,
Recommended cloud sql postgresql client settings
describes this
error
being caused by connection timeouts , have you found better results by increasing the connection life ? On Friday, May 13, 2022 at 6:31:53 PM UTC-5 r...@transcarent
22. 5. 16.
Giovanni Minchio
,
fiescocasasola
2
22. 5. 11.
ENOENT connecting to a mySQL instance using node.js
> The
error
happend when i try to query the db , here a code snippet: > > ABOUT THE POOL INSTANCE > const pool = mysql.createPool({ > user:'username', > password
읽지 않음,
ENOENT connecting to a mySQL instance using node.js
> The
error
happend when i try to query the db , here a code snippet: > > ABOUT THE POOL INSTANCE > const pool = mysql.createPool({ > user:'username', > password
22. 5. 11.
Neil Ghosh
,
Kurtis Van Gent
2
22. 4. 27.
DNS in CloudSQL wth private IP
the following
error
when using the > private IP in nodejs code. > > "code":"ERR_T │ > │ LS_CERT_ALTNAME_INVALID","message":"
읽지 않음,
DNS in CloudSQL wth private IP
the following
error
when using the > private IP in nodejs code. > > "code":"ERR_T │ > │ LS_CERT_ALTNAME_INVALID","message":"
22. 4. 27.
Eric Ho
, …
cristianrm
3
22. 4. 11.
Support statement_timeout for postgresql
email in
error
, > please advise me immediately by reply email, do not disclose, copy, or > distribute the contents, and immediately delete the message and any > attachments
읽지 않음,
Support statement_timeout for postgresql
email in
error
, > please advise me immediately by reply email, do not disclose, copy, or > distribute the contents, and immediately delete the message and any > attachments
22. 4. 11.
Harpal Khing
, …
Horace (Cloud Platform Support)
4
22. 3. 28.
Use `gcloud sql export csv ... ` for multiple calls at the same time
:409
error
because most operations in Cloud SQL >> are synchronous and you can only run one operation at a time. You can >> perform only one import or export operation at
읽지 않음,
Use `gcloud sql export csv ... ` for multiple calls at the same time
:409
error
because most operations in Cloud SQL >> are synchronous and you can only run one operation at a time. You can >> perform only one import or export operation at
22. 3. 28.
Sujit Ramugade
, …
Scott Ertel
4
22. 3. 15.
Integration CloudPostgreSQL to PowerBi.
communication in
error
, please notify us immediately by responding to this email and then delete it from your system. Searce is neither liable for the proper and complete transmission
읽지 않음,
Integration CloudPostgreSQL to PowerBi.
communication in
error
, please notify us immediately by responding to this email and then delete it from your system. Searce is neither liable for the proper and complete transmission
22. 3. 15.
Daria Aleksich
, …
Alex johson
3
22. 2. 25.
Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint
>>
error
in the sql server logs in SSMS: >> >> Login failed for user '3aec90b46f01d28\3aec90b46f01d28$'. Reason: >> Token-based server access
읽지 않음,
Token-based server access validation failed with an infrastructure error. Login lacks connect endpoint
>>
error
in the sql server logs in SSMS: >> >> Login failed for user '3aec90b46f01d28\3aec90b46f01d28$'. Reason: >> Token-based server access
22. 2. 25.
Dani Daryaweesh
, …
Horace (Cloud Platform Support)
4
22. 2. 22.
Cloud SQL update operations issue
a similar
error
message such as [1, 2]? Can you kindly include the stack trace that you are getting and furthermore a sample query and call that resulted in this
error
. However, I would
읽지 않음,
Cloud SQL update operations issue
a similar
error
message such as [1, 2]? Can you kindly include the stack trace that you are getting and furthermore a sample query and call that resulted in this
error
. However, I would
22. 2. 22.
S M
, …
jack jee
3
22. 2. 14.
Failed to serialize json to table row
a similar
error
> message [1]. For them the issue was caused because their output did not > match the template output. > > > [1]: https://stackoverflow.com/questions
읽지 않음,
Failed to serialize json to table row
a similar
error
> message [1]. For them the issue was caused because their output did not > match the template output. > > > [1]: https://stackoverflow.com/questions
22. 2. 14.
Bart Kus
, …
George (Cloud Platform Support)
4
22. 2. 11.
Is is possible to run postgREST on google cloud sql
get `
ERROR
: permission denied to set role "anonymous"` > Everything however works as expected if for example I use > postgres/postgresPassword uri and with `grant
읽지 않음,
Is is possible to run postgREST on google cloud sql
get `
ERROR
: permission denied to set role "anonymous"` > Everything however works as expected if for example I use > postgres/postgresPassword uri and with `grant
22. 2. 11.
Travis Marble
, …
goya
5
22. 2. 10.
Sql Logs filled with Logon Login failed for user 'a-...-\a-...-$'.
> This
error
can be ignored for the moment until the Cloud SQL product >>> team roll out a fix from Microsoft, for which there is currently no >>> timeline. Microsoft
읽지 않음,
Sql Logs filled with Logon Login failed for user 'a-...-\a-...-$'.
> This
error
can be ignored for the moment until the Cloud SQL product >>> team roll out a fix from Microsoft, for which there is currently no >>> timeline. Microsoft
22. 2. 10.
Nara Ramakrishnan
, …
Lluis Munoz Ladron de Guevara
6
22. 2. 4.
CloudSQL SqlServer user not able to access database
user"
error
. The Cloud SQL product team >> have been made aware of this issue and we are currently waiting on a roll >> out of the fix from Microsoft. Microsoft seems
읽지 않음,
CloudSQL SqlServer user not able to access database
user"
error
. The Cloud SQL product team >> have been made aware of this issue and we are currently waiting on a roll >> out of the fix from Microsoft. Microsoft seems
22. 2. 4.
Meryl Ong
, …
goya
3
22. 2. 3.
Lock wait timeout exceeded; try restarting transaction
a MySQL
error
. I recommend you to ask in the Integromat Community group [1] to check if there are any known settings that might be causing this issue. [1]: https://www.facebook.com
읽지 않음,
Lock wait timeout exceeded; try restarting transaction
a MySQL
error
. I recommend you to ask in the Integromat Community group [1] to check if there are any known settings that might be causing this issue. [1]: https://www.facebook.com
22. 2. 3.
David Irivbogbe
,
chorny
2
22. 1. 5.
Data Migration cloud SQL in one project to another
> with
error
: > > Migration job new-db status changed from RUNNING, CDC in progress to > FAILED, during CDC. Failure due to the following
error
:
error
code: 0, >
error
읽지 않음,
Data Migration cloud SQL in one project to another
> with
error
: > > Migration job new-db status changed from RUNNING, CDC in progress to > FAILED, during CDC. Failure due to the following
error
:
error
code: 0, >
error
22. 1. 5.
Henri Dubois-Ferriere
,
nopa...@google.com
2
21. 11. 19.
instance won't start
an unknown
error
and don't see > any logs or further info. Could someone please recommend steps to > troubleshoot/fix? > > > > $ gcloud sql instances patch xyz
읽지 않음,
instance won't start
an unknown
error
and don't see > any logs or further info. Could someone please recommend steps to > troubleshoot/fix? > > > > $ gcloud sql instances patch xyz
21. 11. 19.
tomer a
, …
Peter Kok
3
21. 11. 12.
Update conf file with ALTER SYSTEM SET on Postgres
I get
error
that its not allowed when running this: >> >> >> *ALTER SYSTEM SET max_logical_replication_workers = 8;* >> >> *
ERROR
: must be superuser
읽지 않음,
Update conf file with ALTER SYSTEM SET on Postgres
I get
error
that its not allowed when running this: >> >> >> *ALTER SYSTEM SET max_logical_replication_workers = 8;* >> >> *
ERROR
: must be superuser
21. 11. 12.
Justis Gipson
,
rwabukumba
3
21. 11. 12.
Cloud SQL Proxy invalid json coming from Docker Compose
on the
error
message, it does appear there is a missing secret perhaps due to how volumes are mounted. Please consult this docker file structure guide , then carefully follow the steps
읽지 않음,
Cloud SQL Proxy invalid json coming from Docker Compose
on the
error
message, it does appear there is a missing secret perhaps due to how volumes are mounted. Please consult this docker file structure guide , then carefully follow the steps
21. 11. 12.
Shazad Saleem
,
Javier Merida Morales
4
21. 11. 4.
Unable to Demote SQL Cloud Master to act as Slave
and the
error
message, it seems to be a matter of a wrong user and/or password. Could you please double check if you are using the correct credentials? Please, remember to NOT SHARE any
읽지 않음,
Unable to Demote SQL Cloud Master to act as Slave
and the
error
message, it seems to be a matter of a wrong user and/or password. Could you please double check if you are using the correct credentials? Please, remember to NOT SHARE any
21. 11. 4.
kaze anime
,
Van Duong
2
21. 10. 4.
How to Connect Google SQL database from AWS EC2
can't connect with
error
"
ERROR
2003 > (HY000): Can't connect to MySQL server on '10.xx.xx.xx' (110)" what must be > to do? > > thanks >
읽지 않음,
How to Connect Google SQL database from AWS EC2
can't connect with
error
"
ERROR
2003 > (HY000): Can't connect to MySQL server on '10.xx.xx.xx' (110)" what must be > to do? > > thanks >
21. 10. 4.
Jack Pordi
,
babdelrahman
2
21. 7. 19.
"too many connections for database" in Postgres.
full exact
error
message. Thank you. On Friday, July 16, 2021 at 9:25:27 AM UTC-4 ja...@theclub.tv wrote: > Hey all, > > I've been having an issue where the postgres database
읽지 않음,
"too many connections for database" in Postgres.
full exact
error
message. Thank you. On Friday, July 16, 2021 at 9:25:27 AM UTC-4 ja...@theclub.tv wrote: > Hey all, > > I've been having an issue where the postgres database
21. 7. 19.
Devendra Bhandari
,
wokmou
2
21. 7. 15.
Cloud SQL Import API Issue
there any
error
message you are seeing while completing the process? As this may have multiple causes, any information displayed while the behavior is occurring may guide us in identifying
읽지 않음,
Cloud SQL Import API Issue
there any
error
message you are seeing while completing the process? As this may have multiple causes, any information displayed while the behavior is occurring may guide us in identifying
21. 7. 15.
Mike Berman
, …
barrado
5
21. 7. 15.
Service temporarily unavailable
> "
error
": { >>>> >>>> "code": 503, >>>> >>>> "message": "Service temporarily
읽지 않음,
Service temporarily unavailable
> "
error
": { >>>> >>>> "code": 503, >>>> >>>> "message": "Service temporarily
21. 7. 15.
Eugene Pirogov
, …
wushawn
10
21. 7. 5.
Consistent "Segmentation fault" error in logs when running a query
fault"
error
in logs for our staging >>>>>> environment, caused by a single specific DB query. >>>>>> >>>>>> I
읽지 않음,
Consistent "Segmentation fault" error in logs when running a query
fault"
error
in logs for our staging >>>>>> environment, caused by a single specific DB query. >>>>>> >>>>>> I
21. 7. 5.
Vyshnave Bobburi
21. 6. 30.
Single row output at random times
unless explicitly stated. Please see our Privacy Policy for details. Contents of this Email are confidential. Please contact Sender if you have received this Email in
error
.
읽지 않음,
Single row output at random times
unless explicitly stated. Please see our Privacy Policy for details. Contents of this Email are confidential. Please contact Sender if you have received this Email in
error
.
21. 6. 30.
Mike Bowerman
,
Sergi Ferre Albiol
2
21. 6. 25.
Getting pymysql.err.OperationalError: (2013, 'Lost connection to MySQL server during query')
of this
error
and the possible solutions for each case. [1] https://dev.mysql.com/doc/refman/5.7/en/
error
-lost-connection.html On Thursday, June 24, 2021 at 9:02:53 AM UTC
읽지 않음,
Getting pymysql.err.OperationalError: (2013, 'Lost connection to MySQL server during query')
of this
error
and the possible solutions for each case. [1] https://dev.mysql.com/doc/refman/5.7/en/
error
-lost-connection.html On Thursday, June 24, 2021 at 9:02:53 AM UTC
21. 6. 25.
Hugues Alary
, …
goya
7
21. 6. 15.
Major Google Cloud SQL issue - SQL Cloud unresponsive
get the
error
you see below. I have included the logs for the > boot up sequence of one of our app engine instances: > > It seems to have to do with initial connects to our db? (elate
읽지 않음,
Major Google Cloud SQL issue - SQL Cloud unresponsive
get the
error
you see below. I have included the logs for the > boot up sequence of one of our app engine instances: > > It seems to have to do with initial connects to our db? (elate
21. 6. 15.
Thierry Falvo
2
21. 5. 20.
Strange error log "Improper path /cloudsql/..."
a strange
error
message in Cloud > Run log when attempting to connect to Cloud SQL : > > Improper path /cloudsql/INSTANCE_NAME to connect to Postgres Cloud SQL > instance
읽지 않음,
Strange error log "Improper path /cloudsql/..."
a strange
error
message in Cloud > Run log when attempting to connect to Cloud SQL : > > Improper path /cloudsql/INSTANCE_NAME to connect to Postgres Cloud SQL > instance
21. 5. 20.