Server Version#: 4.100.1
Player Version#: N/A
When I bring up the Home page I receive a “Something went wrong” message. Tested movies, TV shows and music in the inventory play correctly.
Hit Control F5 and let it reload.
Plex/web will display this message if the server doesn’t respond to it as soon as it thinks it should.
Did that. Same problem.
Grab the Logs manually (tar.gz of the ‘Logs’ directory) and attach here
I tried to attach the logs and received this error:
Sorry, the file you are trying to upload is too big (maximum size is 10 KB).
ZIP files / tar.gz are 5 MB. The forum allows 35 MB uploads
You can’t upload ‘log’ files individually. That is probably what it complained at.
It worked this time. I used the same process.
Your server itself is running well.
I can see the scanner running and all looks good.
There is a lot of playback, some concurrent with scanning.
Might you be running out of another resource?
The server is a dedicated Linux CentOS 8 VM running on Hyper-V. The Host is an Intel NUC with three other VMs, all with very low usage.
The storage is a dedicated file server sharing files over NFS.
The network connecting all of this is overkill.
We’re not running out of resources anywhere, except possibly within Plex code.
Your stacking here is: CentOS → Hyper-V → Windows ??
If so, why did you decide to use Linux?
If so, why did you decide to use Linux?
Because Linux is a small-footprint system and Windows isn’t. For the Host, Linux doesn’t have drivers for the hardware. So it’s Windows-10/Hyper-V/Linux.
The Linux partition is 100GB on a 2TB SATA SSD (shared with other VMs), four cores and 32GB of memory.
The NFS server has >60TB of storage dedicated to Plex (17 TB free).
This is NOT a resource issue.
You’re not seeing the point.
Linux , in a virtual machine (virtual, imaginary, hardwrae) , on top of Windows.
There is no gain from a smaller footprint; only loss. You’re still subject to all of windows networking underneath.
You’re far better off running Plex native on Windows.
There is no gain from a smaller footprint; only loss. You’re still subject to all of windows networking underneath.
You’re far better off running Plex native on Windows.
Except that would be Windows under Hyper-V under Windows. The Host has a total of 4 VMs.
Also, this has been my configuration for 2+ years. This problem just now appeared.
Exactly, You’re wholly at the mercy of Windows underneath. One change in windows and it stops working.
In this configuration, you’re dependent on Windows networking, HyperV networking and Linux networking.
There are no errors showing up in your logs.
By definition, on Linux, it should be working.
Now that we know it’s in a VM on Windows, it starts to make sense.
Any one of the updates in either operating system can bring it down.
Any one of the updates in either operating system can bring it down.
In theory, this is correct. In practice, the ONLY updates being receives are Plex updates. Specifically, CentOS 8 updates are no longer being delivered and I haven’t released updates through WSUS for a while. The ONLY update received in the past few months is Plex.
Moving on.
Apparently, Chuck doesn’t want to do anything here except point fingers at everything except Plex. Is there anybody who has a clue and can look at the logs? Maybe even someone who actually understands how VMs function?
EDIT:
OK. You seem to have had some issues once upon a time with Virtualization and are now blaming it where it’s being used. FYI, there’s nothing “imaginary” (post 12) about the virtualized resources that are available to, and used by, a VM. Your lack of comprehension of how Hypervisors work makes you a poor choice for assisting with this issue. It needs to be handed off to someone who can look at the issue being encountered without the false preconceptions that you’ve so clearly demonstrated in your above few posts.
I am not pointing fingers. I don’t do that.
What I cannot figure out , because there are no errors whatsoever in your logs and I don’t have hands-on to test things, is where it is.
This whole misunderstanding is because of Windows.
- I don’t understand it
- It’s heavy as hell
- It’s unpredictable
Setting that all aside.
If it works one time and then doesn’t work, I will ask you.
WHY?
Network?
Device ?
Returning to the original problem “Something went wrong”.
This happens when PMS does not respond as fast as Plex/web or apps expect.
- It happens during initialization
- It happens when the DB is extremely fragmented
- It happens when there is insufficient CPU or memory to get the job done fast enough.
- It happens in Plex/web when the network isn’t fast enough to load the page.
In a Linux-only implementation (or a Type 1 hypervisor VM), this is very easy to resolve. The resolution order is: DB, CPU, then network.
In this configuration, it’s unknown because of the complexity.
1 Like
Still waiting for the handoff.
Since you are unwilling to accept chuck’s help I doubt anyone here will do more for you.
Chuck’s point is you have layers Windows (A), Hyper V (B), CentOS (C)
Plex is currently running on C, why not just run it on A without virtualization.
Chuck looked at your logs and didnt see anything wrong, and since you wont accept his help, few people are better at parsing the logs…
Can you clarify on which client(s) you’re experiencing this problem? Also, have you made any other changes to your server recently, such as adding or removing libraries?
It seemed to me that his point was “That’s too hard” (with a whine).
Because A is running four VMs. In order to retain enough unused processor time for the other VMs while performing transcoding, the Plex resources need to be limited. Using a VM is the best way to do this.
It’s the Plex web console, not a client.
NOTHING else has changed. No Linux patches and no Windows patches. No libraries added. No plugins installed or updated. The ONLY recent change is that Plex decided to update itself.
Also, I noticed that the “Continue Watching” doesn’t appear on the client. Another change since the latest Plex update.
