Interstellar

Sorry, stupid mistake not including them... here you go: Seems to be running the scripts, I'll run them again once its started... Mar 30 13:32:44 eaf70ed4c604 syslog-ng[14]: EOF on control channel, closing connection; *** Running /etc/my_init.d/20_apt_update.sh... Hit:1 http://archive.ubuntu.com/ubuntu xenial InRelease Get:2 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB] Get:4 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [102 kB] Get:5 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages [962 kB] Get:6 http://archive.ubuntu.com/ubuntu xenial-updates/universe amd64 Packages [792 kB] Fetched 2060 kB in 3s (650 kB/s) Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. *** Running /etc/my_init.d/30_gen_ssl_keys.sh... using existing keys in "/config/keys" *** Running /etc/my_init.d/40_firstrun.sh... File zm.conf already exists Using existing ssmtp configuration Using existing mysql database Using existing skins directory Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp no crontab for root Setting shared memory to : 50% of 16456852 bytes Starting services * Starting MariaDB database server mysqld ...done. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[474]: Upgrading MySQL tables if necessary. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysql' as: /usr/bin/mysql Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[478]: This installation of MySQL is already upgraded to 10.0.34-MariaDB, use --force if you still need to run mysql_upgrade Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[485]: Checking for insecure root accounts. Mar 30 13:32:51 eaf70ed4c604 /etc/mysql/debian-start[489]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Database already at version 1.30.4, update aborted. Freshening configuration in database Loading config from DB Saving config to DB * Starting Apache httpd web server apache2 * Starting ZoneMinder: Mar 30 13:33:11 eaf70ed4c604 zmdc[572]: ERR ['zmc -m 1' exited abnormally, exit status 255] Mar 30 13:33:11 eaf70ed4c604 zmeventnotification[612]: INF [Push enabled via FCM] success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (Skipping @reboot jobs -- not system startup) success *** Running /etc/rc.local... *** Booting runit daemon... *** Runit started as PID 642 Mar 30 13:33:12 eaf70ed4c604 cron[645]: (CRON) INFO (pidfile fd = 3) Edit: OK, ran the following after start: chown -R root:www-data /var/cache/zoneminder chmod -R go+rw /var/cache/zoneminder And it works. So it begs the question, what is changing the permissions after start?

Hi, Sadly no dice. Creates the events/images/temp folders and then nothing. Restarted it a few times and tried it using the default setup, to an array disk, to the cache disk and finally to my intended out-of-array disk. Nothing works. From the docker side: root@eaf70ed4c604:/var/cache/zoneminder# ls -al total 0 drwxrwxrwx 5 root www-data 46 Mar 30 09:26 . drwxr-xr-x 1 root root 70 Mar 14 23:42 .. drwxr-xr-x 2 root www-data 6 Mar 29 18:44 events drwxr-xr-x 2 root www-data 6 Mar 29 18:44 images drwxr-xr-x 2 root www-data 6 Mar 29 18:44 temp From the server side: root@UnRAID:/mnt/disks/CCTV1/Front_Door# ls -al total 0 drwxrwxrwx 5 root sshd 46 Mar 30 09:26 ./ drwxrwxrwx 3 root sshd 24 Mar 29 18:38 ../ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 events/ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 images/ drwxr-xr-x 2 root sshd 6 Mar 29 18:44 temp/ Is that right?

I've also got the "web_php[9233]: ERR [Cannot write to content dirs('events','images'). Check that these exist and are owned by the web account user]" error... /config <-> /mnt/cache/appdata/Zoneminder /var/cache/zoneminder <-> /mnt/cache/appdata/Zoneminder/data This is a default install (bar changing the unraid side of things as I don't use /mnt/user/appdata...) From within the docker: oot@03fff72fd46e:/# ls -l /var/cache/zoneminder/ total 0 drwxr-xr-x 2 root www-data 6 Mar 29 18:47 events drwxr-xr-x 2 root www-data 6 Mar 29 18:47 images drwxr-xr-x 2 root www-data 6 Mar 29 18:47 temp From the docker log... Mar 29 18:55:04 03fff72fd46e zmwatch[9307]: ERR [Error getting last capture time for Front-Door] Mar 29 18:55:04 03fff72fd46e zmwatch[9307]: INF [Restarting analysis daemon for Front-Door] Mar 29 18:55:04 03fff72fd46e zmdc[9262]: INF ['zma -m 1' starting at 18/03/29 18:55:04, pid = 9472] Mar 29 18:55:04 03fff72fd46e zmdc[9472]: INF ['zma -m 1' started at 18/03/29 18:55:04] Mar 29 18:55:04 03fff72fd46e zma_m1[9472]: ERR [Can't make events/1: Permission denied] Mar 29 18:55:04 03fff72fd46e zma_m1[9472]: FAT [Can't symlink '1' to 'Front-Door': Permission denied] Mar 29 18:55:04 03fff72fd46e zmdc[9262]: ERR ['zma -m 1' exited abnormally, exit status 255] Mar 29 18:55:07 03fff72fd46e zmeventnotification[9295]: INF [Broadcasting new events to all 0 websocket clients] Mar 29 18:55:07 03fff72fd46e zmeventnotification[9295]: INF [Broadcasting new events to all 0 websocket clients] Mar 29 18:55:12 03fff72fd46e zmeventnotification[9295]: INF [Broadcasting new events to all 0 websocket clients] Mar 29 18:55:13 03fff72fd46e zmc_m1[9365]: INF [Front-Door: 5000 - Capturing at 25.00 fps] Otherwise it works...!

Bumping this because it’s desperately needed for those running pfsense and the like.

Dunno what it is but it just isn’t happy. Just going to pull the drives and do a rebuild - only 4 hours as it only needs to do half the array.

Regarding the clearing an array drive script - why is it so slow (even with reconstruct write on?) Doing dd bs=4M if=/dev/zero of=test to a mounted disk = max disk speed (~130MB/sec) dd bs=1M if=/dev/zero of=/dev/md7 results in ~2MB/sec. There should be no difference? Take years to clear 2TB drive at 2MB/sec!

Has the way this works changed recently? CCC is now backing up files it thinks have changed on the server but in reality haven't (the Archived file has today's time and date) so every time I backup it backs up a new set of files!!? Something has completely buggered up my backups to UnRAID.

Can someone clarify something for me regarding the way this plugin works. I assume that from a 'client' PoV (i.e. my mac) doesn't see any of the extended attributes that contains the checksum, so that my backup software isn't going to have a fit and see all the data has changed? Short version: The checksum info is only visible to the server, not to clients? I always previously wanted the checksums to go to a file, but I suppose if I move data around the attributes would follow the files and thus checksums would never be lost? Thanks!

Last restarted on the 31-07-2016 IIRC.

All A-OK here. Last backup 3.9 days ago to a friends server (we host each others backups), 2.2TB to his, 1TB to mine.

Hey Interstellar, did you end up figuring this out? Sadly no - I'm assuming that you can specify a variable with this but from my 15 mins of searching and tinkering, nothing bar changing the actual run.conf results in increased memory limits. gfjardim or some other clever docker owner may be able to work this out?

True - however, the original preclear script works perfectly every time, the 'beta' script crashes with OOM errors on my box. Why does the new script require so much memory!? I'd be concerned if it was using more than 200-300MB!

Gone back to the original 'faster preclear' script with the sed mod as it works. No output in any log to suggest why the beta just doesnt work on my system - manually running it from the command line results in the ./preclear_disk.sh: fork: Cannot allocate memory error. Again, nothing in any log. If it aint broke...!

Same issue! Nothing in the logs at all. Edit: Running the script manually results in preclear_disk.sh: fork: Cannot allocate memory Edit 2: Closed a few dockers - now running... (only will work from the command line but GUI updates...) Nothing in any logs!? Edit 3: Crashed 8 hours in with: ./preclear_disk.sh: fork: Cannot allocate memory ./preclear_disk.sh: fork: Cannot allocate memory Never had this before!? Edit 4: Closed crashplan docker (which was using 1.5GB or so) and now it has almost run to completion. Why on earth is preclear requiring so much memory!?

Has anyone managed to change 'run.conf' to increase the memory and keep it that way? I keep increasing it to >2GB but something resets it at some point resulting it **** upload speeds.. How can we set it to change this value every time crashplan docker restarts? Cheers!

I think I got all I need for the supermicro x9 & x10 boards. There's really only three settings for your board so far. I'll have to go back a few pages and re read to be sure. But there's low, normal and high. I'll just need some time to put together the fan settings page for your board and add a section to the ipmifan script. Looking forward to it If my board can't do proportional control it would be nice if a disk gets over say, 35C, it turns to medium and then 40C up to high! Edit: Using the command a few pages back it seems all I have is minimum and maximum (00 min, 01 max). Suppose it will have to do, better than nothing.

Thanks for this plugin - works a treat bar saying my board isn't supported for Fan control. This would actually be VERY useful because the BMC default is rubbish - as someone said above the CPU temp isn't in line with disk temps (esp during a parity check!) My board is a Supermicro X10SLL-F, what do you need from me/do I need to do to make this work? Cheers!

If you're using 6.2, you need to map the drive with the "slave" option (but then it will need to be mounted within /mnt/disks) If your not using 6.2, then you have to stop the entire docker service (not just crashplan) and then restart it for any app to see the mapping Thanks. Found the answer just before seeing this!! Working a treat now

Any ideas on this one guys: I mounted a (empty) xfs drive at /mnt/crashplan and added that to the docker as /Write and /mnt/crashplan. Problem comes to writing to it - crashplan simply wont, instead writing to 'cache' which eventually fills up and crashes it. Tried root:root and nobody:user permissions, ln -s to a folder where I know it writes to (E.g. if I point /Write to /mnt/cache/Data it works!?!). I've even started the archive creation off on the cache disk, stopped it, moved it to /mnt/crashplan where it sees the archive but then can't write to it even when selected as 'Read/Write' I don't understand why this isn't working - any ideas why the crashplan docker plainly refuses to write to a manually mounted disk!?

Just installed the system temp and system stats plugins. The latter works fine but the sensors one doesn't work. I click detect, it gets 'coretemp jc42', hit save. Options for sensors come up - select my CPU temp and MB temp (both showing temps) - hit save and then the sensor selection goes blank! I get an error 'Error: File /etc/sensors.d/sensors.conf, line 4: undeclared bus ID referenced' over and over in the console. X10SLL-F Supermicro. I'll try the method listed a few pages back later, but whatever this issue is needs to be fixed for ease of use!

Same here... nothing in the log either!

Supplied GUI - Offical 'Stable' GUI. webGUI on Github - 'beta/testing' GUI. SimpleFeatures - User made GUI - no longer works on 5 stable and later (properly) Bottom line is the supplied GUI is the supported one, above and beyond that it is down to you what you use.

Should cache_dirs help when loading drives via AFP? I only ask because via SMB my "Films" folder shows instantly but takes a few seconds for AFP to show anything. Ideas? Also, given I have 4Gb memory and don't really have anything running in the background apart from PS3 MS which uses a max of 600MB, can I get cache_dirs to use more of it? Cheers!