Selfhosted

39987 readers

963 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

This happens after 3-4 days of running the server, then I have to restart it manually. (discuss.tchncs.de)

submitted 3 months ago* (last edited 2 months ago) by nutbutter@discuss.tchncs.de to c/selfhosted@lemmy.world

38 comments fedilink hide all child comments

I bought an Optiplex 5040, with an i5-6500TE, and 8 GB DDR3L RAM.

When I bought it, I installed Fedora Server on it. It got stuck every few days but I could never see the error. The services just stopped working, I couldn't ssh into it, and connecting it to a monitor showed a black screen.

So, I thought let's install Ubuntu Server, maybe Fedora isn't compatible with all of its hardware. The same thing is happening, now, but I can see this error. Even when there's nothing installed on it, no containers, nothing other than base packages, this happens.

I have updated the bios. I have tried setting nouveau.modeset=0 in the grub config file. I have tried disabling and enabling c-states. No luck till now.

Would really appreciate if anyone helps me with this.

UPDATE:

I cleaned everything and reapplied the thermal paste. I did not see any change in the thermals. It never goes over 55°C even under full load.
I reset the motherboard by removing that jumper thing.
I ran memtest86, which took over 2½ hours. It did not show any errors.
I ran a CPU stress test for over 15 hours, and nothing crashed.
I also ran the Dell's diagnostic tool, available in the boot menu of the motherboard. The whole test took over 2 hours but did not show any errors. It tested the memory, CPU, fans, storage drives, etc.

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

[–] possiblylinux127@lemmy.zip 3 points 3 months ago (2 children)

Don't try to clean CPU pins. That is a very bad idea

[–] loganb@lemmy.world 4 points 3 months ago (1 children)

I mean speaking from experience, its resurrected a couple problematic CPUs for me. CPU pins no, pads on an LGA style CPU, sure.

[–] possiblylinux127@lemmy.zip 1 points 3 months ago

It is much harder to mess up pads

[–] admin@sh.itjust.works 2 points 3 months ago (1 children)

The CPU in this has no pins, is just contacts on the chip. The pins are in the motherboard, like the new 7000 series Ryzen.

[–] possiblylinux127@lemmy.zip 1 points 3 months ago

Clean pads not pins