this post was submitted on 10 May 2024
26 points (88.2% liked)

Selfhosted

40329 readers
421 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
26
How to detect problems on computer? (lemmy.ml)
submitted 6 months ago by GravitySpoiled@lemmy.ml to c/selfhosted@lemmy.world
17 comments fedilink hide all child comments
 

My server (fedora) stops all podman containers after 2-3 hours since 3 days. I can start all containers again, and the same happens after a while. I do not know where to look for the problem.

In top, I found a oom message. I assume that the system runs out of memory and stops all services. How can I find the problem? I can’t find anything in the container logs.

I can see that systemctl status is always starting. It doesn’t become “running”. But I do not know how to proceed.

you are viewing a single comment's thread
view the rest of the comments
[–] neidu2@feddit.nl 11 points 6 months ago (1 children)

The issue with diagnosing memory issues is that it usually results in no memory available to handle the logging of such a problem when it happens.

I've found that the easieat approach is to set up a file as additional swap space, and swapon, then see if the problem disappears, either partially or fully.