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. Re: defunct sh processes (Dougie Nisbet) 2. Re: defunct sh processes (Dave Howorth) ---------------------------------------------------------------------- Message: 1 Date: Sat, 03 Feb 2024 20:05:13 +0000 From: Dougie Nisbet <dou...@katsura.uk> To: Motion discussion list <motion-user@lists.sourceforge.net> Subject: Re: [Motion-user] defunct sh processes Message-ID: <93ebad3223df58dd1b8c499436ae7e45d1c7cdf2.ca...@katsura.uk> Content-Type: text/plain; charset="UTF-8" That's interesting. When I looked at Mathias's motion.conf I noticed we both used on_movie_end so I did a test with this commented out and the problem still happened. I also use on_event_end though - I'll try removing that too. Dougie On Sat, 2024-02-03 at 15:39 +0000, genius3000 via Motion-user wrote: > (apologies if a blank reply came through, I hit the send button by > mistake) > > The GitHub issue tracker had a bug for this reported a few years > back. It was identified that it only occurred when using the > libcamerify wrapper. See: > https://github.com/Motion-Project/motion/issues/1522#issuecomment-1099658250 > > I've never used the wrapper, so can't speak further on whether Motion > could do something different to help prevent this or if it's directly > due to libcamerify. Would seem the best solution for now is the > scheduled restart of Motion. > > - Matt > > > On February 3, 2024 12:23:40?p.m. UTC, Mathias Koerber > <math...@koerber.org> wrote: > > That's right. I also use camerify (and this what is different > > to the prior incarnation of this server which used an older > > version). Humm. > > > > I think I will just use cron to restart motion once in a while for > > now > > until I can figure out a solution, or someone else has a > > workaround/fix > > > > On 3/2/24 20:21, motion-user-requ...@lists.sourceforge.net wrote: > > > 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. Re: defunct sh processes (Dougie Nisbet)Message: 1 > > > Date: Sat, 03 Feb 2024 12:05:34 +0000 > > > From: Dougie Nisbet <dou...@katsura.uk> > > > To: Motion discussion list <motion-user@lists.sourceforge.net> > > > Subject: Re: [Motion-user] defunct sh processes > > > Message-ID: > > > ?<7be9a6bb6762dcd1204359a43bcb22292d5ec35a.ca...@katsura.uk> > > > Content-Type: text/plain; charset="UTF-8" > > > > > > On Fri, 2024-02-02 at 12:39 +0800, Mathias Koerber wrote: > > > > Why is motion 4.6.0 leaving definct sh processes when it > > > > detects > > > > motion? > > > > > > > > > > I've just noticed this too. I don't know how long it's being > > > going on, > > > or whether it's just started. I'm running version 4.5.1 > > > > > > However, I'm ONLY seeing it on raspberry pi cameras where I'm > > > running > > > using the camera module, and starting motion using libcamerify. > > > i.e. > > > > > > /usr/bin/libcamerify /usr/bin/motion > > > > > > It doesn't happen with USB cameras where I don't use libcamerify. > > > > > > The defunct processes seem to correlate with motion detection > > > events. > > > > > > Dougie > > > > > > > > > > > > > > > dougie@pi12-garden2:~ $ ps -ef | grep defunct > > > dougie 524 13401 0 10:16 ? 00:00:00 [sh] <defunct> > > > dougie 656 13401 0 10:17 ? 00:00:00 [sh] <defunct> > > > dougie 657 13401 0 10:17 ? 00:00:00 [sh] <defunct> > > > dougie 894 13401 0 10:17 ? 00:00:00 [sh] <defunct> > > > dougie 1018 13401 0 10:18 ? 00:00:00 [sh] <defunct> > > > dougie 1019 13401 0 10:18 ? 00:00:00 [sh] <defunct> > > > dougie 2739 13401 0 10:30 ? 00:00:00 [sh] <defunct> > > > dougie 2883 13401 0 10:30 ? 00:00:00 [sh] <defunct> > > > dougie 2885 13401 0 10:30 ? 00:00:00 [sh] <defunct> > > > dougie 3947 13401 0 10:36 ? 00:00:00 [sh] <defunct> > > > dougie 4125 13401 0 10:37 ? 00:00:00 [sh] <defunct> > > > dougie 4126 13401 0 10:37 ? 00:00:00 [sh] <defunct> > > > dougie 4362 13401 0 10:38 ? 00:00:00 [sh] <defunct> > > > dougie 4498 13401 0 10:38 ? 00:00:00 [sh] <defunct> > > > dougie 4499 13401 0 10:38 ? 00:00:00 [sh] <defunct> > > > dougie 5028 13401 0 10:41 ? 00:00:00 [sh] <defunct> > > > dougie 5114 13401 0 10:41 ? 00:00:00 [sh] <defunct> > > > dougie 5115 13401 0 10:41 ? 00:00:00 [sh] <defunct> > > > dougie 6827 13401 0 10:53 ? 00:00:00 [sh] <defunct> > > > dougie 6944 13401 0 10:53 ? 00:00:00 [sh] <defunct> > > > dougie 6945 13401 0 10:53 ? 00:00:00 [sh] <defunct> > > > dougie 7222 13401 0 10:54 ? 00:00:00 [sh] <defunct> > > > dougie 7308 13401 0 10:54 ? 00:00:00 [sh] <defunct> > > > dougie 7309 13401 0 10:54 ? 00:00:00 [sh] <defunct> > > > dougie 7739 13401 0 10:56 ? 00:00:00 [sh] <defunct> > > > dougie 7806 13401 0 10:56 ? 00:00:00 [sh] <defunct> > > > dougie 7807 13401 0 10:56 ? 00:00:00 [sh] <defunct> > > > dougie 9487 13401 0 11:07 ? 00:00:00 [sh] <defunct> > > > dougie 9610 13401 0 11:08 ? 00:00:00 [sh] <defunct> > > > dougie 9611 13401 0 11:08 ? 00:00:00 [sh] <defunct> > > > dougie 9718 13401 0 11:08 ? 00:00:00 [sh] <defunct> > > > dougie 9901 13401 0 11:08 ? 00:00:00 [sh] <defunct> > > > dougie 9902 13401 0 11:08 ? 00:00:00 [sh] <defunct> > > > dougie 10516 13401 0 07:55 ? 00:00:00 [sh] <defunct> > > > dougie 10633 13401 0 07:55 ? 00:00:00 [sh] <defunct> > > > dougie 10634 13401 0 07:55 ? 00:00:00 [sh] <defunct> > > > dougie 12554 13401 0 08:08 ? 00:00:00 [sh] <defunct> > > > dougie 12633 13401 0 08:09 ? 00:00:00 [sh] <defunct> > > > dougie 12634 13401 0 08:09 ? 00:00:00 [sh] <defunct> > > > dougie 16977 13401 0 08:39 ? 00:00:00 [sh] <defunct> > > > dougie 17161 13401 0 08:40 ? 00:00:00 [sh] <defunct> > > > dougie 17162 13401 0 08:40 ? 00:00:00 [sh] <defunct> > > > dougie 17228 13736 0 12:00 pts/0 00:00:00 grep --color=auto > > > defunct > > > dougie 17347 13401 0 08:40 ? 00:00:00 [sh] <defunct> > > > dougie 17475 13401 0 08:41 ? 00:00:00 [sh] <defunct> > > > dougie 17476 13401 0 08:41 ? 00:00:00 [sh] <defunct> > > > dougie 19244 13401 0 08:52 ? 00:00:00 [sh] <defunct> > > > dougie 19346 13401 0 08:52 ? 00:00:00 [sh] <defunct> > > > dougie 19347 13401 0 08:52 ? 00:00:00 [sh] <defunct> > > > dougie 19704 13401 0 08:54 ? 00:00:00 [sh] <defunct> > > > dougie 19955 13401 0 08:55 ? 00:00:00 [sh] <defunct> > > > dougie 19956 13401 0 08:55 ? 00:00:00 [sh] <defunct> > > > dougie 20047 13401 0 08:55 ? 00:00:00 [sh] <defunct> > > > dougie 20142 13401 0 08:55 ? 00:00:00 [sh] <defunct> > > > dougie 20143 13401 0 08:55 ? 00:00:00 [sh] <defunct> > > > dougie 20262 13401 0 08:55 ? 00:00:00 [sh] <defunct> > > > dougie 20432 13401 0 08:56 ? 00:00:00 [sh] <defunct> > > > dougie 20433 13401 0 08:56 ? 00:00:00 [sh] <defunct> > > > dougie 22352 13401 0 09:08 ? 00:00:00 [sh] <defunct> > > > dougie 22473 13401 0 09:09 ? 00:00:00 [sh] <defunct> > > > dougie 22474 13401 0 09:09 ? 00:00:00 [sh] <defunct> > > > dougie 22572 13401 0 09:09 ? 00:00:00 [sh] <defunct> > > > dougie 22760 13401 0 09:09 ? 00:00:00 [sh] <defunct> > > > dougie 22762 13401 0 09:09 ? 00:00:00 [sh] <defunct> > > > dougie 22870 13401 0 09:09 ? 00:00:00 [sh] <defunct> > > > dougie 23005 13401 0 09:10 ? 00:00:00 [sh] <defunct> > > > dougie 23006 13401 0 09:10 ? 00:00:00 [sh] <defunct> > > > dougie 24617 13401 0 09:21 ? 00:00:00 [sh] <defunct> > > > dougie 24740 13401 0 09:22 ? 00:00:00 [sh] <defunct> > > > dougie 24741 13401 0 09:22 ? 00:00:00 [sh] <defunct> > > > dougie 25034 13401 0 09:23 ? 00:00:00 [sh] <defunct> > > > dougie 25146 13401 0 09:23 ? 00:00:00 [sh] <defunct> > > > dougie 25147 13401 0 09:23 ? 00:00:00 [sh] <defunct> > > > dougie 27120 13401 0 09:36 ? 00:00:00 [sh] <defunct> > > > dougie 27243 13401 0 09:36 ? 00:00:00 [sh] <defunct> > > > dougie 27244 13401 0 09:36 ? 00:00:00 [sh] <defunct> > > > dougie 32584 13401 0 10:15 ? 00:00:00 [sh] <defunct> > > > dougie 32714 13401 0 10:16 ? 00:00:00 [sh] <defunct> > > > dougie 32715 13401 0 10:16 ? 00:00:00 [sh] <defunct>Subject: > > > Digest FooterMotion-user mailing list > > > Motion-user@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/motion-userEnd of > > > Motion-user Digest, Vol 210, Issue 2 > > > ******************************************* > > > > > 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 > _______________________________________________ > 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 ------------------------------ Message: 2 Date: Sat, 3 Feb 2024 20:35:55 +0000 From: Dave Howorth <d...@howorth.org.uk> To: motion-user@lists.sourceforge.net Subject: Re: [Motion-user] defunct sh processes Message-ID: <20240203203555.1f049...@acer-suse.fritz.box> Content-Type: text/plain; charset=US-ASCII On Sat, 03 Feb 2024 15:39:44 +0000 genius3000 via Motion-user <motion-user@lists.sourceforge.net> wrote: > (apologies if a blank reply came through, I hit the send button by > mistake) > > The GitHub issue tracker had a bug for this reported a few years > back. It was identified that it only occurred when using the > libcamerify wrapper. See: > https://github.com/Motion-Project/motion/issues/1522#issuecomment-1099658250 I don't use the wrapper either but I see that the motion issue is marked as completed, and I can't find anything related at https://bugs.libcamera.org/ so maybe somebody who does use the wrapper should file a bug there? > I've never used the wrapper, so can't speak further on whether Motion > could do something different to help prevent this or if it's directly > due to libcamerify. Would seem the best solution for now is the > scheduled restart of Motion. ------------------------------ ------------------------------ 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 210, Issue 4 *******************************************