I use Jasmin sms Gateway, and I have to connect to a server: smpp-1-ire.smscarrier.com at port 8011, I following your instructions but I can not connect, all other configurations and test works :
Establishing TCP connection to smpp-1-ire.smscarrier.com:8011
2018-04-10 15:24:06 INFO 11188 Connecting to IPv4Address(TCP, 'smpp-1-ire.smscarrier.com', 8011) ...
2018-04-10 15:24:07 WARNING 11188 SMPP connection established from 52.31.169.62 to port 51982
2018-04-10 15:24:07 INFO 11188 Connection made to smpp-1-ire.smscarrier.com:8011
2018-04-10 15:24:07 WARNING 11188 Requesting bind as transceiver
2018-04-10 15:24:07 ERROR 11188 Bind failed [[Failure instance: Traceback (failure with no frames): <class 'jasmin.vendor.smpp.pdu.error.SMPPTransactionError'>: ESME_RBINDFA$
]]. Disconnecting...
I tried to change the 2275 listening port in 8011 on jasmin.cfg , nothing...
But this works :
System ID: test
Password: test
host: smsc-sim.smscarrier.com
Port: 2775
Log:
*2018-04-10 17:35:21 INFO 14022 Establishing TCP connection to smsc-sim.smscarrier.com:2775
2018-04-10 17:35:21 INFO 14022 Connecting to IPv4Address(TCP, 'smsc-sim.smscarrier.com', 2775) ...
2018-04-10 17:35:21 WARNING 14022 SMPP connection established from 35.177.141.136 to port 48570
2018-04-10 17:35:21 INFO 14022 Connection made to smsc-sim.smscarrier.com:2775
2018-04-10 17:35:21 WARNING 14022 Requesting bind as transceiver*
2018-04-10 17:35:21 WARNING 14022 Bind succeeded...now in state BOUND_TRX
I am still convinced that Jasmin can be configured with my service provider, but I do not know all JasminSMS settings, as with NowSMS it worked, and that I used for tests, I took a screenshot of the configuration, if someone one can help me find the 2 parameters that are missing, systype smpp which is accepted but also maybe SMSC Character Set whose value should be: IA5 (GSM).
JasminSMS Gateway is perhaps not compatible with this provider, it would still be extraordinary, given the notoriety of Jasmin.
Anyway, thank you for your help.
I suggest improving logging where you got error response to your SMPP bind request, print request parameters and response error code. Have a look at SMPP specification as well to see the meaning of the error code. Potential reasons :
At least one of the following parameter values are wrong: system_id, system_type or password.
Your bind requestor origin host IP is not white listed on SMPP server side.
SMPP server side might be refusing 2nd client bind using the same system_id.
Address Range parameter usage might have been enforced by SMPP serve
There can be system_id or password character length limitation on your API side
Related
I'm using JavaMailSender and Outlook SMTP server for sending emails in a SpringBoot project.
Mail config:
host=smtp-mail.outlook.com
port=587
mail.transport.protocol=smtp
mail.smtp.auth=true
mail.smtp.starttls.enable=true
mail.debug=true
When testing locally, everything works fine - email is sent to port 587 (see below) and delivered to the user.
DEBUG SMTP: trying to connect to host "smtp-mail.outlook.com", port 587, isSSL false
DEBUG SMTP: connected to host "smtp-mail.outlook.com", port: 587
The problem: When testing on production (Heroku server), email is being sent to port 5104:
DEBUG SMTP: trying to connect to host "smtp-mail.outlook.com", port 5104, isSSL false
That eventually ends with timed out connection exception and email is never sent to the user.
java.net.ConnectException: Connection timed out (Connection timed out). Failed messages: com.sun.mail.util.MailConnectException: Couldn't connect to host, port: smtp-mail.outlook.com, 5104; timeout -1;
Edit: I've also figured that it uses different port on every email send try:
DEBUG SMTP: trying to connect to host "smtp-mail.outlook.com", port 58079, isSSL false
What is the reason for this behaviour? Why is it not using given port?
I am new to axon server. I use axon server as remote server in spring boot. not in the localhost. but when the spring boot application connect to the server it fails and show the fallowing error.
Connecting to AxonServer node [174.298.31.***:8024] failed: UNAVAILABLE: Network closed for unknown reason
Failed to get connection to AxonServer. Scheduling a reconnect in 2000ms
my property file like below,
axon:
axonserver:
servers: 174.298.31.***:8024
if you didn't change the default port, 8024 is the default port for HTTP access to the server dashboard. but when you try to connect to the server using a client, it is not the communication port, the communication protocol is 8124. please try putting 8124 port. 8024 only for the dashboard.
axon:
axonserver:
servers: 174.298.31.***:8124
I'm new on Golang and mqtt.
I'm trying to connect to a broker. It works when I'm using MQTT.fx or my terminal with mosquitos.
But in my program, I create my opts with the address & clientID and when I try to connect there is an error "Unknow protocol"
panic: Network Error : Unknown protocol
goroutine 1 [running]:
panic(0x347b20, 0xc820072fe0)
/usr/local/go/src/runtime/panic.go:481 +0x3e6
main.main()
test.go:29 +0x1cd
I checked the protocol version on MQTT.fx and it's TLSv1.2.
The Paho library support TLS protocol. I'm a bit confused
Is there someone who got the same issue ?
Cheers
I fixed it. Just forgot to precise the protocol at the beginning of the url.
The type of connection required is specified by the scheme of the connection URL set in the ClientOptions struct, for example:
tcp://iot.eclipse.org:1883 - connect to iot.eclipse.org on port 1883 using plain TCP
ws://iot.eclipse.org:1883 - connect to iot.eclipse.org on port 1883 using WebSockets
tls://iot.eclipse.org:8883 - connect to iot.eclipse.org on port 8883 using TLS (ssl:// and tcps:// are synonyms for tls://)
That works :-)
I have created a Consul architecture that spans across different consul datacenters.
When I now open the UI on one of the consul servers, and switch via the little dropdown menu
to look at at a different datacenter the request times out. In the log I can see this error message:
2016/05/03 06:26:08 [ERR] http: Request GET /v1/internal/ui/nodes?dc=dc1-live&token=<hidden>, error: rpc error: failed to get conn: dial tcp xx.xxx.xxx.xxx:8300: i/o timeout from=xxx.xxx.xxx.xxx:53174
Does this mean I need to open port 8300 additionally to port 8302 between the servers of the different datacenters?
I ended up having port 8300 being opended and that made the error messages go away. So I conclude that it is necessary.
I deployed a long running Storm topology. After several hours running, the whole topology went down. I checked worker logs, and found these logs . As it says, zookeeper client session timed out and it caused reconnection. I suspect it was relate to my broken topology. Now I try to find out what can cause clients timeout.
2016-02-29T10:34:12.386+0800 o.a.s.z.ClientCnxn [INFO] Client session timed out, have not heard from server in 23789ms for sessionid 0x252f862028c0083, closing socket connection and attempting reconnect
2016-02-29T10:34:12.986+0800 o.a.s.c.f.s.ConnectionStateManager [INFO] State change: SUSPENDED
2016-02-29T10:34:13.059+0800 b.s.cluster [WARN] Received event :disconnected::none: with disconnected Zookeeper.
2016-02-29T10:34:13.197+0800 o.a.s.z.ClientCnxn [INFO] Opening socket connection to server zk-3.cloud.mos/172.16.13.147:2181. Will not attempt to authenticate using SASL (unknown error)
2016-02-29T10:34:13.241+0800 o.a.s.z.ClientCnxn [WARN] Session 0x252f862028c0083 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
at sun.nio.ch.SocketChannelImpl.checkConnect(Native Method) ~[na:1.8.0_31]
at sun.nio.ch.SocketChannelImpl.finishConnect(SocketChannelImpl.java:716) ~[na:1.8.0_31]
at org.apache.storm.zookeeper.ClientCnxnSocketNIO.doTransport(ClientCnxnSocketNIO.java:361) ~[storm-core-0.9.6.jar:0.9.6]
at org.apache.storm.zookeeper.ClientCnxn$SendThread.run(ClientCnxn.java:1081) ~[storm-core-0.9.6.jar:0.9.6]
Your client can no longer talk to the ZooKeeper server. The first thing that happened was there was no answer to the heartbeats within the negotiated session timeout:
2016-02-29T10:34:12.386+0800 o.a.s.z.ClientCnxn [INFO] Client session timed out, have not heard from server in 23789ms for sessionid 0x252f862028c0083, closing socket connection and attempting reconnect
Then when it tried to reconnect, it got a connection refused:
2016-02-29T10:34:13.241+0800 o.a.s.z.ClientCnxn [WARN] Session 0x252f862028c0083 for server null, unexpected error, closing socket connection and attempting reconnect
java.net.ConnectException: Connection refused
This means either your ZooKeeper server:
Is not reachable (network connection down)
Is dead (so nothing is listening on the socket)
Is GCing itself to death and cannot communicate (although that might have issued a connection timeout error, I'm not sure)
To tell more you will need to check the ZooKeeper server logs on your (Hadoop?) cluster.
Its worked for me by increasing the connection timeout in server.properties:
zookeeper.connection.timeout.ms=60000
One way that this can happen is if you start zookeeper, then break in the terminal, then try to start kafka.
In order to use kafka, you really should use 3 terminal windows (or 3 PuTTY sessions if you are SSHing into your instance from Windows)
First Session for Zookeeper server.
Second Session for Kafka server.
Third Session for running Kafka commands to do things like create topics.
I have started Kafka in cluster mode with 3 zookeeper server and 3 Kafka server. All zookeeper server started successfully but while starting Kafka server its get disconnected stating "fatal error during Kafka server startup. prepare to shutdown (kafka.server.kafkaserver)". while investigation, I found that Kafka server get disconnected every time after 18 seconds[which is zookeeper.connection.timeout.ms = 18000 default value] so I updated the same and issue get resolved.
always use 2181 as port number for zookeeper connection until you haven't configured your zookeeper !!!