Welcome, Guest Login

Support Center

"Could not connect to service" Error When Attempting to log into Momentum 4 Web UI

Last Updated: Jun 14, 2016 03:32PM EDT
"Could not connect to service" error when attempting to log into Momentum 4 web UI

When you attempt log into the Momentum 4 Web UI and that error is pops up, go back and check your install????????.log file (located in the directory from which you installed the Momentum bundle). There may be a few of these errors listed:

ERROR creating user: Unexpected error.
{ name: 'PoolConnectionError', 
info: 'Represents a error while trying to connect the pool, all the connections failed.', 
[ { name: 'ResponseError', 
message: 'Keyspace \'authentication\' does not exist',  info: 'Represents a error message from the server', 
code: 8704, 
isServerUnhealthy: false }, 
{ name: 'ResponseError', 
message: 'Keyspace \'authentication\' does not exist',  info: 'Represents a error message from the server',  code: 8704,  

stack: 'undefined\n (event loop)\n at Client.executeAsPrepared (/opt/msys/app/users-api/node_modules/node-cassandra-cql/index.js:242:9)\n at Object.model.checkUserExists (/opt/msys/app/users-api/resources/model.js:486:10)\n at Object.<anonymous> (/opt/msys/app/users-api/etc/add_user.js:40:7)\n at Module._compile (module.js:456:26)\n at Object.Module._extensions..js (module.js:474:10)\n at Module.load (module.js:356:32)\n at Function.Module._load (module.js:312:12)\n at Function.Module.runMain (module.js:497:10)\n at startup (node.js:119:16)\n at node.js:902:3',
query: 'SELECT * FROM users WHERE username = ?' }
These errors indicate that the installer was unable to fully create the schema within the Cassandra data store. Here is the portion of the installer script that failed to execute:

qx|/etc/init.d/msys-cassandra start|;
my $keyspace = $selections->{'cluster'}
? 'load_cluster_keyspace.cql'
: 'load_singlenode_keyspace.cql';
qx|cd $etcdir/cql ; $thirdparty/bin/cqlsh $ipaddress -f $keyspace|;
qx|cd $appdir/users-api/cql; $thirdparty/bin/cqlsh $ipaddress -f $keyspace
qx|cd $appdir/webhooks-api/cql; $thirdparty/bin/cqlsh $ipaddress -f $keysp
qx|/etc/init.d/msys-cassandra stop|;

If you are running in a cluster, you'll want to select the load_cluster_keyspace.cql keyspace, and if you are running a single node, you'll want to select the load_singlenode_keyspace.cql keyspace. Both keyspaces are located in /opt/msys/ecelerity/etc/cql/. Here is an example of actual commands to run in the command line:

/etc/init.d/msys-cassandra start cd /opt/msys/ecelerity/etc/cql /opt/msys/3rdParty/bin/cqlsh <IP.of.first.Cassandra.node> -f /opt/msys/ecelerity/etc/cql/load_cluster_keyspace.cql cd /opt/msys/app/users-api/cql /opt/msys/3rdParty/bin/cqlsh <IP.of.first.Cassandra.node> -f /opt/msys/ecelerity/etc/cql/load_cluster_keyspace.cql cd /opt/msys/app/webhooks-api/cql /opt/msys/3rdParty/bin/cqlsh <IP.of.first.Cassandra.node> -f /opt/msys/ecelerity/etc/cql/load_cluster_keyspace.cql
/etc/init.d/msys-cassandra stop

/etc/init.d/msys-cassandra start

That should recreate the schema, and you should be able to log in afterwards.
seconds ago
a minute ago
minutes ago
an hour ago
hours ago
a day ago
days ago
Invalid characters found