Author Topic: Here we go again....4.9 version not working....  (Read 21283 times)

0 Members and 1 Guest are viewing this topic.

Offline oco101

  • Hero Member
  • *****
  • Posts: 586
    • View Profile
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.

I got that too but if you let is "sit" it seems to start synching...slowly...

Now it got the connection but gets stuck on block 321976.
Is there anything I should do to make it go further?

I could not connect either with 0.4.9-a. I removed all files except wallet, and sync again and it works now I have 8 connections.

Offline GaltReport

I added this and got more connections:

network_set_advanced_node_parameters { "peer_connection_retry_timeout": 30, "desired_number_of_connections": 50, "maximum_number_of_connections": 200 }

Not sure if it helped or placebo effect.  :)

but it also started crashing after that.... :'(


jakub

  • Guest
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.

I got that too but if you let is "sit" it seems to start synching...slowly...

Now it got the connection but gets stuck on block 321976.
Is there anything I should do to make it go further?

Xeldal

  • Guest
For me 4.9-a did not connect at all(waited 15mins or so).  I had to delete my default wallet directory and now its got 1 connection that comes in and out. very slow.
https://bitsharestalk.org/index.php?topic=7768.msg102881#msg102881
« Last Edit: August 28, 2014, 06:44:31 pm by Xeldal »

Offline G1ng3rBr34dM4n

Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.

I waited a few minutes and then my client connected.  Currently have 8 network connections, although the sync does appear to be taking longer than usual...

Offline GaltReport

Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.

I got that too but if you let is "sit" it seems to start synching...slowly...

jakub

  • Guest
Still getting "Not Connected" with 0.4.9-a
So am I.
0.4.9-a on Windows 7 does not connect.

Offline doxymoron

  • Jr. Member
  • **
  • Posts: 43
    • View Profile
Still getting "Not Connected" with 0.4.9-a
wallet_approve_delegate doxymoron-delegate
75% pay rate
BTSX: doxymoron

Offline G1ng3rBr34dM4n

I would assume the version is not updated in the build process and thus requires manual intervention which hasn't been done... meaning ..  it doesn't really matter.  You're getting the right code. ;)

Cool, thanks gamey

Offline G1ng3rBr34dM4n

I had initial crash as well.  Removed all files except wallet and am now on the slow synch path....fingers crossed.

ich auch.

Offline GaltReport

I had initial crash as well.  Removed all files except wallet and am now on the slow synch path....fingers crossed.

Offline gamey

  • Hero Member
  • *****
  • Posts: 2253
    • View Profile
Installed 0.4.9a, still crashing.  Why does the crash report say app version 0.4.1...?

Code: [Select]
<?xml version="1.0" encoding="UTF-8" ?>
<CrashRpt version="1402">
    <CrashGUID>d4948a18-d9f4-4cd1-afa1-02d8c415e851</CrashGUID>
    <AppName>BitSharesX</AppName>
    <AppVersion>0.4.1</AppVersion>
    <ImageName>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ImageName>
    <OperatingSystem>Windows 7 Professional Build 7601</OperatingSystem>
    <OSIs64Bit>1</OSIs64Bit>
    <GeoLocation>en-us</GeoLocation>
    <SystemTimeUTC>2014-08-28T18:13:57Z</SystemTimeUTC>
    <ExceptionAddress>0x1378c64</ExceptionAddress>
    <ExceptionModule>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ExceptionModule>
    <ExceptionModuleBase>0x12b0000</ExceptionModuleBase>
    <ExceptionModuleVersion>0.0.0.0</ExceptionModuleVersion>
    <ExceptionType>0</ExceptionType>
    <ExceptionCode>-1073741819</ExceptionCode>
    <GUIResourceCount>100</GUIResourceCount>
    <OpenHandleCount>1841</OpenHandleCount>
    <MemoryUsageKbytes>153500</MemoryUsageKbytes>
    <ScreenshotInfo>
        <VirtualScreen left="0" top="0" width="3840" height="1080" />
        <Monitors>
            <Monitor left="0" top="0" width="1920" height="1080" file="screenshot0.jpg" />
            <Monitor left="1920" top="0" width="1920" height="1080" file="screenshot1.jpg" />
        </Monitors>
        <Windows>
            <Window left="31" top="132" width="1040" height="753" title="BitShares X" />
        </Windows>
    </ScreenshotInfo>
    <CustomProps />
    <FileList>
        <FileItem name="crashdump.dmp" description="Crash Minidump" />
        <FileItem name="crashrpt.xml" description="Crash Description XML" />
        <FileItem name="p2p.log" description="P2P Log File" />
        <FileItem name="qt_temp.Hp3448" description="Log File" />
        <FileItem name="screenshot0.jpg" description="Desktop Screenshot" />
        <FileItem name="screenshot1.jpg" description="Desktop Screenshot" />
    </FileList>
</CrashRpt>

I would assume the version is not updated in the build process and thus requires manual intervention which hasn't been done... meaning ..  it doesn't really matter.  You're getting the right code. ;)
I speak for myself and only myself.

Offline G1ng3rBr34dM4n

Installed 0.4.9a, still crashing.  Why does the crash report say app version 0.4.1...?

Code: [Select]
<?xml version="1.0" encoding="UTF-8" ?>
<CrashRpt version="1402">
    <CrashGUID>d4948a18-d9f4-4cd1-afa1-02d8c415e851</CrashGUID>
    <AppName>BitSharesX</AppName>
    <AppVersion>0.4.1</AppVersion>
    <ImageName>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ImageName>
    <OperatingSystem>Windows 7 Professional Build 7601</OperatingSystem>
    <OSIs64Bit>1</OSIs64Bit>
    <GeoLocation>en-us</GeoLocation>
    <SystemTimeUTC>2014-08-28T18:13:57Z</SystemTimeUTC>
    <ExceptionAddress>0x1378c64</ExceptionAddress>
    <ExceptionModule>C:\Program Files (x86)\BitSharesX\bin\BitSharesX.exe</ExceptionModule>
    <ExceptionModuleBase>0x12b0000</ExceptionModuleBase>
    <ExceptionModuleVersion>0.0.0.0</ExceptionModuleVersion>
    <ExceptionType>0</ExceptionType>
    <ExceptionCode>-1073741819</ExceptionCode>
    <GUIResourceCount>100</GUIResourceCount>
    <OpenHandleCount>1841</OpenHandleCount>
    <MemoryUsageKbytes>153500</MemoryUsageKbytes>
    <ScreenshotInfo>
        <VirtualScreen left="0" top="0" width="3840" height="1080" />
        <Monitors>
            <Monitor left="0" top="0" width="1920" height="1080" file="screenshot0.jpg" />
            <Monitor left="1920" top="0" width="1920" height="1080" file="screenshot1.jpg" />
        </Monitors>
        <Windows>
            <Window left="31" top="132" width="1040" height="753" title="BitShares X" />
        </Windows>
    </ScreenshotInfo>
    <CustomProps />
    <FileList>
        <FileItem name="crashdump.dmp" description="Crash Minidump" />
        <FileItem name="crashrpt.xml" description="Crash Description XML" />
        <FileItem name="p2p.log" description="P2P Log File" />
        <FileItem name="qt_temp.Hp3448" description="Log File" />
        <FileItem name="screenshot0.jpg" description="Desktop Screenshot" />
        <FileItem name="screenshot1.jpg" description="Desktop Screenshot" />
    </FileList>
</CrashRpt>

Offline oco101

  • Hero Member
  • *****
  • Posts: 586
    • View Profile
we maybe should stop trading before this bug is fixed

I doubt the recent sell off is due to bug issues but even so I'm looking at it as a shorting opportunity in the future ;D

Well you need a functional wallet in order to short ... Hopefully a fix will be release soon.

Offline Riverhead

we maybe should stop trading before this bug is fixed

I doubt the recent sell off is due to bug issues but even so I'm looking at it as a shorting opportunity in the future ;D


I doubt it's bug related as well but frankly I don't care. Cheap BTSX is good BTSX :)