0.10.1-win64 does not start

vayvanne commented at 6:22 pm on April 28, 2015: none

On some windows setups path to DB includes windows username, like C:\Users\uzza\AppData\Roaming\Bitcoin. If uzza is in non-English locale bitcoind does not start. 0.10.0 was all right although it did show unreadable symbols in place of username.

jonasschnelli commented at 7:48 pm on April 28, 2015: contributor

Tested 0.10.1 on windows 7 with a username containing a “ä” and a “ö”. No problems (see proof screen below). @vayvanne: could you be more precise?

Define “does not start” (any output in the log)?
Windows version?
What do you mean with “path to DB”? Do you mean –datadir=?

bildschirmfoto 2015-04-28 um 21 45 59

vayvanne commented at 8:25 pm on April 28, 2015: none

I have got the following

in russian windows 7 x64 generally I do see russian letters in console but these printed out by bitcoind are unreadable.

jonasschnelli commented at 6:38 am on April 29, 2015: contributor

Indeed. This is an issue. It looks like that the boost filesystem library can’t handle non-latin chars (or similar). Will analyze this more precise. I could also reproduce the issue with 0.10. @vayvanne: are you sure that 0.10 didn’t had this problem? Can you post a screenshot/log of the startup using 0.10?

I also wonder why my windows shell is not capable of displaying a correct unicode value (but that’s probably a different story).

bildschirmfoto 2015-04-29 um 08 28 14

bildschirmfoto 2015-04-29 um 08 28 49

vayvanne commented at 4:25 pm on April 29, 2015: none

I am sure that 0.10.0 was running well on the same system. But I can not get it running now: bitcoin-0 10 0

Error message is other than from first screenshot this time. My guess is it was ok because DB was created with non-English symbols in paths. It is confirmed by this: bitcoin-0 10 0-init

As you can see 0.10.0 inits ok with empty DB. Then bitcoind was upgraded several times from 0.8 to 0.10. Not sure why the boot error is triggered on only in 0.10.1. PS. you can get non-English letters in place of question marks if you set your language support for all programs that does not support unicode in windows control panel. For russian windows 7 it looks like this: non-unicode

vayvanne commented at 5:14 pm on April 29, 2015: none

I was wrong that 0.10.0 inits correctly with empty DB. It shuts down in short time:

2015-04-29 17:00:09 2015-04-29 17:00:09 Bitcoin version v0.10.0 (2015-02-13 09:55:11 +0100) 2015-04-29 17:00:09 Using OpenSSL version OpenSSL 1.0.1k 8 Jan 2015 2015-04-29 17:00:09 Using BerkeleyDB version Berkeley DB 4.8.30: (April 9, 2010) 2015-04-29 17:00:09 Default data directory C:\Users\юзза\AppData\Roaming\Bitcoin 2015-04-29 17:00:09 Using data directory C:\Users\юзза\AppData\Roaming\Bitcoin 2015-04-29 17:00:09 Using config file C:\Users\юзза\AppData\Roaming\Bitcoin\bitcoin.conf 2015-04-29 17:00:09 Using at most 125 connections (2048 file descriptors available) 2015-04-29 17:00:09 Using 2 threads for script verification 2015-04-29 17:00:09 Allowing RPC connections from: 127.0.0.0/255.0.0.0 ::1/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff 2015-04-29 17:00:09 Using wallet wallet.dat 2015-04-29 17:00:09 init message: Verifying wallet… 2015-04-29 17:00:09 CDBEnv::Open : LogDir=C:\Users\юзза\AppData\Roaming\Bitcoin\database ErrorFile=C:\Users\юзза\AppData\Roaming\Bitcoin\db.log 2015-04-29 17:00:09 Bound to [::]:8333 2015-04-29 17:00:09 Bound to 0.0.0.0:8333 2015-04-29 17:00:09 init message: Loading block index… 2015-04-29 17:00:09 Opening LevelDB in C:\Users\юзза\AppData\Roaming\Bitcoin\blocks\index 2015-04-29 17:00:09 Opened LevelDB successfully 2015-04-29 17:00:09 Opening LevelDB in C:\Users\юзза\AppData\Roaming\Bitcoin\chainstate 2015-04-29 17:00:09 Opened LevelDB successfully 2015-04-29 17:00:09 LoadBlockIndexDB: last block file = 0 2015-04-29 17:00:09 LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=1, size=293, heights=0…0, time=2009-01-03…2009-01-03) 2015-04-29 17:00:09 Checking all blk files are present… 2015-04-29 17:00:09 LoadBlockIndexDB(): transaction index disabled 2015-04-29 17:00:09 LoadBlockIndexDB(): hashBestChain=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f height=0 date=2009-01-03 18:15:05 progress=0.000000 2015-04-29 17:00:09 init message: Verifying blocks… 2015-04-29 17:00:09 Shutdown requested. Exiting. 2015-04-29 17:00:09 Shutdown: In progress… 2015-04-29 17:00:09 StopNode() 2015-04-29 17:00:09 Committing 0 changed transactions (out of 0) to coin database… 2015-04-29 17:00:09 Shutdown: done

Diapolo commented at 6:35 am on April 30, 2015: none

@laanwj AFAIK there was a patch which changed some locale stuff and was related to boost? Can you perhaps shed some light in here?

dexX7 commented at 6:50 am on April 30, 2015: contributor

https://github.com/bitcoin/bitcoin/commit/c9e022b7eee9f77cd33b333d6ff52f711d3bc989 and https://github.com/bitcoin/bitcoin/commit/df45564cf0ad3b591d4eb8cc2354093bcb7df14c set a locale explicitly for boost::path, where the “C” locale is used as default and as fallback, if no valid environment locale is detected in POSIX systems.

However, what strikes me is #6078 (comment), which hints a path/locale related issue, before those changes were adopted.

jonasschnelli commented at 8:49 pm on April 30, 2015: contributor

I just invested some hours to track this down without success. Tried to change https://github.com/bitcoin/bitcoin/blob/master/src/util.cpp#L672 from A(nsi) to W(widechar). Worked partial but produced issues wherever a boost path was converted to c_str() (Databases, etc.).

Also figured out that 0.10 was running fine in Russian but not in Tajiki (chosen by random). 0.10.1 Does not run on Russian Window; therefore i think is serious and should get fixed asap.

theuni commented at 4:01 am on May 1, 2015: member

@jonasschnelli Indeed. Thanks for looking into this. I’ll join you in the hunt.

jonasschnelli referenced this in commit b3ffcdf916 on May 1, 2015

jonasschnelli commented at 12:05 pm on May 1, 2015: contributor

I have tested bitcoind and Bitcoin-Qt 0.9.2, 0.9.3 and 0.10.0 and 0.10.1 on Windows 7 with Russian, Chinese, Tajik and German. If you use usernames (or lets say a –datadir path) with special characters from one of these languages you might run into this boost::filesystem chars issue. #6093 fixes this only partial.

jonasschnelli commented at 12:05 pm on May 1, 2015: contributor

@vayvanne: can you test #6093? If you can’t build yourself you can try use a prebuilt binary: https://builds.jonasschnelli.ch/pulls/6093/

laanwj added the label Bug on May 1, 2015

laanwj added the label Windows on May 1, 2015

laanwj commented at 4:12 pm on May 1, 2015: member

I think this warrants a 0.10.2 release for Windows. If we don’t find a better fix, I’ll just roll back the patch that caused this on the 0.10 branch. This will re-introduce a rare shutdown race condition (#3136), but is preferable to users not being able to use the software at all.

dexX7 commented at 4:30 pm on May 1, 2015: contributor

I’m currently testing two alternatives: https://gist.github.com/dexX7/7394a947b29c7d84c710

To test it, I’m trying to use different paths with those builds, as well as 0.9.3, 0.10.1 on Windows 8.1 x64, and I should have a list of results in a few minutes.

The “classic” route has a similar faulty behavior as 0.10.1, but the “dummy” route works very well so far.

vayvanne commented at 5:04 pm on May 1, 2015: none

@jonasschnelli I have got running 0.10.0, the problem was probably wrong permissions to %appdata%\bitcoin. The build you proposed does run ok too on my setup.

theuni commented at 9:11 pm on May 1, 2015: member

As mentioned here: #6093 (comment) I propose this fix: https://github.com/theuni/bitcoin/commit/a0828049a7aa8dba3bfd12964ac897cbf1698a03

laanwj closed this on May 10, 2015

laanwj referenced this in commit 424ae6629b on May 11, 2015

laanwj commented at 9:28 am on May 14, 2015: member

@vayvanne Should be fixed in the 0.10.2 release candidate - you’re very welcome to test. See https://bitcoin.org/bin/bitcoin-core-0.10.2/test for executables.

vayvanne commented at 5:00 pm on May 14, 2015: none

Yep. 0.10.2rc1 running good on my setup although the non-English symbols in console are still not readable.

laanwj commented at 7:44 am on May 16, 2015: member

Thanks for testing.

The character handling in the logging output is an orthogonal issue, and the result of mixing different kinds of encodings. On Linux and MacOSX this issue doesn’t exist as everything from front-end to back-end is UTF-8, but Windows is the odd duck out. Needs to be fixed some day but is much lower priority than ’not running at all'.

reddink referenced this in commit 200b5b8c93 on May 27, 2020

DrahtBot locked this on Sep 8, 2021

owlhooter referenced this in commit ab06889595 on Dec 10, 2021

0.10.1-win64 does not start #6078