ch00f

I’m running funkwhale in docker. This consists of a half dozen docker containers one of which is postgres.

To run a backup, funkwhale suggests shutting down all of the containers and then docker compose running pg_dump on the postgres container. Presumably this is to copy the database when nobody is accessing it.

For some reason when I do this, I get an error like:

pg_dump: error: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory
	Is the server running locally and accepting connections on that socket?

It would seem that postgres isn’t running. I see the same error with other commands such as psql.

If I fully boot the container and then try exec-ing the command, it works fine.

So it would seem that the run command isn’t fully booting the instance before running the command? What’s going on here?

The container is built from postgres:15-alpine

I'm moving my music library to a funkwhale instance, but I don't want to have to keep two copies of every song (one imported to Funkwhale, one on a local drive).

It looks like Funkwhale will let you download a single song at a time from your own library , but there doesn't seem to be a similar button for albums or playlists.

The files themselves are obfuscated in whatever indexing system it uses, so there's nothing to be done there.

Anyone know how this is possible?

Just got Whisper working on my local server so I can send it audio files via curl POST request and receive transcribed text.

Are there any keyboard plugins for phones that could be directed to a personal server running Whisper to replace functions like Siri/Google assistant voice transcription?

Over the week, I've been slowly moving from mdadm raid to ZFS. My process was:

• create ZFS pool on secondary server
• rsync all files over to zfs server
• Nuke mdadm array on primary and set up zpool
• ssh dataset from secondary server to primary server.

This is 15tb of data and even over gigabit, it took a day and a half to transfer. It finally finished tonight, and somehow I'm the owner and group of every single file. In addition to this generally being weird, it also broke some docker volume binds, and I generally don't want it.

It looks like the same is the case for the files on the secondary server too, so it must have happened during the initial rsync.

Fortunately, I also rsynced to some offline drives which kept ownership fine.

Anyway, I'm trying to figure out how the hell this happened. The rsync command I used was:

sudo rsync -ahu --delete --info=progress2 -e ssh /mnt/MONSTERDRIVE/ ch00f@192.168.1.65:/bluepool/monsterdrive/

At least I'm pretty sure this is what I used. I had to reverse-i-search to find it.

This is similar to the command I use when backing up to cold storage which has worked fine in the past. My understanding is that -a is shorthand for -rlptgoD where -o is "preserve owner."

So how could this have happened?

Does it matter that the secondary server doesn't have the same users as the primary server?

[SOLUTION]

From what I read online, using rsync over ssh as I did does not establish root permissions on the receiving end. So while I have the rights to modify the owners on the local side, I can only set the owners to the user I ssh'd as on the receiving side. Thus, I was the owner of every file.

The solution is two fold. First, I need to specify --rsync-path "sudo rsync" This tells the receiving side to use rsync as a super user.

Secondly, because there is no way to enter a super user password on the receiving side, I added a file to /etc/sudoers.d/ with

ch00f ALL=NOPASSWD:/usr/bin/rsync

This makes it so that the ch00f user doesn't need to enter a password when running rsync as a super user.

I don't think this is a security hole, and it got it to work.

Just noticed this a week or so ago. When I try to scroll the feed on lemmy.world, my page will halt and go even though I'm scrolling consistently on my trackpad. No other website has this problem to my knowledge.

Info: Framework 13 AMD laptop 32 gigs memory Firefox 136.0.1 64-bit

Any ideas? It's really irritating.

I'm hosting a few services using docker. For something like an openstreetmap tileserver, I'd like it to remain on my SSD because high speed improves performance, and the directory is unlikely to grow and fill the drive.

For other services like NextCloud, speed isn't as important as storage size, so I might want it on a larger HDD raid.

I know it's trivial to move the volumes directory to wherever, but can I move some volumes to one directory and some volumes to another?

https://en.wikipedia.org/wiki/Tipperary_Hill

You always hear about gun sales in the US, but you never hear about what happens to the guns at the end of their lifecycle. I assume guns wear out eventually, and I assume you can't just chuck them in the garbage when they do. What happens to them?

I'm working on trying to streamline the process of ripping my blu-ray collection. The biggest bottlneck in this process has always been dealing with subtitles and converting from image-based PGS to textbased SRT. I usually use SubtitleEdit which does okay with occasional mistakes. My understanding is that it combines Tesseract with a decent library to correct errors.

I'm trying to find something that works in the command line and found pgs-to-srt. It also uses Tesseract, but it appears without the library, the results are...not good:

Here's the first two minutes of Love, Actually:

00:01:13,991 --> 00:01:16,368
DAVID: Whenever | get gloomy
with the state of the world,

2
00:01:16,451 --> 00:01:19,830
| think about
the arrivals gate
alt [Heathrow airport.

3
00:01:20,38 --> 00:01:21,415
General opinion
Started {to make oul

This is just OCR of plain text on a transparent background. How is it this bad? This is using the Tesseract "best" training data.

Edit: I’ve been playing around with ocr-to-pgs which also uses tesseract and discovered that subtitles having black outlines really messes with it. I made some improvements.

https://github.com/wydengyre/pgs-to-srt/pull/348

Upgrading a server for the first time in 10 years, so I’m a little out of the loop. I was surprised to find that the RAM I bought didn’t fit.

This is my first time dabbling in ECC RAM, so I figured there was some minor detail I missed when purchasing, but I eventually came across the data sheet for this stick, and the dimensions given don’t match the measurements I’m making. The tip of the caliper should be in the middle of the notch at 68.1mm.

What’s more is that the dimensions in the data sheet seem to match the dimensions on my motherboard. What’s going on here?

[SOLVED] I and Kingston are morons. I ordered RDIMM instead of UDIMM. The Kingston datasheet gives the wrong dimensions.

I hate the cloud.