@fbartels said in How do you handle (auto/manual) updating apps with confidence?:
@joseph said in How do you handle (auto/manual) updating apps with confidence?:
based on the update schedule
Which just to have it said, could be adjusted to install a new version every hour.
@joseph Yes, I understand why it must be "rolling updates", that's fine by me, it's not really the issue. The issue rather lies in the fact I wasn't fully aware of that, and how can I run many of those rolling updates quickly?
If I re-enable auto-update, how will it behave, assuming it's 10 versions behind the latest?
Will it do 1 update every day until it has caught up?
I discovered something new today with how Cloudron performs App updates.
I disabled the auto-update of my n8n server, because n8n is a very sensitive/critical piece in our system, and I didn't want to run into troubles with "automated regressions" caused by automated updates.
Naively, and without checking it, I thought that when I clicked on "Update" button, it would update to the latest version available.
But it doesn't! It only updates 1 version per 1 version.
I updated n8n two days ago to v1.53.1, and noticed today the regression (which was fixed in 1.53.2 and was able to update it to fix the regression.
And that's when I noticed those releases were quite old already! The latest version is 1.58.1.
But n8n will only allow me to update to 1.54.2:
And, considering each update creates a downtime of 2-4 minutes, I can't really chain manual updates like that. Even without downtime, it would take me too much time to manually chain updates to reach the latest stable version.
Also, I understand Cloudron performs a backup when doing an update, but I couldn't find any way to "rollback" to a previous version for instance. What if I run into an issue like what happened in 1.53.1 but there is no fix released to address it yet, what are my options then?
I certainly wish to handle my updates in a more reliable way:
1.53.1 on Sept 1st, and then 1.53.2 the next day, and 1.53.3 the next day again, then combined with "awaiting 2 weeks" rule, the auto updater should chain update 1.53.1, 1.53.2 and 1.53.3 at the same time, around Sept 15th.Those abilities combined together would feel much more reassuring from my point of view, I don't feel safe enabling auto-update on critical apps at this time, although I really don't want to manually update version one by one either, and wish to keep up-to-date, even if it's a bit delayed.
The Self-hosted AI Starter Kit is an open-source template that quickly sets up a local AI environment. Curated by n8n, it provides essential tools for creating secure, self-hosted AI workflows.
https://github.com/n8n-io/self-hosted-ai-starter-kit
I believe this could be very interesting to support. n8n is already supported, but this tool seems like a completely different tool, with more pieces.
Already supports Docker Compose, so it seems it could be possible to add it as a new Cloudron App.
I'd typically want to spawn a new server and start testing things without bothering with all the installation details.
Also, providing some tips about optimizing its performances (using "Nvidia GPU") would be very helpful when selecting the server to host this app. I believe Cloudron might have a few partnerships with Cloud providers to help us pick a good choice for improved performances out of the box.
Restarting the app didn't work.
There was an awaiting Ubuntu update, I restarted the whole server and n8n booted properly this time.
So, it seems to be related to Ubuntu update, which got stuck the whole startup process.
I'm not sure what can be done to avoid this kind of situation.
yes, it seems self-hostable.
https://github.com/netdata/netdata
https://www.reddit.com/r/netdata/comments/1cjo9za/self_hosting_netdata/
I'm not sure about the technical details, but I don't believe it processes the apps logs indeed.
It's more about monitoring of the system that is common for all computers.
Although I noted it does check individual processes, like one of my Cloudron App was relying on Postgres and it notified me when the RAM about that particular process was too high, which helped me increase it (for that process) before running out.
Apparently, my n8n app is down with "n8n is starting up. Please wait" since yesterday and I'm noticing it just now.
The issue seems to be related to an update. I restarted the app and now it's stuck at Starting migration AddConstraintToExecutionMetadata1720101653148 for 15mn without anything happening in the logs and web app is still down.
Is that a known issue?
Jul 18 23:01:44 box:docker pullImage: {"status":"Extracting","progressDetail":{"current":1372,"total":1372},"progress":"[==================================================>] 1.372kB/1.372kB","id":"3f0342ae64ba"}
Jul 18 23:01:44 box:docker pullImage: {"status":"Extracting","progressDetail":{"current":1372,"total":1372},"progress":"[==================================================>] 1.372kB/1.372kB","id":"3f0342ae64ba"}
Jul 18 23:01:44 box:docker pullImage: {"status":"Pull complete","progressDetail":{},"id":"3f0342ae64ba"}
Jul 18 23:01:44 box:docker pullImage: {"status":"Digest: sha256:b7f6e86bb634b0fc68c2020ec7760e3de437db744ac474a70137b16590a496a4"}
Jul 18 23:01:44 box:docker pullImage: {"status":"Status: Downloaded newer image for cloudron/io.n8n.cloudronapp:20240718-050754-90025e1e0"}
Jul 18 23:01:44 box:docker downloaded image cloudron/io.n8n.cloudronapp:20240718-050754-90025e1e0 . error: false
Jul 18 23:01:44 box:tasks update 1511: {"percent":35,"message":"Cleaning up old install"}
Jul 18 23:01:44 box:apptask deleteContainer: deleting app containers (app, scheduler)
Jul 18 23:01:44 box:shell removeLogrotateConfig /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurelogrotate.sh remove 693caa42-bcf9-44c2-8f44-78f8676fe44c
Jul 18 23:02:18 box:services teardownAddons: Tearing down []
Jul 18 23:02:18 box:tasks update 1511: {"percent":45,"message":"Downloading icon"}
Jul 18 23:02:18 box:apptask downloadIcon: Downloading icon of io.n8n.cloudronapp@3.41.0
Jul 18 23:02:19 box:tasks update 1511: {"percent":60,"message":"Updating addons"}
Jul 18 23:02:19 box:services setupAddons: Setting up ["localstorage","postgresql","sendmail"]
Jul 18 23:02:19 box:services setupAddons: setting up addon localstorage with options {}
Jul 18 23:02:19 box:services setupLocalStorage
Jul 18 23:02:19 box:shell createVolume /usr/bin/sudo -S /home/yellowtent/box/src/scripts/mkdirvolume.sh /home/yellowtent/appsdata/693caa42-bcf9-44c2-8f44-78f8676fe44c/data
Jul 18 23:02:19 box:services setupAddons: setting up addon postgresql with options {}
Jul 18 23:02:19 box:services Setting up postgresql
Jul 18 23:02:19 box:services Setting postgresql addon config to [{"name":"CLOUDRON_POSTGRESQL_URL","value":"postgres://user693caa42bcf944c28f4478f8676fe44c:e86932a5f7a3594662665ca9471e8369daecdaf0047796c38a928558e2678cd16a39086932e427b94f104606d5d9534487d9d9020683d8e13bd3f2280a3385f5@postgresql/db693caa42bcf944c28f4478f8676fe44c"},{"name":"CLOUDRON_POSTGRESQL_USERNAME","value":"user693caa42bcf944c28f4478f8676fe44c"},{"name":"CLOUDRON_POSTGRESQL_PASSWORD","value":"e86932a5f7a3594662665ca9471e8369daecdaf0047796c38a928558e2678cd16a39086932e427b94f104606d5d9534487d9d9020683d8e13bd3f2280a3385f5"},{"name":"CLOUDRON_POSTGRESQL_HOST","value":"postgresql"},{"name":"CLOUDRON_POSTGRESQL_PORT","value":"5432"},{"name":"CLOUDRON_POSTGRESQL_DATABASE","value":"db693caa42bcf944c28f4478f8676fe44c"}]
Jul 18 23:02:19 box:services setupAddons: setting up addon sendmail with options {"supportsDisplayName":true}
Jul 18 23:02:19 box:services Setting up SendMail
Jul 18 23:02:19 box:services Setting sendmail addon config to [{"name":"CLOUDRON_MAIL_SMTP_SERVER","value":"mail"},{"name":"CLOUDRON_MAIL_SMTP_PORT","value":"2525"},{"name":"CLOUDRON_MAIL_SMTPS_PORT","value":"2465"},{"name":"CLOUDRON_MAIL_STARTTLS_PORT","value":"2587"},{"name":"CLOUDRON_MAIL_SMTP_USERNAME","value":"n8n@unly.org"},{"name":"CLOUDRON_MAIL_SMTP_PASSWORD","value":"a36d29838cf0ff6943b73e69475aa61a6bfda56caff91d43"},{"name":"CLOUDRON_MAIL_FROM","value":"n8n@unly.org"},{"name":"CLOUDRON_MAIL_DOMAIN","value":"unly.org"},{"name":"CLOUDRON_MAIL_FROM_DISPLAY_NAME","value":"my.n8n.unly.org"}]
Jul 18 23:02:19 box:tasks update 1511: {"percent":70,"message":"Creating container"}
Jul 18 23:02:19 box:apptask createContainer: creating container
Jul 18 23:02:19 box:shell getSwaps execArgs: swapon ["--noheadings","--raw","--bytes","--show=type,size,used,name"]
Jul 18 23:02:57 box:shell addLogrotateConfig /usr/bin/sudo -S /home/yellowtent/box/src/scripts/configurelogrotate.sh add 693caa42-bcf9-44c2-8f44-78f8676fe44c /tmp/693caa42-bcf9-44c2-8f44-78f8676fe44c.logrotate
Jul 18 23:02:57 box:apptask startApp: starting container
Jul 18 23:02:59 box:tasks update 1511: {"percent":90,"message":"Configuring reverse proxy"}
Jul 18 23:02:59 box:tasks update 1511: {"percent":100,"message":"Done"}
Jul 18 23:02:59 box:tasks setCompleted - 1511: {"result":null,"error":null}
Jul 18 23:02:59 box:tasks update 1511: {"percent":100,"result":null,"error":null}
Jul 18 23:02:59 box:taskworker Task took 177.89 seconds
Jul 19 09:10:35 Stopping n8n... "{ file: 'start.js', function: 'stopProcess' }"
Jul 19 09:10:35 2024-07-19T07:10:35.205Z | info | Received SIGTERM. Shutting down... "{ file: 'BaseCommand.js' }"
Jul 19 09:10:35 2024-07-19T07:10:35.211Z | debug | Shutting down component "Queue.pause()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.212Z | info |
Jul 19 09:10:35 2024-07-19T07:10:35.214Z | error | Error: There was an error shutting down n8n. "{ file: 'LoggerProxy.js', function: 'exports.error' }"
Jul 19 09:10:35 2024-07-19T07:10:35.214Z | error | TypeError: Cannot read properties of undefined (reading 'removeAllQueuedWorkflowActivations') "{ file: 'LoggerProxy.js', function: 'exports.error' }"
Jul 19 09:10:35 2024-07-19T07:10:35.216Z | debug | Shutting down component "License.shutdown()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.216Z | debug | Shutting down component "Push.onShutdown()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.217Z | debug | Shutting down component "ActiveWorkflowManager.removeAllTriggerAndPollerBasedWorkflows()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.217Z | debug | Shutting down component "ExecutionRecoveryService.shutdown()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.218Z | debug | Removing all trigger- and poller-based workflows "{\n file: 'ActiveWorkflowManager.js',\n function: 'removeAllTriggerAndPollerBasedWorkflows'\n}"
Jul 19 09:10:35 2024-07-19T07:10:35.219Z | debug | Shutting down component "AbstractServer.onShutdown()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.219Z | debug | Shutting down component "PruningService.shutdown()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.221Z | debug | Shutting down component "RedisClientService.disconnectClients()" "{ file: 'Shutdown.service.js', function: 'shutdownComponent' }"
Jul 19 09:10:35 2024-07-19T07:10:35.221Z | debug | [Pruning] Removing soft-deletion and hard-deletion timers "{ file: 'pruning.service.js', function: 'stopPruning' }"
Jul 19 09:10:35 box:taskworker Starting task 1518. Logs are at /home/yellowtent/platformdata/logs/693caa42-bcf9-44c2-8f44-78f8676fe44c/apptask.log
Jul 19 09:10:35 box:apptask run: startTask installationState: pending_restart runState: running
Jul 19 09:10:35 box:tasks update 1518: {"percent":10,"message":"Starting app services"}
Jul 19 09:10:35 box:tasks update 1518: {"percent":20,"message":"Restarting container"}
Jul 19 09:10:38 => Ensure directories
Jul 19 09:10:38 => Loading configuration
Jul 19 09:10:38 => Setting permissions
Jul 19 09:10:38 box:tasks update 1518: {"percent":80,"message":"Configuring reverse proxy"}
Jul 19 09:10:38 box:shell providerMatches execArgs: openssl ["x509","-noout","-subject","-issuer"]
Jul 19 09:10:38 box:reverseproxy providerMatches: subject=CN = *.unly.org domain=*.unly.org issuer=C = US, O = Let's Encrypt, CN = E5 wildcard=true/true prod=true/true issuerMismatch=false wildcardMismatch=false match=true
Jul 19 09:10:38 box:shell getCertificateDates execArgs: openssl ["x509","-startdate","-enddate","-subject","-noout"]
Jul 19 09:10:38 box:reverseproxy expiryDate: subject=CN = *.unly.org notBefore=Jun 13 02:10:26 2024 GMT notAfter=Sep 11 02:10:25 2024 GMT daysLeft=53.791505925925925
Jul 19 09:10:38 box:reverseproxy ensureCertificate: n8n.unly.org acme cert exists and is up to date
Jul 19 09:10:38 box:reverseproxy needsRenewal: false. force: false
Jul 19 09:10:38 box:shell isOscpEnabled execArgs: openssl ["x509","-in","/home/yellowtent/platformdata/nginx/cert/_.unly.org.cert","-noout","-ocsp_uri"]
Jul 19 09:10:38 box:reverseproxy writeAppLocationNginxConfig: writing config for "n8n.unly.org" to /home/yellowtent/platformdata/nginx/applications/693caa42-bcf9-44c2-8f44-78f8676fe44c/n8n.unly.org.conf with options {"sourceDir":"/home/yellowtent/box","vhost":"n8n.unly.org","hasIPv6":true,"ip":"172.18.19.176","port":5678,"endpoint":"app","redirectTo":null,"certFilePath":"/home/yellowtent/platformdata/nginx/cert/_.unly.org.cert","keyFilePath":"/home/yellowtent/platformdata/nginx/cert/_.unly.org.key","robotsTxtQuoted":"\"User-agent: *\\nDisallow: /\"","cspQuoted":null,"hideHeaders":[],"proxyAuth":{"enabled":false,"id":"693caa42-bcf9-44c2-8f44-78f8676fe44c","location":"/"},"upstreamUri":"","ocsp":true,"hstsPreload":false}
Jul 19 09:10:38 box:shell reload /usr/bin/sudo -S /home/yellowtent/box/src/scripts/restartservice.sh nginx
Jul 19 09:10:39 => Installing cloudinary@2.2.0 node-fetch@3.1.1 form-data@4.0.0
Jul 19 09:10:39 box:tasks update 1518: {"percent":100,"message":"Done"}
Jul 19 09:10:39 box:taskworker Task took 4.249 seconds
Jul 19 09:10:39 box:tasks setCompleted - 1518: {"result":null,"error":null}
Jul 19 09:10:39 box:tasks update 1518: {"percent":100,"result":null,"error":null}
Jul 19 09:10:40 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.176:5678
Jul 19 09:10:50 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.176:5678
Jul 19 09:10:54 [..................] - idealTree:code: sill idealTree buildDeps [..................] \ idealTree:code: sill idealTree buildDeps [..................] \ idealTree:code: sill idealTree buildDeps [..................] \ idealTree:code: sill idealTree buildDeps [..................] \ idealTree:code: sill idealTree buildDeps [..................] \ idealTree:code: sill idealTree buildDeps [..................] | idealTree:code: sill idealTree buildDeps [..................] | idealTree:code: sill idealTree buildDeps [..................] - idealTree:code: sill idealTree buildDeps [..................] | idealTree:code: sill idealTree buildDeps [#########.........] \ idealTree: timing idealTree Completed in 4204ms [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] \ reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] - reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] / reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [#####
Jul 19 09:10:54 #############] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t [##################] | reify:@msgpackr-extract/msgpackr-extract-darwin-arm64: t <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - up to date, audited 1657 packages in 15s <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - 185 packages are looking for funding <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - run `npm fund` for details
Jul 19 09:10:54 <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - 19 vulnerabilities (9 moderate, 3 high, 7 critical) <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - To address issues that do not require attention, run: <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - npm audit fix <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - To address all issues (including breaking changes), run: <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - npm audit fix --force
Jul 19 09:10:54 <30>1 2024-07-19T07:10:54Z unly-n8n 693caa42-bcf9-44c2-8f44-78f8676fe44c 1050 693caa42-bcf9-44c2-8f44-78f8676fe44c - Run `npm audit` for details.
Jul 19 09:10:55 => Starting N8N
Jul 19 09:10:57 User settings loaded from: /app/data/user/.n8n/config
Jul 19 09:10:57 Loaded config overwrites from /app/data/configs/default.json
Jul 19 09:11:00 => Healtheck error: Error: connect ECONNREFUSED 172.18.19.176:5678
Jul 19 09:11:00 2024-07-19T07:11:00.894Z | info | Initializing n8n process "{ file: 'start.js', function: 'init' }"
Jul 19 09:11:01 2024-07-19T07:11:01.209Z | debug | Lazy Loading credentials and nodes from n8n-nodes-base "{\n credentials: 356,\n nodes: 455,\n file: 'LoggerProxy.js',\n function: 'exports.debug'\n}"
Jul 19 09:11:01 2024-07-19T07:11:01.231Z | debug | Lazy Loading credentials and nodes from @n8n/n8n-nodes-langchain "{\n credentials: 15,\n nodes: 75,\n file: 'LoggerProxy.js',\n function: 'exports.debug'\n}"
Jul 19 09:11:01 2024-07-19T07:11:01.514Z | debug | [Concurrency Control] Service disabled "{ file: 'concurrency-control.service.js', function: 'log' }"
Jul 19 09:11:01 2024-07-19T07:11:01.528Z | info | n8n ready on 0.0.0.0, port 5678 "{ file: 'AbstractServer.js', function: 'init' }"
Jul 19 09:11:01 2024-07-19T07:11:01.594Z | warn | Migrations in progress, please do NOT stop the process. "{ file: 'migrationHelpers.js', function: 'logMigrationStart' }"
Jul 19 09:11:01 2024-07-19T07:11:01.595Z | info | Starting migration AddConstraintToExecutionMetadata1720101653148 "{ file: 'migrationHelpers.js', function: 'logMigrationStart' }"
Here are the full logs:
https://gist.github.com/Vadorequest/7f879c614d8d6a4e40597bdad1c6b9bc
I ran into a similar issue today, here is my solution:
Note: I manually created a
n8n-uploadsfolder in my case.
In n8n, using the "Read/Write Files from Disk" action:
File Path and Name: /app/data/n8n-uploads/file.jpeg/app/data/file.jpeg works out of the box, but I wanted to store all my files in the same folder.
Here is a video:
https://www.loom.com/share/5e6bccdbd19842a489cc10f90ea871d4
Figured it out.
Note: I manually created a
n8n-uploadsfolder in my case.
In n8n, using the "Read/Write Files from Disk" action:
File Path and Name: /app/data/n8n-uploads/file.jpeg/app/data/file.jpeg works out of the box, but I wanted to store all my files in the same folder.
Here is a video:
https://www.loom.com/share/5e6bccdbd19842a489cc10f90ea871d4
@shrey Could you post the solution? I'm also stuck with it
Tried various things but none worked, and error messages are completely useless, logs, too.
Just for the sake of documenting, here is what I ended up with, in my .env.sh file:
# ------------- NODE MODULES ---------------------
# Allow node modules to be used in code node - https://docs.n8n.io/hosting/configuration/#use-built-in-and-external-modules-in-the-code-node
# Allows usage of all builtin modules
export NODE_FUNCTION_ALLOW_BUILTIN=*
# FYI This is a SPACE separated list
export EXTRA_NODE_MODULES="cloudinary@2.2.0 node-fetch@3.1.1"
# Allow usage of external npm modules
# Those modules are auto-installed by Cloudron upon app restart, see https://forum.cloudron.io/topic/11946/how-to-install-npm-packages-that-n8n-app-can-use/4?_=1719382777426
# FYI This is a COMMA separated list
export NODE_FUNCTION_ALLOW_EXTERNAL=cloudinary,node-fetch
I'm the CTO of a few companies and I haven't noticed anything wrong regarding security.
Sorry my phrasing made you believe otherwise.
I think something might be wrong with how Rallly has been setup then. The upstream is 500MB, the Cloudron's is 10Gb, 20 times more.
I don't recognize this behavior with other apps:
root@unly-misc:~# docker images --format "{{.Repository}}:{{.Tag}} {{.ID}} {{.Size}}"
cloudron/com.metabase.cloudronapp:20240628-191401-64473d75c 702ac40462e0 2.79GB
cloudron/co.rallly.cloudronapp:20240620-132420-727aea519 6724902697a3 10.2GB
cloudron/io.changedetection.cloudronapp:20240617-125108-019d2ff03 b23079c56084 3.92GB
cloudron/tech.ittools.cloudron:20240515-092352-014c36070 3fccf9f15005 2.22GB
registry.docker.com/cloudron/postgresql:5.2.1 333f887a27f7 2.75GB
registry.docker.com/cloudron/sftp:3.8.6 b735f2120189 2.23GB
registry.docker.com/cloudron/mail:3.12.1 ea18fc4dd1c7 2.96GB
registry.docker.com/cloudron/mongodb:6.0.0 4b95d24318a2 2.69GB
registry.docker.com/cloudron/graphite:3.4.3 dbd026164ada 2.28GB
cloudron/it.kutt.cloudronapp:20231017-142419-29446a137 847c1860e3df 2.94GB
registry.docker.com/cloudron/redis:3.5.2 80e7a4079e6b 2.22GB
registry.docker.com/cloudron/mysql:3.4.2 c7085a52532b 2.53GB
registry.docker.com/cloudron/turn:1.7.2 152b1fb9690e 2.22GB
registry.docker.com/cloudron/base:4.2.0 6ec7c1ab3983 2.21GB
Other apps are 2-4GB.
Also, in my case, the issue happened while updating Rallly.
I looked for the size of the Docker Image, and it's about 500mb
root@unly-misc:~# curl -s https://hub.docker.com/v2/repositories/lukevella/rallly/tags/latest/ | jq '.full_size'
510832205
So, I fail to understand why it's failing the update with 8Gb of disk space left.
Edit: Looking at the Docker images directly, the file is 10.2GB.
That's odd it weights so much, it's hard to explain.
root@unly-misc:~# docker images --format "{{.Repository}}:{{.Tag}} {{.ID}} {{.Size}}"
cloudron/co.rallly.cloudronapp:20240620-132420-727aea519 6724902697a3 10.2GB
...
I just ran into a similar issue as this one, when the app Rallly tried to update today.
My server has about 8GB space left, but that's apparently not enough to run the update.
The main issue isn't so much the update failing, Cloudron can't do much about that.
The issue is rather that Cloudron is trying to perform the update daily, despite the fact it failed yesterday already, due to the same issue (not enough disk space on device).
But, when if failed yesterday, I didn't have monitoring on the server, and I noticed the app "Rallly" was broken, but I didn't understand why. Now, I understand it tried to update yesterday, and failed, and did so again today.
Now that I understand the issue better (thanks to my Netdata monitoring), I wonder about:
I know I can stop automated updates for this app, but that's a manual solution, I think Cloudron could help us by avoiding running into this kind of issue (which might tear down other apps in the process).
@girish said in Guide: How to add monitoring to your Cloudron server for free (RAM/Disk/etc.), using Netdata (5mn setup):
@AmbroiseUnly What's your GitLab id? We have to bump the repo limit on our side and then you should be able to fork.
5263
Thanks
Well, https://contributing.md/how-to-build-contributing-md/ is a good starting point.
I tried to fork, but to be frank the process is super annoying... Here is what I did:
And I believe I'll also need to setup SSH to be able to write/push.
This isn't contributor-friendly, the root issue is the fact we can't simply use our existing GitLab/GitHub account to contribute. Forking isn't possible without an account (and I guess cloning neither)
But all of that isn't really related to this topic, maybe it should be moved onto a new post?
@necrevistonnezr said in Guide: How to add monitoring to your Cloudron server for free (RAM/Disk/etc.), using Netdata (5mn setup):
This should go to https://docs.cloudron.io/guides/community/ - you can create a PR yourself!
Great suggestion, I'll do that now!
I looked at https://git.cloudron.io/cloudron/docs, and it doesn't provide a "Contributing" section or Contributing.md about how to provide a contribution.
It would help external contributors to get started autonomously while ensuring we're following the expected procedure. Right now, I'm a bit at a loss with how to contribute. Do I need to create an account? Should I just clone (or fork?) and just create a branch? I don't see where Pull Requests are located.
Plenty of questions that could be addressed with a short guide 
For anyone interested in configuring proper monitoring on your Cloudron server, I wrote a guide about it, and I hope you'll find it useful! 
It's the kind of guide I wish I would have found when first looking at this topic.