Syracuse Installation Fail

SOLVED

Attempting to install V7 on a VM.  When I get to install Syracuse with the key I got from Partner Services and I get the following output from the zpack installer window:

Task: Create new certificate and private key
Generate key pair ...
Generate certificate ...
Write private key private/ca.cakey ...
Write certificate output/ca.cacrt ...
Finished
1 file(s) copied.

loading database ...
Streamline config from version.json
Need a license to start. Error: Cannot find module 'syracuse-main/lib/syracuse'
starting syracuse ...
Service start ...
generating server certificate ...
Read certificate output/ca.cacrt

Task: Create new certificate and private key
Read private key private/ca.cakey ...
Generate key pair ...
Generate certificate ...
Write private key output/rubicon.key ...
Write certificate output/rubicon.crt ...
Write public key output/rubicon.pem ...
Transfer data to rubicon:8124 ...
Try to connect to server ...

I then attempt to manually start Syracuse using the 'manual-start.cmd' command, which returns this:

Streamline from version file
Server name RUBICON
Error: collection already exists MongoError: collection already exists
at toError (C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\utils.js:110:11)
at C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\utils.js:157:55
at C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\db.js:1809:9
at Server.Base._callHandler (C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\base.js:404:41)
at C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\server.js:485:18
at MongoReply.parseBody (C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\responses\mongo_reply.js:68:5)
at null.<anonymous> (C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\server.js:443:20)
at EventEmitter.emit (events.js:95:17)
at null.<anonymous> (C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\connection_pool.js:191:13)
at EventEmitter.emit (events.js:98:17)
at Socket.<anonymous> (C:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\connection.js:399:22)
at Socket.EventEmitter.emit (events.js:95:17)
at Socket.<anonymous> (_stream_readable.js:746:14)
at Socket.EventEmitter.emit (events.js:92:17)
at emitReadable_ (_stream_readable.js:408:10)
at emitReadable (_stream_readable.js:404:5)
at readableAddChunk (_stream_readable.js:165:9)
at Socket.Readable.push (_stream_readable.js:127:10)
at TCP.onread (net.js:526:21)
at makeError (C:\Sage\Syracuse\syracuse\bin\node_modules\streamline\lib\fibers-fast\runtime.js:176:9)
at Object.invoke (C:\Sage\Syracuse\syracuse\bin\node_modules\streamline\lib\fibers-fast\runtime.js:127:9)
at Db.fstreamline__.create.dbProto.createCollection (C:\Sage\Syracuse\syracuse\bin\node_modules\streamline-mongodb\index._js:68:58)
at Object.fstreamline__.create.exports.createCollection (C:\Sage\Syracuse\syracuse\bin\node_modules\syracuse-load\lib\dbDriver.js:45:12)
at start (C:\Sage\Syracuse\syracuse\bin\node_modules\syracuse-load\lib\balancer.js:439:34)

This suggests to me that Syracuse is accessing MongoDB, but it's colliding with some existing collection.

So to be sure, I go back a drop the syracuse db in mongodb and restart the installation process.

> show dbs
local 0.000GB
syracuse 0.000GB
> use syracuse
switched to db syracuse
> db.dropDatabase()
{ "dropped" : "syracuse", "ok" : 1 }
> show dbs
local 0.000GB
>

Same results every time.

Perhaps might there be something wrong with my license file?

 

 

Parents
  • 0

    Okay, tried this on another VM today.

    I no longer get the "Need a license to start. Error: Cannot find module 'syracuse-main/lib/syracuse'" but I still end up with the same result.  

    Attempts to run the 'manual-start.cmd' result in the usual MongoDB error.  Syracuse logs, event viewer, etc show nothing of interest.  

    Here's the installer output FWIW:

    Prepare folders ...
    Grant rights on bin directory ...
    Successfully processed 9685 files; Failed processing 0 files
    Create rel directory ...
    8544 File(s) copied
    Create temp directory ...
    8544 File(s) copied
    1 dir(s) moved.
    Grant rights on temp directory ...
    Successfully processed 9685 files; Failed processing 0 files
    Creating logpath and certificate directory ...
    Successfully processed 1 files; Failed processing 0 files
    Successfully processed 2 files; Failed processing 0 files
    D:\Sage\Syracuse\syracuse\bin\cert_gen\.checksums
    D:\Sage\Syracuse\syracuse\bin\cert_gen\bcpkix-jdk15on-150.jar
    D:\Sage\Syracuse\syracuse\bin\cert_gen\bcprov-jdk15on-150.jar
    D:\Sage\Syracuse\syracuse\bin\cert_gen\BouncyCastle_License
    D:\Sage\Syracuse\syracuse\bin\cert_gen\certgen.bat
    D:\Sage\Syracuse\syracuse\bin\cert_gen\certgen.jar
    6 file(s) copied.
    1 file(s) copied.
    Copy agent files ...
    1 file(s) copied.
    1 file(s) copied.
    Successfully processed 1 files; Failed processing 0 files
    Syracuse inits ...
    Streamline from version file
    Server name WIN-OT28OTUNRA3
    Host inserted WIN-OT28OTUNRA3
    Service creation ...
    D:\Sage\Syracuse\syracuse\bin\cert_gen\.checksums
    D:\Sage\Syracuse\syracuse\bin\cert_gen\bcpkix-jdk15on-150.jar
    D:\Sage\Syracuse\syracuse\bin\cert_gen\bcprov-jdk15on-150.jar
    D:\Sage\Syracuse\syracuse\bin\cert_gen\BouncyCastle_License
    D:\Sage\Syracuse\syracuse\bin\cert_gen\certgen.bat
    D:\Sage\Syracuse\syracuse\bin\cert_gen\certgen.jar
    6 file(s) copied.

    Task: Create new certificate and private key
    Generate key pair ...
    Generate certificate ...
    Write private key private/ca.cakey ...
    Write certificate output/ca.cacrt ...
    Finished
    1 file(s) copied.

    loading database ...
    Streamline config from version.json
    starting syracuse ...
    Service start ...
    generating server certificate ...
    Read certificate output/ca.cacrt

    Task: Create new certificate and private key
    Read private key private/ca.cakey ...
    Generate key pair ...
    Generate certificate ...
    Write private key output/win-ot28otunra3.key ...
    Write certificate output/win-ot28otunra3.crt ...
    Write public key output/win-ot28otunra3.pem ...
    Transfer data to win-ot28otunra3:8124 ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Try to connect to server ...
    Cannot connect to server: java.net.ConnectException: Connection refused: connect

    and of course the sage_syracuse_-_node0-stdout.2016-10-21. This entry happens every 20 seconds or so:

    2016-10-22 12:21:40 Commons Daemon procrun stdout initialized
    Streamline from version file
    Server name WIN-OT28OTUNRA3
    Error: collection already exists MongoError: collection already exists
    at toError (D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\utils.js:110:11)
    at D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\utils.js:157:55
    at D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\db.js:1809:9
    at Server.Base._callHandler (D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\base.js:404:41)
    at D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\server.js:485:18
    at MongoReply.parseBody (D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\responses\mongo_reply.js:68:5)
    at null.<anonymous> (D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\server.js:443:20)
    at EventEmitter.emit (events.js:95:17)
    at null.<anonymous> (D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\connection_pool.js:191:13)
    at EventEmitter.emit (events.js:98:17)
    at Socket.<anonymous> (D:\Sage\Syracuse\syracuse\bin\node_modules\mongodb\node-mongodb-native\lib\mongodb\connection\connection.js:399:22)
    at Socket.EventEmitter.emit (events.js:95:17)
    at Socket.<anonymous> (_stream_readable.js:746:14)
    at Socket.EventEmitter.emit (events.js:92:17)
    at emitReadable_ (_stream_readable.js:408:10)
    at emitReadable (_stream_readable.js:404:5)
    at readableAddChunk (_stream_readable.js:165:9)
    at Socket.Readable.push (_stream_readable.js:127:10)
    at TCP.onread (net.js:526:21)
    at makeError (D:\Sage\Syracuse\syracuse\bin\node_modules\streamline\lib\fibers-fast\runtime.js:176:9)
    at Object.invoke (D:\Sage\Syracuse\syracuse\bin\node_modules\streamline\lib\fibers-fast\runtime.js:127:9)
    at Db.fstreamline__.create.dbProto.createCollection (D:\Sage\Syracuse\syracuse\bin\node_modules\streamline-mongodb\index._js:68:58)
    at Object.fstreamline__.create.exports.createCollection (D:\Sage\Syracuse\syracuse\bin\node_modules\syracuse-load\lib\dbDriver.js:45:12)
    at start (D:\Sage\Syracuse\syracuse\bin\node_modules\syracuse-load\lib\balancer.js:439:34)

    Still hammering.

  • 0 in reply to David Canatsey
    A not so technical answer.

    nowadays I'm mostly working on PU9. but whenever I go back to work on (the frustrating) V7 and I have to install it, I would face this problem at first if I have not used the correct MongoDB version or if i installed it using the msi installer.

    What I usually do, is that I copy over the mongodb files from Sage's FTP server, install it and test it. after that syracuse installation usually goes fine.

    I don't know if this helps, but I hope it does.

    Mahmoud
  • 0 in reply to Mahmoud UBA
    Hi Mahmoud,
    Thanks for the reply. This is a new installation of Syracuse, MongoDB is therefore being created. I will post the solution on this forum.

    Regards,
    Renier
  • 0 in reply to Renier
    Hi All,
    This did not turn out so great for us, and we are left speculating on the cause for this. Tried Bob's escalated user privileges running and executing all the *.jar installations in a Admin Command prompt, yielding the same result.

    Should I come across this type of case again and a solution, I will post it in this forum.

    Thanks for the advice provided by everyone on this chat.

    Regards,
    Renier
  • 0 in reply to Renier
    verified answer

    Thanks everyone...I finally figured it out!

    Since all errors pointed towards MongoDB, I decided to uninstall it (latest version) and go back to the earliest version of MongoDB that was released after the V7 Syracuse installer jar was created (6/12/2014).

    After a handful of installs, I found one that starts up (2.7.4).

    Then I uninstalled Syracuse and reinstalled it and bingo!

    It turns out that X3 v7 wasn’t liking the latest version of MongoDB.  So now I have an http listener on port 8124 that works!

  • 0 in reply to David Canatsey
    Thank you David,
    For PU9 this does not resolve the issue, this is a fresh install of MongoDB 3.0.2 Enterprise. Also remove all the registry keys for all the Syracuse components including MongoDB.

    Glad to hear there is a work around for V7 though.
Reply Children