Playlists disappeared after latest update?

[captainkev]

OK, here goes!

I have a single server, with a 13th gen Intel i7 processor and 128GB memory. On this I run Proxmox VE (latest release). In Proxmox I have a number of Virtual Machines:

1) Truenas Scale - (4 vCPUs, 24GB RAM) this has a PCI Host Bus Adapter passed through in hardware from Proxmox to the VM. Attached to the HBA card are two Seagate 18TB drives, configured in a ZFS mirror pool. The 18TB is split into two volumes - "Media" and "Users". Media contains the music (in a dedicated folder), along with movies and photos. Both volumes are shared via CIFS/SMB
2) Ubuntu Server 22.04 LTS - (6 vCPUs, 32GB RAM) The sole purpose of this VM is to run Docker containers. There are 24 containers in total, including Minimserver, Plex, Frigate, MQTT-Broker, Immich, Portainer and others
3) TP-Link Omada Controller (Running as an LXC container with 2 vCPUs and 4GB RAM)
4) Home Assistant (2 vCPUs, 8GB RAM)
5) Windows 11 - this is generally left shutdown and only booted for certain tasks
6) Ubuntu Server 22.04 LTS (4 vCPUs and 16GB RAM) Running nextcloud - but never actually used.
7) Ubuntu Server 22.04 LTS (4 vCPUs and 16GB RAM) Running ZabbixNMS - not yet configured this fully.

I've already tried shutting down any docker containers that could possibly be writing to the Music folder but something I'll be trying today will be to shut down everything except Truenas and the Minimserver container.

Hope that covers it.

[captainkev]

Quick update - shut down all VMs except Ubuntu (for Docker) and Truenas, and also stopped all containers except minimserver and and scan has completed successfully. Playlists are back and Minimstreamer is working.

So two things left to figure out - 1) Which container or VM is interfering with the scan and 2) why can't Minimserver coexist with other services

[captainkev]

Further update... I have no idea what's going on now. After Minimserver seeming to work perfectly when it was just Truenas and Minimserver running, I started adding the containers back one by one. All is well until I get to about 16 containers, then the same issue starts happening - and continues to happen until I return to having just one container.

There doesn't seem to be any one container which is causing the problem.

[stefano_mbp]

Couldn’t it be due to a lack of ram? 24 containers in a 32GB ram VM seems too much stuff running

[captainkev]

I don't think so. 32GB assigned, 25GB free. Here's the output from top when Minimserver is started alongside all the other containers:

top - 14:00:40 up 1:15, 2 users, load average: 0.34, 0.16, 0.14
Tasks: 383 total, 1 running, 382 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.6 us, 0.3 sy, 0.0 ni, 95.7 id, 3.3 wa, 0.0 hi, 0.2 si, 0.0 st
MiB Mem : 32092.8 total, 25883.8 free, 2243.0 used, 3966.0 buff/cache
MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 29369.0 avail Mem

When I start the library scan it drops down to 20GB free:

top - 14:07:29 up 1:22, 2 users, load average: 0.52, 0.62, 0.36
Tasks: 608 total, 1 running, 607 sleeping, 0 stopped, 0 zombie
%Cpu(s): 0.3 us, 0.1 sy, 0.0 ni, 99.4 id, 0.1 wa, 0.0 hi, 0.1 si, 0.1 st
MiB Mem : 32092.8 total, 20432.1 free, 2691.8 used, 8969.0 buff/cache
MiB Swap: 8192.0 total, 8192.0 free, 0.0 used. 28914.0 avail Mem

[simoncn]

MinimServer uses Java APIs to walk the file tree. The Java runtime implements these APIs by making calls to the Linux file system. If the Linux file system encounters an error when reading the name of the next entry in a directory, it returns null. A null return indicates that no more entries are available.

This error could be caused by some other container modifying the directory contents. Perhaps (this is pure speculation on my part) it could also be caused by some other process using a short intensive burst of CPU cycles that causes the read operation in the MinimServer container to time out. A short burst like this would not show in top. Another possibility is that some other container is locking the file system for a short time in some way that prevents the MinimServer container from reading it.