Bug 1113815 - Zoneminder runs but won't create any events
Summary: Zoneminder runs but won't create any events
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: zoneminder
Version: 20
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Orphan Owner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-27 02:17 UTC by Bill Gradwohl
Modified: 2015-06-29 21:21 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2015-06-29 21:21:34 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
This is repeated endlessly in the log. (1.62 KB, text/x-log)
2014-06-27 02:17 UTC, Bill Gradwohl
no flags Details

Description Bill Gradwohl 2014-06-27 02:17:31 UTC
Created attachment 912648 [details]
This is repeated endlessly in the log.

Description of problem:
I'm familiar with installing ZM.
Fresh F20 install, fully patched.
Have kernel.shmmax=536870912 in /etc/sysctl.d/60-kernel-shm.conf .
SeLinux disabled, as it won't run at all otherwise.

ZM Console looks normal. When a camera is set to Modect, no events are ever saved. I don't think any are created/detected. When set to Record, 1000 jpg files end up in the swap area but these don't get saved either. The Event area is always empty.

Streaming works fine in Firefox, but is intermittent in Chrome.

In Firefox, the images look fine, as expected, but no events are saved.

When set to 15 frames, errors appear in the log within the HTML system, but no errors are ever recorded in /var/log/zoneminder.
Lowering frames to 5 eliminates the errors related to volume, but other errors are still present and repeat endlessly. Section of log attached.

I have a few boxes available for testing for a while, if that helps.

Comment 1 Fedora Admin XMLRPC Client 2015-04-07 22:20:59 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 2 Fedora End Of Life 2015-05-29 12:14:11 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2015-06-29 21:21:34 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.