Motion - Bug Report 2004x 10x 26x 134906

BUG: Receiving application bug warnings from SYSLOG in Redhat AS 3

When running motion as daemon, I am getting application bug warnings emitted from SYSLOG an Redhat AS 3. The error is as follows.

Oct 26 08:43:43 localhost kernel: application bug: motion(13593) has SIGCHLD set to SIG_IGN but calls wait().
Oct 26 08:43:43 localhost kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.

Here are the results of the following commands.

[root@localhost motion]# rpm -qa curl xmlrpc-c ffmpeg mysql postgresql
xmlrpc-c-0.9.9-1
mysql-3.23.58-2.3
curl-7.10.6-4.1
ffmpeg-0.4.8-3.1.fc2.fr
[root@localhost motion]# cat /etc/redhat-release
Red Hat Enterprise Linux AS release 3 (Taroon Update 3)
[root@localhost motion]# cat /proc/version
Linux version 2.4.21-20.ELsmp (bhcompile@tweety.build.redhat.com) (gcc version 3.2.3 20030502 (Red Hat Linux 3.2.3-42)) #1 SMP Wed Aug 18 20:46:40 EDT 2004

Test case

Setup motion to run as a daemon on Redhat AS 3. Setup SYSLOG to emit to a file. View the SYSLOG log file after running motion as a daemon.

Environment

Motion version: 3.1.17
Shared libraries: curl, xmlrpc, ffmpeg, mysql, postgresql
Server OS: Redhat AS 3

-- PeterS - 26 Oct 2004

Follow up

This is an old known problem and I believe it is only visible in certain 2.4 kernel versions from Red Hat.

I am curious about one thing. Does this problem happen with the experimental release I made last night? There is code related to Berkeley encoding that is removed and it contained the only wait() in the entire code.

Get it here: http://www.lavrsen.dk/twiki/bin/view/Motion/MotionRelease3x1x18snap2

There is an extra patch file attached. You do not need it to do the test. It does not harm either. It just makes the example motion-dist.conf more complete.

-- KennethLavrsen - 26 Oct 2004

Follow up

I am now using the version you reference above but am still receiving the message.

Nov  2 16:35:06 localhost motion: Processing thread 0 - config file /etc/motion/motion.conf
Nov  2 16:35:06 localhost motion: Unknown config option: "mpeg_encode"
Nov  2 16:35:06 localhost motion: Unknown config option: "mpeg_encode_bin"
Nov  2 16:35:06 localhost motion: Unknown config option: "adjust_rate"
Nov  2 16:35:06 localhost motion: Unknown config option: "jpg_cleanup"
Nov  2 16:35:06 localhost motion: Unknown config option: "berkeley_single_directory"
Nov  2 16:35:06 localhost motion: Unknown config option: "sql_log_image"
Nov  2 16:35:06 localhost motion: Unknown config option: "sql_log_snapshot"
Nov  2 16:35:06 localhost motion: Unknown config option: "sql_log_mpeg"
Nov  2 16:35:06 localhost motion: Unknown config option: "sql_log_timelapse"
Nov  2 16:35:06 localhost motion: Unknown config option: "sql_log_prediction"
Nov  2 16:35:06 localhost motion: Processing thread 1 - config file /etc/motion/cam1.conf
Nov  2 16:35:06 localhost motion: Processing thread 2 - config file /etc/motion/cam2.conf
Nov  2 16:35:06 localhost motion: Processing thread 3 - config file /etc/motion/cam3.conf
Nov  2 16:35:06 localhost motion: Processing thread 4 - config file /etc/motion/cam4.conf
Nov  2 16:35:06 localhost motion: motion running as daemon process
Nov  2 16:35:06 localhost kernel: application bug: motion(9247) has SIGCHLD set to SIG_IGN but calls wait().
Nov  2 16:35:06 localhost kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.
Nov  2 16:36:06 localhost kernel: application bug: motion(9250) has SIGCHLD set to SIG_IGN but calls wait().
Nov  2 16:36:06 localhost kernel: (see the NOTES section of 'man 2 wait'). Workaround activated.

-- PeterS - 02 Nov 2004

Fix Record

A change of signal handling has been implemented which should eliminate this bug. Please confirm that MotionRelease3x1x18snap10 no longer produces the warning.

-- KennethLavrsen - 15 Jan 2005

BugReportForm edit

TopicTitle Receiving application bug warnings from SYSLOG in Redhat AS 3
BugStatus Released
AssignedBugTo KennethLavrsen
SubmittedBy PeterS
Topic revision: r5 - 30 Jan 2005, KennethLavrsen
Copyright © 1999-2017 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Please do not email Kenneth for support questions (read why). Use the Support Requests page or join the Mailing List.
This website only use harmless session cookies. See Cookie Policy for details. By using this website you accept the use of these cookies.