Crash when updating to v4.61.0
-
@girish actually trying
sudo swapoff /apps.swap
seems to have worked and I cansudo rm /apps.swap
now. 4gb freeAs an aside, if I
truncate -s 1G /apps.swap
and then eithersudo swapon -a
orsudo swapon /apps.swap
I get this error:swapon: /apps.swap: swapon failed: Invalid argument
I guess will leave it off for now, but maybe at some point I would try to turn it on.
-
@girish Okay still getting this error with 4.67 GB free:
Oct 11 09:31:57box:docker pullImage: {"errorDetail":{"message":"failed to register layer: Error processing tar file(exit status 1): open /home/cloudron/ghost/versions/5.61.1/node_modules/express-hbs/test/apps/async/index.js: no space left on device"},"error":"failed to register layer: Error processing tar file(exit status 1): open /home/cloudron/ghost/versions/5.61.1/node_modules/express-hbs/test/apps/async/index.js: no space left on device"} Oct 11 09:31:57box:docker pullImage error cloudron/org.ghost.cloudronapp2:20230904-084557-30794834d: failed to register layer: Error processing tar file(exit status 1): open /home/cloudron/ghost/versions/5.61.1/node_modules/express-hbs/test/apps/async/index.js: no space left on device Oct 11 09:31:57box:docker downloaded image cloudron/org.ghost.cloudronapp2:20230904-084557-30794834d . error: true layerError.includes is not a function at IncomingMessage.<anonymous> (/home/yellowtent/box/src/docker.js:138:44) at IncomingMessage.emit (node:events:525:35) at IncomingMessage.emit (node:domain:489:12) at endReadableNT (node:internal/streams/readable:1359:12) at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Seems like the same issue as the other thread I referenced, but not sure what else I can do to reduce space if that's the issue. Any ideas?
-
-
If you run just
swapon
, it will say the swap devices also. But really, trying to shave off 2-3GB here and there is just going to error somewhere else (or sometime later), I think. -
@girish said in Crash when updating to v4.61.0:
@rosano can you can try
docker pull cloudron/org.ghost.cloudronapp2:20230904-084557-30794834d
directly.Still a space issue:
failed to register layer: Error processing tar file(exit status 1): open /home/cloudron/ghost/versions/5.61.1/node_modules/node-gyp/gyp/pylib/gyp/common_test.py: no space left on device
Turns out swap comes back after rebooting, so I deleted it again but still get the same issue.
Is your server so short of space? How much is remaining?
According to
df -h
5-6 GB after deleting swap?:/dev/sda1 38G 30G 5.8G 84% /
It surprises me more than this would be necessary for Ghost. I wonder what's going on.
-
-
Ran
docker volume prune
to reclaim 1.3 GB. Was able to successfully pull directly with 7.7 GB free. I randocker image prune -a
to remove that pull and was able to install via the Cloudron panel.Will comment out the swap but hopefully there isn't some other issue as it's odd to need so much space in order to update ghost.
-
-
Sorry to extend this thread, just noticing that the swap seems to return after rebooting even though
/apps.swap none swap sw 0 0
is commented out in/etc/fstab
. This blocks other attemps when Ghost updates… For now I'll just delete swap it occurs, but if there's another step please share. -
-
-