Bricksync issues after newest release

Not sure if anyone else is having issues but lately if bricklink API goes down at all bricksync says it going to re-try but never actually connects. Happened today as well as after the 4 hour maintenance the other day. The only fix is to close and re-open bricksync.

Comments

  • 11 Comments sorted by Votes Date Added
  • I'm not seeing this issue and I am using an older version of BrickSync, so it might be that a bug was introduced in the latest version.
  • I have noticed this a few times as well. Seems to be ever since BL had that 4 or 5 hour down time for maintenance recently. At first I figured it might be because I had the older Bricksync so I updated it and restarted. It work ok after that, but I've since noticed it happen a few more times in the last week. It connects to BO ok, just gives an error for BL. A quick restart seems to sort it.
  • OK, I am going to ask for a registration code for the older version, I don't want to have to babysit this instance of bricksync. I fear now that it is free development may have come to an end by the original author due to a lack of time.
  • That is unexpected...

    When you say a previous version worked fine, was that 1.6.9 or 1.7.0? On Windows, between 1.6.9 and 1.7.0, I switched from a Posix threads library to native threads. There was very few changes with 1.7.1, besides updating the OpenSSL dependency and removing registration limitations.

    Feel free to throw more information so I can try to guess what's going on!
  • edited December 2019 Vote Up0Vote Down
    11-28
    05:55:25 WARNING: Failed to connect to server, trying again shortly...
    05:55:25 ERROR: Too many connection errors, giving up.
    05:57:22 INFO: Fetching the BrickOwl Order List...

    lots of similar errors, can connect to BO the whole time but not BL.

    16:18:43 INFO: Updating BrickLink inventory, 0 lots to create, 2 lots to update.
    16:18:43 WARNING: BrickLink update did not complete successfully!
    16:18:43 INFO: BrickLink flagged MUST_SYNC for deep synchronization.

    19:16:03 INFO: Fetching the BrickLink Order List...
    19:17:06 WARNING: Failed to connect to server, trying again shortly...
    19:17:06 ERROR: Too many connection errors, giving up.
    19:17:06 INFO: BrickLink is flagged MUST_SYNC for deep synchronization in 1737 seconds.

    Closed and reopened, connected right away. I can provide any logs needed.
    Issue not reported with 1.6.9 This was 1.7.1
  • I've experienced the same problems as well (it happened two times last week). I've recently switched from version 1.6.9 to 1.7.1 running it on an Ubuntu 16.04 LTS server.
  • Its bricklink not bricksync... Grrr

    11-19
    21:33:31 LOG: Resolved api.bricklink.com as 34.198.65.76
    21:33:31 LOG: Resolved www.bricklink.com as 52.54.219.19
    11-21
    18:01:26 LOG: Resolved api.bricklink.com as 3.209.39.225
    18:01:26 LOG: Resolved www.bricklink.com as 54.165.89.221
    11-28
    19:19:30 LOG: Resolved api.bricklink.com as 34.192.118.49
    19:19:30 LOG: Resolved www.bricklink.com as 3.232.178.46
  • Hmm, maybe not the issue, went back to 11-10 and that is different as well and I didn't have an issue.
  • Oh I see, so the IPs keep changing. And BrickSync resolves the IP addresses just once, when started, then remember them forever. That is the problem.

    I have seen requests for registration keys for previous versions, so here's the compiled win64 program to generate registration keys matching registration codes:
    http://www.bricksync.net/rsabscrypt.exe
    (It is and was included in the source package, with the asymmetric encryption key plainly visible)

    Once downloaded, it can be used from the command line/terminal (cmd.exe) as such:
    rsabscrypt.exe "0123456789abcdef0123456789abcdef"
    where "0123456789abcdef0123456789abcdef" would be the actual registration code (what appears when typing "register" in BrickSync). Running the program will print something like:

    registrationkey = "0894f044ce21cbf703c0bd54eb879c127a69621407cb1aeaecbf5ac685511
    9dbb9a826ef07bb0927465b6212cb2bdd079b2db9124da7998dd2f2c9c277d25ee8089c6380cbf26
    8d9dfb2fe3f6bb4f126434233c5fb5ba4bff492eabde1afd3b2ff36eabc78baca47e32822e2461a9
    d7bf91b890a5240c93221d06708eeb9f495";

    which can be copied to the BrickSync configuration file, the rest of the output isn't relevant (encryption sanity checks).

    I think copy/paste from a terminal isn't very convenient on Windows, so you can also do:
    rsabscrypt.exe "0123456789abcdef0123456789abcdef" > zzz.txt
    And the text output will be stored in the file zzz.txt

    For those on Linux/OSX, you can produce the "rsabscrypt" executable with these commands while in the directory of the unpacked source code:
    gcc -std=gnu99 -m64 cpuconf.c cpuinfo.c -O2 -s -o cpuconf
    ./cpuconf -h
    gcc rsabscrypt.c rsabn.c rand.c cc.c ccstr.c bn128.c bn192.c bn256.c bn512.c bn1024.c bnstdio.c -s -O2 -ffast-math -fomit-frame-pointer -msse -msse2 -msse3 -o rsabscrypt -lm -Wall
  • Thanks for that @Stragus! I've been wanting to move BrickSync to another server and this will come in handy (although I could also just get the newest version...).
Sign In or Register to comment.