Selfhosted

38832 readers

153 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:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
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.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Proxmox VM's hanging when one has issues (lemmy.world)

submitted 10 months ago by root@lemmy.world to c/selfhosted@lemmy.world

19 comments fedilink hide all child comments

I've noticed that sometimes when a particular VM/ service is having issues, they all seem to hang. For example, I have a VM hosting my DNS (pihole) and another hosting my media server (jellyfin). If Jellyfin crashes for some reason, my internet in the entire house also goes down because it seems DNS is unable to be reached for a minute or so while the Jellyfin VM recovers.

Is this expected, and is there a way to prevent it?

you are viewing a single comment's thread
view the rest of the comments

[–] apigban@lemmy.dbzer0.com 4 points 10 months ago* (last edited 10 months ago) (5 children)

I'd check high I/O wait, specially if your all of the vms are on HDDs.

one of the solution I had for this issue was to have multiple DNS servers. solved it by buying a raspberry pi zero w and running a 2nd small instance of pihole there. I made sure that the piZeroW is plugged on a separate circuit in my home.

[–] root@lemmy.world 2 points 10 months ago (4 children)

Good point. I just checked and streaming something to my TV causes IO delay to spike to like 70%. I'm also wondering if maybe me routing my Jellyfin (and some other things) through NGINX (also hosted on Proxmox) has something to do with it.. Maybe I need to allocate more resources to NGINX(?)

The system running Proxmox has a couple Samsung Evo 980s in it, so I don't think they would be the issue.

[–] apigban@lemmy.dbzer0.com 0 points 10 months ago

I had this issue when I used kubernetes, sata SSDs cant keep up, not sure what Evo 980 is and what it is rated for but I would suggest shutting down all container IO and do a benchmark using fio.

my current setup is using proxmox, rusts configured in raid5 on a NAS, jellyfin container.

all jf container transcoding and cache is dumped on a wd750 nvme, while all media are store on the NAS (max. BW is 150MBps)

you can monitor the IO using IOstat once you've done a benchmark.

load more comments (3 replies)