Jump to content

dlandon

Community Developer
  • Posts

    10,398
  • Joined

  • Last visited

  • Days Won

    20

Everything posted by dlandon

  1. Be sure to use all the defaults in the docker template. Don't make any networking or port adjustments until the docker is working. After you install the docker, left click on the icon and choose WebUI. You will be taken to the UI. You will be using https and you'll see the url to get to the docker. Once you've done that, you can make network and port changes to the docker.
  2. Several issues: This message occurs when you have left an open browser session when rebooting the server: Oct 24 18:41:59 Tower root: error: /plugins/unassigned.devices/UnassignedDevices.php: wrong csrf_token ### [PREVIOUS LINE REPEATED 41 TIMES] ### Be sure to close all browser sessions when you reboot the server. You need to look at these FCP warnings and fix them: Oct 24 18:47:00 Tower root: Fix Common Problems Version 2018.10.21 Oct 24 18:47:00 Tower root: Fix Common Problems: Warning: Share domains set to not use the cache, but files / folders exist on the cache drive Oct 24 18:47:11 Tower root: Fix Common Problems: Warning: Marvel Hard Drive Controller Installed ** Ignored This is confusing to me: Oct 27 10:48:03 Tower kernel: CIFS VFS: No task to wake, unknown frame received! NumMids 1 Oct 27 10:48:03 Tower kernel: 00000000: 424d53fe 00000040 00000000 00000012 .SMB@........... Oct 27 10:48:03 Tower kernel: 00000010: 00000001 00000000 ffffffff ffffffff ................ Oct 27 10:48:03 Tower kernel: 00000020: 00000000 00000000 00000000 00000000 ................ Oct 27 10:48:03 Tower kernel: 00000030: 00000000 00000000 00000000 00000000 ................ Oct 27 10:48:47 Tower kernel: CIFS VFS: No task to wake, unknown frame received! NumMids 1 Oct 27 10:48:47 Tower kernel: 00000000: 424d53fe 00000040 00000000 00000012 .SMB@........... Oct 27 10:48:47 Tower kernel: 00000010: 00000001 00000000 ffffffff ffffffff ................ Oct 27 10:48:47 Tower kernel: 00000020: 00000000 00000000 00000000 00000000 ................ Oct 27 10:48:47 Tower kernel: 00000030: 00000000 00000000 00000000 00000000 ................ Oct 27 10:49:18 Tower kernel: CIFS VFS: No task to wake, unknown frame received! NumMids 1 Oct 27 10:49:18 Tower kernel: 00000000: 424d53fe 00000040 00000000 00000012 .SMB@........... Oct 27 10:49:18 Tower kernel: 00000010: 00000001 00000000 ffffffff ffffffff ................ Oct 27 10:49:18 Tower kernel: 00000020: 00000000 00000000 00000000 00000000 ................ Oct 27 10:49:18 Tower kernel: 00000030: 00000000 00000000 00000000 00000000 ................ Oct 27 10:49:44 Tower emhttpd: req (7): csrf_token=***************&title=System+Log&cmd=%2FwebGui%2Fscripts%2Ftail_log&arg1=syslog Oct 27 10:49:44 Tower emhttpd: cmd: /usr/local/emhttp/plugins/dynamix/scripts/tail_log syslog Oct 27 10:49:55 Tower unassigned.devices: Removing Remote SMB share '//TOWERII/backupshare'... Oct 27 10:49:55 Tower unassigned.devices: Device '//TOWERII/backupshare' script file not found. 'REMOVE' script not executed. Oct 27 10:49:55 Tower unassigned.devices: Unmounting Remote SMB Share '//TOWERII/backupshare'... Oct 27 10:49:55 Tower unassigned.devices: Unmounting '//TOWERII/backupshare'... Oct 27 10:49:55 Tower unassigned.devices: Unmount cmd: /bin/umount -t cifs '//TOWERII/backupshare' 2>&1 Oct 27 10:49:55 Tower unassigned.devices: Successfully unmounted '//TOWERII/backupshare' Oct 27 10:49:55 Tower unassigned.devices: Removing SMB share file '/etc/samba/unassigned-shares/TOWERII_backupshare.conf' Oct 27 10:49:55 Tower unassigned.devices: Removing SMB share definitions from '/boot/config/smb-extra.conf' Oct 27 10:49:55 Tower unassigned.devices: Reloading Samba configuration.. Oct 27 10:49:55 Tower unassigned.devices: Successfully removed SMB share 'TOWERII_backupshare'. Oct 27 10:49:55 Tower unassigned.devices: Share '//TOWERII/backupshare' unmount successfull. Oct 27 10:49:58 Tower unassigned.devices: Mount SMB share '//TOWERII/backupshare' using SMB3 protocol. Oct 27 10:49:58 Tower kernel: CIFS VFS: error -95 on ioctl to get interface list Oct 27 10:49:58 Tower unassigned.devices: Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,,vers=3.0,username=xxx=******* '//TOWERII/backupshare' '/mnt/disks/TOWERII_backupshare' Oct 27 10:49:58 Tower unassigned.devices: Successfully mounted '//TOWERII/backupshare' on '/mnt/disks/TOWERII_backupshare'. Oct 27 10:49:58 Tower unassigned.devices: Defining share 'TOWERII_backupshare' with file '/etc/samba/unassigned-shares/TOWERII_backupshare.conf' Oct 27 10:49:58 Tower unassigned.devices: Adding share 'TOWERII_backupshare' to '/boot/config/smb-extra.conf' Oct 27 10:49:58 Tower unassigned.devices: Reloading Samba configuration... Oct 27 10:49:58 Tower unassigned.devices: Directory '/mnt/disks/TOWERII_backupshare' shared successfully. Oct 27 10:49:58 Tower unassigned.devices: Device '//TOWERII/backupshare' script file not found. 'ADD' script not executed. Oct 27 10:57:18 Tower kernel: mdcmd (278): spindown 1 Oct 27 10:57:21 Tower kernel: mdcmd (279): spindown 3 Oct 27 11:01:42 Tower unassigned.devices: Removing Remote SMB share '//TOWERII/backupshare'... Oct 27 11:01:42 Tower unassigned.devices: Device '//TOWERII/backupshare' script file not found. 'REMOVE' script not executed. Oct 27 11:01:42 Tower unassigned.devices: Unmounting Remote SMB Share '//TOWERII/backupshare'... Oct 27 11:01:42 Tower unassigned.devices: Unmounting '//TOWERII/backupshare'... Oct 27 11:01:42 Tower unassigned.devices: Unmount cmd: /bin/umount -t cifs '//TOWERII/backupshare' 2>&1 Oct 27 11:01:42 Tower unassigned.devices: Successfully unmounted '//TOWERII/backupshare' Oct 27 11:01:42 Tower unassigned.devices: Removing SMB share file '/etc/samba/unassigned-shares/TOWERII_backupshare.conf' Oct 27 11:01:42 Tower unassigned.devices: Removing SMB share definitions from '/boot/config/smb-extra.conf' Oct 27 11:01:42 Tower unassigned.devices: Reloading Samba configuration.. Oct 27 11:01:42 Tower unassigned.devices: Successfully removed SMB share 'TOWERII_backupshare'. Oct 27 11:01:42 Tower unassigned.devices: Share '//TOWERII/backupshare' unmount successfull. Oct 27 11:01:54 Tower unassigned.devices: Mount SMB share '//TOWERII/backupshare' using SMB3 protocol. Oct 27 11:01:54 Tower kernel: CIFS VFS: error -95 on ioctl to get interface list Oct 27 11:01:54 Tower unassigned.devices: Mount SMB/NFS command: mount -t cifs -o rw,nounix,iocharset=utf8,_netdev,file_mode=0777,dir_mode=0777,,vers=3.0,username=xxx=******* '//TOWERII/backupshare' '/mnt/disks/TOWERII_backupshare' Oct 27 11:01:54 Tower unassigned.devices: Successfully mounted '//TOWERII/backupshare' on '/mnt/disks/TOWERII_backupshare'. Oct 27 11:01:54 Tower unassigned.devices: Defining share 'TOWERII_backupshare' with file '/etc/samba/unassigned-shares/TOWERII_backupshare.conf' Oct 27 11:01:54 Tower unassigned.devices: Adding share 'TOWERII_backupshare' to '/boot/config/smb-extra.conf' Oct 27 11:01:54 Tower unassigned.devices: Reloading Samba configuration... Oct 27 11:01:54 Tower unassigned.devices: Directory '/mnt/disks/TOWERII_backupshare' shared successfully. Oct 27 11:01:54 Tower unassigned.devices: Device '//TOWERII/backupshare' script file not found. 'ADD' script not executed. It looks like CIFS VFS is having a problem. It also appears that you are unmounting and re-mounting the shares constantly manually. Fix the FCP issues, reboot the server, mount the shares and then capture the diagnostics right after the shares disconnect. Your constant mounting and unmounting the shares makes it hard for me to see what is happening.
  3. You won't see anything logged for a SMB share, just a physical disk. Your remote share is probably going off-line. Post your diagnostics.
  4. If you have upgraded from 1.30, I would review your camera settings to the default 1.32 camera settings and make adjustments as necessary. This may help in your cpu loading and operation of Zoneminder.
  5. Check your docker space used. You can see it on the "Dashboard" page.
  6. A new docker is building to handle the user script. You will need to edit the docker template xml and add a variable: ADVANCED_SCRIPT with a value of 1. This will enable your script. Put your script in /config/userscript.sh. Your script needs some changes: apt-get -y install python-pip pip install opencv-python apt-get -y install libsm6 libxext6 libxrender1
  7. Yes. Removed in the latest release. There are too many variations to include in the docker. It depends on which method you use. Adding the scripts for your particular situation is the cleanest way to handle this feature. I don't want to load up the docker with a lot of unused stuff. The support for another docker is more than I care to take on.
  8. Cache Dirs has a bug that keeps it from running when the server is started. @bonienl is aware of it and will fix it. For the time being, just start it manually. I am not seeing any of the spin up issues you are talking about. You are caching only one share. Maybe your other shares are being accessed causing the spin ups. For the time being, set all your shares in Cache Dirs and see if that helps. Install the File Activity plugin and see if that can help you find the files that are causing the spin ups.
  9. I've applied a fix to the docker to not overwrite the zmeventnotification.ini file. I've also implemented the zmevent hook feature. A /config/hook/ folder is created and you place the scripts and executable files you need for your implementation of the hook feature. Be sure to set the file permissions. The docker will copy the files in the /config/hook/ folder to /usr/bin/ when the docker is started.
  10. I would delete the docker and then add it back.
  11. I'm working on a solution. What client do you use with MQTT? What is detect_wrapper.sh? Ok, I see it. That is the zmeventnotification hook script. I'll need to see what is needed to implement that feature.
  12. The reason I do that is because it seems to change on each update. I kind of figured this would come up. I’ll work on a solution. What modifications are you doing in the .ini file?
  13. Install the Oauth2 app from the Market for better security.
  14. That is not necessary. ownCloud manages the time zone.
  15. You can also add this to the ownCloud config.php file: 'filesystem_check_changes' => 1, This will do the same thing with all users.
  16. The latest version of the docker will run zmaudt once a week because of reports of zmaudit loading the processor. I would try to put back your settings slowly and see which ones are really affecting you. I'll keep trying to find more things to try.
  17. I've updated the docker to run zmaudit once a week. Turn off RUN_AUDIT in the options and restart Zoneminder. Zmaudit has been known to take up too much processor time and does not need to run continuously.
  18. No. That is actually preferred over a hard drive.
  19. I have something for you to try. Turn off zmaudit in the options. Is your appdata/Zoneminder folder on an SSD?
  20. Get connected to the Internet and solve the issues in FCP (Fix Common Problems). You have an issue with the cache drive and need to solve it, along with other issues.
×
×
  • Create New...