Anyone else getting an error where BitHopper stops after a period of time?
It just gets stuck...
[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
It just gets stuck...
[14:16:38] writing to database
[14:17:38] writing to database
[14:18:38] writing to database
[14:19:38] writing to database
[14:20:38] writing to database
[14:21:38] writing to database
[14:22:38] writing to database
[14:23:38] writing to database
+1 for this since i got the latest version
EDIT: this still isn't fixed in the latest version... just a heads up.
I get an LP call then constant "writing to database" messages.
renders my miner useless until i restart bithopper
occurs every 30 minutes approximately for me.
+1
occurs on BH 0.2.2.4-68.
As a workaround I wrote a very simple windows console script which restarts the BH about every 30 minutes. It assumes that there is only a single python.exe process running and that it is a BH.
Code:
@echo off
set DELAY=1800
set PYTHON_IM=python.exe
set PYTHON_PATH=c:\Python27\python.exe
set BH_PATH=d:\c00w-bitHopper\bitHopper.py
:loop
echo Restarting BitHopper....
taskkill /T /IM %PYTHON_IM%
start %PYTHON_PATH% %BH_PATH%
echo Waiting %DELAY% sec...
ping 127.0.0.1 -n %DELAY% >nul
goto :loop
set DELAY=1800
set PYTHON_IM=python.exe
set PYTHON_PATH=c:\Python27\python.exe
set BH_PATH=d:\c00w-bitHopper\bitHopper.py
:loop
echo Restarting BitHopper....
taskkill /T /IM %PYTHON_IM%
start %PYTHON_PATH% %BH_PATH%
echo Waiting %DELAY% sec...
ping 127.0.0.1 -n %DELAY% >nul
goto :loop