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


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

Message: 1
Date: Wed, 22 May 2019 11:15:36 +0200
From: Alexandre Adam <rezza...@gmail.com>
To: Motion discussion list <motion-user@lists.sourceforge.net>
Subject: Re: [Motion-user] Unable to launch web control and webstream
        since update
Message-ID:
        <CAK=w6KK96ZKxfx=Uw=adltibej8g2gqxx+fv6juwgyoynj6...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hello and thank you very much for your answer.

I found that I have "*Package libmicrohttpd-ssl (0.9.62-2) installed in
root is up to date*".

My Motion is installed here.
/volume1/.@plugins/AppCentral/entware-ng/opt/etc/motion

and here what I foud concerning LibMicrohttpd :

root@xxxx:/ # find -name *libmicrohttpd*
./volume1/.@plugins/AppCentral/entware-ng/opt/lib/libmicrohttpd.so.12.49.0
./volume1/.@plugins/AppCentral/entware-ng/opt/lib/opkg/info/libmicrohttpd-ssl.list
./volume1/.@plugins/AppCentral/entware-ng/opt/lib/opkg/info/libmicrohttpd-ssl.control
./volume1/.@plugins/AppCentral/entware-ng/opt/lib/libmicrohttpd.so
./volume1/.@plugins/AppCentral/entware-ng/opt/lib/libmicrohttpd.so.12


It seems I can't launch any MHD command in the terminal being root, any
MHD_xxxx command seems to be recognized.
My distro is very specific (NAS Asustor).

Being not a linux expert, What can you recommand to me ?

thanks again

rezza


On Sun, 19 May 2019 at 18:21, MrDave <motionmrd...@gmail.com> wrote:

> 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 
> listMotion-user@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/motion-userhttps://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
-------------- 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 16
********************************************

Reply via email to