connection dropped: not accepting new connections

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: malikusama on September 18, 2018, 12:54:48 AM

Quote from: calkob on September 15, 2018, 12:45:19 PM

Thanks for the replies guys. my node is running fine and has both incoming and out going connections. i was just interested in knowing what this IP address was up to and why it couldn't connect.

Check your firewall settings, [...]

Huh ?

A single dropped node has nothing to do with the firewall.. at least if this specific IP isn't explicitly blocked (which is not the case here).
It is completely normal that connections to some nodes get dropped or that some nodes do get banned from connecting to your own node.

This is because the nodes are not being compliant to the network rules.

Checking the firewall is necessary if ALL connections (or the majority) somehow get rejected / dropped. Not if you just can't connect to one single node while still having enough incoming/outgoing connections.

malikusama

copper member

Activity: 1050

Merit: 294

Quote from: calkob on September 15, 2018, 12:45:19 PM

Thanks for the replies guys. my node is running fine and has both incoming and out going connections. i was just interested in knowing what this IP address was up to and why it couldn't connect.

thanks again

Check your firewall settings, i doubt you had a problem over there because it usually denies new connections which results frequent drops in connection.

bob123

legendary

Activity: 1624

Merit: 2481

Quote from: calkob on September 15, 2018, 12:45:19 PM

i was just interested in knowing what this IP address was up to and why it couldn't connect.

This most probably is due to the node having some bad configuration.
A lot of people who try to run a node of a BTC fork (e.g. bcash) start their node with wrong configurations.

These nodes are regarded as bad nodes since they do not follow the correct rules / format. This happens more frequently than one would think.

As long as your node is connected to several other nodes, those log entries are nothing to worry about.

calkob

hero member

Activity: 1106

Merit: 521

Thanks for the replies guys. my node is running fine and has both incoming and out going connections. i was just interested in knowing what this IP address was up to and why it couldn't connect.

thanks again

bob123

legendary

Activity: 1624

Merit: 2481

This may be just connection dropping from bad nodes.
If core is running as it should (and has outgoing connections), there is no need to worry about it.

Or doesn't core connect at all suddenly ?

AdolfinWolf

legendary

Activity: 1946

Merit: 1427

Quote from: calkob on September 14, 2018, 12:06:22 PM

Been getting this in my node debug log: connection from 162.218.65.128:27555 dropped: not accepting new connections. Its like every minute this is happening and it has been going on for weeks. Huh

Any ideas?

Are you trying to connect to a node or are you running a node?

did this problem introduced itself suddenly, or was it after a software/hardware change? Were you ever able to connect/let connections be made without problems?

As of right now it seems to me that there could be many reasons for you not being able to connect; (Firewall, portforwarding, software issues.)

Maybe you could post the entirety of the debug.log so the issue might become a bit more clear for the users that are trying to help?

calkob

hero member

Activity: 1106

Merit: 521

Been getting this in my node debug log: connection from 162.218.65.128:27555 dropped: not accepting new connections. Its like every minute this is happening and it has been going on for weeks. Huh

Any ideas?

Topic: connection dropped: not accepting new connections (Read 239 times)