chaosratt

Here's my setup. I've adjusted a few settings here and there. Gives very nice data you can put into a graph:

How do I get userparameter support with this? I updated my unraid from an older version and my locally "installed" version of the stand-alone agent segfaults on launch now. Switching to this container works, but I cannot seem to figure out how to get all my custom userparameter scripts over for monitoring individual disks.

Is there any reason why on Sunday (the 1st) this, and only this, docker seems to have just poofed out of existence? No longer appears in my docker list, and cant find it by searching. Had all my apps working off of it just fine, then noticed that I hadn't been downloading anything in a week and found this docker just missing.

I just wanted to chime in here on a fix for the the container seeming to not start properly. There's no need to do a full appdata rollback usually. Log into the container: docker exec -ti mariadb /bin/bash run mysqld from the commandline and you'll get a full dump of what's wrong. It's likely *not* a corrupt database, but rather a transaction stuck in a partially completed state: root@dc9091e5cc9e:/# mysqld blah blah blah blah InnoDB: Transaction 133548158 was in the XA prepared state. InnoDB: 1 transaction(s) which must be rolled back or cleaned up InnoDB: in total 0 row operations to undo InnoDB: Trx id counter is 205501440 2017-12-01 21:37:20 47062243925760 [Note] InnoDB: 128 rollback segment(s) are active. 2017-12-01 21:37:20 47063031092992 [Note] InnoDB: Starting in background the rollback of recovered transactions 2017-12-01 21:37:20 47063031092992 [Note] InnoDB: Rollback of non-prepared transactions completed 2017-12-01 21:37:20 47062243925760 [Note] InnoDB: Waiting for purge to start 2017-12-01 21:37:20 47062243925760 [Note] InnoDB: Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 72011254996 2017-12-01 21:37:20 47062243925760 [Note] Plugin 'FEEDBACK' is disabled. 2017-12-01 21:37:20 47063066740480 [Note] InnoDB: Dumping buffer pool(s) not yet started 2017-12-01 21:37:20 2acd8854df00 InnoDB: Starting recovery for XA transactions... 2017-12-01 21:37:20 2acd8854df00 InnoDB: Transaction 133548158 in prepared state after recovery 2017-12-01 21:37:20 2acd8854df00 InnoDB: Transaction contains changes to 8 rows 2017-12-01 21:37:20 2acd8854df00 InnoDB: 1 transactions in prepared state after recovery 2017-12-01 21:37:20 47062243925760 [Note] Found 1 prepared transaction(s) in InnoDB 2017-12-01 21:37:20 47062243925760 [ERROR] Found 1 prepared transactions! It means that mysqld was not shut down properly last time and critical recovery in formation (last binlog or tc.log file) was manually deleted after a crash. You have to start mysqld with --tc-heuristic-recover switch to commit or rollback pending transactions. 2017-12-01 21:37:20 47062243925760 [ERROR] Aborting Your choice is to "hulk smash" the partial transaction through, or revert it like it never happened. Both have potential consequences. mysqld --tc-heuristic-recover commit or mysqld --tc-heuristic-recover rollback Also, you have backups, right?

Ugh, that's basically an even more PITA way of doing the advanced_script, I understand why they don't want to support it, but still, would be nice to have a way of consistently adding packages that we might need to the image. Unless they want to go ahead and add handbrake, ffmpeg, comskip, etc now that plex has native DVR capabilities ...

SO there's no way for us to add customization to the docker (such as install handbrakecli for post-processing) that can survive an image update?

Does the 'ADVANCED_SCRIPT' variable no longer work on this container?

Is it possible to get BorgBackup added to the pack? https://borgbackup.readthedocs.io/en/stable/installation.html#standalone-binary

Unraid is 6.3.5, plugin is 2017.03.03

Not sure what just happened, but the layout tab spits this error out at me now: Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 126 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 Warning: array_key_exists() expects parameter 2 to be array, null given in /usr/local/emhttp/plugins/serverlayout/php/serverlayout_constants.php on line 165 And the data tab's historical table is empty and all the assignments are lost.

Reinstalling and deleting the folder did the trick!. I am seeing an error in the console about a missing file, path: /plugins/ipmi/images/.png. The network tab lists the initiator as "other" so I'm not sure what's requesting that.

Any way to disable the internal MYSQL server and use an external one if you already have a dedicated server and/or docker running for it?

I've also tried both Chrome & Firefox on two different computers (both Win 7).

Awesome, I know what I'm doing this weekend.

You say you use it for KVM docker, do the pools get properly mounted and unmounted at startup/shutdown?

I deleted the /boot/config/plugins/dynamix.plg file, but not the associated folder (I notice every *.plg has a matching folder) and rebooted, no change.

I do have this: https://img.computing.zone/image/lyx9

So I tried uninstalling the plugin (which was installed from the "apps" tab) and installing manually from the link in the first post. The installed version number is the same in both. No change. Syslog from today is attached. syslog.txt

I've tried it even in incognito, still happens. One thing to mention, I did move the Unraid interface off port 80, everything else works just fine, just not this IPMI plugin. Regarding which pages generate the error, both the Setting and Fan Control tab have this error whenever I click apply.

Interesting, I do now. When I replied earlier they were broken image icons.

Awesome idea, but you might want to revisit your images from the original post, they're not working now.

I'm having some issues with this plugin. It seems to be pulling the data just fine from my SuperMicro board, but I am unable to change any of its settings. The screen simply refreshes and the settings do not appear to "stick". Reviewing the Unraid logs I see this: Unraid root: error: update.php: missing csrf_token Doing some googling I see that there was a change to the webui in 6.3.0 RC that needs to be accounted for in plugins:

I'll second this, I guess I should have said that myself. If a drive has an assigned location when removed, then that should be included with the drive data in the historical listing with the other metrics that are retained.

So I've just run across a rather interesting flaw. When a drive is "removed" it is also imediatly removed from any layout settings and is only listed under historical devices. Which makes it impossible to figure out which of the 24 bays is occupied by a drive that just shat itself. If it was full I guess I could look for the empty one, but since its only half full, I guess I can just go and start yanking supposedly empty bays until I find one with a drive in it.

You will receive a notice in the "Docker" tab of Unraid under the version column. When the author updates the docker image the "up-to-date" text will change to "update available" I believe, and its a link that can be clicked to stop/update/restart the docker image. This only happens with the docker author updates the image, which is about once a week currently. The built-in updater for Radarr is disabled I believe. So you will receive a notice in the app that an update is available, but you should wait until docker reports an update.