windows has closed port 8333 EDIT - database corrupt problems.

shorena

copper member

Activity: 1498

Merit: 1528

No I dont escrow anymore.

Quote from: squall1066 on December 17, 2014, 10:24:05 AM

-snip-
I was hopeing you would not have said that, I have big problems in the UK with torrents, Virgin have pritty much blocked everything, We are in a policed state and can only view propaganda, It will take me 3 weeks to re-download the blockchain from scratch, And that keeps getting stuck on the way, It takes me 4-5 attempts to get it on any system.

Is there a way to commit the whole system in working the blockchain, My cpu is never more than 1% working on it, I have large sata 3 SSD's in raid 1+0 with 16GB ram, I wonder why It messed up in the first place?

Not sure what caused this or why you cant get inbound connections, but if you want to sync fast, feel free to hammer my server with requests.

Run bitcoin core from "run" (Win + R)

Code:

c:\Program Files\Bitcoin\bitcoin-qt.exe -connect=213.165.91.169

or take any of the servers below to sync a single node from your local network. Connect all other local nodes in the same fashion to the local IP of the node thats connected to the outside.

Code:

last updated 2014.11.25
-------------------------------------------------------------------------------------------------
IP - location - owner[1] - speed - info/stats page[2] - testnet
-------------------------------------------------------------------------------------------------
eldinhadzic.org[4] - LA, USA - eldinhadz - 1000 mbit/s - no - no
84.200.34.113 - Freinsheim, DE, EU - Newar - 1000 mbit/s - yes - no
185.45.192.129 - Amsterdam, NL, EU - anon - 1000 mbit/s - /node.php[3] - yes
213.165.91.169 - Germany, EU - shorena - 100 mbit/s - yes - no
50.7.68.180 - New York, USA - Newar - 100 mbit/s - yes - no
5.9.24.81 - Germany, EU - zvs - unknown - no - no
178.79.173.71 - United Kingdom, EU - zvs - unknown - no - no
107.155.104.194 - Dalls, USA - zvs - unknown - no - no
106.185.32.195 - Japan, Asia - zvs - unknown - no - no
94.242.57.173 - Russia, Asia - zvs - unknown - no - no
-------------------------------------------------------------------------------------------------
[1] refers to a bitcointalk.org username or anon if requested
[2] same IP, port 80 or path/port given
[3] work in progress
[4] IP is 173.236.158.177

Quote from: ?? on ??

first of all, why are you storing your bitcoins on windows ? Cheesy

If your car broke do you want to hear: Why are you using a car in the first place? Take a bike its better for the environment!

Its perfectly fine if you hate windows and do not want to support it, but other people may have other opinions on the matter.

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: ?? on ??

first of all, why are you storing your bitcoins on windows ? Cheesy

I'm not, I have a linux cold wallet for that and my escrows. Huh

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 10:41:59 AM

Quote from: OnkelPaul on December 17, 2014, 10:36:29 AM

Are you sure we're looking at the same screenshot?
It's clearly showing 2 LISTENING lines, one for IPv4 and one for IPv6.
I would still suspect the firewall.

Hmm... seems I am having troubles reading tonight (for some reason I was only looking at the RHS column but yes now that I look at the LHS column it is indeed LISTENING on 8333).

So it's a toss up between the firewall still running and the corrupt blockchain I guess.

You can probably check running processes to detect if a firewall is running.

I have opened applications as admin and checked everything, As I say I dont have alot running on this system, I am pritty much certain there is nothing else running, I do have MWB (premium) that I have disabled for this test, nothing.

I have deleted the last two 00207.dat and 00206.dat and its checking up to tat point, this is at least 2 months before I get the hard fork errors in my log, I am back up to 2 years behind from 5 years plus so I will see, if this does not work I will delete root directories and start again. Embarrassed

zetaray

hero member

Activity: 658

Merit: 500

Can you download a portscanner on your phone and scan the ports of your desktop to see if 8333 is listening? That sound like is the easiest way to be sure.

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Quote from: OnkelPaul on December 17, 2014, 10:36:29 AM

Are you sure we're looking at the same screenshot?
It's clearly showing 2 LISTENING lines, one for IPv4 and one for IPv6.
I would still suspect the firewall.

Hmm... seems I am having troubles reading tonight (for some reason I was only looking at the RHS column but yes now that I look at the LHS column it is indeed LISTENING on 8333).

So it's a toss up between the firewall still running and the corrupt blockchain I guess.

You can probably check running processes to detect if a firewall is running.

OnkelPaul

legendary

Activity: 1039

Merit: 1005

Quote from: CIYAM on December 17, 2014, 09:52:27 AM

Quote from: squall1066 on December 17, 2014, 09:50:51 AM

sorry, I attack my problems not run away Grin

That is admirable - your netstat did not show anything listening on 8333 (it only shows outbound connections).

Are you sure we're looking at the same screenshot?
It's clearly showing 2 LISTENING lines, one for IPv4 and one for IPv6.
I would still suspect the firewall.

Onkel Paul

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 10:28:17 AM

Hard to say why it messed up but presumably the upgrade had something to do with it.

I'm sorry I don't have a better idea - you could try working out which files from the blocks and chainstate directories to delete (before starting bitcoind/-qt) to minimise the resync (but I am not your guy for that sorry).

Hay, I appreciate the time tho, I am only stuck 42 hours behind, I think a few .dat deletions should get me past the problem, in fact I will try that now.

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Hard to say why it messed up but presumably the upgrade had something to do with it.

I'm sorry I don't have a better idea - you could try working out which files from the blocks and chainstate directories to delete (before starting bitcoind/-qt) to minimise the resync (but I am not your guy for that sorry).

Of course if you delete files you are going to have to use the -reindex option at startup to repair (but that should be much quicker than downloading the entire blockchain again).

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 10:17:56 AM

Quote from: squall1066 on December 17, 2014, 10:16:02 AM

I am not running a .conf file.

I allways just download the core from here and run, never had the need to use one.

In that case - here is my theory - because your blockchain is screwed bitcoind/-qt is not getting to the point of listening at all (I haven't checked the source code to see if it does check the blockchain before starting the listening port so that is why it is a theory).

If this theory is correct then you should be able to fix this issue by downloading a torrent of the blockchain (after deleting your current one) and restarting it.

so it was coincidence it happened after a win 7 update? On three units? all the same problem? what are the chances of that! LOL

I was hopeing you would not have said that, I have big problems in the UK with torrents, Virgin have pritty much blocked everything, We are in a policed state and can only view propaganda, It will take me 3 weeks to re-download the blockchain from scratch, And that keeps getting stuck on the way, It takes me 4-5 attempts to get it on any system.

Is there a way to commit the whole system in working the blockchain, My cpu is never more than 1% working on it, I have large sata 3 SSD's in raid 1+0 with 16GB ram, I wonder why It messed up in the first place?

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Quote from: squall1066 on December 17, 2014, 10:16:02 AM

I am not running a .conf file.

I allways just download the core from here and run, never had the need to use one.

In that case - here is my theory - because your blockchain is screwed bitcoind/-qt is not getting to the point of listening at all (I haven't checked the source code to see if it does check the blockchain before starting the listening port so that is why it is just a theory).

If this theory is correct then you should be able to fix this issue by downloading a torrent of the blockchain (after deleting your current one) and restarting it.

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 10:07:11 AM

Hmm... that doesn't look good in regards to the fork situation (so you do have a problem with your bitcoin blockchain) - but I don't think that should stop your bitcoind/-qt server from listening.

Do you have a bitcoin.conf file?

And if so you need to make sure it doesn't have this:

nolisten=1

In any case you are going to have to fix up your blockchain.

I am not running a .conf file.

I allways just download the core from here and run, never had the need to use one.

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Hmm... that doesn't look good in regards to the fork situation (so you do have a problem with your bitcoin blockchain) - but I don't think that should stop your bitcoind/-qt server from listening.

Do you have a bitcoin.conf file?

And if so you need to make sure it doesn't have this:

nolisten=1

In any case you are going to have to fix up your blockchain.

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 09:52:27 AM

Quote from: squall1066 on December 17, 2014, 09:50:51 AM

sorry, I attack my problems not run away Grin

That is admirable - your netstat did not show anything listening on 8333 (it only shows outbound connections).

Is your bitcoind/bitcoin-qt not configured to listen?

As far as I know, I keep getting this in the log, anything important?

Code:

2014-12-17 12:57:01 ProcessBlock: ACCEPTED
2014-12-17 12:57:04 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334606 (000000000000000009756a33660d7efafc073722e18eb22a6a2187d4be407253).
Chain state database corruption likely.
2014-12-17 12:57:04 ProcessBlock: ACCEPTED
2014-12-17 12:57:06 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334607 (00000000000000001796e0f3a1a0f32a2fe6b9fc2200d86a84f9b2da76cd6fa7).
Chain state database corruption likely.
2014-12-17 12:57:06 ProcessBlock: ACCEPTED
2014-12-17 12:57:12 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334608 (00000000000000000d11ca539189583fb86044a68f6cd9a29659aac76c162715).
Chain state database corruption likely.
2014-12-17 12:57:12 ProcessBlock: ACCEPTED
2014-12-17 12:57:13 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334609 (00000000000000001b129e7662848cbc6d2f17d887abd69e91c8d955a5c46d37).
Chain state database corruption likely.
2014-12-17 12:57:13 ProcessBlock: ACCEPTED
2014-12-17 12:57:18 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334610 (0000000000000000092e6c82a01d10489282f2eca468ac7ef2ddcdc9e09900dd).
Chain state database corruption likely.
2014-12-17 12:57:18 ProcessBlock: ACCEPTED
2014-12-17 12:57:19 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334611 (000000000000000006237551bebb034dadfc7a66786d724927d4c85a8a96d4b4).
Chain state database corruption likely.
2014-12-17 12:57:19 ProcessBlock: ACCEPTED
2014-12-17 12:57:20 CheckForkWarningConditions: Warning: Large valid fork found
forking the chain at height 334464 (00000000000000001b62197088516f7cb4717c2a62e4280c8810ea77de5418c0)
lasting to height 334612 (0000000000000000043208a7f8c5351dd3e21552c88b8d86624e654b5eb6c11c).
Chain state database corruption likely.

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Quote from: squall1066 on December 17, 2014, 09:50:51 AM

sorry, I attack my problems not run away Grin

That is admirable - your netstat did not show anything listening on 8333 (it only shows outbound connections).

Is your bitcoind/bitcoin-qt not configured to listen?

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 09:45:44 AM

Of course - you could just "stop using Windows" and your problem will just go away.

sorry, I attack my problems not run away Grin

squall1066

copper member

Activity: 2310

Merit: 1032

squall1066

copper member

Activity: 2310

Merit: 1032

Quote from: CIYAM on December 17, 2014, 09:36:02 AM

Although you say you have stopped all firewalls, etc. this looks like firewall blocking to me.

Assuming it is not your router then I think that maybe you are running a firewall even though you think you are not (maybe some new sort of "net nanny" behaviour that Windows has that makes it impossible to disable the firewall?).

I know, my systems are fairly clean, Here is some pics to help.

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Of course - you could just "stop using Windows" and your problem will just go away.

cakir

legendary

Activity: 1274

Merit: 1000

★ BitClave ICO: 15/09/17 ★

Well, There's a way to understand it's blocked or not.
Open a command prompt (cmd)

And enter this command: netstat -an | find "8333"
if it's not listening there's a problem that can be fixed via software.
if it's listening you should restart your computer.

CIYAM

legendary

Activity: 1890

Merit: 1086

Ian Knowles - CIYAM Lead Developer

Although you say you have stopped all firewalls, etc. this looks like firewall blocking to me.

Assuming it is not your router then I think that maybe you are running a firewall even though you think you are not (maybe some new sort of "net nanny" behaviour that Windows has that makes it impossible to disable the firewall?).

squall1066

copper member

Activity: 2310

Merit: 1032

For some reason I have several windows 7 ultimate systems, and since the last update, I cannot connect to port 8333 atall! it is closed to the net despite being open according to windows?

Note I can have 8 "outbound" connections but never any "inbound"

I can run fine on linux based systems, with the port checking tool showing 8333 is open, My router is fine.

On my win7 units, I have closed all firewalls, stopped all webcheckers/antivirus and the like, I have added port exceptions in the windows firewall list before I stopped it, I cant connect to port 8333 for love nor money.

I can only see through commands 0:0:0:0;8333 listening I have no idea what but that's the closest I can get.

If anyone can help me I can post anything needed.

EDIT - Just for a tl/dr I have got bad database problems, I have checked out hardware on many systems, It cant be just me that gets so far and "database is corrupt, would you like to rebuild now" so you are FORCED to start again.

Topic: windows has closed port 8333 EDIT - database corrupt problems. (Read 2565 times)