Cloudron did a restart or crashed

[warg]

Hello,

I was just logged in to Cloudron and tried to open some view and then it took like > 10 seconds and nothing happened. Several refreshes didn't help. Then the connection to the backend was lost and it looks like Cloudron just did a restart. How do I find out what happened?

Event log shows this:

/logs.html?id=box shows nothing suspicious.

So how do I find out what happened?

Best Regards,

[girish]

I think it just updated to Cloudron 7.4.2 (that's what the eventlog is trying to say). I guess it should have said "Cloudron updated to version 7.4.2"

[warg]

Nope, that didn't happen: I updated to v7.4.2 yesterday manually (after I got some notification).

[girish]

@warg You can check the logs at /home/yellowtent/platformdata/logs/box.log . Maybe it did crash!

[warg]

Ah, I thought the logs just keep some specific amount of entries (thought the Log Viewer shows all but it just shows a limited amout ...). Yes, looks like a technical issue:

[...]
2023-05-05T16:21:50.114Z box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
ServerError [ServiceUnavailableError]: Response timeout
    at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8)
    at IncomingMessage.emit (node:events:513:28)
    at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ETIMEDOUT',
  timeout: 20000
}
Box GET /api/v1/cloudron/status 500 Internal Server Error Response timeout 20003.519 ms - 72
ServerError [ServiceUnavailableError]: Response timeout
    at IncomingMessage.<anonymous> (/home/yellowtent/box/node_modules/connect-timeout/index.js:84:8)
    at IncomingMessage.emit (node:events:513:28)
    at Timeout._onTimeout (/home/yellowtent/box/node_modules/connect-timeout/index.js:49:11)
    at listOnTimeout (node:internal/timers:559:17)
    at processTimers (node:internal/timers:502:7) {
  code: 'ETIMEDOUT',
  timeout: 20000
}
Box GET /api/v1/cloudron/avatar?910448935665957 500 Internal Server Error Response timeout 20000.737 ms - 72
2023-05-05T16:22:42.389Z box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
2023-05-05T16:22:42.391Z box:apphealthmonitor app health: 2 running / 0 stopped / 0 unresponsive
Error [ERR_HTTP_HEADERS_SENT]: Cannot set headers after they are sent to the client
    at new NodeError (node:internal/errors:387:5)
    at ServerResponse.setHeader (node:_http_outgoing:644:11)
    at ServerResponse.header (/home/yellowtent/box/node_modules/express/lib/response.js:794:10)
    at getCloudronAvatar (/home/yellowtent/box/src/routes/branding.js:103:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
2023-05-05T16:22:58.629Z box:server ==========================================
2023-05-05T16:22:58.630Z box:server            Cloudron 7.4.2
2023-05-05T16:22:58.630Z box:server ==========================================
[...]

[girish]

@warg Yes, that crash happens when the server becomes unresponsive . So, the code restarts itself. If it happens often, it's something to investigate. But the root cause can be network or VM related.