fireplex

Hi, I've tried a restart and a reinstall of the plugin but still the same issue. I don't use SSL and use port 80 (I'm running 6.9.0) On the GUI I don't see any dockers or VMs:

I can't add my server, keep seeing a weird error as per screenshot.

Just had this same issue with "guest has not initialized the display (yet)", deleting the VM (keeping the image) and re-creating fixed it. Thanks.

Thanks for all your work on this, completely understand. It's been great to use. [emoji106][emoji106][emoji106] Sent from my Pixel 3a using Tapatalk

Excellent thanks. So I presume the 5G just sets the highest amount of memory it can allocate from my total of 32GB, to stop it overwhelming the whole system.

Thanks, the ES is working again for me. I have never adjusted shared memory before so will have to read about that, currently it reports 16% with the 5G default from the template, my server has total 32GB installed.

I did use swag to access zoneminder remotely without use of my VPN for a while, worked ok. Sent from my Pixel 3a using Tapatalk

Thanks, appreciated! Sent from my Pixel 3a using Tapatalk

Well, just gone through this all again several times with complete cleans installs and still get this error: root@ea33b3d5e334:/var/lib/zmeventnotification/bin# sudo -u www-data ./zm_event_start.sh 1 1 Traceback (most recent call last): File "/var/lib/zmeventnotification/bin/zm_detect.py", line 27, in <module> import zmes_hook_helpers.utils as utils ModuleNotFoundError: No module named 'zmes_hook_helpers' Anyone recently done a fresh install of this docker in last few days and got ES working ?

This docker used to work for me fine but recently (last few weeks?) I noticed I've not being receiving any zmNinja alerts. Digging further I notice that something has caused one of the zmninja scripts to fail (this script is used to test your config # sudo -u www-data /var/lib/zmeventnotification/bin/zm_event_start.sh 1 1 Traceback (most recent call last): File "/var/lib/zmeventnotification/bin/zm_detect.py", line 27, in <module> import zmes_hook_helpers.utils as utils ModuleNotFoundError: No module named 'zmes_hook_helpers' So I've just done a brand new install of this docker from scratch (deleted old image and appdata) and enabled hook processing and yolo v4 options on the docker screen. Once installed I went into ZM options and enabled OPT_USE_EVENTNOTIFICATION, rebooted and then tried the above command again and it fails in the same manner :-( Looks like something has broken the docker ZM event notification ? I did notice some errors relating to scikit-learn failing to install when the docker installed ?

I'd like to know the answer to this also....

I have been using this same VM config for over a year without any issues so doubt its that.

Have a strange issue. When I try and start one of my Windows VMs unRAID GUI reports an I/O error accessing the VirtIO drivers which are on a share /mnt/user/Downloads, and the VM fails to start. Then, I see that the parity disk is disabled?..... To try and resolve the issue I have already tried: 1. Shutdown & poweroff 2. Reseat all SATA cables 3. Stop array, unassign parity drive 4. Start array so parity drive forgot 5. Stop array, assign parity drive 6. After 7hrs odd parity drive is rebuilt with zero hours reported anywhere After I try and start the VM I see in syslog: Jul 25 22:19:10 Tower kernel: ata7.00: disabled Jul 25 22:19:10 Tower kernel: print_req_error: I/O error, dev sdg, sector 244304594 Jul 25 22:19:10 Tower kernel: XFS (sdg1): metadata I/O error: block 0xe8fca92 ("xlog_iodone") error 5 numblks 64 Jul 25 22:19:10 Tower kernel: XFS (sdg1): xfs_do_force_shutdown(0x2) called from line 1232 of file fs/xfs/xfs_log.c. Return address = 0xffffffffa023f5de Jul 25 22:19:10 Tower kernel: XFS (sdg1): Log I/O Error Detected. Shutting down filesystem Jul 25 22:19:10 Tower kernel: XFS (sdg1): Please umount the filesystem and rectify the problem(s) Jul 25 22:19:10 Tower kernel: sd 7:0:0:0: [sdg] Synchronizing SCSI cache Jul 25 22:19:10 Tower kernel: sd 7:0:0:0: [sdg] Synchronize Cache(10) failed: Result: hostbyte=0x04 driverbyte=0x00 sdg is my parity drive so: 7. Start drive maintenance mode, run a xfs_repair on the cache XFS drive - all OK 8. Run SMART test, all OK Any ideas what is wrong, how to fix and especially why the parity drive is disabled when it appears the issue is related to my cache drive ? Diagnostics attached. Thanks. edit: left the system running memtest86 overnight although a quick test everything seemed fine tower-diagnostics-20180725-2222.zip

You mean TV headend? Guess I could look at that but no experience as use sagetv, dvb plugin screen a bit broke now after downgrading so driver not reported but it reports the card tuners fine. Will investigate Linux commands to run a channel scan. Guess otherwise will have to switch back to PCI passthrough and Windows [emoji26] Sent from my Nexus 5X using Tapatalk

Tbs6285 tune in sage directly Sent from my Nexus 5X using Tapatalk

OK, any idea why DVB-T channels work OK and it's just the DVB-T2 (HD) channels that won't work ? Seems a bit strange. Where should I log an issue ?

Hi, I was running 6.3.5 with the official TBS DVB drivers with no issues (TBS 6285 tuner). I upgraded to 6.4.0 and then only had 2 options for TBS drivers, open source or crazycat. So I tried opensource but that driver does not work with any DVB-T2 (high definition) channels, it fails to find them or tune to them (I am using SageTV). So, I tried crazycat and the same issue :-( I backed out back to 6.3.5 and all working OK again. Can we get the official TBS DVB drivers that were in 6.3.5 as an option with unraid 6.4.0 ? Thanks!

6.3.5 resolves the issue

Seems to fix it thanks

Downgrading to 6.3.3 resolves the issue

Just upgraded to 6.3.4 and now cannot access any shares, turned on debugging and see similar to you: [ 2017/05/25 19:53:53.106382, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [raspberry] -> [raspberry] -> [raspberry] succeeded [2017/05/25 19:53:53.119154, 0] ../lib/util/fault.c:78(fault_report) =============================================================== [2017/05/25 19:53:53.119177, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 25811 (4.5.7) Please read the Trouble-Shooting section of the Samba HOWTO [2017/05/25 19:53:53.119188, 0] ../lib/util/fault.c:81(fault_report) =============================================================== [2017/05/25 19:53:53.119195, 0] ../source3/lib/util.c:791(smb_panic_s3) PANIC (pid 25811): internal error [2017/05/25 19:53:53.120239, 0] ../source3/lib/util.c:902(log_stack_trace) BACKTRACE: 31 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x2b9beedfdbaa] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x2b9beedfdc80] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x2b9bec4c2baf] #3 /usr/lib64/libsamba-util.so.0(+0x1bdb6) [0x2b9bec4c2db6] #4 /lib64/libpthread.so.0(+0x115b0) [0x2b9bec29a5b0] #5 /usr/lib64/libsamba-util.so.0(all_zero+0x24) [0x2b9bec4c1e14] #6 /usr/lib64/libsamba-util.so.0(smb_xmemdup+0x14) [0x2b9bec4c1d44] #7 /usr/lib64/libsmbd-base-samba4.so(+0xfff58) [0x2b9bec81bf58] #8 /usr/lib64/libsmbd-base-samba4.so(+0xebfee) [0x2b9bec807fee] #9 /usr/lib64/libsmbd-base-samba4.so(+0x11805f) [0x2b9bec83405f] #10 /usr/lib64/libsmbd-base-samba4.so(+0x118bf1) [0x2b9bec834bf1] #11 /usr/lib64/libsmbd-base-samba4.so(make_connection+0x220) [0x2b9bec8350f0] #12 /usr/lib64/libsmbd-base-samba4.so(reply_tcon_and_X+0x684) [0x2b9bec7e2594] #13 /usr/lib64/libsmbd-base-samba4.so(+0x11233a) [0x2b9bec82e33a] #14 /usr/lib64/libsmbd-base-samba4.so(+0x114183) [0x2b9bec830183] #15 /usr/lib64/libsmbd-base-samba4.so(+0x1157cc) [0x2b9bec8317cc] #16 /usr/lib64/libtevent.so.0(+0x98b3) [0x2b9bed4818b3] #17 /usr/lib64/libtevent.so.0(+0x7df7) [0x2b9bed47fdf7] #18 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x2b9bed47c01d] #19 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x2b9bed47c1bb] #20 /usr/lib64/libtevent.so.0(+0x7d97) [0x2b9bed47fd97] #21 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x6c9) [0x2b9bec832ae9] #22 /usr/sbin/smbd(+0xcf84) [0x5649d7f89f84] #23 /usr/lib64/libtevent.so.0(+0x98b3) [0x2b9bed4818b3] #24 /usr/lib64/libtevent.so.0(+0x7df7) [0x2b9bed47fdf7] #25 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x2b9bed47c01d] #26 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x2b9bed47c1bb] #27 /usr/lib64/libtevent.so.0(+0x7d97) [0x2b9bed47fd97] #28 /usr/sbin/smbd(main+0x1755) [0x5649d7f84cf5] #29 /lib64/libc.so.6(__libc_start_main+0xf0) [0x2b9bf01e3350] #30 /usr/sbin/smbd(_start+0x2a) [0x5649d7f84eaa] [2017/05/25 19:53:53.120340, 0] ../source3/lib/dumpcore.c:303(dump_core) dumping core in /var/log/samba/cores/smbd [2017/05/25 19:53:53.121556, 1] ../source3/smbd/server.c:868(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2017/05/25 19:54:01.197073, 1] ../source3/smbd/server.c:1438(smbd_parent_sig_hup_handler) parent: Reloading services after SIGHUP [2017/05/25 19:54:01.197462, 1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter) WARNING: The "null passwords" option is deprecated Have you managed to fix this ?

So, I turned on samba debugging and find: [2017/05/25 19:53:53.106382, 2] ../source3/auth/auth.c:305(auth_check_ntlm_password) check_ntlm_password: authentication for user [raspberry] -> [raspberry] -> [raspberry] succeeded [2017/05/25 19:53:53.119154, 0] ../lib/util/fault.c:78(fault_report) =============================================================== [2017/05/25 19:53:53.119177, 0] ../lib/util/fault.c:79(fault_report) INTERNAL ERROR: Signal 11 in pid 25811 (4.5.7) Please read the Trouble-Shooting section of the Samba HOWTO [2017/05/25 19:53:53.119188, 0] ../lib/util/fault.c:81(fault_report) =============================================================== [2017/05/25 19:53:53.119195, 0] ../source3/lib/util.c:791(smb_panic_s3) PANIC (pid 25811): internal error [2017/05/25 19:53:53.120239, 0] ../source3/lib/util.c:902(log_stack_trace) BACKTRACE: 31 stack frames: #0 /usr/lib64/libsmbconf.so.0(log_stack_trace+0x1a) [0x2b9beedfdbaa] #1 /usr/lib64/libsmbconf.so.0(smb_panic_s3+0x20) [0x2b9beedfdc80] #2 /usr/lib64/libsamba-util.so.0(smb_panic+0x2f) [0x2b9bec4c2baf] #3 /usr/lib64/libsamba-util.so.0(+0x1bdb6) [0x2b9bec4c2db6] #4 /lib64/libpthread.so.0(+0x115b0) [0x2b9bec29a5b0] #5 /usr/lib64/libsamba-util.so.0(all_zero+0x24) [0x2b9bec4c1e14] #6 /usr/lib64/libsamba-util.so.0(smb_xmemdup+0x14) [0x2b9bec4c1d44] #7 /usr/lib64/libsmbd-base-samba4.so(+0xfff58) [0x2b9bec81bf58] #8 /usr/lib64/libsmbd-base-samba4.so(+0xebfee) [0x2b9bec807fee] #9 /usr/lib64/libsmbd-base-samba4.so(+0x11805f) [0x2b9bec83405f] #10 /usr/lib64/libsmbd-base-samba4.so(+0x118bf1) [0x2b9bec834bf1] #11 /usr/lib64/libsmbd-base-samba4.so(make_connection+0x220) [0x2b9bec8350f0] #12 /usr/lib64/libsmbd-base-samba4.so(reply_tcon_and_X+0x684) [0x2b9bec7e2594] #13 /usr/lib64/libsmbd-base-samba4.so(+0x11233a) [0x2b9bec82e33a] #14 /usr/lib64/libsmbd-base-samba4.so(+0x114183) [0x2b9bec830183] #15 /usr/lib64/libsmbd-base-samba4.so(+0x1157cc) [0x2b9bec8317cc] #16 /usr/lib64/libtevent.so.0(+0x98b3) [0x2b9bed4818b3] #17 /usr/lib64/libtevent.so.0(+0x7df7) [0x2b9bed47fdf7] #18 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x2b9bed47c01d] #19 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x2b9bed47c1bb] #20 /usr/lib64/libtevent.so.0(+0x7d97) [0x2b9bed47fd97] #21 /usr/lib64/libsmbd-base-samba4.so(smbd_process+0x6c9) [0x2b9bec832ae9] #22 /usr/sbin/smbd(+0xcf84) [0x5649d7f89f84] #23 /usr/lib64/libtevent.so.0(+0x98b3) [0x2b9bed4818b3] #24 /usr/lib64/libtevent.so.0(+0x7df7) [0x2b9bed47fdf7] #25 /usr/lib64/libtevent.so.0(_tevent_loop_once+0x8d) [0x2b9bed47c01d] #26 /usr/lib64/libtevent.so.0(tevent_common_loop_wait+0x1b) [0x2b9bed47c1bb] #27 /usr/lib64/libtevent.so.0(+0x7d97) [0x2b9bed47fd97] #28 /usr/sbin/smbd(main+0x1755) [0x5649d7f84cf5] #29 /lib64/libc.so.6(__libc_start_main+0xf0) [0x2b9bf01e3350] #30 /usr/sbin/smbd(_start+0x2a) [0x5649d7f84eaa] [2017/05/25 19:53:53.120340, 0] ../source3/lib/dumpcore.c:303(dump_core) dumping core in /var/log/samba/cores/smbd [2017/05/25 19:53:53.121556, 1] ../source3/smbd/server.c:868(remove_child_pid) Scheduled cleanup of brl and lock database after unclean shutdown [2017/05/25 19:54:01.197073, 1] ../source3/smbd/server.c:1438(smbd_parent_sig_hup_handler) parent: Reloading services after SIGHUP [2017/05/25 19:54:01.197462, 1] ../lib/param/loadparm.c:1729(lpcfg_do_global_parameter) WARNING: The "null passwords" option is deprecated

Definitely an unRAID issue, I have a backup script on a Raspberry Pi that now fails: pi@raspberrypi:~/scripts $ sudo mount -t cifs -o username=raspberry,password=password //192.168.1.25/PiBackup /mnt/backups mount error(11): Resource temporarily unavailable Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) How can I debug samba/cifs on unRAID, any logs anywhere ?

C:\WINDOWS\system32>nbtstat -c VirtualBox Host-Only Network #2: Node IpAddress: [192.168.56.1] Scope Id: [] No names in cache Ethernet 2: Node IpAddress: [0.0.0.0] Scope Id: [] No names in cache Ethernet: Node IpAddress: [192.168.1.31] Scope Id: [] NetBIOS Remote Cache Name Table Name Type Host Address Life [sec] ------------------------------------------------------------ TOWER <00> UNIQUE 192.168.1.25 365 Strange, it seems to know about it....

Hi, yes I googled and https://scottiestech.info/2009/02/14/how-to-determine-the-master-browser-in-a-windows-workgroup/ was the first thing I have tried. net view just reports my own PC and nothing else and C:\WINDOWS\system32>nbtstat -a FIREPLEX VirtualBox Host-Only Network #2: Node IpAddress: [192.168.56.1] Scope Id: [] Host not found. Ethernet 2: Node IpAddress: [0.0.0.0] Scope Id: [] Host not found. Ethernet: Node IpAddress: [192.168.1.31] Scope Id: [] Host not found. 192.168.1.31 is my PC The thing is, everything was fine for years before I upgraded unRAID to this latest release