Send Motion-user mailing list submissions to
        motion-user@lists.sourceforge.net

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/motion-user
or, via email, send a message with subject or body 'help' to
        motion-user-requ...@lists.sourceforge.net

You can reach the person managing the list at
        motion-user-ow...@lists.sourceforge.net

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Motion-user digest..."


Today's Topics:

   1. Random thread crashing (R. M.)
   2. Motion on OpenBSD (Allan Peda)
   3. Re: Random thread crashing (tosiara)


----------------------------------------------------------------------

Message: 1
Date: Tue, 7 May 2019 13:36:01 -0700
From: "R. M." <rmbusy+mot...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Random thread crashing
Message-ID:
        <caeefi2yovcq+zjxxr3rvmzp0y2q9p6w4phybcgvio2xrjiv...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi,

   I'm using Motion 4.0.1, with 8 threads all using networked IP cameras.
Five are configured for snapshots, 3 are streaming at low frame rates (5
frames/sec).  All cameras are on their own network (dedicated wire).  A
second network interface is connected to the main network, for accessing
image data.

   A couple times a week, I have to restart one to three threads (gray
image on web page).  Is this a known issue?  I searched around but didn't
find
anything relevant to this issue.  I reviewed the release notes from
4.0.1 to 4.2.2, but nothing jumped out as a likely fix, or even as a
related
issue.

   I'm considering upgrading everything to the latest (OS plus Motion),
but really don't have the time to invest in this at the moment.  If this
was a known issue and was fixed, I'll bite the bullet and do the
upgrades.  Otherwise, is there a way to get Motion to detect a problem,
and auto restart a thread?  On rare occasions, I need to reboot the
offending camera, but usually just a thread restart from the web page
fixes the issue.

   I'm running Motion on a Rock64 w/4GB RAM, 8TB USB HS drive, running
Arch64 Linux.


--
Rob.
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 2
Date: Tue, 7 May 2019 23:42:05 -0400
From: Allan Peda <bizco...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: [Motion-user] Motion on OpenBSD
Message-ID:
        <CAEPoj6xF0Nb2pv+7X9U2Q-rf+GnhwQdhAmT4oteYpfPe0JO=a...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

I prefer OpenBSD for dedicated server installs such as video surveillance,
but had thought that motion was not ported to that OS.  It seems I may be
mistaken.

https://github.com/Motion-Project/motion/search?q=openbsd&unscoped_q=openbsd

Any experience here building/using motion on OpenBSD?
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------

Message: 3
Date: Wed, 8 May 2019 07:48:27 +0300
From: tosiara <tosi...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Random thread crashing
Message-ID:
        <cachtdwtotbmfyenyak__sdwzh3ezrjv5fwgakgrmwfs8ihh...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Try to increase motion logging and ispect what happens when you get grey
image

On Tue, May 7, 2019, 23:36 R. M. <rmbusy+mot...@gmail.com> wrote:

> Hi,
>
>    I'm using Motion 4.0.1, with 8 threads all using networked IP cameras.
> Five are configured for snapshots, 3 are streaming at low frame rates (5
> frames/sec).  All cameras are on their own network (dedicated wire).  A
> second network interface is connected to the main network, for accessing
> image data.
>
>    A couple times a week, I have to restart one to three threads (gray
> image on web page).  Is this a known issue?  I searched around but didn't
> find
> anything relevant to this issue.  I reviewed the release notes from
> 4.0.1 to 4.2.2, but nothing jumped out as a likely fix, or even as a
> related
> issue.
>
>    I'm considering upgrading everything to the latest (OS plus Motion),
> but really don't have the time to invest in this at the moment.  If this
> was a known issue and was fixed, I'll bite the bullet and do the
> upgrades.  Otherwise, is there a way to get Motion to detect a problem,
> and auto restart a thread?  On rare occasions, I need to reboot the
> offending camera, but usually just a thread restart from the web page
> fixes the issue.
>
>    I'm running Motion on a Rock64 w/4GB RAM, 8TB USB HS drive, running
> Arch64 Linux.
>
>
> --
> Rob.
>
> _______________________________________________
> Motion-user mailing list
> Motion-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/motion-user
> https://motion-project.github.io/
>
> Unsubscribe: https://lists.sourceforge.net/lists/options/motion-user
-------------- next part --------------
An HTML attachment was scrubbed...

------------------------------



------------------------------

Subject: Digest Footer

_______________________________________________
Motion-user mailing list
Motion-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/motion-user


------------------------------

End of Motion-user Digest, Vol 155, Issue 5
*******************************************

Reply via email to