Mongo still tries to connct to port 39001 while base port changed

Troubleshooting
1

Hi All,

I am trying to change the cyrosparc (4.4.1) base port for an existing installation but starting the master fails because it seems that mongo is still trying to connect to port 39001 (see below). I suppose the port is somehow written into the db. So is there a way to fix that?

Many thanks,

Oren

2024-05-29T12:15:09.593+0300 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/app/cryosparc_database/diagnostic.data'
2024-05-29T12:15:09.625+0300 I REPL     [initandlisten] Rollback ID is 1
2024-05-29T12:15:10.541+0300 I REPL     [initandlisten] No oplog entries to apply for recovery. appliedThrough and checkpointTimestamp are both null.
2024-05-29T12:15:10.541+0300 I CONTROL  [LogicalSessionCacheRefresh] Sessions collection is not set up; waiting until next sessions refresh interval: Replication has not yet been configured
2024-05-29T12:15:10.541+0300 I NETWORK  [initandlisten] listening via socket bound to 127.0.0.1
2024-05-29T12:15:10.542+0300 I NETWORK  [initandlisten] listening via socket bound to /tmp/mongodb-51868.sock
2024-05-29T12:15:10.542+0300 I NETWORK  [initandlisten] waiting for connections on port 51868
2024-05-29T12:15:10.542+0300 W NETWORK  [replexec-0] Failed to connect to 127.0.0.1:39001, in(checking socket for error after poll), reason: Connection refused
2024-05-29T12:15:10.542+0300 W REPL     [replexec-0] Locally stored replica set configuration does not have a valid entry for the current node; waiting for reconfig or remote heartbeat; Got "NodeNotFound: No host described in new configuration 1 for replica set meteor maps to this node" while validating { _id: "meteor", version: 1, protocolVersion: 1, members: [ { _id: 0, host: "localhost:39001", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: ObjectId('6638c67b0bd3c2b97ff1b579') } }
2024-05-29T12:15:10.542+0300 I REPL     [replexec-0] New replica set config in use: { _id: "meteor", version: 1, protocolVersion: 1, members: [ { _id: 0, host: "localhost:39001", arbiterOnly: false, buildIndexes: true, hidden: false, priority: 1.0, tags: {}, slaveDelay: 0, votes: 1 } ], settings: { chainingAllowed: true, heartbeatIntervalMillis: 2000, heartbeatTimeoutSecs: 10, electionTimeoutMillis: 10000, catchUpTimeoutMillis: -1, catchUpTakeoverDelayMillis: 30000, getLastErrorModes: {}, getLastErrorDefaults: { w: 1, wtimeout: 0 }, replicaSetId: ObjectId('6638c67b0bd3c2b97ff1b579') } }
2

Did you try
cryosparcm changeport ...?

3

crosparcm changeport and cyrosparcm fixdbport don’t seem to help. I get either the same error or connection error, depends on the sequence of actions

4

@orenshaniathuji Please can you

  1. Confirm that none of the ports in the new 10-port range are in use. If, for example, you wanted to define 61000 as your new CRYOSPARC_BASE_PORT, you could check with the command
    sudo ss -anp | grep 6100  | sed "s/\s\+/ /g"
  2. Post the output of the following command sequence:
    cryosparcm stop
ps -eo pid,ppid,command | grep -e cryosparc_ -e mongo
cryosparcm changeport 61000 # substitute actual new BASE_PORT