sync-demo | Sync Demo | Data Processing library

I am trying to install mongodb on my Ubuntu 18.04 LTS, but it has the following error saying

You might want to run 'apt --fix-broken install' to correct these. The following packages have unmet dependencies: mongodb-org : Depends: mongodb-org-server but it is not going to be installed Depends: mongodb-org-mongos but it is not going to be installed Depends: mongodb-org-tools but it is not going to be installed E: Unmet dependencies. Try 'apt --fix-broken install' with no packages (or specify a solution). umar@umar-Lenovo-ideapad-320-15ISK:~/Desktop/portfolio/async-demo$ sudo apt-get install -y mongodb

I beleieve the reason behind this is already mentioned on their website, clearly saying

PLATFORM SUPPORT

MongoDB only provides packages for 64-bit LTS (long-term support) Ubuntu releases; for example, 14.04 LTS (trusty) and 16.04 LTS (xenial). See Supported Platforms for more information.

These packages may work with other Ubuntu releases; however, they are not supported.

So how can I install mongodb on my latest Ubuntu 18.04 LTS? For sake of clarity, I am listing the things I did to correct the errors: I followed their official website to install mongodb

(x-post from SymmetricDS forum)

Do you have a working example of using SymmetricDS 3.8 to sync an Android application with a demo root node? I've worked through both of JumpMind's examples, and both fail with ECONNREFUSED against localhost:31415.

It looks like even though they know how to register with the root node on a different machine, they try to sync with it on localhost instead.

Here's a walkthrough of how to build and (unsuccessfully) run both of the existing samples.

Sample 1:

Jumpmind's original demo from 2012 used the Notepad Application, and many of the steps assume you're running in Eclipse and have their Pro version. There are a few hoops to make it compile in a modern Android Studio with the freeware version of SymmetricDS.

• in Studio, New Project -> Import from Android/Sdk/samples/android-23/legacy/NotePad
• do a test compile and run to make sure it works unmodified
• download and extract sample 2 to get the libs
• extract the libs into Notepad/app/libs/

• edit your apps gradle rule, add a compile dependency, thus:

  dependencies { compile fileTree(dir: 'libs', include: '*.jar') }

• gradle sync
• paste the recommended code from the tutorial into the second OnCreate in NotePadProvider.java.(the first one is in a static class DatabaseHelper)
• modify REGISTRATION_URL to point to your root node
• modify NODE_GROUP_ID appropriately. If you're using the demo server, this should be "store".
• I used an external ID of "android-003", because that's what's used in sample #2.

• Don't forget to open registration for your external ID. Something like

  symadmin --properties corp-000.properties open-registration store android-003

• observe the logcat failure

  Building transport url: http://localhost:31415/sync/corp-000/push?nodeId=android-003&securityToken=88b79dcc9617099aec015ae5ed800b&hostName=localhost&ipAddress=10.0.2.15 Could not communicate with node 'corp:000:000' at http://localhost:31415/sync/corp-000 because of unexpected error org.jumpmind.exception.IoException: java.net.ConnectException: failed to connect to localhost/127.0.0.1 (port 31415) after 20000ms: isConnected failed: ECONNREFUSED

Sample 2:

Jumpmind's newer sample includes support for file sync, which I don't care about right now. But it's supposed to work against the demo node corp-000 right out of the box. At least for me, it doesn't.

Here's what you have to do:

• download the source
• modify REGISTRATION_URL (to use the dev machine's non-localhost IP address)
• modify the manifest as described in the tutorial
• attempting to run the app will fail with INSTALL_FAILED_CONFLICTING_PROVIDER, I had to change the provider defined in the manifest to com.jumpmind.syncds3.DbProvider, because there's already an app on the default Android image that uses provider com.google.provider.NotePad.
• open registration for android-003 on the server / root-node
• confirm registration by looking in the server's sym_node_security table.
• Interestingly, there is no initial_load_time in that row, and it shows no sign of syncing.
• Back in your Android app, observe the same logcat errors attempting to sync against a corp-000 node on localhost.