Open reetp opened 10 months ago
reetp
commented
10 months ago As a follow up I just upgraded this docker instance to 6.5.1 Whilst I was about it I removed a deprecated smallFiles option from the mongod,.conf Restarted Mongo and then upgraded Rocket and it now works.
I have another instance I will test tomorrow.
broferek
commented
8 months ago FYI, I had the same issue in 6.5.3. Upgrading to 6.6.1 resolved it without making any modification to the Mongodb config on my side.
reetp
commented
8 months ago Upgrading to 6.6.x seems to have fixed it for me. Must be a related bug/PR but can't see it. Closing.
reetp
commented
6 months ago Ah no - back again on 6.6.6
{"level":35,"time":"2024-04-22T13:52:56.832Z","pid":1,"hostname":"myserver.mydomain.com","name":"API","method":"GET","url":"/api/info","userId":"gsadk424Rbw12546","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36","host":"chat.mydomain.com","referer":"https://chat.mydomain.com/admin/info","remoteIP":"1.2.3.4","status":200,"responseTime":10}
[2024-04-22T13:52:56.875Z] WARN ab400951-0dc3-46df-bb9c-537ac1a2f9c4/BROKER: Service '$node.list' is not available.
{"level":35,"time":"2024-04-22T13:52:56.876Z","pid":1,"hostname":"myserver.mydomain.com","name":"API","method":"GET","url":"/api/v1/instances.get","userId":"gsadk424Rbw12546","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36","host":"chat.mydomain.com","referer":"https://chat.mydomain.com/admin/info","remoteIP":"1.2.3.4","err":
{"type":"ServiceNotAvailableError","message":"Service '$node.list' is not available.","stack":"ServiceNotAvailableError: Service '$node.list' is not available.\n at ServiceBroker.findNextActionEndpoint (/app/bundle/programs/server/npm/node_modules/moleculer/src/service-broker.js:1156:13)\n at ServiceBroker.call (/app/bundle/programs/server/npm/node_modules/moleculer/src/service-broker.js:1197:26)\n at ee/server/local-services/instance/service.ts:215:22\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at app/api/server/v1/instances.ts:27:21\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40\n => awaited here:\n at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)\n at packages/meteor.js:367:22\n at Meteor.EnvironmentVariable.EVp.withValue (packages/meteor.js:1389:31)\n at app/api/server/api.ts:644:39\n at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40","code":404,"data":{"action":"$node.list"},"retryable":true},"status":400,"responseTime":3,"msg":"Service '$node.list' is not available."}
{"level":35,"time":"2024-04-22T13:52:56.906Z","pid":1,"hostname":"myserver.mydomain.com","name":"API","method":"GET","url":"/api/v1/statistics?refresh=false","userId":"gsadk424Rbw12546","userAgent":"Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/122.0.0.0 Safari/537.36","host":"chat.mydomain.com","referer":"https://chat.mydomain.com/admin/info","remoteIP":"1.2.3.4","status":200,"responseTime":11}
And still there on one 6.9.3 but not on another two with identical setups.
prdaneshi
commented
5 days ago same problem here on 6.13. what's the solution?
Description:
Since upgrading Mongo from v4 to v5 I am unable to access /admin/info Workspaces page as per the screenshot attached.
The following error is in the logs.
Steps to reproduce:
Upgrade to local Mongo 5 - (Mongo is not dockerised on this install) Stop/Start rocket docker VM Access Workspace Info page with any client
Expected behavior:
View the Workspace Info page
Actual behavior:
Page displays
"Error loading pages"
Server Setup Information:
Additional context
System upgraded with no issues with docker continuously following my own guide on the help pages ;-)
I am not sure whether this is Rocket/Node or possibly the reverse proxy not understanding a URL used to access the page?
How would you normally access '$node.list' ?