PlutoniumAcid

I mean, the simplest answer is to lay a new cable, and that is definitely what I am going to do - that's not my question.

But this is a long run, and it would be neat if I could salvage some of that cable. How can I discover where the cable is damaged?

One stupid solution would be to halve the cable and crimp each end, and then test each new cable. Repeat iteratively. I would end up with a few broken cables and a bunch of tested cables, but they might be short.

How do the pro's do this? (Short of throwing the whole thing away!)

edit: you are right, it's the I/O WAIT that it destroying my performance:
%Cpu(s): 0,3 us, 0,5 sy, 0,0 ni, 50,1 id, 49,0 wa, 0,0 hi, 0,1 si, 0,0 st
I could clearly see it using nmon > d > l > - such as was suggested by @SayCyberOnceMore. Not quite sure what to do about it, as it's simply my sdb1 drive which is a Samsung 1TB 2.5" HDD. I have now ordered a 2TB SSD and maybe I am going to reinstall from scratch on that new drive as sda1. I realize that's just treating the symptom and not the root cause, so I should probably also look for that root cause. But that's for another Lemmy thread!

I really don't understand what is causing this. I run a few very small containers, and everything is fine - but when I start something bigger like Photoprism, Immich, or even MariaDB or PostgreSQL, then something causes the CPU load to rise indefinitely.

Notably, the top command doesn't show anything special, nothing eats RAM, nothing uses 100% CPU. And yet, the load is rising fast. If I leave it be, my ssh session loses connection. Hopping onto the host itself shows a load of over 50,or even over 70. I don't grok how a system can even get that high at all.

My server is an older Intel i7 with 16GB RAM running Ubuntu22. 04 LTS.

How can I troubleshoot this, when 'top' doesn't show any culprit and it does not seem to be caused by any one specific container?

(this makes me wonder how people can run anything at all off of a Raspberry Pi. My machine isn't "beefy" but a Pi would be so much less.)

Having ordered my first 3D printer, I am giddy and preparing various things.

I have installed Octoprint on my home server as a Docker container, but when running it, it seems that it wants to have a serial connection to a printer. Octoprint expects to be running on a Raspberry that is connected via its serial interface.

What am I missing?

The printer I ordered (Prusa Mini) comes with a wifi dongle, so I guess there will be a way to reach it over the network. But that does not automagically mean Octoprint can work with it.

I am looking to buy a 3D printer for my son (and for myself too). We want to print, not tinker, so it should be something that gives great results right from the start.

Can you guide me to a sensible choice?

My first choice would have to be the Prusa MK3S Plus but it is outside the price range I am shopping for, except if I buy used -- would that be bad to do?

Realistic choices:

• €380 used Prusa MK3S+, with 10 days printing time
• €400 new Prusa Mini+
• €250 new Ender 3 V2 Neo

Criteria:

• High quality, no hassle. I want to print, not tinker.
• Preferably (semi)assembled.
• Auto bed leveling.
• Auto error detection (filament, power, etc.?).
• Budget up to 600 EUR/USD including extras, excluding filament.
• Speed is not important.
• Size is not important.
• Must not be cloud-based.

Questions:

• Surface?! Smooth, os satin, or textured? (Why) Should I have more than one kind?
• (Why) Do I need an enclosure?

For all the amazing work and effort that is being poured into the fediverse in the past several weeks, and in particular what we users can see with the Voyager app - this deserves to be said with great gratitude!

❤️ Voyager is such a polished app ❤️

Just small details like how the app takes you one step back for each time you press the "Posts" button, from comment to post, from post to feed, to top of feed, and finally, to communities.

Much elegant, very wow 🐶

TLDR: I consistently fail to set up Nextcloud on Docker. Halp pls?

Hi all - please help out a fellow self-hoster, if you have experience with Nextcloud. I have tried several approaches but I fail at various steps. Rather than describe my woes, I hope that I could get a "known good" configuration from the community?

What I have:

• a homelab server and a NAS, wired to a dedicated switch using priority ports.
• the server is running Linux, Docker, and NPM proxy which takes care of domains and SSL certs.

What I want:

• a docker-compose.yml that sets up Nextcloud without SSL. Just that.
• ideally but optionally, the compose file might include Nextcloud office-components and other neat additions that you have found useful.

Your comments, ideas, and other input will be much appreciated!!

TLDR: I am running some Docker containers on a homelab server, and the containers' volumes are mapped to NFS shares on my NAS. Is that bad performance?

• I have a Linux PC that acts as my homelab server, and a Synology NAS.
• The server is fast but has 100GB SSD.
• The NAS is slow(er) but has oodles of storage.
• Both devices are wired to their own little gigabit switch, using priority ports.

Of course it's slower to run off HDD drives compared to SSD, but I do not have a large SSD. The question is: (why) would it be "bad practice" to separate CPU and storage this way? Isn't that pretty much what a data center also does?

Sorry, noob here. I have been using Linux for a decade at least, but some basic stuff still stump me. Today, it's file sharing: The idea is that the server is good at CPU and the NAS is good at storage. My NAS does run Docker but the services are slow; and my server runs a bunch of Docker containers just fine but has limited disk space (SSD).

Want:

• Share a directory on my NAS, so that my homelab server can use it.
• Security is not important; the share does not need to be locked down.

Have:

• Server+NAS are on their own little 1Gb Cisco switch, so network latency should be minimal.
• Linux NAS and Linux server have separate users/UID/GID.

Whatever I try, it always ends up with errors about 'access denied' or read-only or something. I conclude that I am not smart enough to figure it out.

Help?

Prove me wrong, please?

edit: thanks for all the great comments, this is really helpful. My main take-away is that it does work, but requires dry air. In humid conditions it doesn't really do anything.

Spouse bought this thing that claims to cool the air by blowing across some moist pads. It's about as large as a toaster, and it has a small water tank on the side. The water drips onto the bottom of the device, where it is soaked up by a sort of filter. A fan blows air through the filter.

1. Spouse insists that the AIR gets cooled by evaporation.
2. I say the FILTER gets cooled by evaporation.
3. Spouse says the cooled filter then cools the air, so it works.
4. I say the evaporation pulls heat (and water) from the filter, so the output is actually air that is both warmer and wetter than the input air. That's not A/C, that's a sauna. (Let's ignore the microscopic amount of heat generated by the cheap Chinese fan.)

By my reckoning, the only way to cool a ROOM is to transport the heat outside. This does not do that.

We can cool OURSELVES by letting a regular fan blow on us = WE are the moist filter, and the evaporation of our sweat cools us. One could argue that the slightly more humid air from this device has a better heat transfer capacity than drier air, but still, it is easier to sweat away heat in dry air than in humid air.

Am I crazy? I welcome your judgment!

edit: thank you for all the great comments! It's going to take a while to chew through the suggestions. I just started testing picoshare which is already looking both easy and useful.

Hi all! I am looking for a file-hosting / file-sharing service and hope you guys could recommend something?

Features I would like to see:

• Docker-compose ready to use.
• multi-user, not just for myself.
• individual file size >2GB.
• shared files should be public, not require a login to download.
• optional: secret shares, not listed but public when the link is known.
• optional: private shares that require either a password or a login.

Thanks in advance for sharing your experiences!

Colors are important!

Red = bad, stop, no, don't, forbidden. That does NOT go with upvotes.

The Archbishop of Canterbury and The Royal Commission for Political Correctness announced today that the climate in the UK should no longer be referred to as 'English Weather'.

In order to no longer offend a sizable portion of the UK population, it will now be referred to as 'Muslim Weather' -- partly Sunni, but mostly Shi'ite.