Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About spyd4r

  • Rank


  • Location
  1. I had the same issue as well. Didn't pay too much attention as I had to drive to work and was fine when I checked later in the day.
  2. yeah, unfortunately I use it to write my Security Footage for my cameras to.
  3. twice now, i've had all my shares disappear.. no idea what's wrong or what i've changed. basically everything stops working as you'd expect. Reboot fixes it though. I was up 3 days previously since the patch no problems, not twice today i've had this issue. This diagnostic file is after they disappeared, and after array manually stopped but not yet restarted, server.lan-diagnostics-20191015-1822.zip
  4. I had my Plex DB corrupt as well. On a cache drive, on rc4.. Which I don't believe should ever happen.. I think it may have happened during the upgrade of the container overnight though.
  5. Can confirm with all 6.7.2, had appdata on array and it corrupted immediately and repeatedly. Switched to cache disk and no issues.
  6. 100%, i stuck an old 250GB SSD in mine and moved appdata to cache... no problems since.. previously I was getting corrupted every couple hours.
  7. In the glances container, how can I make it so it can save the glances.conf to appdata so I can make some custom edits?
  8. I am on 6.7.1 and db corruption continues. /mnt/user/appdata and /mnt/disk1/appdata have both suffered corruption. I have no cache disk (out of sata ports until my lsi card gets here). xfs no system crash, just running as expected. This happens frequently in Sonarr/Radarr and Plex I will update to 6.7.2 to test. not sure if it's anyway related.. But I'm seeing tons of "Waited one whole second for a busy database." in the plex console. Not sure if it was like this previously during an import of a library. Update: It happened sometime overnight, I had a few movies queued in in Radarr but it appears those completed. It corrupted sometime after. server-diagnostics-20190626-1058.zip
  9. I got it working (somewhat), i can't get the data to stay persistent in the appdata folder. It appears someone had the same issue as me and left an issue in the git repo. https://github.com/SteveMcGrath/docker-nessus_scanner/issues/5 https://hub.docker.com/r/stevemcgrath/nessus_scanner
  10. i was able to get a beta tag operational by editing /usr/lib/unifi-video/conf/mongodv3.6+.conf and changing it to engine: wiredTiger. i did this during a fresh install and then restored a backup.. it seems to have worked.. although in settings it still thinks its a 3.9.12 controller.
  11. i've tried a clean install after ditching my appdata on beta, testing and latest branches.. and none will start up from scratch on a fresh install.
  12. that didn't work for me, i just ended up rolling back to 3.9.12
  13. I used :beta on a fresh container initialization and it still didn't work correctly.. so i'm not sure. I'm don't think it needs 4.0 as I believe Unifi is still pushing 3.4 on the cloudkeys if i am not mistaken.
  14. This broke my install because of the wiredTiger changes, which i understand.. but I can't even get this to start on a fresh install with 3.10.1... I deleted all my existing folders in relation to the container.. Still no go, trying to gather logs. it appears it's using an older mongo conf file which uses mmap_v1? and the mongo install is still 3.4 but unifi is 3.10.1 root@e50858fa7931:/var/log/unifi-video# dpkg --list | grep -i mongo ii mongodb-org-server 3.4.19 amd64 MongoDB database server ii mongodb-org-shell 3.4.19 amd64 MongoDB shell client root@e50858fa7931:/var/log/unifi-video# dpkg --list | grep -i unifi ii unifi-video 3.10.1 amd64 Ubiquiti Networks UniFi Video controller ----- END BACKTRACE ----- 2019-02-15T14:56:11.834-0500 I CONTROL [main] ***** SERVER RESTARTED ***** 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] MongoDB starting : pid=4189 port=7441 dbpath=/usr/lib/unifi-video/data/db 64-bit host=e50858fa7931 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] db version v3.4.19 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] git version: a2d97db8fe449d15eb8e275bbf318491781472bf 2019-02-15T14:56:11.837-0500 I CONTROL [initandlisten] OpenSSL version: OpenSSL 1.0.2n 7 Dec 2017 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] allocator: tcmalloc 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] modules: none 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] build environment: 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] distmod: ubuntu1604 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] distarch: x86_64 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] target_arch: x86_64 2019-02-15T14:56:11.838-0500 I CONTROL [initandlisten] options: { config: "/usr/lib/unifi-video/conf/mongodv3.0+.conf", net: { bindIp: "", http: { enabled: false }, port: 7441 }, operationProfiling: { mode: "off", slowOpThresholdMs: 500 }, storage: { dbPath: "/usr/lib/unifi-video/data/db", engine: "mmapv1", journal: { enabled: true }, mmapv1: { preallocDataFiles: true, smallFiles: true }, syncPeriodSecs: 60.0 }, systemLog: { destination: "file", logAppend: true, path: "logs/mongod.log" } } 2019-02-15T14:56:11.863-0500 I JOURNAL [initandlisten] journal dir=/usr/lib/unifi-video/data/db/journal 2019-02-15T14:56:11.863-0500 I JOURNAL [initandlisten] recover : no journal files present, no recovery needed 2019-02-15T14:56:11.864-0500 I CONTROL [initandlisten] LogFile::synchronousAppend failed with 8192 bytes unwritten out of 8192 bytes; b=0x559a580de000 Invalid argument 2019-02-15T14:56:11.864-0500 I - [initandlisten] Fatal Assertion 13515 at src/mongo/db/storage/mmap_v1/logfile.cpp 248 2019-02-15T14:56:11.864-0500 I - [initandlisten] ***aborting after fassert() failure 2019-02-15T14:56:11.873-0500 F - [initandlisten] Got signal: 6 (Aborted). 0x559a548a27d1 0x559a548a19e9 0x559a548a1ecd 0x14f306a7a890 0x14f3066b5e97 0x14f3066b7801 0x559a53b369c5 0x559a54531370 0x559a54506084 0x559a54506675 0x559a5450d966 0x559a544ffb95 0x559a54475985 0x559a53b22dc3 0x559a53b42876 0x14f306698b97 0x559a53ba2a29
  15. would it be possible to get the beta branch for the Video Controller brought up to 3.10.0 Beta 1? Thanks