JDK

my dude! thanks for the quick reply. that did do the trick, and i can now wipe the nervous sweat off my brow and move on - thank you!

So I'm a bit stuck here, still at the start of troubleshooting and investigating this but in attempt to minimize how long I stay down for, I'm posting so long to see if anyone has a quick solution. I upgraded to 6.12.0 this morning and no issues there; things were running fine after upgrade. I then decided to convert my cache pool to zfs per this guide from Space Invader. Again no issues following this, but when it got time to format the cache pool after the array startup, it now looks like it wants to format my array disks as well! Has anyone run into this? server-diagnostics-20230617-1519.zip

were you able to get renaming to work? from the worker logs i dont even see an attempt to call the External Post-processor Script.

Updating to 4.7.6.0 fixed my image extract issue. At the time i tried, the binhex image hadn't updated to 4.7.6.0 yet, so i just switched to the official docker image. I simply had to point it to the previous appdata location and it fired right up.

I've had this issue now for a while, but only on certain video files, not all. take a look at this thread here: https://emby.media/community/index.php?/topic/110537-image-extraction-error/&do=findComment&comment=1169206 I was able to get things working again by going to binhex/arch-emby:4.6.7.0-3-01. I also just noticed from post above that binhex/arch-emby:4.6.7.0-4-02 works, so i tried that and can confirm this works for me as well.

You should be able to use one of the other elastic dockers and just specify the tag. for example i remember using FoxxMD's image. if you just look at the template you'll see where to change it to "elasticsearch:5.6.16". thats how i had v1.5 running before. I won't get to try installing v1.5 for a couple of days, but ill update here with my progress once i do get back to it.

Awesome, thanks. ill give this a poke tomorrow to see if i can get v1.5 back up. v2 was really simple actually and fewer steps since it no longer seems to require Redis or a specific version of Elastic (i have it running against 7.10.2). That said there is now so much confusing information because so many struggled getting v1.5 up in the first place that there are a loads of loose bits of info that can throw you off course when v2 really doesnt need it. If it helps you, these are the exact steps i followed while installing v2: Install CA User Scripts Create a new script named vm.max_map_count Contents of script as follows: #!/bin/bash sysctl -w vm.max_map_count=262144 Set script schedule to At Startup of Array. Add the docker container. Install Elasticsearch container from CA (for me, 7.10.2 works just fine using d8sychain's release) Install diskover container from CA configure all your variables, do not start the container upon creation. if you did, no problem, just power it down. i had to manually edit the config file (/appdata/diskover/diskover-web.conf.d/Constants.php) to set the ES_HOST variable. it does not seem to update from the docker template, resulting in failed connection to ES. start the container The diskover Application Setup documentation mentions the issue "The application doesn't start an index by default.", so i had to manually create the first index using below. docker exec -u abc -d diskover python3 /app/diskover/diskover.py -i diskover-my_index_name /data you can exclude the "-i diskover-my_index_name" and it will create an index using this pattern "diskover-data-211128210916". the index may take a while to crawl. you can see its progress here: http://server:9200/_cat/indices?v where 9200 is your ES port. optional: go back to CA User Scripts and create a new script using the command from previous step. i may have missed something in the config, but the v2 container is not creating indices automatically like the v1.5 container did. For me it took a few minutes for the first index to become accessible and i could actually use the diskover app. one thing to note is that you need to be careful to not delete the index you have selected in diskover ("Save selection" option). i did this and the app broke completely, not defaulting to one of the other indices. the only way i could fix this was to recreate the index using the command from step #4...at least the error gives you the name of the missing index.

So i had been using this container for a couple of years at least, then a few weeks (maybe months now?) ago it broke with some error in the logs that i didn't get to figure out at the time. Fast forward to this week and i finally get back to fixing this container on my server and see that we are now on v2. That seems to bring with it the fact that most of the great features are now locked behind pay editions. The v1.5 tags are still available, and i realize now that the initial issue that broke my container was likely due to an update because i can pull one of the more recent v1.5 tags and the same error is there, but going back a few versions (~JUN 2021) and no error. But the template is no longer available..does anyone have v1.5 still running and mins posting a screenshot of the template so i can see which variables to set up again?

server was stable for a good 5 or so days, but then just crashed again. I dont see any new logs on the flash, and of course the logs get flushed when the server comes back up. im not sure what im missing. any thoughts?

Hi everyone, I was really trying to not create a new topic just for this, but I could not find a solution: my understanding is that when I setup syslog to mirror to flash the logs should be going to the /logs/ folder on flash. Unless I have the wrong location it should be this /boot/logs/. I have Krusader set up to map a path variable to this location, and I see historical logs there in zip files, but nothing recent enough. I am trying to troubleshoot a freezing issue with my server that has been plaguing me for the last couple of weeks, so I also set up remote logging since i couldnt track down logs on the flash. Below is how I configured the syslog options Here is what is available in /boot/logs/ This is how I mapped the path in Krusader, if that helps.

I've been meaning to ask if there are any high level instructions for getting this set up on unraid?

Depending on which version you installed, you can use one of the management tools like 7D2D RAT (Windows), Botman (Linux), or simply telnet to the server and issue commands that way. If you're just looking to change some of the basic server setup, you would use the serverconfig.xml for that though having the server up and running already, im assuming youre looking for something beyond that.

You are too awesome, thanks @ich777. Yeah, I only spent about 15min on A18 yesterday. Now that the docker has been updated I can roll in a few more hrs to really get a feel for it, but good vibes so far ✌️

From the release notes it looks like they have spent a lot of time implementing positive features and listened to the community closely. Performance seems better from just a quick test too, so that is very positive for me I just updated the GAME ID field to be "294420 -beta latest_experimental". This downloads the correct server version, but i haven't yet been able to get it to run. Still tinkering...

A18 experimental is out today