You are viewing a single comment's thread from:

RE: MySBDS - Steem Blockchain Data Service in MySQL

in #utopian-io • 7 years ago

Sorry you had to start over but I'm glad you're up and running again. The learning curve here is a little steep but I've ran into most of the problems you'll see so don't hesitate to follow up if you have any other issues.

7 years ago in #utopian-io by
$0.88
  • Past Payouts $0.88
  • - Author $0.66
  • - Curators $0.22
1 vote
Reply 22
Sort:  
  • Trending
    • [-]
     7 years ago 

    I'm running into an issue on my fresh install. The command "mysql -h 172.17.0.2 -u root -p" used to work for me during the download or restore phase, but now that I am in the "build/run sdbs" phase, that same mysql command produces the error, "ERROR 2003 (HY000): Can't connect to MySQL server on '172.17.0.2' (113)". I also tried connecting to the database remotely using the droplet IP (instead of 172.17.0.2), and I got a similar error except it mentioned (111) instead of (113). Do I just need to wait for the install script to finish or is there something else I need to do?

    $0.82
    • Past Payouts $0.82
    • - Author $0.61
    • - Curators $0.20
    1 vote
    Reply
    [-]
     7 years ago 

    Check docker to make sure mysql is running:

    docker ps

    If not, you can try starting it again:

    docker start steem_mysql

    And if you're still having troubles, you can take a look at logs:

    docker logs steem_mysql

    This assumes you used the name steem_mysql as specified in my script, change as necessary.

    $0.90
    • Past Payouts $0.90
    • - Author $0.68
    • - Curators $0.23
    1 vote
    Reply
    [-]
     7 years ago 

    Thanks for helping me with the basics of docker. The "docker ps" showed that steem_mysql wasn't running so I ran "docker start steem_mysql" and then I saw that it was running, but I still couldn't connect so I ran the "docker logs steem_mysql" command and noticed a bunch of recent messages about doing a recovery, but the recovery seemed to finish in about three minutes and after that everything seems to work as expected :)

    $0.83
    • Past Payouts $0.83
    • - Author $0.62
    • - Curators $0.21
    1 vote
    Reply
    [-]
     7 years ago 

    Awesome, glad you got it going!

    This all underscores how many 'grey areas' I left ambiguous in here, so I'm putting together a more thorough tutorial that'll go into docker and other details a bit more.

    $0.89
    • Past Payouts $0.89
    • - Author $0.67
    • - Curators $0.22
    1 vote
    Reply
    [-]
     7 years ago 

    Sorry to keep troubling you. I'm noticing that steem_mysql keeps stopping and gives the following type of error, "Aborted connection 5 to db: 'steem' user: 'root' host: '172.17.0.3' (Got an error reading communication packets)". I keep restarting steem_myslq (I've restarted at least 10 times and probably closer to 20 times) and it was stuck on the lastblock of 20080434 for a long time, and then I checked again and and the lastblock jumped to 20192434. Is having to restart steem_mysql this many times normal?

    $0.84
    • Past Payouts $0.84
    • - Author $0.64
    • - Curators $0.21
    1 vote
    Reply
    [-]
     7 years ago 

    No worries, it's good to document these issues in the blockchain so others can learn too!

    Interestingly, this is one issue I have not yet run into. For me, steem_mysql has been running flawlessly, it's the steem_sbds container that has stopped and had issues so far.

    My general thoughts are this may be system level issues. How much memory do you have? I've tested this in a 4GB instance and can say it definitely does NOT work with less, at least not reliably.

    Also, you mentioned installing other tools so these may also have an impact.

    Something to check is to dump all the logs to local files so you can parse and review more easily. Docker makes it a little weird, so use this technique:

    docker logs steem_mysql > mysql.log 2>&1
docker logs steem_sbds > sbds.log 2>&1
    $0.85
    • Past Payouts $0.85
    • - Author $0.65
    • - Curators $0.20
    1 vote
    Reply
    [-]
     7 years ago 

    I didn't install any other tools in this particular setup (I destroyed the server with the other tools), and I think I adhered very closely to the instructions you provided. I'm using the 16GB digitalocean server and 500GB volume that were recommended in the instructions, and I used the high memory script.

    $0.86
    • Past Payouts $0.86
    • - Author $0.65
    • - Curators $0.21
    1 vote
    Reply
    [-]
     7 years ago 

    Alright, with that deploy when you're doing the database restore, that does hammer mysql pretty hard so that's probably the main issue here.

    Again, check the docker logs to see if anything obvious pops out there. Beyond that, watch mysql to see what it's doing by running this command:

    mysqladmin -h 172.17.0.2 -u root -p processlist

    While the restore is running, you should see 'INSERT INTO...' in the process list for many hours.

    If mysql dies, you shouldn't need to start all the way over. Assuming that you still have all the .gz files in the dump/ folder you can run this:

    mysql_password="mystrongcomplexpassword"
volume_name="volume-tor1-01"
mysql_ip=`docker inspect --format "{{ .NetworkSettings.IPAddress }}" steem_mysql`
for i in /mnt/$volume_name/dump/*.gz ; do gunzip < $i | mysql -h $mysql_ip -p$mysql_password steem ; done

    Obviously, update the password and volume. This is just part of the script that calls the import.

    $0.87
    • Past Payouts $0.87
    • - Author $0.65
    • - Curators $0.21
    1 vote
    Reply
    Show 14 more replies

    Coin Marketplace

    STEEM 0.25
    TRX 0.20
    JST 0.035
    BTC 95037.22
    ETH 3446.03
    USDT 1.00
    SBD 3.46