Plex Container not Starting after adding cache pool


Recommended Posts

I had a 250gb SSD that I used as my disk2 since it was lying around. It was only used by the iso share. Yesterday when the cache became full, I thought, I could remove it from disk 2 and make it as slot 2 of a cache pool. I did this Tools>new config>Preserve All. 
Once that was done, I added disk 2 as my cache pool and went to sleep. Today morning when I check, it looks like my plex container is not starting. I had updated plex as well just before this. All my other container seems to be running fine.
I thought this might be due to the cache pool not setup correctly, so I went and balanced the cache pool to single. After doing this I'm getting the following 

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.


I feel like the appdata that plex uses was in cache and it got corrupt. What can I do to get back my plex container. 
Should I go to docker settings and delete my docker.img and recreate container from my template?

I'm worried if I lost my plex library matches.

diagnostics-20200630-1055.zip

Link to comment

The end of your syslog

Jun 30 10:54:24 unMHN sshd[15251]: Failed password for root from 87.251.74.48 port 46684 ssh2
Jun 30 10:54:24 unMHN sshd[15252]: Failed password for root from 87.251.74.48 port 46682 ssh2
Jun 30 10:54:24 unMHN sshd[15251]: Connection closed by authenticating user root 87.251.74.48 port 46684 [preauth]
Jun 30 10:54:24 unMHN sshd[15252]: Connection closed by authenticating user root 87.251.74.48 port 46682 [preauth]

 

https://www.abuseipdb.com/check/87.251.74.48

 

Also some ftp logins from various. Are these expected?

Jun 30 10:33:26 unMHN sshd[10227]: Accepted none for ftp from 167.71.222.119 port 58092 ssh2
...
Jun 30 10:34:04 unMHN sshd[12055]: Accepted none for ftp from 68.183.180.132 port 59740 ssh2
...
Jun 30 10:34:31 unMHN sshd[13178]: Accepted none for ftp from 104.248.156.167 port 34192 ssh2

 

Link to comment
1 minute ago, trurl said:

The end of your syslog


Jun 30 10:54:24 unMHN sshd[15251]: Failed password for root from 87.251.74.48 port 46684 ssh2
Jun 30 10:54:24 unMHN sshd[15252]: Failed password for root from 87.251.74.48 port 46682 ssh2
Jun 30 10:54:24 unMHN sshd[15251]: Connection closed by authenticating user root 87.251.74.48 port 46684 [preauth]
Jun 30 10:54:24 unMHN sshd[15252]: Connection closed by authenticating user root 87.251.74.48 port 46682 [preauth]

 

https://www.abuseipdb.com/check/87.251.74.48

 

Also some ftp logins from various. Are these expected?


Jun 30 10:33:26 unMHN sshd[10227]: Accepted none for ftp from 167.71.222.119 port 58092 ssh2
...
Jun 30 10:34:04 unMHN sshd[12055]: Accepted none for ftp from 68.183.180.132 port 59740 ssh2
...
Jun 30 10:34:31 unMHN sshd[13178]: Accepted none for ftp from 104.248.156.167 port 34192 ssh2

 

Thanks a lot for pointing this out. I have closed all ports

The FTP is also not expected. What does this mean. Someone was able to transfer files?

---
I realized I had port 22 open for ssh, which I dont plan on using. 
I also had these ports open 
Ombi => 3579

OpenVpn => 1194
Plex => 32400
Http : 443/80 => 1443/180 for reverse proxy

I guess the open port 22 caused the issue. Is the above configuration vulnerable even after closing port 22. What should I change? 
I want to be able to use Plex without configuring OpenVpn on every client device.
---
 

Link to comment

I just realized that I had opened the ports to the dashboard long back when I followed some tutorial. The server was off for 3mo, and I just got back into setting everything up. Forgot about this setting. 😧 . I have turned of these setting in Management access as follow.
What should I do now, if the server might be compromised.
image.png.4637324688e79847fec1358403b6e70c.png

Link to comment
3 minutes ago, mhn_10 said:

No VM's
Only running docker. 1x 12tb parity disk, 1x 10tb data disk, 2x cache pool

Go to Settings - VM Manager, disable VMs, then delete libvirt image from that same page.

 

Go to Settings - Docker, disable Dockers, then delete docker image from that same page.

 

Then post new diagnostics.

Link to comment

Seems like plex still has the same issue even after creating new docker container.

 

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 40-plex-first-run: executing...
Plex Media Server first run setup complete
[cont-init.d] 40-plex-first-run: exited 0.
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: executing...
[cont-init.d] 45-plex-hw-transcode-and-connected-tuner: exited 0.
[cont-init.d] 50-plex-update: executing...
[cont-init.d] 50-plex-update: exited 0.
[cont-init.d] done.
[services.d] starting services
Starting Plex Media Server.
[services.d] done.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

Starting Plex Media Server.
Stopping Plex Media Server.
kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec]

[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
s6-svwait: fatal: timed out
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

Link to comment

Did you do this before posting those latest diagnostics?

1 hour ago, trurl said:

Go to Settings - VM Manager, disable VMs, then delete libvirt image from that same page.

 

Go to Settings - Docker, disable Dockers, then delete docker image from that same page.

If so you must have done a lot more than that since your dockers and VMs are still enabled in those diagnostics. And your system share still has files on disk1.

 

 

 

Link to comment

This is the steps I performed

  1. Disabled docker
  2. Deleted Docker Image
  3. Enabled Docker
  4. Performed the Same for VM
  5. Went and added new container from My Template. 

It was in the middle of adding the docker containers from templates, I took the diagnostic.
Do you want a clean diagnostic just after clearing the Docker/VM image?

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.