December 2, 201411 yr It seems that the update to the webGui has broken the docker plugin. Unable to start any of my installed containers. The Docker page now looks like the image. Kevin [Edit] All the status/log pages return blank. Please remove the DockerMan plugin under the Plugins tab. It's no longer needed (and actually causing a conflict). Perfect, solved
December 2, 201411 yr The upgrade from 10a to 12 was flawless but I too have noticed the CPU speed reported at a constant max.
December 2, 201411 yr It seems that the update to the webGui has broken the docker plugin. Unable to start any of my installed containers. The Docker page now looks like the image. Kevin [Edit] All the status/log pages return blank. Please remove the DockerMan plugin under the Plugins tab. It's no longer needed (and actually causing a conflict). Thank you. Working ok now. Kevin.
December 2, 201411 yr It seems that the update to the webGui has broken the docker plugin. Unable to start any of my installed containers. The Docker page now looks like the image. Kevin [Edit] All the status/log pages return blank. Please remove the DockerMan plugin under the Plugins tab. It's no longer needed (and actually causing a conflict). This should be added to the upgrade notes
December 2, 201411 yr Getting an email about log rotations not working: Subject: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null error: skipping "/var/log/apcupsd.events" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation.
December 2, 201411 yr I did the upgrade from 10a to 12 yesterday. I used the autoupdate function and after it finished I had to reboot. I rebooted the system but it didn't come up anymore with the message "Boot Error" on the screen. I fixed it by using "make_bootable". Just in case anyone else has this problem.
December 2, 201411 yr Getting an email about log rotations not working: Subject: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null error: skipping "/var/log/apcupsd.events" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Same here.
December 2, 201411 yr Getting an email about log rotations not working: Subject: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null error: skipping "/var/log/apcupsd.events" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Same here. Getting this as well.
December 2, 201411 yr Getting an email about log rotations not working: Subject: cron for user root /usr/bin/run-parts /etc/cron.daily 1> /dev/null error: skipping "/var/log/apcupsd.events" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/docker.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/syslog" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/vsftpd.log" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/wtmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. error: skipping "/var/log/btmp" because parent directory has insecure permissions (It's world writable or writable by group which is not "root") Set "su" directive in config file to tell logrotate which user/group should be used for rotation. Same here. Getting this as well. Me too, and the one related to sysstat reported by dlandon here. Everything else working great so far.
December 2, 201411 yr Thanks for the feedback folks. Please keep it coming. Several issues reported here have already been patched by the team!
December 2, 201411 yr It must be nice that unRAID is sending you emails True that Thanks for the feedback folks. Please keep it coming. Several issues reported here have already been patched by the team! Awesome! Good to hear! Keep up the great work!
December 2, 201411 yr SO I got the email working again... I went to the first spot "Sending email address:" and tabbed through the entire page and then I clicked save at the bottom. I clicked test and got an email. Restarted my server and I am still getting test emails. I am guessing that my ssmtp file didn't get saved properly the first time? I really wish I wasen't always the "special" one all the time
December 2, 201411 yr I restarted my server this morning. Should have I received an email? What are the triggers?
December 2, 201411 yr Please remove the DockerMan plugin under the Plugins tab. It's no longer needed (and actually causing a conflict). Are you referring to the "Docker Manager" (by gfjardim) listed in Plugins?
December 2, 201411 yr I restarted my server this morning. Should have I received an email? What are the triggers? I already asked that. No answer yet.
December 2, 201411 yr Please remove the DockerMan plugin under the Plugins tab. It's no longer needed (and actually causing a conflict). Are you referring to the "Docker Manager" (by gfjardim) listed in Plugins? Yes. The Docker Manager is built into unRAID.
December 2, 201411 yr Not sure where to report this, but since Dynamix is the new WebGUI I will place it here. If I am posting it in the wrong place let me know. On the Dashboard the Utilization percentage for the Cache drive is incorrect, this could be due to my use of a cache pool and the code is not calculating that. It shows a -293%. This was also true for the Stats page, but bonienl has already corrected that. Anyway attached is a screenshot showing the error.
December 2, 201411 yr Yes. The Docker Manager is built into unRAID. This messed up my docker tab... http://i.imgur.com/Aj0RpWm.png
December 2, 201411 yr Yes. The Docker Manager is built into unRAID. This messed up my docker tab... http://i.imgur.com/Aj0RpWm.png Goto the plugins tab and remove the dockerMan plugin from there.
December 2, 201411 yr Also, the reported memory issue that people have reported has been fixed. There is actually a tagged update available already in the webGui under Dynamix that fixes that and a few other aesthetic issues. Gotta love being able to patch things without a full release of the base OS!
December 2, 201411 yr Not sure where to report this, but since Dynamix is the new WebGUI I will place it here. If I am posting it in the wrong place let me know. On the Dashboard the Utilization percentage for the Cache drive is incorrect, this could be due to my use of a cache pool and the code is not calculating that. It shows a -293%. This was also true for the Stats page, but bonienl has already corrected that. Anyway attached is a screenshot showing the error. Odd. Can you click on the "Main" tab, then "Cache Devices", and then click on your first cache device. From that page, please copy and paste what you see under "Pool info." Thanks! - Jon
December 2, 201411 yr Also, the reported memory issue that people have reported has been fixed. There is actually a tagged update available already in the webGui under Dynamix that fixes that and a few other aesthetic issues. Gotta love being able to patch things without a full release of the base OS! So when I go to upgrade tonight by pasting that link into my gui and rebooting I will still need to go and update the GUI after everything comes back up to get the latest?
December 2, 201411 yr Also, the reported memory issue that people have reported has been fixed. There is actually a tagged update available already in the webGui under Dynamix that fixes that and a few other aesthetic issues. Gotta love being able to patch things without a full release of the base OS! So when I go to upgrade tonight by pasting that link into my gui and rebooting I will still need to go and update the GUI after everything comes back up to get the latest? From what I understand yes. This information and the critical step of having to delete certain addons (i.e. docker) should be in the OP ASAP
December 2, 201411 yr I'm seeing this same screenshot as well and I do not have the dockerman plugin listed under my plugins tab. Is there something on my flash share that I need to clean up? Yes. The Docker Manager is built into unRAID. This messed up my docker tab... http://i.imgur.com/Aj0RpWm.png Goto the plugins tab and remove the dockerMan plugin from there.
Archived
This topic is now archived and is closed to further replies.