spyd4r

Members
  • Posts

    55
  • Joined

  • Last visited

Everything posted by spyd4r

  1. in regards to the pid file edit /data/turnserver.conf, add the following and restart pidfile=/data/turnserver.pid userdb=/data/turnserver.db perhaps, @yinzer should add this to the original post. I believe you can set "no-cli" in turnserver.conf as well to remove the other message. reference: https://github.com/instrumentisto/coturn-docker-image/issues/13
  2. if you don't have ipv6 make sure you don't have it listed ['::1', '0.0.0.0'] or whatever it looked like, make sure you set it as TeddyTux mentioned above... Took me a couple minutes to notice this.
  3. spyd4r

    Jitsi?

    +1 would also like the ability to have it configured easily for authentication on rooms.
  4. I love being able to easily manage docker and vms right from the GUI.
  5. 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.
  6. yeah, unfortunately I use it to write my Security Footage for my cameras to.
  7. 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
  8. 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.
  9. Can confirm with all 6.7.2, had appdata on array and it corrupted immediately and repeatedly. Switched to cache disk and no issues.
  10. 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.
  11. 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?
  12. 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
  13. 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
  14. 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.
  15. 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.
  16. that didn't work for me, i just ended up rolling back to 3.9.12
  17. 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.
  18. 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: "127.0.0.1", 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
  19. would it be possible to get the beta branch for the Video Controller brought up to 3.10.0 Beta 1? Thanks
  20. fryfrog, thanks for the last update.. can you try updating the beta branch to the new 3.10 beta 1? https://community.ubnt.com/t5/UniFi-Video-Beta/UniFi-Video-3-10-0-Beta-1-Release/m-p/2513135#M19784
  21. would it be possible to have someone update the beta branch to include the new unifi video 3.9.9-beta2? I tried in my clone of the branch but kept having issues i couldn't solve with the patch.
  22. I'm having a similar issue and i think it's related to UEFI, when I reboot sometimes I just get a black screen.. I'll even power it off and turn it back on just black screen after post... but if i force a UEFI boot in the BIOS it'll come up. Never had this issue before 6.5.2 and 6.5.2-RCs
  23. I seem to be getting NIC interuptions as well. Only since the latest 6.5.2 and the RCs from what I can tell. seeing this numerous times today [Wed May 16 09:32:51 2018] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: TDH <60> TDT <7a> next_to_use <7a> next_to_clean <5f> buffer_info[next_to_clean]: time_stamp <1023d45d8> next_to_watch <60> jiffies <1023d6fc1> next_to_watch.status <0> MAC Status <40080083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Wed May 16 09:32:52 2018] NETDEV WATCHDOG: eth0 (e1000e): transmit queue 0 timed out [Wed May 16 09:32:52 2018] ------------[ cut here ]------------ [Wed May 16 09:32:52 2018] WARNING: CPU: 5 PID: 0 at net/sched/sch_generic.c:320 dev_watchdog+0x157/0x1b8 [Wed May 16 09:32:52 2018] Modules linked in: xt_CHECKSUM iptable_mangle ipt_REJECT nf_reject_ipv4 ebtable_filter ebtables ip6table_filter ip6_tables vhost_net tun vhost tap xt_nat veth ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod nct6775 hwmon_vid x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul crc32c_intel ghash_clmulni_intel pcbc aesni_intel aes_x86_64 crypto_simd glue_helper e1000e cryptd intel_cstate ahci wmi_bmof libahci wmi ptp intel_uncore pps_core video i2c_i801 intel_rapl_perf i2c_core ie31200_edac backlight thermal button fan [Wed May 16 09:32:52 2018] CPU: 5 PID: 0 Comm: swapper/5 Not tainted 4.14.40-unRAID #1 [Wed May 16 09:32:52 2018] Hardware name: System manufacturer System Product Name/P8Z77-I DELUXE, BIOS 1201 06/20/2014 [Wed May 16 09:32:52 2018] task: ffff88040d5b5280 task.stack: ffffc90001928000 [Wed May 16 09:32:52 2018] RIP: 0010:dev_watchdog+0x157/0x1b8 [Wed May 16 09:32:52 2018] RSP: 0018:ffff88041fb43e98 EFLAGS: 00010292 [Wed May 16 09:32:52 2018] RAX: 000000000000003a RBX: ffff880409b1c000 RCX: 0000000000000000 [Wed May 16 09:32:52 2018] RDX: 0000000000040001 RSI: 00000000000000f6 RDI: 0000000000000300 [Wed May 16 09:32:52 2018] RBP: 0000000000000000 R08: 0000000000000003 R09: ffffffff81fe7200 [Wed May 16 09:32:52 2018] R10: 0000000000000082 R11: 000000000000005c R12: ffff880409b1c39c [Wed May 16 09:32:52 2018] R13: 0000000000000005 R14: 0000000000000001 R15: ffff88040d267880 [Wed May 16 09:32:52 2018] FS: 0000000000000000(0000) GS:ffff88041fb40000(0000) knlGS:0000000000000000 [Wed May 16 09:32:52 2018] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [Wed May 16 09:32:52 2018] CR2: 00001529a39fa000 CR3: 0000000004c0a001 CR4: 00000000001626e0 [Wed May 16 09:32:52 2018] Call Trace: [Wed May 16 09:32:52 2018] <IRQ> [Wed May 16 09:32:52 2018] ? qdisc_rcu_free+0x39/0x39 [Wed May 16 09:32:52 2018] ? qdisc_rcu_free+0x39/0x39 [Wed May 16 09:32:52 2018] call_timer_fn.isra.4+0x14/0x70 [Wed May 16 09:32:52 2018] expire_timers+0x82/0x95 [Wed May 16 09:32:52 2018] run_timer_softirq+0x62/0xe5 [Wed May 16 09:32:52 2018] ? tick_sched_timer+0x33/0x61 [Wed May 16 09:32:52 2018] ? recalibrate_cpu_khz+0x6/0x6 [Wed May 16 09:32:52 2018] ? ktime_get+0x3a/0x8d [Wed May 16 09:32:52 2018] __do_softirq+0xcd/0x1c2 [Wed May 16 09:32:52 2018] irq_exit+0x4f/0x8e [Wed May 16 09:32:52 2018] smp_apic_timer_interrupt+0x7a/0x85 [Wed May 16 09:32:52 2018] apic_timer_interrupt+0x7d/0x90 [Wed May 16 09:32:52 2018] </IRQ> [Wed May 16 09:32:52 2018] RIP: 0010:cpuidle_enter_state+0xe3/0x135 [Wed May 16 09:32:52 2018] RSP: 0018:ffffc9000192bef8 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff10 [Wed May 16 09:32:52 2018] RAX: ffff88041fb60980 RBX: 0000000000000000 RCX: 000000000000001f [Wed May 16 09:32:52 2018] RDX: 0000227425969198 RSI: 0000000000020180 RDI: 0000000000000000 [Wed May 16 09:32:52 2018] RBP: ffff88041fb68700 R08: 00007944edee82d9 R09: 0000000000000060 [Wed May 16 09:32:52 2018] R10: ffffc9000192bed8 R11: 000000000c7ac3f4 R12: 0000000000000004 [Wed May 16 09:32:52 2018] R13: 0000227425969198 R14: ffffffff81c59258 R15: 0000227424d0f9bb [Wed May 16 09:32:52 2018] ? cpuidle_enter_state+0xbb/0x135 [Wed May 16 09:32:52 2018] do_idle+0x11a/0x179 [Wed May 16 09:32:52 2018] cpu_startup_entry+0x18/0x1a [Wed May 16 09:32:52 2018] secondary_startup_64+0xa5/0xb0 [Wed May 16 09:32:52 2018] Code: 3d a5 44 7c 00 00 75 35 48 89 df c6 05 99 44 7c 00 01 e8 6c 2b fe ff 89 e9 48 89 de 48 c7 c7 70 71 b8 81 48 89 c2 e8 ca 61 ba ff <0f> 0b eb 0e ff c5 48 05 40 01 00 00 39 cd 75 9d eb 13 48 8b 83 [Wed May 16 09:32:52 2018] ---[ end trace e0df5652918bcbb6 ]--- [Wed May 16 09:32:52 2018] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly [Wed May 16 09:36:39 2018] e1000e 0000:00:19.0 eth0: Detected Hardware Unit Hang: TDH <38> TDT <57> next_to_use <57> next_to_clean <37> buffer_info[next_to_clean]: time_stamp <10240c4ee> next_to_watch <38> jiffies <10240ea80> next_to_watch.status <0> MAC Status <40080083> PHY Status <796d> PHY 1000BASE-T Status <3800> PHY Extended Status <3000> PCI Status <10> [Wed May 16 09:36:40 2018] e1000e 0000:00:19.0 eth0: Reset adapter unexpectedly
  24. is it possible to get dig added to this container? or is there a way of pushing it in without cloning the github?
  25. found the culprit jshridha/motioneye:latest was writing locally. yikes..