All problems are now fixed.
Bitcoin shows up in seconds (certainly less than 30 seconds) and happily does the downloading of the latest blocks.
Unbelievable easy fix!
Thanks
Topic: 'sk_wait_data' problem (Read 2686 times)
I am on cable with no problems downloading.
Bitcoin has started but is not showing after some 2.5 hours and I have to leave home and shut down computer.
You are saying "no problem downloading". Like one network connection downloading single file? What about using a Bittorrent client Transmission to download Fedora-16 ISOs? I've seen many cable modems and home routers failing under the load of multiple peer-to-peer connections: this is exactly what bitcoin does. Using Transmission to download a freshly released Linux (like Fedora-16) should max out your network connection and will be a good test.Bitcoin has started but is not showing after some 2.5 hours and I have to leave home and shut down computer.
First simbly reboot the cable modem and the gateway router. If this doesn't help only then reinstall your Linux. Transmission is included with Ubuntu: use it to download some well-seeded torrent and and verify port forwarding on the router.
Thanks '2112 '
please let me know if there is anything I can do.
I am on cable with no problems downloading.
Bitcoin has started but is not showing after some 2.5 hours and I have to leave home and shut down computer.
'sk_wait_data' is still waiting. Both "tailf" "tail-f" have printed 10 lines (9 addresses) and they are also waiting.
Anything wrong? Anything I can do?
Reinstall lucid? Reinstall Bitcoin?
please let me know if there is anything I can do.
I am on cable with no problems downloading.
Bitcoin has started but is not showing after some 2.5 hours and I have to leave home and shut down computer.
'sk_wait_data' is still waiting. Both "tailf" "tail-f" have printed 10 lines (9 addresses) and they are also waiting.
Code:
-printtoconsole :
Bitcoin version 0.4.0-beta
OS version Linux 2.6.32-35-generic i686
System default language is 60 en_US.UTF-8
Language file locale/en_US/LC_MESSAGES/bitcoin.mo (English (U.S.))
Default data directory /home//.bitcoin
Bound to port 8333
Loading addresses...
dbenv.open strLogDir=/home//.bitcoin/database strErrorFile=/home/ /.bitcoin/db.log
Loaded 53669 addresses
addresses 4995ms
Loading block index...
LoadBlockIndex(): hashBestChain=00000000000001afb9d0 height=152620
block index 24836ms
Loading wallet...
nFileVersion = 40000
fGenerateBitcoins = 0
nTransactionFee = 0
fMinimizeToTray = 0
fMinimizeOnClose = 0
fUseProxy = 0
addrProxy = 127.0.0.1:9050
fUseUPnP = 1
wallet 137ms
Done loading
mapBlockIndex.size() = 152622
nBestHeight = 152620
setKeyPool.size() = 100
mapWallet.size() = 24
mapAddressBook.size() = 23
Loading addresses from DNS seeds (could take a while)
AddAddress(128.189.187.27:8333)
AddAddress(91.85.220.84:8333)
AddAddress(174.120.185.74:8333)
AddAddress(178.79.147.99:8333)
AddAddress(190.101.85.148:8333)
AddAddress(109.75.176.193:8333)
AddAddress(69.163.132.101:8333)
AddAddress(62.155.236.249:8333)
AddAddress(142.58.248.28:8333)
Anything wrong? Anything I can do?
Reinstall lucid? Reinstall Bitcoin?
It is pointless to look at wait channel in system monitor. Bitcoin is a multi-threaded application and to get a real picture you would need to watch wait channels for each thread.
To get a sensible picture of what's going on open a terminal and do "tailf ~/.bitcoin/debug.log", or alternatively start the bitcoin from the command line with the "-printtoconsole" flag.
By the way: sk_wait_data() simply means that the thread is waiting for the data to come through the network socket. I see no problem with this. Bitcoin is indeed heavily depending on the correct network operation.
To get a sensible picture of what's going on open a terminal and do "tailf ~/.bitcoin/debug.log", or alternatively start the bitcoin from the command line with the "-printtoconsole" flag.
By the way: sk_wait_data() simply means that the thread is waiting for the data to come through the network socket. I see no problem with this. Bitcoin is indeed heavily depending on the correct network operation.
After starting Bitcoin, System Monitor shows Status going from Uninterruptible-->Running-->Sleeping . Memory shows about 30 MiB. But the Waiting Channel after syncing gets stuck in 'sk_wait_data' . Already tried to Change Priority in 'Nice' to -20 but to no avail.
I tried to google and see what it is waiting for but all the information about 'sk_wait_data' is well above my level.
I use lucid. Any help appreciated.
Jump to: