Motion - Support Question 2007x 07x 03x 090059

netcam_url added, but no daemon process started or images captured.

Question

additional: apologies, I attached the config from another server. This is the correct file. I have uncommented that line, assigned a username and password to the camera and added this entry to the file. It still says the below error messages, "problem connecting to the stream".Rich.

I have added my netcam_url and have validated that i can access the images in a web browser. When I start motion, there is no daemon process started and i do not receive any snapshots.(i do not require videos).

; http://192.168.0.113:80/image.jpg (dcs-900)

# Make automated snapshot every N seconds (default: 0 = disabled)
snapshot_interval 2

i do not have a password set for the camera.


# Target base directory for pictures and films
# Recommended to use absolute path. (Default: current working directory)

Attached is the motion conf. I have made the suggested changes and am now receiving the following error messages when running the application.

[0] Processing thread 0 - config file /usr/local/etc/motion.conf
[0] Unknown config option "ffmpeg_cap_new"
[0] Unknown config option "ffmpeg_cap_motion"
[0] Unknown config option "ffmpeg_timelapse"
[0] Unknown config option "ffmpeg_timelapse_mode"
[0] Unknown config option "ffmpeg_bps"
[0] Unknown config option "ffmpeg_variable_bitrate"
[0] Unknown config option "ffmpeg_video_codec"
[0] Unknown config option "ffmpeg_deinterlace"
[0] Unknown config option "movie_filename"
[0] Unknown config option "timelapse_filename"
[0] Unknown config option "sql_log_image"
[0] Unknown config option "sql_log_snapshot"
[0] Unknown config option "sql_log_mpeg"
[0] Unknown config option "sql_log_timelapse"
[0] Unknown config option "sql_query"
[0] Thread 1 is from /usr/local/etc/motion.conf
[1] Thread started
[0] httpd bind(): Cannot assign requested address
[1] bind(): Cannot assign requested address
[1] Problem enabling stream server: Cannot assign requested address
[1] Started stream webcam server in port 8081
[1] netcam camera handler: finish set, exiting
[1] Thread exiting
[0] Motion terminating

target_dir /var/motion_images/cam1

Environment

Motion version: 3.2.7
ffmpeg version:  
Libraries:  
Server OS: rhel3 ES 2.4.21-4.EL

-- RichardBall - 03 Jul 2007

Answer

The above syntax looks wrong.

The ; means comment. And there is not netcam_url in front of the url.

You can attach your motion.conf to this topic and let us look what is wrong.

If you start Motion with -n then you get better error feedback (no daemon mode)

-- KennethLavrsen - 03 Jul 2007


As Kenneth already told you the syntax is wrong , take a look to this :

http://www.lavrsen.dk/twiki/bin/view/Motion/WorkingDevices#D_Link_DCS_900_net_camera

Moreover your motion.conf is quite "weird" :

1-. netcam_url is not set ( you must remove ; to enable it )
; http://192.168.0.113/video.cgi

2-. set motion in no daemon mode
daemon off

3-. change control_port to any port not used
control_port 10081

4-. change webcam_port value to any port not used
webcam_port 10080

Good luck !

Please recheck the guide http://www.lavrsen.dk/twiki/bin/view/Motion/MotionGuide all your question are well explained there

-- AngelCarpintero - 04 Jul 2007


Please post your comments following the logical order , not changing all the time your question.

You didn't post your update motion log either set daemon off .... and you didn't follow the advice about your camera

http://www.lavrsen.dk/twiki/bin/view/Motion/WorkingDevices#D_Link_DCS_900_net_camera

-- AngelCarpintero - 04 Jul 2007

SupportForm edit

TopicTitle netcam_url added, but no daemon process started or images captured.
SupportStatus AnsweredQuestions
AssignedQuestionTo
SubmittedBy RichardBall
Topic attachments
I Attachment Action Size Date Who Comment
motion.confconf motion.conf manage 21 K 04 Jul 2007 - 05:30 UnknownUser motion.conf
Topic revision: r6 - 04 Jul 2007, AngelCarpintero
Copyright © 1999-2019 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.