Jump to content

thegizzard

Members
  • Posts

    259
  • Joined

  • Last visited

Posts posted by thegizzard

  1. Does anyone have problems with MODECT recording a few seconds of gray screen instead of actual motion? It looks almost like signal loss but happens very frequently. I am getting a lot of junk on my disk. I've searched the zone minder docs and forums and can't find a reference to this. I am using amcrest cams.

    Sent from my SM-N950U using Tapatalk

  2. 33 minutes ago, dlandon said:

    Yes.  The file has to be linux format.

    BOOM.

     

    That was it.

     

    Below is now the output from the terminal.

     

    root@GrimLock:~# docker exec -it Zoneminder bash
    root@8a037a6782e7:/# crontab -l
    # Daytime camera operation
    0 8 * * * /usr/bin/zmpkg.pl Daytime
    
    # Nighttime camera operation
    0 20 * * * /usr/bin/zmpkg.pl Nighttime
    root@8a037a6782e7:/#

     

    Awesome as always dlandon

  3. 12 minutes ago, dlandon said:

    Run the commands manually and see if the state changes.

    Both commands work manually from the terminal.

     

    Below is from the log

     

    Aug 5 07:32:08 8a037a6782e7 zmpkg[3118]: INF [Command: Nightime]
    Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Command: Nighttime]
    Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Sanity checking States table...]
    Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Command: state]
    Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Updating DB: Nighttime]
    Aug 5 07:32:35 8a037a6782e7 zmpkg[3124]: INF [Marking Nighttime as Enabled]
    
    Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Command: Daytime]
    Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Sanity checking States table...]
    Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Command: state]
    Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Updating DB: Daytime]
    Aug 5 07:36:50 8a037a6782e7 zmpkg[3390]: INF [Marking Daytime as Enabled]

     

    But when I check for cron I get this result

     

    root@8a037a6782e7:/# crontab -l
    no crontab for root

     

    This is the contents of my 'cron' file in appdata/Zoneminnder/

    # Daytime camera operation
    0 8 * * * /usr/bin/zmpkg.pl Daytime
    
    # Nightime camera operation
    0 20 * * * /usr/bin/zmpkg.pl Nighttime

     

    Could the problem be that I created that file with notepad on windows?  just a guess.

     

     

     

  4. Your cameras need to be set for the two states - 'Daytime' and 'Nightime'.  Check the Zoneminder docs for how to set the camera states.
    Understood.  I have 2 camera states.  One used for Daytime and one for Nighttime. They are called Daytime and Nightime.  I can change these manually in Zoneminder or zmNinja.  What I cannot do is automate the changing of these states.  The first post shows how to do it using the commands i quoted above, but it does not seem to work for me.  

    Any suggestions?



    Sent from my SM-N950U using Tapatalk

  5. On 5/2/2018 at 7:14 PM, dlandon said:

    You have to be more specific on what didn't work.  Verify that the 'cron' file was loaded properly.  You can check if your 'cron' file is being loaded by getting into the Zoneminder command line:

    
    docker exec -it Zoneminder bash

    Then type the following command:

    
    crontab -l

    You should see your cron entries.  If not, troubleshoot the 'cron' file name and placement.  Be sure you are using a Linux type editor to create the 'cron' file.

     

    If the 'cron file is loaded properly but still not doing what you want, check that you have created the events properly.  You can test that on the command line of the docker:

    
    /usr/bin/zmpkg.pl Daytime

    This will put Zoneminder in the Daytime mode of operation.

    
    /usr/bin/zmpkg.pl Nightime

    This will put Zoneminder in the Nightime mode of operation.

     

    You'll have to consult the Zoneminder documentation on configuring these different modes.

    Does this work?

     

    I have a single file called cron

     

    It contains:

     

    # Daytime camera operation
    0 8 * * * /usr/bin/zmpkg.pl Daytime

    # Nightime camera operation
    0 20 * * * /usr/bin/zmpkg.pl Nighttime

     

    I restarted the zoneminder docker

     

    When i run the commands ...

     

    docker exec -it Zoneminder bash

    crontab -l

     

    It returns

     

    no crontab for root

     

    i dont think these commands were added to crontab and zoneminder has not switched modes.

     

    Any recommendations?

     

    I am not even sure I have cron on my system.  I have never used it for anything else.

  6. 2 hours ago, dlandon said:

    There is an update to the Zoneminder Docker.  This is still version 1.30.4.  I will be working on 1.32 soon.

    The update included:

    • zmeventnotification updated to v1.6.  The zmeventnotification.ini appears to be updated on each release.  The zmeventnotification.ini file will be copied to the /config/ directory on every update of the docker.  If you make any changes to the zmeventnotification.ini file, you'll need to make those changes after a docker update.
    • Changes to Apache server for better security.  If you have a problem with the Zoneminder webpage, clear your browser cache as the old settings will prevent the web page from showing up.  You may get a php file display instead of the Zoneminder webpage.

    Thanks dlandon.  Your efforts are much appreciated.  Donation Sent!

  7. This may be a dumb question, so forgive me.

     

    I am trying to figure out the easiest way to display my IP Cams on my TV.  The IP Cams display on a browser.  I would like to run the browser on my unraid machine and display it on my TV via an HDMI cable.  Is there an easy way to do this? 

     

    I currently have no monitor attached to the unraid machine and use IPMI if I need to access the console directly.

     

    I am trying to avoid buying a machine to display one web page.

     

  8. I intended disk9 to be a dedicated disk for ipcam jpgs.  this is a lot of small files and i didnt want to have the array spinning all disks for these files.  so i put it to only use disk9 and for the share to be one of the few that use the cache.

     

    i imagine i could have done this without using the global settings, but thats where i screwed up.

     

  9. Ok.  

     

    So I removed disk9 from the array.  i checked then checked and fixed the file system.  mover still reported no space left on device for disk9

     

    I reformatted disk9.  I removed all of the ipcams files from the cache drive.  tried the mover again and i still get the same error.  Can you think of any reason why it thinks disk9 is full?  or maybe more importantly why mover cannot write to disk9?

     

    updated diagnostics.

     

    grimlock-diagnostics-20180410-1146.zip

×
×
  • Create New...