Connection verification failed for data source: HEMJOBS03
java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: localhost:90. Reason: Connection refused: connect
The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: localhost:90. Reason: Connection refused: connect
Looks like datasource configuration uses port 90 to connect, which is closed. See this chunk of your error Error establishing socket to host and port: localhost:90.
So, obvious question: have you changed the connection port manually? If yes, are you sure it is correct port?
Related
greengrass v1.8.1 log
[2019-08-02T03:30:28.743-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:49567->127.0.$
[2019-08-02T03:30:28.743-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:30:39.74-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:30:39.74-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "nVwA", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:30:59.742-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:49845->127.0.$
[2019-08-02T03:30:59.742-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:31:10.741-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:31:10.741-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "BAxL", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:31:30.742-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:39151->127.0.$
[2019-08-02T03:31:30.742-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:31:41.741-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:31:41.741-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "mQbd", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:32:03.742-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:46991->127.0.$
[2019-08-02T03:32:03.742-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:32:14.741-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:32:14.741-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "UDaF", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:32:41.743-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:56790->127.0.$
My OS is Ubuntu 18.04. I used AWS IoT greengrass v1.8.1.
I followed the README.md in each package to setup up and install step by step. All lambdas were failed to connect AWS greengrass group I created.
This is all was working and all of a sudden encountered this issue.
I'm trying to transfer logs from Filebeat to Logstash
Both are running on different EC2 instances in the same network.
Apparently the socks5 protocol is used instead of http.
This is my filebeat.yml config file
filebeat.prospectors:
- type: log
paths:
- /camel-logs/app.log
output.logstash:
hosts: ["remote-host:5044"]
proxy_url: socks5://10.0.0.10:5044
filebeat.inputs:
- type: log
paths:
- /camel-logs/app.log
Honestly, I don't really know whether I should use prospectors, inputs, or both here. Neither works for now.
I'm positive that TCP port 5044 between the two hosts is open and accessible, but I don't know if socks5 is even possible over TCP? My knowledge about this stuff is quite limited.
I'm getting this error:
pipeline/output.go:74 Failed to connect: dial tcp 10.0.0.10:5044: getsockopt: connection refused
This could also be interesting:
log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":20,"time":24},"total":{"ticks":40,"time":52,"value":40},"user":{"ticks":20,"time":28}},"info":{"ephemeral_id":"192acef7-0adb-4fbb-adfe-90cade7a5498","uptime":{"ms":30011}},"memstats":{"gc_next":4194304,"memory_alloc":2166616,"memory_total":4100568,"rss":21409792}},"filebeat":{"events":{"active":334,"added":335,"done":1},"harvester":{"open_files":1,"running":1,"started":1}},"libbeat":{"config":{"module":{"running":0}},"output":{"type":"logstash"},"pipeline":{"clients":1,"events":{"active":318,"filtered":17,"published":318,"retry":852,"total":335}}},"registrar":{"states":{"current":1,"update":1},"writes":2},"system":{"cpu":{"cores":2},"load":{"1":3.22,"15":0.47,"5":1.23,"norm":{"1":1.61,"15":0.235,"5":0.615}}}}}}
I have a C++ application that used to read the data from the Firebird SQL server.
when I changed port from 3050 to 3053 it shows error like
DB Error : 0 : Unable to complete network request to host "192.168.1.47".
Failed to establish a connection.
unknown Win32 error 10060
Invalid connection string attribute
conf file is changed like
# Type: string, integer
#
RemoteServiceName = gds_db
RemoteServicePort = 3053
Fb connection string is
Driver=Firebird/InterBase(r) driver;DBNAME=192.168.1.47:CWNPFB;PORT=3053;UID=SYSDBA;PWD=********
Is there any modification is required to solve this? Application can read the data if the port is 3050.
The problem is with your connection string:
You need to
Remove PORT=3053 from the connection string (this causes the "Invalid connection string attribute" message)
Modify DBNAME=192.168.1.47:CWNPFB to DBNAME=192.168.1.47/3053:CWNPFB (to specify the right port)
You might also want to comment out (or remove) the line RemoteServiceName = gds_db, because you are now instructing Firebird to listen on gds_db (== port 3050), and not on port 3053. I believe it usually listens on the last one configured in the config file, but I'm not sure that is always the case.
Is your firewall configuration correct for port 3053? Another service may runs on this special port.
You could do the following steps.
Try to run the application on the database server, please change the IP to 127.0.0.1 or localhost.
If step (1) works: check out the firewall
If step (1) doesn't work: maybe try another port, check whether Firebird is running
I've got 3 servers on aws. each with open jdk 7 and zookeeper 3.4.6 all have unique elastic ip's.
each conf/zoo.cfg has
clientPort=2181
server.1=server1:2888:3888
server.2=server2:2888:3888
server.3=server3:2888:3888
then i start it with ./zkServer.sh start (says STARTED)
and the zookeeper.out says
2015-01-14 09:27:55,919 [myid:1] - INFO [Thread-1:QuorumCnxManager$Listener#504] - My election bind port: /server1ipaddress:3888
2015-01-14 09:27:55,920 [myid:1] - ERROR [/server1ipaddress:3888:QuorumCnxManager$Listener#517] - Exception while listening
java.net.BindException: Cannot assign requested address
at java.net.PlainSocketImpl.socketBind(Native Method)
at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:376)
at java.net.ServerSocket.bind(ServerSocket.java:376)
at java.net.ServerSocket.bind(ServerSocket.java:330)
at org.apache.zookeeper.server.quorum.QuorumCnxManager$Listener.run(QuorumCnxManager.java:507)
So it cant open the port.
i've eventually opened all ports on aws security to rule that out.
telnet into 2181 with ruok gets imok.
telnet into 2888 cannot connect. connection refused.
telnet into 3888 cannot connect. connection refused.
netstat shows that nothing is blocking 2888 and 3888
i've even tried this with all 3 servers having zookeeper started.
whats going on? how do i get those ports open for use.
Your problem is answered here.
In a few words: on each ZooKeeper machine, at your conf/zoo.cfg, you have to set the current server's IP to 0.0.0.0.
For example: if you are currently on server1, the config should contain the following lines:
server.1=0.0.0.0:2888:3888
server.2=server2:2888:3888
server.3=server3:2888:3888
This step solved the problem in my case.
Cross verify myid's on all the nodes based on the zoo.cfg. The same issue happened to me, upon looking myid pattern got changed on 2 of the nodes.
In my C++ application I'm using network connection (TCP).
when I'm identify a network connection error I'm trying to connect to another interface.
in the reconnection the connect function has passed with no error but on send function it return an SOCKET_ERROR and WSGetLastError return 10054.
do you know what is the meaning of this error and what should I do to resolve it?
10x
10054 means connection reset by peer -- the remote endpoint replied with an RST packet to tell you that the connection isn't open. Reconnect with connect() instead of trying to simply change interfaces on your local end.
10054 (connection reset by peer) after successfull connect() means that the server accepts incoming connection but after that it closes the accepted socket without waiting for incoming information. The only way to resolve this is to check the server application logic.