HelloZeroNet / HelloZeroNet/ZeroNet

Database rebuilding... Imported 0000 of 55322 files...

Open
#1,410 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
18.8k
Forks
2.3k
PR merge metrics
No merged PRs in 30d

Description

### Step 1: Please describe your environment

* ZeroNet version: 0.6.2 rev3465
* Operating system: W10
* Web browser: FF
* Tor status: available
* Opened port: no
* Special configuration: --multiuser_local

### Step 2: Describe the problem:

Hello, i tried to Rebuild **ZeroMe** DB, because i lost users i followed and posts i liked, no longer appeared. It happened after my computer crashed.

When i go to ZeroMe and click "Rebuild" button, then the information bubble "Database rebuilding..." appear. Then after some minutes, appear another bubble:

Database rebuilding...
Imported 0000 of 55322 files...

I let that ZN page be and ZN running more than 6 hours, but nothing changed, same bubbles, same 0000 value. I see ZeroHello newsfeed stopped loading since then.

HDD activity of the ZeroNet.exe is 0.1MB/s which is a minimum value shown in Task manager i assume. CPU is at normal values.

debug.log says example:
[2018-05-01 23:39:50,967] DEBUG Site:1SunAW..JN9a Error loading data/users/1BpjTxx3SZuxpicn1gKWPkFPycSkvntxfw/content.json for removeContent: KeyError: u'data/users/1BpjTxx3SZuxpicn1gKWPkFPycSkvntxfw/content.json' in ContentManager.py line 248 > ContentDbDict.py line 59
[2018-05-01 23:39:50,967] WARNING Site:1SunAW..JN9a data/users/content.json parse error: UnicodeDecodeError: 'ascii' codec can't decode byte 0xe9 in position 14: ordinal not in range(128) in ContentManager.py line 184 > ContentManager.py line 264

So my opinion is that the database rebuilding process is not transparent from the user point of view, because it gives impression it is stuck for unknown reason.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.