Bitcoin-qt 0.14.2 opens 8333 successfully with UPNP, yet port closed

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Quote from: Bestcoin-fan on August 09, 2017, 04:00:16 PM

jackg, again thank you very much for the replies.
Numerous shutdowns (restarts) were due to my attempts to try various methods to fix the problem, yet nothing did help

There looked to be a shutdown on the 7th (before the problem started if I'm not wrong) where the client restarted on it's own and didn't manage to shutdown cleanly - which could have caused some sort of problem - though it seemed to boot OK).

I'd also suggest you wait 2/3 minutes before you attempted to start the core once the shutdown is finished. And it does appear to still have been recieving UpdateTip responses during this time and was attempting to connect to other nodes - which means your client was still getting connections somehow.

Bestcoin-fan

member

Activity: 154

Merit: 11

jackg, again thank you very much for the replies.
Numerous shutdowns (restarts) were due to my attempts to try various methods to fix the problem, yet nothing did help

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Based on the Debug.log OP sent me via PM, it looks like there were a large number of shutdowns yesteday. I'm not sure if htese are planned or not (there are a few restarts that appear not to be but no database errors).

It was probably just a simple issue that's fixed itself now as I can't really see anythig that looks suspicious (there are a few misbehaving peers and a few forcible connection interruptions from peers -but these are fairly normal).

As to the error in it stoping downloading blocks, it looks like a lack of connection or an error that forces it to restart, however the cause is not clear in the debug log. Try connecting to a node from a pool if possible in order to try see if it is the connection error.

Bestcoin-fan

member

Activity: 154

Merit: 11

I am home all day today. And all day incoming connections are all OK.
So, I have no ideas what it was yesterday. I'll go on monitoring the situation as I very much want to contribute the great bitcoin network

Bestcoin-fan

member

Activity: 154

Merit: 11

Quote from: ranochigo

Can you check it with canyouseeme.org the next time it goes off?

Of course (I did use similar services to test for open port)

Quote from: ranochigo

Were you still synchronizing the blockchain at the time? The blocks has to be verified individually so your client might just stop synchronizing for abit for your CPU to verify the block.

No. My core wallet was fully synced long ago.

ranochigo

legendary

Activity: 2954

Merit: 4158

Quote from: Bestcoin-fan on August 08, 2017, 08:33:09 PM

jackg, thank you very much for reply. You know, just as mysteriously as the incoming connections and open 8333 suddenly disappeared and were totally off for long (restarting the wallet, rebooting the system, router didn't help), just as mysteriously port 8333 became open at a moment.

Can you check it with canyouseeme.org the next time it goes off?

Quote from: Bestcoin-fan on August 08, 2017, 08:33:09 PM

Yet I now recall another common problem with the bitcoin core wallet, I mean it pretty often just stops syncing the blockchain. It as if falls asleep or something like that. I tuned the system so that it never sleeped or hybernated, or enabled power management for a device, so that is not the system problem.

Were you still synchronizing the blockchain at the time? The blocks has to be verified individually so your client might just stop synchronizing for abit for your CPU to verify the block.

Quote from: Bestcoin-fan on August 08, 2017, 08:33:09 PM

My ISP offers static IPs for money, and I don't see it necessary for just opening incoming connections, so I use dynamic IPs. All of my IPs are in the log. I've just reviewed the log, and I can see only "UPnP Port Mapping successful" messages, so why 8333 was closed for pretty long is totally unclear.
I'll send you my log in a private message. Maybe you'll be able to detect something. Thanks in advance.

Yes, it is not necessary. However, your incoming clients will lose the connection to you with your IP change. This is usually not recoverable till your client reboots.

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Quote from: Bestcoin-fan on August 08, 2017, 08:33:09 PM

jackg, thank you very much for reply. You know, just as mysteriously as the incoming connections and open 8333 suddenly disappeared and were totally off for long (restarting the wallet, rebooting the system, router didn't help), just as mysteriously port 8333 became open at a moment.

Yet I now recall another common problem with the bitcoin core wallet, I mean it pretty often just stops syncing the blockchain. It as if falls asleep or something like that. I tuned the system so that it never sleeped or hybernated, or enabled power management for a device, so that is not the system problem.

My ISP offers static IPs for money, and I don't see it necessary for just opening incoming connections, so I use dynamic IPs. All of my IPs are in the log. I've just reviewed the log, and I can see only "UPnP Port Mapping successful" messages, so why 8333 was closed for pretty long is totally unclear.
I'll send you my log in a private message. Maybe you'll be able to detect something. Thanks in advance.

I'm glad to hear the first problem was solved.
I'll have a look at the debug.log and see why that is. Although, from what I can tell, it's a common hardware issue. Normally, unless the ccaus can be detected you'll have to cope with the delays (unless the database keeps becoming corrupted).

Bestcoin-fan

member

Activity: 154

Merit: 11

jackg, thank you very much for reply. You know, just as mysteriously as the incoming connections and open 8333 suddenly disappeared and were totally off for long (restarting the wallet, rebooting the system, router didn't help), just as mysteriously port 8333 became open at a moment.

Yet I now recall another common problem with the bitcoin core wallet, I mean it pretty often just stops syncing the blockchain. It as if falls asleep or something like that. I tuned the system so that it never sleeped or hybernated, or enabled power management for a device, so that is not the system problem.

My ISP offers static IPs for money, and I don't see it necessary for just opening incoming connections, so I use dynamic IPs. All of my IPs are in the log. I've just reviewed the log, and I can see only "UPnP Port Mapping successful" messages, so why 8333 was closed for pretty long is totally unclear.
I'll send you my log in a private message. Maybe you'll be able to detect something. Thanks in advance.

jackg

copper member

Activity: 2856

Merit: 3071

https://bit.ly/387FXHi lightning theory

Quote from: Bestcoin-fan on August 08, 2017, 03:12:49 PM

Hello,
I passionately want to help the great BTC network with my full node bitcoin core wallet!
And everything had been quite fine, I had had port 8333 open all the time, outside sources had been always saying my 8333 was open, the wallet (debug window) had showed 12-30 incoming connections...

But today at some time, without any reason, all outside sources started saying my 8333 is closed. Debug window confirms that by showing 0 incoming connections. But! When I look into the wallet's log it says it has successfully opened UPNP service, successfully registered the 8333 port, and my router does confirm that by showing 8333 has been opened with UPNP (as it had always been before).

Yet, no incoming connections, and outside sources say the port 8333 closed.

Who can guess what??

Can you send the debug.log file? It's located in the data directory (the parent of the directories of "blocks" and "chainstate").
Could you also send your IP if you want that port testing, PM me that if you don't want it publically displayed and I'll test a regular network connection on it (not from the Bitcoin client).

Bestcoin-fan

member

Activity: 154

Merit: 11

Hello,
I passionately want to help the great BTC network with my full node bitcoin core wallet!
And everything had been quite fine, I had had port 8333 open all the time, outside sources had been always saying my 8333 was open, the wallet (debug window) had showed 12-30 incoming connections...

But today at some time, without any reason, all outside sources started saying my 8333 is closed. Debug window confirms that by showing 0 incoming connections. But! When I look into the wallet's log it says it has successfully opened UPNP service, successfully registered the 8333 port, and my router does confirm that by showing 8333 has been opened with UPNP (as it had always been before).

Yet, no incoming connections, and outside sources say the port 8333 closed.

Who can guess what??

Topic: Bitcoin-qt 0.14.2 opens 8333 successfully with UPNP, yet port closed (Read 533 times)