Feedback for no storage left on device #746

New Issue

2026-01-02T15:47:21Z

joe-irving commented

2026-01-02 15:47:21 +00:00

When trying to use Abra on a device with no storage remaining, the errors are quiet.

Not a big deal, but perhaps a more clear "you need to upgrade your VPS" warning would be helpful (especially when the abra admin might not get emails from the host).

This caught me out in my test VM!

When trying to use Abra on a device with no storage remaining, the errors are quiet. Not a big deal, but perhaps a more clear "you need to upgrade your VPS" warning would be helpful (especially when the abra admin might not get emails from the host). This caught me out in my test VM!

joe-irving added the enhancement label 2026-01-02 15:47:21 +00:00

decentral1se commented

2026-01-02 19:34:18 +00:00

@joe-irving can you provide some --debug logs or anything from your output so we can have a better idea of where abra is bailing out? What do you mean "quiet"? In general, abra is not a monitoring tool or can understand the specifics of the server it is being run on (you are running a VPS, others will be running other things, not to mention the differences in storage devices...), so I am not sure I would really see us being able to do anything about this.

@joe-irving can you provide some `--debug` logs or anything from your output so we can have a better idea of where `abra` is bailing out? What do you mean "quiet"? In general, `abra` is not a monitoring tool or can understand the specifics of the server it is being run on (you are running a VPS, others will be running other things, not to mention the differences in storage devices...), so I am not sure I would really see us being able to do anything about this.

joe-irving commented

2026-01-02 22:19:32 +00:00

Good point, on reflection I can probably close this

I just meant that in the docker logs in the server, you can see specific errors, in this case around the device being out of space, but as this came up when I was trying to upgrade an app on a local VM consequence was abra app upgrade or abra app deploy being stuck on "Preparing" in the debug output. I don't have a copy paste of the debug logs, and won't recreate because in writing this response I think this is unnecessary and people can be expected to manage their server

Good point, on reflection I can probably close this I just meant that in the docker logs in the server, you can see specific errors, in this case around the device being out of space, but as this came up when I was trying to upgrade an app on a local VM consequence was abra app upgrade or abra app deploy being stuck on "Preparing" in the debug output. I don't have a copy paste of the debug logs, and won't recreate because in writing this response I think this is unnecessary and people can be expected to manage their server

decentral1se commented

2026-01-03 14:23:05 +00:00

Yeh, I mean, I would like to do something on this but we tried years ago to widen the scope of abra to support this kind of stuff and it created a lot of hard problems. We eventually removed a lot of that code in favour of a plurality of practices that collectives are just doing already (monitoring, plain 'ol sysadmin, $other_tools, etc.). Thanks for weighing in!

Yeh, I mean, I would like to do something on this but we tried years ago to widen the scope of `abra` to support this kind of stuff and it created a lot of hard problems. We eventually removed a lot of that code in favour of a plurality of practices that collectives are just doing already (monitoring, plain 'ol sysadmin, $other_tools, etc.). Thanks for weighing in!

decentral1se closed this issue

2026-01-03 14:23:05 +00:00

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: toolshed/abra#746