Posts by Erinox

Worked without issues for me too. Thanks!

Quote from Blueman2

Followed instructions posted by Zoki in post #2 of this thread. Coming from OMV6. No issues at all.

System is N95 CPU. Had a clean install of OMV6 from about a year ago.

Thanks!!

Display More

Same here. Kept putting off the upgrade since I was afraid of something breaking but everything went smoothly.

Well, after running the old docker image since Sunday I just fired up the up-to-date docker for testing purposes again and the error is gone and plex is running fine.

No clue what happened there.

Yes, it's in the first post in the code box. I don't know what to make of that and can't really read the *.dmp-file either.

I already read that but how is that fix related to my problem? Docker and Portainer were running fine, I didn't have problems installing those.

The only container which isn't working is my Plex-container and I'm not getting any indications in the sparse error message that it's due to Apparmor.

Update:

I have now gone back to a 6-month old docker image which is working without errors.

Still strange, I was on the latest docker version of linuxserver/plex before upgrading to OMV6 and everything was working fine then.

For now I'll probably stay downgraded. If anybody has any idea how this got borked up, I'd still be interested in ideas. Don't really want to stay on an old Plex server version forever.

Hi.

After upgrading today from OMV5 to OMV6 my Plex-Container has stopped working. If I try to start it I'm getting the following error and I can't access Plex through the web interface on port 32400, neither can I access my server through the web anymore ("The server "openmediavault" is unreachable.").

Starting Plex Media Server. . . (you can ignore the libusb_init error)
libc++abi: terminating with uncaught exception of type boost::wrapexcept<boost::uuids::entropy_error>: open /dev/urandom
****** PLEX MEDIA SERVER CRASHED, CRASH REPORT WRITTEN: /config/Library/Application Support/Plex Media Server/Crash Reports/1.31.0.6654-02189b09f/PLEX MEDIA SERVER/2f843df3-4258-4fcb-ca2ddeb9-7a58e0fd.dmp
Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign
Crash Uploader options (all are required):
  --directory arg       Directory to scan for crash reports
  --serverUuid arg      UUID of the server that crashed
  --userId arg          User that owns this product
  --platform arg        Platform string
  --platformVersion arg Platform version string
  --vendor arg          Vendor string
  --device arg          Device string
  --model arg           Device model string
  --sentryUrl arg       Sentry URL to upload to
  --sentryKey arg       Sentry Key for the project
  --version arg         Version of the product
  --allowRetries arg    Whether we will allow retries

I'm using the linuxserver/plex:amd64-latest Image for my Server:

I did create the original Plex container through the Portainer GUI back then but I've tried deploying another Plex-Container (different images too) through a docker compose which looks like this:

Quote

---

version: "2.1"

services:

plex:

image: lscr.io/linuxserver/plex:latest

container_name: plex_test

network_mode: host

environment:

- PUID=1001

- PGID=100

- TZ=Etc/UTC

- VERSION=docker

- PLEX_CLAIM= #optional

volumes:

- /srv/dev-disk-by-label-WDRED1/appdata/plex_test:/config

- /srv/dc198340-8c9e-4fdd-b9d6-eb179fa71b4d/media/tv:/tv

- /srv/dc198340-8c9e-4fdd-b9d6-eb179fa71b4d/media/movies:/movies

restart: unless-stopped

Display More

I'm getting loads of crash dumps in \\OPENMEDIAVAULT\appdata\plex_test\Library\Application Support\Plex Media Server\Crash Reports\1.31.0.6654-02189b09f\PLEX MEDIA SERVER when the container is "running" but I don't really know what to do with them. Since I can't upload the *.dmp files in here I've put one of them in my google-drive if anybody else can make sense of those. This one is of a fresh container which I deployed with the above docker compose through Portainer. I couldn't grab the *.dmp from the original plex container since they were always getting created and deleted within seconds.

Google Drive: Sign-in

If I open that in notepad some of the font seems to be unreadable, and I'm not sure if it helps.

Does anybody know what I can try to get Plex running again? I'm at a loss.

Thanks!

Thank you. I'll give the update a try tomorrow and will report back with my success or failings.

Hi.

I'd like to upgrade my OMV5 to OMV6 and read through this thread a bit. I'm using mergerfs for pooling both of my hard drives together and got the pool referenced in several dockers mostly to the location of media files .

Will this pool still be recognized after the upgrade? Apparently there is a mergerfs plugin in OMV6 too but in this thread a user seems to have had some problems with it? Or was this an outlier since in #2 it mentioned that it should automatically convert when upgrading.

And another question - I use DHCP in my network settings since I have assigned a static IP to my NAS in the router. This should work to connect to the server after the upgrade right?

Thanks.

I have updated OMV a few times since my post and right now it's working again. Not sure if something was changed in OMV in the meantime?

I think it does restart when it stops:

Dec 07 12:46:37 openmediavault.local systemd[1]: Stopping Web Services Dynamic Discovery host daemon...
Dec 07 12:46:38 openmediavault.local systemd[1]: wsdd.service: Succeeded.
Dec 07 12:46:38 openmediavault.local systemd[1]: Stopped Web Services Dynamic Discovery host daemon.
Dec 07 12:46:38 openmediavault.local systemd[1]: Started Web Services Dynamic Discovery host daemon.
Dec 07 12:46:38 openmediavault.local wsdd.py[25341]: WARNING: no interface given, using all interfaces

root@openmediavault:~# systemctl status wsdd.service
● wsdd.service - Web Services Dynamic Discovery host daemon
   Loaded: loaded (/lib/systemd/system/wsdd.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-12-07 12:46:38 CET; 23h ago
 Main PID: 25341 (python3)
    Tasks: 1 (limit: 4915)
   Memory: 10.9M
   CGroup: /system.slice/wsdd.service
           └─25341 python3 /usr/sbin/wsdd.py --shortlog --workgroup=WORKGROUP

Dec 07 12:46:38 openmediavault.local systemd[1]: Started Web Services Dynamic Discovery host daemon.
Dec 07 12:46:38 openmediavault.local wsdd.py[25341]: WARNING: no interface given, using all interfaces

It was gone again just now. When I try to navigate to //openmediavault.local in the file explorer it sends me to the browser log-in page of OMV 5. After restarting the service I can see and access the shares in the network. If I try to access the shares by opening //openmediavault directly it disappears again and sends me to the web-login again. After doing that I have to restart it again to work but it's only working for some time before it disappears again. Pretty strange.

Hi.

I have the same problem that I can not see OMV on my network after it's running for some time.

If I log in and put "systemctl restart wsdd.service" it's appearing again.

Everything else is running fine and I can still access everything with Cloud Commander but it only shows up in Windows 10 if I restart the rsdd.service every now and then. Any idea why the service apparently gets killed after a while?

with omv-mkconf missing, OMV_FSTAB_MNTOPS_EXT4 variable deprecated... how can one modify fstab the "clean" way?

Do you have the FTP service enabled?

I don't and I get the same error on OMV5. I assumed it's there because without FTP running there will be no logs.

Alright on the second try resetting the UI worked. Thank you.

And yes, turning the sortable flag off would work as well. Like I said, I don't see the need for it to be sorted alphabetically.

Quote from macom

Log start date/time and log stop date/time are lines/rows in the log. You probably don't see them as you sorted the log.

I agree but right now there's no way to get it back the way it was before I clicked on Sort by name by accident. From what I can see all the other Syslogs have a date & time column so it would make sense to add that to the Update management as well just for consistency. Even more so since I can't revert back to a chronological order after clicking on sorting right now.

Alright, but are the logs in Chronological order for you? I thought they were like that for me before I accidentally clicked the message column.

I don't really see the sense in sorting the logs by the first letter of the log line:

I just did but it didn't change anything. Can you reproduce this?

Hi.

I've just scrolled through my Update management history and terminal output logs and accidentally clicked on the message column so the messages got sorted by name.
I'm fairly sure there was a Date & Time Column there before? But now I can't access this anymore.

Is this a bug? How do I get the date & time column back?