Marv

Thanks for clarifying :)

Hi, I just noticed that on latest version the logs are not shown in the app anymore. Someone else recognized this?

Ok so I found the link from the first post in the MariaDB thread and recovered my MariaDB container from a backup. This seems to work for MariaDB, but my Nextcloud container still doesn't work. I reach the Nextcloud webUI but when logging in I get: The server was unable to complete your request. If this happens again, please send the technical details below to the server administrator. More details can be found in the server log. Technical details Remote Address: ........... Request ID: QYXatuOnTGfDt565JmdC and the container log shows: Stack trace: #0 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect() #1 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion() #2 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform() #3 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(623): Doctrine\DBAL\Connection->getDatabasePlatform() #4 /config/www/nextcloud/lib/private/DB/Connection.php(151): Doctrine\DBAL\Connection->setTransactionIsolation(2) #5 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172): OC\DB\Connection->__construct(Array, Object(Doctrine\DBAL\Driver in /config/www/nextcloud/lib/private/DB/Connection.php on line 64 [cont-finish.d] executing container finish scripts... [cont-finish.d] done. [s6-finish] syncing disks. [s6-finish] sending all processes the TERM signal. [s6-finish] sending all processes the KILL signal and exiting. [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] 10-adduser: executing... usermod: no changes What can I do here? Do I need to use the Nextcloud backup aswell? Is there anything to worry about regarding my files?

I can't reach the nextcloud webui anymore since the last container update. Nothing unusual in the logs though edit: Ok now I have something in the logs. Seems like its related to MariaDB which got updated aswell (using Linuxserver.io aswell here) The MariaDB container log repeats this 180513 13:03:15 mysqld_safe Starting mysqld daemon with databases from /config/databases 180513 13:03:18 mysqld_safe Logging to syslog. And Nextcloud shows this Stack trace: #0 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(429): OC\DB\Connection->connect() #1 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(389): Doctrine\DBAL\Connection->getDatabasePlatformVersion() #2 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(328): Doctrine\DBAL\Connection->detectDatabasePlatform() #3 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(623): Doctrine\DBAL\Connection->getDatabasePlatform() #4 /config/www/nextcloud/lib/private/DB/Connection.php(151): Doctrine\DBAL\Connection->setTransactionIsolation(2) #5 /config/www/nextcloud/3rdparty/doctrine/dbal/lib/Doctrine/DBAL/DriverManager.php(172): OC\DB\Connection->__construct(Array, Object(Doctrine\DBAL\Driver in /config/www/nextcloud/lib/private/DB/Connection.php on line 64 PHP Fatal error: Uncaught Doctrine\DBAL\DBALException: Failed to connect to the database: An exception occured in driver: SQLSTATE[HY000] [2006] MySQL server has gone away in /config/www/nextcloud/lib/private/DB/Connection.php:64 I didn't change anything in my configurations. Just updated the containers.

ahhh, thanks

Switched from the Tvheadend plugin to this container and noticed that the currently logged in user, the logout button and the available space is not shown next to the ribbons in the webUI. Is this intended or a bug in the current container version?

Do you have an update on this? Does reversing a backup works for you? I have no idea what exactly to change in the script to backup my scsi Win10 vm faster with the options you linked. A short guide would be appreciated

Hi, I'm trying to setup the following wakeup script (under point 4) with the user script plugin. https://tvheadend.org/projects/tvheadend/wiki/Wakeup I modified the path within the script to point to my tvheadend dvr location in appdata but unfortunately when testing the script I get: /tmp/user.scripts/tmpScripts/Wakeup for recordings/script: line 25: 1520374200 1520374500: syntax error in expression (error token is "1520374500") When I check with 'cat /sys/class/rtc/rtc0/wakealarm' afterwards there is a timestamp present but its completely wrong. What am I doing wrong here? Another thing: As I just set this container up.. my log is full of those entries: 2018-03-11 01:54:09.408 [ ERROR] http: 192.168.121.19: HTTP/1.1 GET /imagecache/95 -- 404 2018-03-11 01:46:14.307 [ ERROR] http: 192.168.121.10: HTTP/1.1 GET /stream/channelid -- 503 It seems to be some kind of permission thing? How can I solve this?

I'm using the plugin because you can't wake your server with the container. With this plugin my server wakes up for each recording when shutdown.

Can confirm that all is working again. Thanks a lot

there you go $ ls -al /usr/local/emhttp/plugins/ipmi /bin/ls: cannot access '/usr/local/emhttp/plugins/ipmi': No such file or directory $ ls -al /dev/ipmi0 /bin/ls: cannot access '/dev/ipmi0': No such file or directory $ ls -al /dev/ipmi/0 /bin/ls: cannot access '/dev/ipmi/0': No such file or directory $ ls -al /dev/ipmidev/0 /bin/ls: cannot access '/dev/ipmidev/0': No such file or directory $ ls -al /boot/config/plugins/ipmi/ipmi.cfg /bin/ls: cannot access '/boot/config/plugins/ipmi/ipmi.cfg': No such file or directory $ ls -al /usr/sbin/ipmisensors /bin/ls: cannot access '/usr/sbin/ipmisensors': No such file or directory $ ls -al /usr/local/emhttp/plugins/dynamix.system.temp total 16 drwxr-xr-x 5 root root 160 Aug 26 2016 ./ drwxr-xr-x 28 root root 560 Nov 18 13:54 ../ -rw-r--r-- 1 root root 287 Aug 26 2016 README.md -rw-r--r-- 1 root root 900 Aug 26 2016 TempButton.page -rw-r--r-- 1 root root 8184 Aug 26 2016 TempSettings.page drwxr-xr-x 2 root root 140 Aug 26 2016 icons/ drwxr-xr-x 2 root root 60 Aug 26 2016 images/ drwxr-xr-x 2 root root 60 Aug 26 2016 include/ $ ls -al /usr/bin/sensors -rwxr-xr-x 1 root root 22032 Nov 23 2015 /usr/bin/sensors*

I never installed the ipmi plugin I also didn't change anything in my configuration after upgrading to v6.4.0/1 Your plugin worked before without any issue detecting the sensors used by the dynamix system temp plugin. Really strange

here it is: system temp plugin running fine and ups status is also working with your app I: 2018/02/09 11:56:20 app.go:57: controlr v2.8.0-355-acff82c-v2018.02.02 starting ... I: 2018/02/09 11:56:20 app.go:65: No config file specified. Using app defaults ... I: 2018/02/09 11:56:20 core.go:73: starting service Core ... W: 2018/02/09 11:56:20 core.go:251: Error identifying sensor: open /boot/config/plugins/ipmi/ipmi.cfg: no such file or directory I: 2018/02/09 11:56:20 core.go:263: No sensor detected ... I: 2018/02/09 11:56:20 core.go:276: Created apc ups ... I: 2018/02/09 11:56:20 server.go:70: Starting service Server ... I: 2018/02/09 11:56:20 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/02/09 11:56:20 server.go:139: Server started listening https on :2378 I: 2018/02/09 11:56:20 api.go:46: Starting service Api ... I: 2018/02/09 11:56:20 api.go:90: Api started listening https on :2382 I: 2018/02/09 11:56:20 app.go:85: Press Ctrl+C to stop ... I: 2018/02/09 14:05:59 app.go:89: Received signal: (terminated) ... shutting down the app now ... I: 2018/02/09 14:05:59 api.go:105: stopped service Api ... I: 2018/02/09 14:05:59 server.go:156: stopped service Server ... I: 2018/02/09 14:05:59 core.go:141: stopped service Core ... I: 2018/02/09 14:56:20 app.go:57: controlr v2.8.0-355-acff82c-v2018.02.02 starting ... I: 2018/02/09 14:56:20 app.go:65: No config file specified. Using app defaults ... I: 2018/02/09 14:56:20 core.go:73: starting service Core ... W: 2018/02/09 14:56:20 core.go:251: Error identifying sensor: open /boot/config/plugins/ipmi/ipmi.cfg: no such file or directory I: 2018/02/09 14:56:20 core.go:263: No sensor detected ... I: 2018/02/09 14:56:20 core.go:276: Created apc ups ... I: 2018/02/09 14:56:20 server.go:70: Starting service Server ... I: 2018/02/09 14:56:20 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/02/09 14:56:20 server.go:139: Server started listening https on :2378 I: 2018/02/09 14:56:20 api.go:46: Starting service Api ... I: 2018/02/09 14:56:20 api.go:90: Api started listening https on :2382 I: 2018/02/09 14:56:20 app.go:85: Press Ctrl+C to stop ... I: 2018/02/09 17:24:56 api.go:134: received /info I: 2018/02/09 17:24:56 api.go:142: info({Version:2 Wake:{Mac:78:24:af:3b:1f:a9 Broadcast:255.255.255.255} Prefs:{Number:., Unit:C} Samples:[{Key:UPS STATUS Value:Online Unit: Condition:green} {Key:UPS LOAD Value:26.0 Unit:% Condition:green} {Key:UPS CHARGE Value:100.0 Unit:% Condition:green} {Key:UPS LEFT Value:17.0 Unit:m Condition:green} {Key:UPS POWER Value:140.4 Unit:w Condition:green}] Features:map[sleep:true]}) I: 2018/02/09 17:24:57 api.go:110: log (system) requested

Many thanks for your work. Everything working again for me except I don't get my fan speeds and temperatures shown anymore in the app. This worked before unraid 6.4.0. Not sure if I need to change something now in my system temp plugin or where is the data for your plugin comming from?

So I tested with the above command and the files I moved from cache to array and back to cache again still have hash values saved with them. Is there an easy way to remove them without having to move them back to the array?

nice, I'll test this later. Thanks.

yeah, I know that it doesn't care about cache files. But as the files were moved to the array the plugin created hash values as it should of course. Can I test by just copying over some files from my cache drive to an excluded array folder and then use the clean functon to see if the hash values were saved or not after moving?

Hi, today I replaced my cache drive by moving my cache shares onto the array and back again to the new cache drive after I assigned it. Unfortunately, I forgot that by doing so I generated hash values for all of my cache files at the moment they were moved to one of my data disks. Now, what would be the best way to get rid of the hash values again as the files are placed on my cache drive again right now. Does it even matter? Somehow that disturbs me

without UPS I: 2018/01/29 19:15:30 app.go:57: controlr v2.7.4-327-33467cd-v2018.01.29 starting ... I: 2018/01/29 19:15:30 app.go:65: No config file specified. Using app defaults ... I: 2018/01/29 19:15:30 app.go:201: debug:cert(certificate_bundle.pem) I: 2018/01/29 19:15:30 app.go:150: debug:secure(true):cert(certificate_bundle.pem):usessl(auto):version(6.4.0) I: 2018/01/29 19:15:30 app.go:166: debug:secure(true):cert(certificate_bundle.pem):usessl(auto):version(6.4.0) I: 2018/01/29 19:15:30 app.go:186: debug:host(https://127.0.0.1:442/) I: 2018/01/29 19:15:30 core.go:73: starting service Core ... I: 2018/01/29 19:15:30 core.go:82: debug:getting mac/prefs/features I: 2018/01/29 19:15:30 core.go:88: debug:creating plugins I: 2018/01/29 19:15:30 core.go:264: debug:created system sensor I: 2018/01/29 19:15:30 core.go:294: debug:no ups detected I: 2018/01/29 19:15:30 core.go:93: debug:getting samples I: 2018/01/29 19:15:30 utils.go:175: debug:executing:(/usr/bin/sensors):([-A]) I: 2018/01/29 19:15:30 core.go:96: debug:sensor samples:([{FAN 344 rpm neutral} {BOARD +33.5 C neutral} {CPU +35.0 C neutral}]) I: 2018/01/29 19:15:30 core.go:99: debug:ups samples:([]) I: 2018/01/29 19:15:30 server.go:70: Starting service Server ... I: 2018/01/29 19:15:30 server.go:89: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/01/29 19:15:30 server.go:139: Server started listening https on :2378 I: 2018/01/29 19:15:30 api.go:46: Starting service Api ... I: 2018/01/29 19:15:30 api.go:90: Api started listening https on :2382 I: 2018/01/29 19:15:30 app.go:85: Press Ctrl+C to stop ... with UPS enabled I: 2018/01/29 19:15:39 app.go:57: controlr v2.7.4-327-33467cd-v2018.01.29 starting ... I: 2018/01/29 19:15:39 app.go:65: No config file specified. Using app defaults ... I: 2018/01/29 19:15:39 app.go:201: debug:cert(certificate_bundle.pem) I: 2018/01/29 19:15:39 app.go:150: debug:secure(true):cert(certificate_bundle.pem):usessl(auto):version(6.4.0) I: 2018/01/29 19:15:39 app.go:166: debug:secure(true):cert(certificate_bundle.pem):usessl(auto):version(6.4.0) I: 2018/01/29 19:15:39 app.go:186: debug:host(https://127.0.0.1:442/) I: 2018/01/29 19:15:39 core.go:73: starting service Core ... I: 2018/01/29 19:15:39 core.go:82: debug:getting mac/prefs/features I: 2018/01/29 19:15:39 core.go:88: debug:creating plugins I: 2018/01/29 19:15:39 core.go:264: debug:created system sensor I: 2018/01/29 19:15:39 core.go:285: debug:created apc ups I: 2018/01/29 19:15:39 core.go:93: debug:getting samples I: 2018/01/29 19:15:39 utils.go:175: debug:executing:(/usr/bin/sensors):([-A]) I: 2018/01/29 19:15:39 core.go:96: debug:sensor samples:([{FAN 346 rpm neutral} {BOARD +33.5 C neutral} {CPU +34.0 C neutral}]) I: 2018/01/29 19:15:39 utils.go:175: debug:executing:(/sbin/apcaccess):([])

sorry for the delay. I: 2018/01/29 13:13:42 app.go:57: controlr v2.7.3-323-f049c44-v2018.01.26 starting ... I: 2018/01/29 13:13:42 app.go:65: No config file specified. Using app defaults ... I: 2018/01/29 13:13:42 core.go:73: starting service Core ...

Hi, I'm not able to start the server plugin since upgrading to v6.4.0. Just tried v2.7.3.... still no success.

same problem here

Hi Mettbrot, the plugin isn‘t starting with the latest release anymore. Had to revert back to 4.2.4-10

I solved this issue by adding the following lines to my nextcloud nginx cfg under appdata/nextcloud/nginx/site-confs/default # Fetch forwarded remote IP address instead of IP address of docker0 bridge interface real_ip_header X-Forwarded-For; set_real_ip_from 172.17.0.0/16; real_ip_recursive on; this way you can leave brutforce enabled if you're not using fail2ban, which works for me aswell now