Currently we connect from our app to the RDS endpoint using it's hostname:
xxxx-db.xxxxxxxxxxxxx.eu-west-1.rds.amazonaws.com
It seems the dns service went down for a period of time last night resulting in:
ERROR - 2019-07-11 23:02:46 --> Severity: Warning --> mysqli::real_connect(): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution /var/app/current/system/database/drivers/mysqli/mysqli_driver.php 201
ERROR - 2019-07-11 23:02:46 --> Severity: Warning --> mysqli::real_connect(): (HY000/2002): php_network_getaddresses: getaddrinfo failed: Temporary failure in name resolution /var/app/current/system/database/drivers/mysqli/mysqli_driver.php 201
ERROR - 2019-07-11 23:02:46 --> Unable to connect to the database
Is there a better way to access the DB server skipping the dns?
Related
I have an error popping up randomly and frequently when connecting to a Snwoflake Instance via ODBC (Windows-Excel). Drivers are up to date, and other tools connect without an issue using the same driver. Does anyone have an idea of how to fix it?
Thanks in advance!
Detalles: "ODBC: ERROR [HY000] [Snowflake][Snowflake] (4)
REST request for URL https://xxxxxx.us-east-1.snowflakecomputing.com:443/session/v1/login-request?requestId=f2c84d1a-3bfa-450b-95e4-9d41fe2a302e&request_guid=e090e19b-98af-41b7-8f5f-913e02d3b070 failed: CURLerror (curl_easy_perform() failed) - code=35 msg='SSL connect error'.
ERROR [HY000] [Snowflake][Snowflake] (4)
REST request for URL https://xxxxxx.us-east-1.snowflakecomputing.com:443/session/v1/login-request?requestId=f2c84d1a-3bfa-450b-95e4-9d41fe2a302e&request_guid=e090e19b-98af-41b7-8f5f-913e02d3b070 failed: CURLerror (curl_easy_perform() failed) - code=35 msg='SSL connect error'.
"
ABP version 4.4 APP with identity server with angular EF core
my angular client send the username and password to identity server that is part of my abp application (mean same URL for api and identity server) that returns me token but after very next request for "api/abp/application-configuration" return with CORs error.
same application work for QA local environment with local config.
same call for "api/abp/application-configuration" work on app start because that time token is not attached in request header
i check my app setting CorsOrigins are matching with IdentityServerClientCorsOrigins
no space issue both angular and front end on https but with different port. you can verify with logs. one thing is strange in log no protocol attach # respond. (domain:1000)
I check and confirm that this is Authentication issue. by comment these two line and Authorize attribute from class
My application works fine. no issue for cors
app.UseAuthentication();
app.UseJwtTokenMiddleware();
system log
2021-09-04 10:42:24.731 -04:00 [INF] Request starting HTTP/2 OPTIONS https://domain:1000/.well-known/openid-configuration - -
2021-09-04 10:42:24.745 -04:00 [INF] CORS policy execution successful.
2021-09-04 10:42:24.751 -04:00 [INF] Request finished HTTP/2 OPTIONS https://domain:1000/.well-known/openid-configuration - - - 204 - - 19.7919ms
2021-09-04 10:42:24.793 -04:00 [INF] Request starting HTTP/2 GET https://domain:1000/.well-known/openid-configuration - -
2021-09-04 10:42:24.794 -04:00 [INF] CORS policy execution successful.
2021-09-04 10:42:46.050 -04:00 [ERR] Exception occurred while processing message.
System.InvalidOperationException: IDX20803: Unable to obtain configuration from: 'System.String'.
System.IO.IOException: IDX20804: Unable to retrieve document from: 'System.String'.
System.Net.Http.HttpRequestException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (domain:1000)
System.Net.Sockets.SocketException (10060): A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.
It is not a CORS issue, instead it is because your API (the UseJwtTokenMiddleware part) can't reach your IdentityServer over HTTP(s). I guess you got some DNS/Certificate/Network issue to resolve.
When I try to start odi agent with this command:
C:\ORACLE_HOME\user_projects\domains\ODIDOMAIN\bin>agent -NAME=OracleDIAgent1 -PORT=20910
This error is shown:
ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
the full text is:
2020-11-04 07:17:58.676 NOTIFICATION New data source: [DEV_ODI_REPO/*******#jdbc:oracle:thin:#//10.1.5.66:1521/ORCL66]
2020-11-04 07:18:04.599 NOTIFICATION ODI-1128 Agent OracleDIAgent1 is starting. Container: STANDALONE. Agent Version: 12.2.1. Port: 20910. JMX Port: 21910.
SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
Allowing : 127.0.0.1,10.1.5.66,127.0.0.1
2020-11-04 07:18:10.088 WARNING odi.core.security.SecurityManager.loadAuthenticationMode found the authMode:mUsingLDAPAuthentication: false,mUsingIDCSAuthentication:false,indExternalAuth:null.
2020-11-04 07:18:10.420 ERROR ODI-1131 Agent OracleDIAgent1 encountered an error: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository. Caused by: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.420 WARNING ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.435 WARNING unavailable
2020-11-04 07:18:10.435 WARNING Failed startup of context o.o.#17125ea9{/oraclediagent,file:/C:/ORACLE_HOME/user_projects/domains/ODIDOMAIN/system_components/ODI/OracleDIAgent1/work/webapp/,STARTING}{file:/C:/ORACLE_HOME/odi/agent/lib/./oraclediagent.war}
2020-11-04 07:18:10.435 WARNING FAILED o.o.#17125ea9{/oraclediagent,file:/C:/ORACLE_HOME/user_projects/domains/ODIDOMAIN/system_components/ODI/OracleDIAgent1/work/webapp/,UNAVAILABLE}{file:/C:/ORACLE_HOME/odi/agent/lib/./oraclediagent.war}: javax.servlet.ServletException: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.471 WARNING FAILED org.eclipse.jetty.server.Server#77bca6d6: javax.servlet.ServletException: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.472 ERROR ODI-1443 Error while starting agent : ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.503 ERROR ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
2020-11-04 07:18:10.503 ERROR javax.servlet.ServletException: ODI-1404: Agent OracleDIAgent1 start failure: an authentication error occurred while connecting to the master repository.
Caused by: oracle.odi.core.security.BadCredentialsException: ODI-10199: Incorrect ODI username or password.
The ODI version is 12 and node manager and weblogic is starting correctly.
As the error message states, the ODI username or password that was provided when configuring the agent is incorrect.
To reconfigure the agent and set the correct credentials on Windows :
execute config.cmd in C:\ORACLE_HOME\oracle_common\common\bin
click next on all the steps except the ODI Server Configuration page where you can type the password
start the agent
More info in Oracle Support Doc ID 2386816.1
Its not the problem with SUPERVISOR credentials. if you have multiple Agents in various servers you may face this issue. only one agent may fail out of n.
Copy the ODI_MASTER_ENCODED_PASS value to the expected location within the odiparams.sh file on the system where the agent is not starting.
The odiparams.sh file can be found in:
$ODI_HOME\oracledi\agent\bin
We are facing this below error in Vespa, after restarting the cluster we got this below issue.
1600455444.680758 10.10.000.00 1030/1 container Container.com.yahoo.filedistribution.fileacquirer.FileAcquirerImpl info Retrying waitFor for file 'e0ce64d459828eb0': 103 -- Request timed out after 60.0 seconds.
1600455446.819853 10.10.000.00 32752/146 configproxy configproxy.com.yahoo.vespa.filedistribution.FileReferenceDownloader info Request failed. Req: request filedistribution.serveFile(e0ce64d459828eb0,0)\nSpec: tcp/10.10.000.00:19070, error code: 103, set error for connection and use another for next request
We faced this issue second time, earlier we kept it ideal and it was resolved automatically, but this time it is persistent.
Looks like the configproxy is unable to talk to the config server (which is listening to port 19070 on the same host: Spec: tcp/10.10.000.00:19070). Is the config server really runnning and listening on port 19070 on this host? Try running the vespa-config-status script to see if all is well with the config system
I am trying to setup zookeeper on ec2 two instances. as given here and here.
I am trying to run zookeeper which fails with an error:
command: bin/zkCli.sh -server localhost:2181
> 2015-03-15 00:22:35,644 [myid:] - INFO [main:ZooKeeper#438] - Initiating client connection, connectString=localhost:2181 sessionTimeout=30000 watcher=org.apache.zookeeper.ZooKeeperMain$MyWatcher#3ff0efca
Welcome to ZooKeeper!
2015-03-15 00:22:35,671 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread#975] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
JLine support is enabled
2015-03-15 00:22:35,677 [myid:] - WARN [main-SendThread(localhost:2181):ClientCnxn$SendThread#1102] - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method)
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:739)
at org.apache.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361)
at org.apache.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081)
[zk: localhost:2181(CONNECTING) 0] 2015-03-15 00:22:36,796 [myid:] - INFO [main-SendThread(localhost:2181):ClientCnxn$SendThread#975] - Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error)
2015-03-15 00:22:36,797 [myid:] - WARN [main-SendThread(localhost:2181):ClientCnxn$SendThread#1102] - Session 0x0 for server null, unexpected error, closing socket connection and attempting reconnect
zoo.cfg as bellow
tickTime=2000
initLimit=10
syncLimit=5
dataDir=/var/lib/zookeeper
clientPort=2181
server.1=localhost:2888:3888
server.2=<My ec2 private IPs>:2889:3889
also I have created myId file as on both ec2 instances - /var/lib/zookeeper/myid
I also tried to edit /ect/hosts file but still facing the same issue.
also how I can start both of the zookeeper instances by 1 command?
Note: Server get started successfully if I tried with bin/zkCli.sh start command.
Thanks in advance!
look zk log zookeeper.out，if there have connection limit error, configure the following to zoo.cfg.
# the maximum number of client connections.
# increase this if you need to handle more clients
maxClientCnxns=60
This is temporary error , for mine after some time , It gone away :-
This is my zoo.conf file ::-
Dir=../data
clientPort=2181
tickTime=2000
initLimit=5
This error occurred when I forgot to run% ZOOKEEPER_HOME% \ bin \ zkserver.cmd
By running, the problem has been resolved.
Correct this property on the server.properties
default would be localhost change it to match the zookeeper server starup ip and port
zookeeper.connect=0.0.0.0:2181