Zerreth

So I had a rabbithole adventure today. 🤯 The Adminer image that is live on the community applications will not connect to mongoDb databases at all. it will report the following error: None of the supported PHP extensions (mongo, mongodb) are available. The more info page links to this github: https://gist.github.com/rickxz/e037248e6082c46295ff0d9e22314e30 The key takeaway is this line RUN echo "extension=mongodb.so" > /usr/local/etc/php/conf.d/docker-php-ext-mongodb.ini After checking with the command "php --ini" in the container I could see that no such ini file was ever loaded. Stronger still, the file does simply not exist in the container. /usr/local/etc/ is empty. 🤮 So it could never work! I wouldn't even know where to point the "PHP_INI_SCAN_DIR" environment variable to it. 🧐 I've basically installed docker desktop and setup the whole thing myself. It was quite the learning experience. I'll post a link here to the working dockerhub image (for anyones that's interested) : https://hub.docker.com/repository/docker/zerreth/adminer/general

Presumably you would map `/etc/netdata` to a location in your appdata share (e.g. /mnt/user/System/Appdata/netdata/config/netdata - Note my appdata is in a slightly different location.) And then just edit the netdata.conf file it spits out in there with a text editor.

I'm in the same boat when trying to install it on another unraid server whist I got a working instance on my media unraid server. (v1.42.0-95-nightly on the working one with docker vdisk, docker folders on the other that isn't working and latest nightly) No clue what's wrong, the configuration is identical. (except for the cloud connection token ofc) Mapping /var/log/netdata to e.g. /mnt/user/appata/netdata/log/netdata (or wherever) so I can inspect the logs more easily & compairing logs with the working server: 2023-08-27 22:00:15: apps.plugin ERROR : APPS_READER : Received error on stdin. (errno 22, Invalid argument) Seems to be that it's trying to open a file but the file path is invalid/deesn't exist.

Yeah reinstalling the plugin fixes it. But my feeling is that i'm gonna be back here in a week. debug-DOCKER.json {"veriosn":"2023.08.11","folders":{"CyWcuHp71eIxPOEjvCnf0YBa8":{"name":"Smart Home","icon":"https://fonts.gstatic.com/s/i/materialicons/home/v16/24px.svg","regex":"","settings":{"preview":1,"preview_border":true,"preview_border_color":"#ff7ae7","preview_hover":false,"preview_vertical_bars":true,"preview_update":true,"preview_grayscale":true,"preview_webui":true,"preview_logs":true,"expand_tab":false,"expand_dashboard":false},"containers":["HomeAssistant","NodeRed","ESPHome","Mosquitto","Zigbee2MQTT"]},"Rlw7ityxszdiaBRLeBEWZ4m7Zo":{"name":"Network","icon":"https://fonts.gstatic.com/s/i/materialicons/wifi/v12/24px.svg","regex":"","settings":{"preview":1,"preview_border":true,"preview_border_color":"#05ffee","preview_hover":false,"preview_vertical_bars":true,"preview_update":true,"preview_grayscale":true,"preview_webui":true,"preview_logs":true,"expand_tab":false,"expand_dashboard":false},"containers":["IPerf3","Unifi","OpenSpeedTest"]}},"unraidOrder":[],"originalOrder":["ESPHome","HomeAssistant","IPerf3","Mosquitto","NodeRed","OpenSpeedTest","Unifi","Zigbee2MQTT"],"newOnes":["ESPHome","HomeAssistant","IPerf3","Mosquitto","NodeRed","OpenSpeedTest","Unifi","Zigbee2MQTT"],"order":["ESPHome","HomeAssistant","IPerf3","Mosquitto","NodeRed","OpenSpeedTest","Unifi","Zigbee2MQTT"],"containersInfo":{"ESPHome":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"http://10.0.0.3:6052/","icon":"/state/plugins/dynamix.docker.manager/images/ESPHome-icon.png","shell":"bash","registry":"https://hub.docker.com/r/esphome/esphome","Support":"https://forums.unraid.net/topic/72033-support-digiblurs-docker-template-repository/","Project":"https://esphome.io/","DonateLink":"https://www.paypal.me/digiblurDIY","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-ESPHome.xml"},"IPerf3":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"","icon":"/state/plugins/dynamix.docker.manager/images/IPerf3-icon.png","shell":"bash","registry":"https://hub.docker.com/r/networkstatic/iperf3","Support":"https://forums.unraid.net/topic/130827-support-kilrahiperf3/","Project":"https://iperf.fr/","DonateLink":"","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-IPerf3.xml"},"Mosquitto":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"","icon":"/state/plugins/dynamix.docker.manager/images/Mosquitto-icon.png","shell":"sh","registry":"https://hub.docker.com/_/eclipse-mosquitto","Support":"https://github.com/simonsickle/unraid-templates/discussions/categories/q-a-support","Project":"https://mosquitto.org","DonateLink":"https://cash.app/$ssickle","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-Mosquitto.xml"},"NodeRed":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"http://10.0.0.3:1880","icon":"/state/plugins/dynamix.docker.manager/images/NodeRed-icon.png","shell":"sh","registry":"https://hub.docker.com/r/nodered/node-red/","Support":"http://forums.unraid.net/index.php?topic=38486.0","Project":"https://nodered.org","DonateLink":"","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-NodeRed.xml"},"OpenSpeedTest":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"http://10.0.0.3:3000","icon":"/state/plugins/dynamix.docker.manager/images/OpenSpeedTest-icon.png","shell":"sh","registry":"https://hub.docker.com/repository/docker/openspeedtest/latest","Support":"http://openspeedtest.com/Contact-us.php","Project":"http://openspeedtest.com/","DonateLink":"https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=TY2D56BYPKEXU","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-OpenSpeedTest.xml"},"Unifi":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"https://10.0.0.3:10000","icon":"/state/plugins/dynamix.docker.manager/images/Unifi-icon.png","shell":"bash","registry":"https://github.com/orgs/linuxserver/packages/container/package/unifi-controller","Support":"https://github.com/linuxserver/docker-unifi-controller/issues/new/choose","Project":"https://www.ubnt.com/enterprise/#unifi","DonateLink":"https://www.linuxserver.io/donate","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-Unifi.xml"},"Zigbee2MQTT":{"running":false,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"http://[IP]:[PORT:9442]/","icon":"/state/plugins/dynamix.docker.manager/images/Zigbee2MQTT-icon.png","shell":false,"registry":"https://hub.docker.com/r/koenkk/zigbee2mqtt/","Support":"https://forums.unraid.net/topic/72033-support-digiblurs-docker-template-repository/","Project":"https://github.com/koenkk/zigbee2mqtt","DonateLink":"https://www.paypal.me/digiblurDIY","ReadMe":"","updated":"true","template":"/boot/config/plugins/dockerMan/templates-user/my-Zigbee2MQTT.xml"},"HomeAssistant":{"running":true,"paused":false,"autostart":true,"cpuset":"2,3,4,5,8,9,10,11","url":"http://10.0.0.3:8123","icon":"/state/plugins/dynamix.docker.manager/images/HomeAssistant-icon.png","shell":"bash","registry":"https://github.com/orgs/linuxserver/packages/container/package/homeassistant","Support":"https://github.com/linuxserver/docker-homeassistant/issues/new/choose","Project":"https://www.home-assistant.io/","DonateLink":"https://www.linuxserver.io/donate","ReadMe":"","updated":"false","template":"/boot/config/plugins/dockerMan/templates-user/my-HomeAssistant.xml"}}} Also an aside, "veriosn" should be "version", no ? edit: ah this is an unraid thing, not a folder.view plugin thing.

(6.12.3) I've had it 3 times now that on 2 diffrent servers that it has been disabled and is listed under Plugin File Install Errors. /boot/config/plugins-error/folder.view.plg

When installing RedmineX CK Editr (free) plugin for Redmine, it requires a bundle install & migration command: Installation info which will throw an issue with mimemagic, which I resolved by adding FREEDESKTOP_MIME_TYPES_PATH variable pointing to a freedesktop.org.xml file. this now causes another issue, any help to point me in the right direction? : /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/callbacks.rb:25:in `on_file_autoloaded': expected file /usr/local/bundle/bundler/gems/rich-f5b5b07f10af/app/inputs/rich_input.rb to define constant RichInput, but didn't (Zeitwerk::NameError) raise Zeitwerk::NameError.new("expected file #{file} to define constant #{cpath}, but didn't", cref.last) ^^^^^ from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:31:in `require' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/helpers.rb:135:in `const_get' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/helpers.rb:135:in `cget' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:169:in `block in actual_eager_load_dir' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/helpers.rb:40:in `block in ls' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/helpers.rb:25:in `each' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/helpers.rb:25:in `ls' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:164:in `actual_eager_load_dir' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:17:in `block (2 levels) in eager_load' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:16:in `each' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:16:in `block in eager_load' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:10:in `synchronize' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader/eager_load.rb:10:in `eager_load' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader.rb:296:in `block in eager_load_all' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader.rb:294:in `each' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/loader.rb:294:in `eager_load_all' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/application/finisher.rb:133:in `block in <module:Finisher>' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/initializable.rb:32:in `instance_exec' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/initializable.rb:32:in `run' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/initializable.rb:61:in `block in run_initializers' from /usr/local/lib/ruby/3.1.0/tsort.rb:228:in `block in tsort_each' from /usr/local/lib/ruby/3.1.0/tsort.rb:350:in `block (2 levels) in each_strongly_connected_component' from /usr/local/lib/ruby/3.1.0/tsort.rb:431:in `each_strongly_connected_component_from' from /usr/local/lib/ruby/3.1.0/tsort.rb:349:in `block in each_strongly_connected_component' from /usr/local/lib/ruby/3.1.0/tsort.rb:347:in `each' from /usr/local/lib/ruby/3.1.0/tsort.rb:347:in `call' from /usr/local/lib/ruby/3.1.0/tsort.rb:347:in `each_strongly_connected_component' from /usr/local/lib/ruby/3.1.0/tsort.rb:226:in `tsort_each' from /usr/local/lib/ruby/3.1.0/tsort.rb:205:in `tsort_each' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/initializable.rb:60:in `run_initializers' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/application.rb:391:in `initialize!' from /usr/src/redmine/config/environment.rb:16:in `<top (required)>' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require' from /usr/local/bundle/gems/zeitwerk-2.6.6/lib/zeitwerk/kernel.rb:38:in `require' from /usr/local/bundle/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in `block in require' from /usr/local/bundle/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:299:in `load_dependency' from /usr/local/bundle/gems/activesupport-6.1.7/lib/active_support/dependencies.rb:332:in `require' from config.ru:3:in `block in <main>' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/builder.rb:116:in `eval' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/builder.rb:116:in `new_from_string' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/builder.rb:105:in `load_file' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/builder.rb:66:in `parse_file' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/server.rb:349:in `build_app_and_options_from_config' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/server.rb:249:in `app' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/server.rb:422:in `wrapped_app' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/server.rb:312:in `block in start' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/server.rb:379:in `handle_profiling' from /usr/local/bundle/gems/rack-2.2.4/lib/rack/server.rb:311:in `start' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/commands/server/server_command.rb:39:in `start' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/commands/server/server_command.rb:144:in `block in perform' from <internal:kernel>:90:in `tap' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/commands/server/server_command.rb:135:in `perform' from /usr/local/bundle/gems/thor-1.2.1/lib/thor/command.rb:27:in `run' from /usr/local/bundle/gems/thor-1.2.1/lib/thor/invocation.rb:127:in `invoke_command' from /usr/local/bundle/gems/thor-1.2.1/lib/thor.rb:392:in `dispatch' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/command/base.rb:69:in `perform' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/command.rb:48:in `invoke' from /usr/local/bundle/gems/railties-6.1.7/lib/rails/commands.rb:18:in `<top (required)>' from bin/rails:4:in `require' from bin/rails:4:in `<main>' Use `bundle info [gemname]` to see where a bundled gem is installed. Post-install message from paperclip: ################################################## # NOTE FOR UPGRADING FROM 4.3.0 OR EARLIER # ################################################## Paperclip is now compatible with aws-sdk-s3. If you are using S3 storage, aws-sdk-s3 requires you to make a few small changes: * You must set the `s3_region` * If you are explicitly setting permissions anywhere, such as in an initializer, note that the format of the permissions changed from using an underscore to using a hyphen. For example, `:public_read` needs to be changed to `public-read`. For a walkthrough of upgrading from 4 to *5* (not 6) and aws-sdk >= 2.0 you can watch http://rubythursday.com/episodes/ruby-snack-27-upgrade-paperclip-and-aws-sdk-in-prep-for-rails-5 => Booting Puma => Rails 6.1.7 application starting in production => Run `bin/rails server --help` for more startup options W, [2022-11-17T17:09:16.058434 #1] WARN -- : Creating scope :system. Overwriting existing method Enumeration.system. W, [2022-11-17T17:09:16.211994 #1] WARN -- : Creating scope :sorted. Overwriting existing method User.sorted. W, [2022-11-17T17:09:16.291201 #1] WARN -- : Creating scope :sorted. Overwriting existing method Group.sorted. Exiting

Could you elaborate how you managed to do this ?

In my case, I got an old 2012 APC SMT1500I HWID=18 model for free, just needed to replace the battery. The firmware on there was 8.3, which has no ModBus option. However, APC added it with firmware 9.1 so I had to disconnect the ups from my server, attach it to my Windows PC via the USB A->B cable and run the APC firmware upgrade wizard: Smart-UPS Firmware Upgrade Wizard v4.2.0 - APC USA (you could also this this via a VM if needed) Running the wizard will automatically detect your ups firmware & model and will ask you to select a firmware file to upload. Clicking the browse/select button will take you to the "FirmwareFiles" subfolder of the wizard which has all of the latest firmwares for all compatible devices. The only file that is visible will be the one you need, so it's pretty idiot proof. After updating it will reboot a bunch and you should now be able to select & enable the modbus option in the configuration submenu AFTER you have set the menu display type to advanced, otherwise the option will be hidden.

First of all, sorry that I didn't see your post sooner. I just stumbled on it when checking the thread for activity yesterday. To check if there was any issue with the latest Confluence release I updated to the latest image. I've been putting it off since if it ain't broken, don't fix it. Yet I wanted to see if I could replicate your issue. So for me I jumped a lot of versions: 7.5.0 on May 27, 2020 >> 7.11.1 on Mar 09, 2021 When doing sensitive updates like this I usually backup the appdata, database & perform a backup in confluence. I also create a new docker container using the old one as a template and update that one rather than overwriting/upgrading my existing one just so I have an easy road back when things don't work out as expected. For me the upgrade went smoothly, it just nagged about increasing the max connections for my database connection, which I did shortly afterwards. If you have auto update on for your docker container you might want to turn that off since if you're using confluence, it will most likely be used in a mission critical situation. Have you tried to start it since or have you tried to create another docker container (clean, don't reuse appdata or database) using the latest image ? Worst case you can try do extract all data and migrate it to a fresh instance.

So any attempt at login / password does not work anymore. Removing the config folder/files & setting the default login & password in the container variables had no effect. Seems very broken to me...

Upon reboot, photostructure won't start anymore: {"fatal":true,"exit":true,"status":12,"pid":13,"ppid":6,"error":"Library.setup() failed¹: Error: Library is already opened by 66eeaf175a5a (sync:194) (library setup)¹⁶²"} Deleting the Library & Backup folders seem to have fixed this. Is this a permission issue ? Also, processing of /pictures takes forever. There are only 163 files in there, mixed .NEF, .xmp & .jpg files.

Cool, nice to see that there are people out there that want Jira on Unraid I'll update the Github Documentation page with a lowercase disclaimer & the letcencrypt proxy-conf for good measure.

Updated Nextcloud, now refuses to connect. Log seems to indicate stuck in Upgrade. Initializing nextcloud 20.0.1.1 ... Upgrading nextcloud from 20.0.0.9 ... Workaround: Deleting appdata and going through setup again

Overview: Confluence for Unraid Application Site: https://www.atlassian.com/software/confluence Docker Hub: https://hub.docker.com/r/atlassian/confluence-server/ ▶️ GitHub & Documentation: https://github.com/Zerreth/UnraidConfluence Please post any questions/issues relating to this docker you have in this thread. 🔗 Also check out my Jira Unraid Docker App

Overview: Jira for Unraid Application Site: https://www.atlassian.com/software/jira Docker Hub: https://hub.docker.com/r/atlassian/jira-software ▶️ GitHub & Documentation: https://github.com/Zerreth/UnraidJira Please post any questions/issues relating to this docker you have in this thread. 🔗 Also check out my Confluence Unraid Docker App