Shyrka973

Members
  • Posts

    38
  • Joined

  • Last visited

About Shyrka973

  • Birthday 07/30/1969

Converted

  • Gender
    Male

Recent Profile Visitors

667 profile views

Shyrka973's Achievements

Noob

Noob (1/14)

0

Reputation

  1. Hi @dlandon, In zmeventnotification.ini.default, the [mqtt] section is missing. Thanks.
  2. I finally understood how the script is launched: /etc/my_init.d/999_advanced_script.sh. This is a basic feature of the image. Thanks again.
  3. Thank dlandon ! In your last commit, i do not see how this script is launched? I do not see any changes in the 40_firstrun.sh script.
  4. Yes. I understand. I need to execute these commands in this docker after its update: apt-get install python-pip pip install opencv-python apt install libsm6 libxext6 libxrender1 Can you add the execution of a script (example: update.sh ) if it is present in /config each time the docker is launched ? Thanks.
  5. Hi dlandon, Thank you very very much. Look this: 2018-10-28 12:03:59 zmeventnotification 1051 INF hook script returned with text:detected:person:100% diningtable:77% chair:64% cell phone:52% exit:0 Now, I do not have any more false alarm because it must detect someone to warn me. To test in the long term. Can you remove "chmod -R 666 /config/hook" ? I put executable scripts in /config/hook/ folder that are copied to /usr/bin folder in the docker but after restarting the docker, the scripts are no longer executable. If it interests the world, I can write a howto. If it interests a lot of people, maybe dlandon can integrate it into the docker or create a specific docker.
  6. Il use mosquitto with MQTT. Extract from here (read the original): zmeventnotification.ini now contains a hook attribute. If you specify a script file there, every time the notification server detects an alarm (it interacts with ZM using shared memory and checks the shared_data structure for events), it passes the event id, monitor id and monitor name to this script. The script can do what it chooses and if it returns 0 then the event server will process the notification and send it out to listeners. If it returns 1 it will not. So the script is where all the action is. I then used this framework to do object detection and based on the results, either notify or not. The goal: be notified of vehicles and people.
  7. II disable ssl and I configure mqtt. This container is the only one I do not update automatically. No problem. I'm waiting for your solution. Thank you very much. Do you already test or do you think to integrate as an option (a cocker variable ?) this: detect_wrapper.sh ? Just add the necessary: detect_wrapper.sh, openCV, yolov3-tiny.weights, yolov3.weights, yolov3-tiny.cfg, yolov3.cfg, coco.names, ...
  8. Hi, At each update of the container, I lose the modifications of zmeventnotification.ini. Can you copy the new zmeventnotification.ini to /config/zmeventnotification.ini.template ? And if /config/zmeventnotification.ini does not exist (new install), create it with /config/zmeventnotification.ini.template. This is just an example. Tkanks.
  9. Hi, With the new iOS app, I can see log files now. Thanks.
  10. Hi, With this latest version, I have the same access problem. I: 2018/10/03 22:27:30 app.go:57: controlr v2.14.0-394-675a295-v2018.10.03 starting ... I: 2018/10/03 22:27:30 app.go:65: No config file specified. Using app defaults ... I: 2018/10/03 22:27:30 core.go:73: starting service Core ... I: 2018/10/03 22:27:30 core.go:266: Created system sensor ... I: 2018/10/03 22:27:30 core.go:287: Created apc ups ... I: 2018/10/03 22:27:30 server.go:94: Starting service Server ... I: 2018/10/03 22:27:30 server.go:113: Serving files from /usr/local/emhttp/plugins/controlr I: 2018/10/03 22:27:30 server.go:173: Server started listening http on :2378 I: 2018/10/03 22:27:30 server.go:185: Server started listening https on :2379 I: 2018/10/03 22:27:30 api.go:46: Starting service Api ... I: 2018/10/03 22:27:30 api.go:94: Api started listening https on :2382 I: 2018/10/03 22:27:30 app.go:85: Press Ctrl+C to stop ... W: 2018/10/03 22:27:40 core.go:153: Unable to get unRAID state (dockers): Get https://127.0.0.1/plugins/dynamix.docker.manager/include/DockerContainers.php: dial tcp 127.0.0.1:443: connect: connection refused W: 2018/10/03 22:27:47 server.go:291: error reading from connection: EOF
  11. Hi, here is the diagnostic file. [75712.030094] ------------[ cut here ]------------ [75712.030097] nfsd: non-standard errno: -103 [75712.030128] WARNING: CPU: 0 PID: 12163 at fs/nfsd/nfsproc.c:817 nfserrno+0x44/0x4a [nfsd] [75712.030129] Modules linked in: macvlan xt_CHECKSUM iptable_mangle ipt_REJECT xt_nat ebtable_filter ebtables veth ip6table_filter ip6_tables vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid bonding r8169 mii intel_powerclamp coretemp kvm_intel kvm crc32c_intel intel_cstate intel_uncore i2c_i801 i2c_core ahci mxm_wmi i7core_edac libahci pata_jmicron wmi button pcc_cpufreq acpi_cpufreq [last unloaded: mii] [75712.030165] CPU: 0 PID: 12163 Comm: nfsd Tainted: G I 4.18.8-unRAID #1 [75712.030166] Hardware name: Gigabyte Technology Co., Ltd. X58A-UD7/X58A-UD7, BIOS F2 11/10/2009 [75712.030171] RIP: 0010:nfserrno+0x44/0x4a [nfsd] [75712.030172] Code: c0 48 83 f8 22 75 e2 80 3d b3 06 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 3b ba 1a a0 c6 05 9c 06 01 00 01 e8 8a cc ea e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25 [75712.030203] RSP: 0000:ffffc90001267df0 EFLAGS: 00010286 [75712.030205] RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007 [75712.030206] RDX: 0000000000000000 RSI: ffff880199216470 RDI: ffff880199216470 [75712.030207] RBP: ffffc90001267e40 R08: 0000000000000003 R09: ffffffff82213400 [75712.030209] R10: 0000000000000567 R11: 000000000001ba1c R12: ffff88019312d008 [75712.030210] R13: ffffffffa01ab6d0 R14: 000000000000001c R15: ffffffffa01ab2a0 [75712.030212] FS: 0000000000000000(0000) GS:ffff880199200000(0000) knlGS:0000000000000000 [75712.030213] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [75712.030215] CR2: 0000154eab4fa690 CR3: 000000014a0d8000 CR4: 00000000000006f0 [75712.030216] Call Trace: [75712.030223] nfsd_open+0x15e/0x17c [nfsd] [75712.030228] nfsd_commit+0x5a/0xbf [nfsd] [75712.030233] nfsd3_proc_commit+0x65/0x69 [nfsd] [75712.030238] nfsd_dispatch+0xb4/0x169 [nfsd] [75712.030249] svc_process+0x4b5/0x666 [sunrpc] [75712.030255] ? nfsd_destroy+0x48/0x48 [nfsd] [75712.030258] nfsd+0xeb/0x142 [nfsd] [75712.030263] kthread+0x10b/0x113 [75712.030265] ? kthread_flush_work_fn+0x9/0x9 [75712.030268] ret_from_fork+0x35/0x40 [75712.030271] ---[ end trace 1687ae2bf8531519 ]--- tower-diagnostics-20180925-0719.zip
  12. OK, i'm waiting for that to happen again. I hope this tool will work because volumes are frozen. This occurs during a backup of a Proxmox VM to the unRaid server.
  13. Hi, I have had this problem twice since 6.6.0. Volumes are inaccessible since. I have to reboot. [241269.176121] ------------[ cut here ]------------ [241269.176123] nfsd: non-standard errno: -103 [241269.176155] WARNING: CPU: 5 PID: 12157 at fs/nfsd/nfsproc.c:817 nfserrno+0x44/0x4a [nfsd] [241269.176156] Modules linked in: macvlan xt_CHECKSUM iptable_mangle ipt_REJECT xt_nat ebtable_filter ebtables ip6table_filter ip6_tables veth vhost_net tun vhost tap ipt_MASQUERADE iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 iptable_filter ip_tables nf_nat xfs nfsd lockd grace sunrpc md_mod it87 hwmon_vid bonding r8169 mii intel_powerclamp coretemp kvm_intel kvm crc32c_intel i2c_i801 i2c_core intel_cstate mxm_wmi intel_uncore i7core_edac ahci wmi libahci pata_jmicron button pcc_cpufreq acpi_cpufreq [last unloaded: mii] [241269.176193] CPU: 5 PID: 12157 Comm: nfsd Tainted: G I 4.18.8-unRAID #1 [241269.176194] Hardware name: Gigabyte Technology Co., Ltd. X58A-UD7/X58A-UD7, BIOS F2 11/10/2009 [241269.176198] RIP: 0010:nfserrno+0x44/0x4a [nfsd] [241269.176199] Code: c0 48 83 f8 22 75 e2 80 3d b3 06 01 00 00 bb 00 00 00 05 75 17 89 fe 48 c7 c7 3b 0a 1d a0 c6 05 9c 06 01 00 01 e8 8a 7c e8 e0 <0f> 0b 89 d8 5b c3 48 83 ec 18 31 c9 ba ff 07 00 00 65 48 8b 04 25 [241269.176231] RSP: 0000:ffffc90001227df0 EFLAGS: 00010286 [241269.176233] RAX: 0000000000000000 RBX: 0000000005000000 RCX: 0000000000000007 [241269.176234] RDX: 0000000000000000 RSI: ffff880199356470 RDI: ffff880199356470 [241269.176235] RBP: ffffc90001227e40 R08: 0000000000000003 R09: ffffffff82215d00 [241269.176237] R10: 000000000000060f R11: 000000000001e35c R12: ffff8801943a3c08 [241269.176238] R13: ffffffffa01d06d0 R14: 000000000000001c R15: ffffffffa01d02a0 [241269.176240] FS: 0000000000000000(0000) GS:ffff880199340000(0000) knlGS:0000000000000000 [241269.176241] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [241269.176243] CR2: 000014a4eacd60b0 CR3: 00000000806f2000 CR4: 00000000000006e0 [241269.176244] Call Trace: [241269.176250] nfsd_open+0x15e/0x17c [nfsd] [241269.176255] nfsd_commit+0x5a/0xbf [nfsd] [241269.176259] nfsd3_proc_commit+0x65/0x69 [nfsd] [241269.176263] nfsd_dispatch+0xb4/0x169 [nfsd] [241269.176275] svc_process+0x4b5/0x666 [sunrpc] [241269.176281] ? nfsd_destroy+0x48/0x48 [nfsd] [241269.176284] nfsd+0xeb/0x142 [nfsd] [241269.176288] kthread+0x10b/0x113 [241269.176291] ? kthread_flush_work_fn+0x9/0x9 [241269.176295] ret_from_fork+0x35/0x40 [241269.176298] ---[ end trace d6f4f9a9f4819224 ]---