Selfhosted

40296 readers

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

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

-7

Something gone bad (no.lastname.nz)

submitted 9 months ago* (last edited 9 months ago) by BlueEther@no.lastname.nz to c/selfhosted@lemmy.world

5 comments fedilink hide all child comments

Oh well good by:

top 5 comments

sorted by: hot top controversial new old

[–] solrize@lemmy.world 5 points 9 months ago (1 children)

Looks like someone pwned your box and installed a ddos bot on it?

[–] Link@rentadrunk.org 2 points 9 months ago (1 children)

Where do you see that? Looks like a torrent client let running to me.

[–] BlueEther@no.lastname.nz 3 points 9 months ago

It looks like it was a Plex scan that tied it's self up in knots and locked up the SMB share and it just happened that it was the QBT container that I noticed it on first.

[–] Cyber@feddit.uk 2 points 9 months ago (1 children)

Weird. netin was busy, yet the bottom of the screen implies more outbound traffic (I guess it's connected the other way around?)

And the log looks like a SMB/CIFS issue... maybe not the interweb?

But, it definitely looks like something got stuck in a loop and triggered a memory leak.

Whatever VM / CT was using CPUs 7 & 10 at the time was the problem... find that and you'll find the next step down the rabbit hole...

[–] BlueEther@no.lastname.nz 1 points 9 months ago

It looks like it was a Plex scan that tied it's self up in knots and locked up the SMB share and it just happened that it was the QBT container that I noticed it on first.

Some of the logs did mention Plex was soft locked as well.