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. Unable to launch web control and webstream since update
      (Alexandre Adam)
   2. Re: Unable to launch web control and webstream since update
      (MrDave)


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

Message: 1
Date: Sun, 19 May 2019 15:14:53 +0200
From: Alexandre Adam <rezza...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: [Motion-user] Unable to launch web control and webstream
        since update
Message-ID:
        <CAK=w6K+Zg8=egq8h4ze3uueupfafd6hna5mbw3pf_vhyuzo...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello.

Since my update from motion 3.4 to 4.2.1, I have adapted my conf file and
sucessfully launched motion as deamon at start-up.

Nevertheless, I have this persistent errors preventing to laucnh web stream
and web control :

here is my logs :

[0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Motion 4.2.1
Started
[0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Using default log
type (ALL)
[0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Using log type
(ALL) log level (NTC)
[0:motion] [NTC] [ALL] [May 19 15:03:59] become_daemon: Motion going to
daemon mode
[0:motion] [NTC] [ALL] [May 19 15:03:59] become_daemon: Created process id
file /var/run/motion/motion.pid. Process ID is 23751
[0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Motion running as
daemon process
[0:motion] [NTC] [STR] [May 19 15:03:59] webu_start_ctrl: Starting
webcontrol on port 6789
[0:motion] [NTC] [STR] [May 19 15:03:59] *webu_start_ctrl: Unable to start
MHD*
[0:motion] [NTC] [ENC] [May 19 15:03:59] ffmpeg_global_init: No ffmpeg
functionality included
[0:motion] [NTC] [ALL] [May 19 15:03:59] translate_init: Language: English
[0:motion] [NTC] [ALL] [May 19 15:03:59] motion_start_thread: Camera ID: 0
is from /volume1/.@plugins/AppCentral/entware-ng/opt/etc/motion/motion.conf
[0:motion] [NTC] [ALL] [May 19 15:03:59] motion_start_thread: Camera ID: 0
Camera Name: (null) Service: http:
[0:motion] [NTC] [ALL] [May 19 15:03:59] main: Waiting for threads to
finish, pid: 23751
[1:ml1] [NTC] [ALL] [May 19 15:03:59] motion_init: Camera 0 started: motion
detection Enabled
[1:ml1] [NTC] [VID] [May 19 15:03:59] vid_start: Opening Netcam
[1:ml1] [NTC] [NET] [May 19 15:03:59] netcam_start: Network Camera starting
for camera ((null))
[1:ml1] [NTC] [NET] [May 19 15:03:59] netcam_setup_html: connected, going
on to read image.
[1:ml1] [NTC] [ALL] [May 19 15:03:59] image_ring_resize: Resizing
pre_capture buffer to 1 items
[1:ml1] [WRN] [NET] [May 19 15:03:59] netcam_next: called with no data in
buffer
[1:nc2] [NTC] [NET] [May 19 15:03:59] netcam_handler_loop: Camera handler
thread [2] started
[1:ml1] [NTC] [ALL] [May 19 15:04:01] image_ring_resize: Resizing
pre_capture buffer to 3 items


and here is my conf file concerning webcontrol and livestream :

############################################################
# Webcontrol configuration parameters
############################################################

# Port number used for the webcontrol.
webcontrol_port 6789

# Restrict webcontrol connections to the localhost.
webcontrol_localhost off

# Type of configuration options to allow via the webcontrol.
webcontrol_parms 2

webcontrol_interface 0
webcontrol_ipv6 on

############################################################
# Live stream configuration parameters
############################################################

# The port number for the live stream.
stream_port 0

# Restrict stream connections to the localhost.
stream_localhost off




I have disabled livestream to isolate one problem from another.

It seems my webcam (Wifi) is accessed after motion try to launch the web
server. Could that explain that we can't have a web interface withtout a
working cam accessed by motion ?

Thnaks for your feedback

regards

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

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

Message: 2
Date: Sun, 19 May 2019 10:20:43 -0600
From: MrDave <motionmrd...@gmail.com>
To: motion-user@lists.sourceforge.net
Subject: Re: [Motion-user] Unable to launch web control and webstream
        since update
Message-ID: <6ce5fe72-35ab-abd9-a718-42ff50345...@gmail.com>
Content-Type: text/plain; charset="utf-8"; Format="flowed"

The camera connecting should not cause the message below.? I suspect 
permissions or a port conflict since there only a few options that 
Motion sets for MHD and the message indicates that it can not start.? 
You can try:

1. Run from command line to see whether a normal user can start the MHD

2. Run as sudo

If either of the above work then it would be a question of what groups 
need to get added to the "motion" user which runs the daemon.? (The 
other distros do not have permission issues so I do not know which to 
add specifically).

For port conflicts, validate that Motion is not already running as a 
second instance (turn off daemon mode and reboot and validate it is not 
running when getting back in).? Also, try changing the port number 
and/or ensuring that no other process is using port 6789

Finally, if the above does not work, it would be a question of what 
options does MHD actually support on your distro which may be in the 
build log associated with MHD.? Motion is setting the following:

MHD_USE_THREAD_PER_CONNECTION, MHD_USE_POLL , MHD_USE_SELECT_INTERNALLY

and MHD_USE_DUAL_STACK (for the IPV6)


on 5/19/19 7:14 AM, Alexandre Adam wrote:
> Hello.
>
> Since my update from motion 3.4 to 4.2.1, I have adapted my conf file 
> and sucessfully launched motion as deamon at start-up.
>
> Nevertheless, I have this persistent errors preventing to laucnh web 
> stream and web control :
>
> here is my logs :
>
> [0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Motion 4.2.1 
> Started
> [0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Using default 
> log type (ALL)
> [0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Using log 
> type (ALL) log level (NTC)
> [0:motion] [NTC] [ALL] [May 19 15:03:59] become_daemon: Motion going 
> to daemon mode
> [0:motion] [NTC] [ALL] [May 19 15:03:59] become_daemon: Created 
> process id file /var/run/motion/motion.pid. Process ID is 23751
> [0:motion] [NTC] [ALL] [May 19 15:03:59] motion_startup: Motion 
> running as daemon process
> [0:motion] [NTC] [STR] [May 19 15:03:59] webu_start_ctrl: Starting 
> webcontrol on port 6789
> [0:motion] [NTC] [STR] [May 19 15:03:59] *webu_start_ctrl: Unable to 
> start MHD*
> [0:motion] [NTC] [ENC] [May 19 15:03:59] ffmpeg_global_init: No ffmpeg 
> functionality included
> [0:motion] [NTC] [ALL] [May 19 15:03:59] translate_init: Language: English
> [0:motion] [NTC] [ALL] [May 19 15:03:59] motion_start_thread: Camera 
> ID: 0 is from 
> /volume1/.@plugins/AppCentral/entware-ng/opt/etc/motion/motion.conf
> [0:motion] [NTC] [ALL] [May 19 15:03:59] motion_start_thread: Camera 
> ID: 0 Camera Name: (null) Service: http:
> [0:motion] [NTC] [ALL] [May 19 15:03:59] main: Waiting for threads to 
> finish, pid: 23751
> [1:ml1] [NTC] [ALL] [May 19 15:03:59] motion_init: Camera 0 started: 
> motion detection Enabled
> [1:ml1] [NTC] [VID] [May 19 15:03:59] vid_start: Opening Netcam
> [1:ml1] [NTC] [NET] [May 19 15:03:59] netcam_start: Network Camera 
> starting for camera ((null))
> [1:ml1] [NTC] [NET] [May 19 15:03:59] netcam_setup_html: connected, 
> going on to read image.
> [1:ml1] [NTC] [ALL] [May 19 15:03:59] image_ring_resize: Resizing 
> pre_capture buffer to 1 items
> [1:ml1] [WRN] [NET] [May 19 15:03:59] netcam_next: called with no data 
> in buffer
> [1:nc2] [NTC] [NET] [May 19 15:03:59] netcam_handler_loop: Camera 
> handler thread [2] started
> [1:ml1] [NTC] [ALL] [May 19 15:04:01] image_ring_resize: Resizing 
> pre_capture buffer to 3 items
>
>
> and here is my conf file concerning webcontrol and livestream :
>
> ############################################################
> # Webcontrol configuration parameters
> ############################################################
>
> # Port number used for the webcontrol.
> webcontrol_port 6789
>
> # Restrict webcontrol connections to the localhost.
> webcontrol_localhost off
>
> # Type of configuration options to allow via the webcontrol.
> webcontrol_parms 2
>
> webcontrol_interface 0
> webcontrol_ipv6 on
>
> ############################################################
> # Live stream configuration parameters
> ############################################################
>
> # The port number for the live stream.
> stream_port 0
>
> # Restrict stream connections to the localhost.
> stream_localhost off
>
>
>
>
> I have disabled livestream to isolate one problem from another.
>
> It seems my webcam (Wifi) is accessed after motion try to launch the 
> web server. Could that explain that we can't have a web interface 
> withtout a working cam accessed by motion ?
>
> Thnaks for your feedback
>
> regards
>
> RezzA
>
>
> _______________________________________________
> 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 13
********************************************

Reply via email to