dlandon
-
Posts
10,398 -
Joined
-
Last visited
-
Days Won
20
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Everything posted by dlandon
-
The only ports I would open are 8443 (8443 external mapped to internal 443 when you have a static IP) and 9000. Access ZM using https:// through port 8443 external, and the 9000 port is for the events notification. Be sure to enable the event notifications (OPT_USE_EVENTNOTIFICATION) in the options.
-
Post your diagnostics. SMB and NFS share mounting works fine. There is something unique about your setup that is causing a problem. I suspect a networking issue. That's why I suggested a static IP. You would probably need a static IP address if the VM is a server anyway. -
You should assign a static IP to the docker.
-
You deleted the preclear log that then allows a format.
-
That makes me suspicious about your network and ip addressing. Why are you setting up a Windows server vm on unraid. What does that accomplish?
-
Posting log snippets has no value. Post your diagnostics. Check that you have the destructive mode enabled in the UD settings. That might be the issue with the gray format button.
-
Does the server respond to a ping?
-
Your posts are confusing. The first one shows referring to the server by ip and it was a Windows server. Now it’s by name and not a Windows server.
-
Is that IP address correct. Is Unraid on the same sub-net 192.168.86.x? The Windows server must respond to a ping so UD knows it’s alive.
-
How would you feel about me providing a link to your script in the first post of this thread?
-
I believe this is addressed in the next release of Zoneminder. I saw on GitHub where this was addressed. Seems to be related to running in a Docker
-
[6.6.4] No cron job running during the night
dlandon commented on Niklas's report in Stable Releases
New category needed? ‘Major’ - possible data loss. -
[6.6.4] No cron job running during the night
dlandon commented on Niklas's report in Stable Releases
What he said. I’m just going to roll back and wait for the dust to settle. -
Zoneminder was changed a lot in the latest version. It's possible they made changes that changed the shared memory usage. The docker itself has nothing to do with the shared memory, except for specifying the amount of main memory to use for shared memory. In your case you are using a lot more memory from Unraid than is necessary, possibly causing Unraid to run out of memory at times.
-
Trust me. It's the right thing to do, or I wouldn't do it.
-
No. There are times when the status of the server is checked and the share not mounted.
-
Here is your issue: Nov 6 19:44:12 alael-net2 unassigned.devices: Mounting 'Auto Mount' Devices... Nov 6 19:44:14 alael-net2 unassigned.devices: Error: Remote SMB/NFS server '192.168.75.199' is offline and share '//192.168.75.199/Download' cannot be mounted. Nov 6 19:44:14 alael-net2 unassigned.devices: Error: Remote SMB/NFS server '192.168.75.199' is offline and share '//192.168.75.199/Media' cannot be mounted. UD checks the remote server by pinging it. Be sure the server is online and will respond to a ping.
-
Showing more of the same log messages has no value. If you expect to receive some help, you will post your diagnostics as requested.
-
Not sure. Post your diagnostics.
-
Check the syslog.
-
Check your shared memory. "/dev/shm" on the Zoneminder GUI. Try to keep it 50-70%. If it's too small, you are using too much main memory and starving Unraid. If it's too large you risk running out of memory for Zoneminder. You might want to check your camera settings, especially the buffers.
-
No. That's beyond what I feel UD should be doing.
-
Set the Settings->Unassigned Devices->SMB Security to 'Yes (Hidden)' and the Unraid shares will be hidden and not browseable.
-
It is possible to mount, but I believe the '$' character caused some issues in the share name with UD, so It is not allowed by UD. I don't intend to make any changes to accommodate the '$' character. Rename the share.
-
Nope.
