Jump to content

page3

Members
  • Content Count

    120
  • Joined

  • Last visited

Community Reputation

2 Neutral

About page3

  • Rank
    Advanced Member

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. My Raspberry Pi install of Pihole failed last night due to a corrupted SD card, but I was able to get Pihole back up and running within 5 minutes using this docker. Thank you! The instructions on page 1 of this thread (and also the cron post further down) are a bit confusing in light of version 2. Apart from installing and configuring the docker, is there any other set-up/maintenance necessary? Is the cron still necessary? Are updates done via the docker update mechanism or from within the docker with PiHole -up?
  2. That an interesting observation and one I hadn’t considered. I swap between external drives, taking one offsite so the window of attack is lessoned, if not eliminated. I’ll have to consider if I change my backup practice, or if I’m willing to take the (small imho) risk. Thanks for the clarification.
  3. Essential plugin that's given me years of hassle-free use... I have an external (USB) Segate drive that I use with Duplicati for backups. It is mounted via Unassigned Devices and spins up when a backup is executed and down again after. All is well. I have a new WD MyBook (8tb USB) drive I want to use in the same way. However, it is being temperamental in spinning down when not required. By default the WD has its own power management and APM is set to off. If I use hdparm to set the timeout and enable APM it works for a bit, then resets itself (seemingly randomly after an hour or so, I know it would on server reboot). If I use the built in WD power management it spins down as instructed, but up again at random times. The drive is not being accessed as I only use it for backups at 4am. If I go to the web UI "main" page at any time I always get a pause on the Unassigned Devices section while the drive spins up. The Segate drive behaves perfectly and doesn't do this. Anyway, I'm not expecting a magical solution to this, but with a bit of help I think I have a workaround. If I unmount the device it seems to stay spun-down. I've searched but cannot find a way to mount (and unmount) via the command line. I'm sure it must be possible. I could then add a pre (and post) Duplicati script to mount before a backup and unmount after, which should sort things. Any help with the command I could use to mount (a previously configured drive in Unassigned Devices) would be really helpful. Thanks.
  4. I don't get this comment. It's a backup. It may not be offsite, but it's definitely a backup! Anyway, I have a WD MyBook USB drive attached to my box for on-site backups. It's mounted via Unassigned Devices and backup is via Duplicati (with one backup kicking off each night). I want it spun down the rest of the time. I've found the following works: hdparm -B 127 /dev/sdb hdparm -S 12 /dev/sdb First command switches on power-management. Second sets spin down to 2 minutes. I've had the put these commands in /boot/config/go as they don't persist after a reboot. I've also found that viewing the webUI 'main' screen spins the disk back up, which is a shame but liveable with unless anyone can suggest a way to avoid this. Interestingly I have another drive attached in exactly the same way (Segate external) and this does spin down without any of this. It also doesn't spin up as the WD does when I view the web ui so the WD must be responding to something Unassigned Devices is sending. I hope this is helpful to the OP.
  5. Have I done something stupid? I was running 5.8.30 fine. UnRAID did it's usual weekly update earlier today and now I get the following error on running the controller: "We do not support upgrading from 5.8.30." Any ideas? UPDATE: RESOLVED. Repository had reverted to stable branch. Re-added "unstable" and all is well.
  6. Wow, quick response! Unfortunately, the other docker only keeps logs within the appdata folder, everything else must be within the docker image which seems a bit unusual. This is why I'm keen to move to the Linuxserver.io one. I'm hoping I can do a config back from within the UniFi controller app (.unf file). I can then hopefully import that once I get to the Set-up screen on the UniFi controller on this docker. *** UPDATE *** Just for information. I installed the Linuxserver.io docker. Restored the .unf file from my previous docker and all is up and running in under 5 minutes. I now have my config on my cache in an accessible place, rather than from within the docker image.
  7. Hello all. If I wanted to move from the other UniFi controller docker to this one, is there a "simple" migration path? Can I simply backup my old config from within the UniFi controller app, install this docker, disable the old docker, run up this one and import my config? I'm trying to avoid having to set everything up from scratch again as it was a right pain last time! Many thanks
  8. Excellent. Thank you. One more question if I may. I have automatic backups ON. The backup goes to a backup location within the docker (see below). The docker currently maps: /var/lib/unifi -> /mnt/cache/appdata/unifi/ I thought I could simply add a new route for the backup to expose an external location to the docker, eg: /usr/lib/unifi/data/backup/autobackup -> /mnt/cache/appdata/unifi/autobackup (note the /usr rather than /var) The /var/lib/unifi seem to contain the server.log only. The /usr/lib/unifi seems to contain everything else! When starting the docker with the new path added, the UniFi controller had lost all my settings. Removing this mapping fixed things, but obviously auto backups are back to being within the docker image. I believe the question was asked back in April (by lchichiarelli) but I can't find what the resolution was. ps. Happy Christmas!
  9. A question about the UniFi Controller docker if I may. I've just purchased a USG and Pro access point. Totally new to Unify stuff so took it slowly. Installed Docker. Ran through set-up of Controller software. Followed UniFi instructions to SSH on to the USG and change the IP address to be on the same subnet as my Unraid server. Adopted the USG. Disconnected old router. Adopted access point. All great and working brilliantly. Then I was an idiot. Saw in Unraid there was a docker upgrade. Hit Upgrade. Upon returning to the controller software it appeared to be a fresh install? Wanted me to run set-up again or restore from backup. Backup? I am an idiot - no backup yet. Ok, can "transfer" to new controller using admin login/password. Idiot 2™. Safari auto-fill has screwed up my admin password so it wasn't accepted. Ok. Factory reset of both USG and Access Point. Re-install of docker. Would it adopt? Course not. After two hours SSHing in to USG, changing IP and trying to adopt I eventually restored my old router and followed the instruction AGAIN right from the beginning. Adoption fine. Hurrah. Absolutely no idea why my old router was needed, assume routing wasn't correct without it. Made a backup. Quite a few actually. So my question (see, there is one eventually) is What is the recommended update process for the UniFi controller docker? Is it backup -> update -> restore or should the controller remember its settings? I'd just like not to go through this again! Ps. Thanks for the docker. It's excellent. It's just this user who was an idiot.
  10. This looks excellent - Thank You. I am currently using Borg Backup, but this has a very nice looking UI.
  11. Just to confirm, I too have Margarita running on my Mac. Disabling it stopped the logs
  12. I also tried disabling/enabling notifications. Didn't help. Dockers: Observium Plex Transmission Plugins: statistics.sender.plg ... preclear.disk.plg ... unassigned.devices.plg ... speedtest.plg ... recycle.bin.plg ... open.files.plg ... fix.common.problems.plg ... dynamix.system.temp.plg ... dynamix.system.stats.plg ... dynamix.system.info.plg ... dynamix.ssd.trim.plg ... community.applications.plg ... ca.update.applications.plg ... ca.cleanup.appdata.plg ... NerdPack.plg ... unRAIDServer.plg ... dynamix.plg ... This is the output of my root cron, in case there is something in common: cat /etc/cron.d/root # Scheduled Monday Borg Backup: 15 3 * * 1 /mnt/cache/apps/borg/borgmonday-itunes &> /mnt/cache/apps/borg/itunes.log # Scheduled Tuesday Borg Backup: 15 3 * * 2 /mnt/cache/apps/borg/borgtuesday-photos &> /mnt/cache/apps/borg/photos.log # Scheduled Wednesday Borg Backup: 15 3 * * 3 /mnt/cache/apps/borg/borgwednesday-media &> /mnt/cache/apps/borg/media.log # Generated cron settings for plugin autoupdates 0 0 * * * /usr/local/emhttp/plugins/ca.update.applications/scripts/updateApplications.php >/dev/null 2>&1 # Generated system data collection schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null # Generated docker monitoring schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/dockerupdate.php check &> /dev/null # Generated system monitoring schedule: */1 * * * * /usr/local/emhttp/plugins/dynamix/scripts/monitor &> /dev/null # Generated mover schedule: 40 1 * * * /usr/local/sbin/mover |& logger # Generated parity check schedule: 0 1 1 * * /usr/local/sbin/mdcmd check &> /dev/null # Generated plugins version check schedule: 10 0 * * * /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugincheck &> /dev/null # Purge recycle bin at 3:00 on the first day of the week: 0 3 * * 0 /usr/local/emhttp/plugins/recycle.bin/scripts/rc.recycle.bin cron &> /dev/null # Generated speedtest schedule: 15 2 * * * /usr/sbin/speedtest-xml &> /dev/null # Generated ssd trim schedule: 0 2 * * * /sbin/fstrim -v /mnt/cache | logger &> /dev/null # Generated array status check schedule: 20 0 * * 1 /usr/local/emhttp/plugins/dynamix/scripts/statuscheck &> /dev/null Got to go to work, so can't have a further poke around until tonight...
  13. Thanks. I've checked both these thread and previously had checked all plugins were up to date, after reading about those with similar issues. I've attached diagnostics in case any kind soul is able to figure out where they're coming from. tower-diagnostics-20170215-1914.zip
  14. Since upgrading to 6.3.1 I am also seeing this error every minute: > root: error: webGui/include/Notify.php: missing csrf_token I'm not getting any other csrf_token errors. I did have the /boot/config/plugins/dynamix.plg file present, which I've since deleted and re-booted server. The issue still persists. I've checked all my Dockers and Plugins are up to date. Any suggestions? I can (of course) post diagnostics here once I'm at home in front of the server.