Burst Blockchain DDL - Updated Regular every 24h (Zipped)
-
Update-I have added ip address and run 'run.sh. Here are the last few line of that ongoing run:
2016-10-14 08:29:05 INFO: nxt.allowedBotHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-10-14 08:29:05 INFO: nxt.enableAPIServer = "true"
2016-10-14 08:29:05 INFO: nxt.apiServerPort = "8125"
2016-10-14 08:29:05 INFO: nxt.apiServerHost = "127.0.0.1"
2016-10-14 08:29:05 INFO: nxt.apiSSL = "false"
2016-10-14 08:29:05 INFO: nxt.apiServerIdleTimeout = "30000"
2016-10-14 08:29:05 INFO: nxt.apiResourceBase = "html/ui"
2016-10-14 08:29:05 INFO: nxt.javadocResourceBase = "html/doc"
2016-10-14 08:29:05 INFO: nxt.enableAPIServerGZIPFilter = "false"
2016-10-14 08:29:05 INFO: nxt.apiServerCORS = "false"
2016-10-14 08:29:05 INFO: nxt.allowedUserHosts = "127.0.0.1; localhost; [0:0:0:0:0:0:0:1];"
2016-10-14 08:29:05 INFO: nxt.enableUIServer = "false"
2016-10-14 08:29:05 INFO: User interface server not enabled
2016-10-14 08:29:05 INFO: nxt.debugTraceQuote = """
2016-10-14 08:29:05 INFO: nxt.debugTraceSeparator = " "
2016-10-14 08:29:05 INFO: nxt.debugLogUnconfirmed = "false"
2016-10-14 08:29:05 INFO: nxt.debugTraceAccounts not defined
2016-10-14 08:29:05 INFO: nxt.debugTraceLog = "nxt-trace.csv"
2016-10-14 08:29:05 INFO: Genesis block already in database
2016-10-14 08:30:23 INFO: Last block height: 278332
2016-10-14 08:30:24 INFO: Started API server at 127.0.0.1:8125
2016-10-14 08:30:24 INFO: Started peer networking server at 0.0.0.0:8123
2016-10-14 08:30:24 INFO: Initialization took 79 seconds
2016-10-14 08:30:24 INFO: Burst server 1.2.6 started successfully.
2016-10-14 08:30:24 INFO: burst.mockMining = "false"
2016-10-14 08:39:53 INFO: processed block 280000Can anyone determine if 'run.sh' is working properly? Any help would be greatly appreciated.
Thanks
-
@vadirthedark I will give it a try on my side and let you know with updates.
-
@vadirthedark "2016-10-14 08:39:53 INFO: processed block 280000" means you're within 5,000 blocks of current - the counter only updates every 5,000 - so by now, you should be fully synced.
-
haitch - thanks for the update.
I have opened a wallet account and have PP and ID, etc. and have been following the 'Burstcoin documentattion for GNU/Linux by Kartojal' and also have 14 burstcoins. I am now trying to do plotter setup from 'Readme' file from MDCCT Plotter/.../... from 'Bitcoin Documentation by Kartojal'.Here is the first Linux section of the plotter setup instructions:
Linux
Install the build-essential and g++ packets.
Install OpenCL (available in the manufacturer SDKs).
You may have to install the opencl headers ([apt-get install opencl-headers] on Ubuntu).Modify the [PLATFORM] variable to one of [32] or [64] depending on the target platform.
Modify the [OPENCL_INCLUDE] and [OPENCL_LIB] variables of the Makefile to the correct path.
Example:OPENCL_INCLUDE = /opt/AMDAPPSDK-2.9-1/include OPENCL_LIB = /opt/AMDAPPSDK-2.9-1/lib/x86_64I have Googled this, but I am too new to Linux to understand how to set variables or what the above lines mean. Can anyone help with this?
Thanks
-
@vadirthedark you'll need to edit the Makefile file to change the values. Try nano Makefile, gedit Makefile or vi Makefile (vi is evil so hopefully you have alternatives)
-
Edited 'Makefile'. However, it was empty so I added the two 'OpenCL..' variables. I then went to my '.../plotter' dir and ./gpuPlotGenerator listPlatforms' in terminal. Getting error "Inconsistency detected by ld.so: dl-version.c: 224: _dl_check_map_versions: Assertion `needed != ((void *)0)' failed!' I would greatly appreciate if anyone can help me on this situation and how this pertains to the plotting of drive?
haitch
I have a question concerning the running of 'run.sh' and how to know when it has executed fully. I remember that it ran to 280000 and stopped. However, it did not end and come back to $. Any ideas?
Thanks for any help.
-
@vadirthedark I'd start a new thread about it - with a title about building the plotter. Will get more attention than being buried in this thread.
-
hi guys, is there a file thats more up to date than the one on db.burst-team.us whenever i use this one on my server it gets to about block 284412 and stops and gives me errors and starts blacklisting
-
@Lexicon I've updated the db.zip - see if it works for you now.
-
edit: nvm it works
-
@BurgerBaron The zip failed to create - I've just kicked off a re-zip, try again in 5 minutes,
-
@haitch said in Burst Blockchain DDL - Updated Regular every 24h (Zipped):
@BurgerBaron The zip failed to create - I've just kicked off a re-zip, try again in 5 minutes,
awh, I saw some downloading (fairly slow), but thanks!
Akways the quick replier, hard worker ;)
-
@BurgerBaron The zip should be available now
-
Hi im new here (watched adams videos last night) ive downloaded and setup the wallet but the blockchain is taking ages to download ive put the unzipped files in the burst_db folder i currently have 4 files in there plus one temp file the files names are as follows;
burst.h2.db
burst.lock.db
burst.mv.db
burst.trace.dbis it supposed to take this long any help will be appriciated
many thanks
-
@armz_j Have you downloaded the blockchain and restarted the wallet? The blockchain should only be replaced with the wallet completely closed (check in the tray!)...
For you to use the online wallet you don't need the blockchain to be downloaded, only for the local one! If you downloaded this ZIPed blockchain then your blockchain should be max 24 hours behind so it should catch up in 20 min tops (usually less) but if you replaced the files with the wallet still open you have to close the wallet completelly and then replace the files and then open the wallet, then you wait for 10-20 minutes and your localwallet should be ready! ;P
-
yes i replaced them while the wallet was open i guess ill give it another shot ill close it then replace all 4 .db files once again i.e just copy and paste them over each other and start the wallet. ill try this now and get back to you thanks for you help buddy
-
@armz_j What version of the wallet are you using? There shouldn't be a .h2 DB, the current wallet uses the .mv file.
-
im not exactly sure where i got them files from tbh :s but i deleted everything in the .db folder and unzipped the .zip file again it gave me 2 files
burst.mv.db
burst.trace.dbive put them in the fodler now with the wallet completely closed and im going to try and run it again the version i got is burst 123.zip
-
@armz_j burst 123 is ancient - use https://github.com/burst-team/burstcoin/releases
-
so should i uninstall everything i already have?



