Message: An error occurred. Refreshing recommended. #13
Comments
|
Sorry, I had used: rtsp://192.168.2.9:88/videoSub + credentials in appropriate boxes. The error message disappeared after I deleted the existing thread-X.conf files from /etc/motioneye, so one problem solved! I am now getting 'unable to open video device' + grey camera screen. So, rtsp is not working yet. I do get images when I configure the camera as http (jpeg) camera using the string: http://192.168.2.9:88/cgi-bin/CGIProxy.fcgi?cmd=snapPicture2&usr=XXXX&pwd=XXXX. Any advice re. rtsp configuration? |
|
|
Thanks for your help/ The version of motion I am using is Unofficial-Git-d71cebf I indeed compiled motion from scratch after uninstalling the wheezy distribution version No more error messages. I start-up motioneye server from the command line by running: /etc//init.d//motioneye start In my browser I go to localhost:8765, the program opens and I log in as admin. Two camera screens appear pointing to one and the same camera, the FI9853EP. One is configured as rtsp and the second to http with the strings I gave you earlier in the thread. The first camera screen is grey with an 'unable to open video device' message, the second gives me a good picture. |
|
The fact that Please send me the |
|
That motioneye message no longer appears in the motioneye log file. What I am getting in the motion.log is the following: [0] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motioneye/motion.conf |
|
After installing the new motion, have you restarted motionEye and re-added your cameras? It looks as though motionEye is still using the old directives in the config files. |
|
I actually did. I compiled motion using your wiki instructions, and even Should I make changes in my config files? 2015-09-14 12:52:28: [motioneye] INFO: interrupt signal received, On Mon, Sep 14, 2015 at 1:43 PM, Calin Crisan notifications@github.com
This email and any files sent with it are confidential and intended only United Bible Societies Association, a company limited by guarantee. |
|
There's a reference to a thread-8.conf (!) in your logs. Please remove all the thread-x.conf files as well as motion.conf and re-add everything from scratch. If the problem still persists, I'd need some steps to reproduce it. |
|
I have followed your instructions, deleted the thread-x.config files and the motion.conf. I added the rtsp camera with the rtsp settings and still no image. [0] [NTC] [ALL] conf_load: Processing thread 0 - config file /etc/motioneye/motion.conf and this is motioneye.log: 2015-09-14 14:57:30: [motioneye] INFO: interrupt signal received, shutting down... Kindly advise what I can do next. Thanks for your patience! I have rebooted my camera, just in case....
|
|
|
OK. Re 1) It was commented out (automatic detection), but I enabled it with the right path (/usr/local/bin/motion)
|
|
Could you set up SSH remote access for me on your server so I can try to reproduce the problem? |
|
Sure, but I do not know if I can do that without a bit of help from your side. |
|
I found some instructions and managed to install SSH server. Now I guess I have to forward port 22 to the raspberrypi2, correct? |
|
Yes that is correct. Pls share the information privately with christian ... Cheers, Remko Lodder
|
|
Thanks, I just did. On Monday, 14 September 2015, remkolodder notifications@github.com wrote:
This email and any files sent with it are confidential and intended only United Bible Societies Association, a company limited by guarantee. |
|
@kdeblois the problem with your setup was the fact that motion was compiled without ffmpeg support. This was due to the fact that on Raspbian, ffmpeg files are installed in non-standard locations (as far as I can tell). As a consequence:
|
Using 0.27.2 on a raspberrypi2...
I started getting this message right after upgrading motion from what is in the wheezy distribution to the Mr-Dave fork version. I am no longer able to add and save any camera and keep getting this message. I did uninstall the old version before compiling the new.
No camera configuration works. I had used http://192.168.2.9:88/videoSub with user name and password in the appropriate boxes.
By the way, I did have the camera working in 0.27.2 (but not with rtsp) with the old version of motion from the distribution.
As this tool does not seem to allow me to attach a text file, let me copy and paste part of the log file:
2015-09-13 23:06:17: [motioneye] ERROR: 500 GET /config/list/?_=1442178377588 (127.0.0.1) 12.35ms
2015-09-13 23:10:43: [motioneye] ERROR: 'stream_localhost'
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1369, in _stack_context_handle_exception
raise_exc_info((type, value, traceback))
File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1572, in wrapper
result = method(self, _args, *_kwargs)
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 175, in get
self.list()
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 121, in wrapper
return func(self, _args, *kwargs)
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 590, in list
ui_config = config.motion_camera_dict_to_ui(local_config)
File "/usr/local/lib/python2.7/dist-packages/motioneye/config.py", line 929, in motion_camera_dict_to_ui
'video_streaming': not data['stream_localhost'],
KeyError: 'stream_localhost'
2015-09-13 23:10:43: [motioneye] ERROR: 500 GET /config/list/?=1442178643356 (127.0.0.1) 12.14ms
2015-09-13 23:25:35: [motioneye] ERROR: 'stream_localhost'
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1369, in _stack_context_handle_exception
raise_exc_info((type, value, traceback))
File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1572, in wrapper
result = method(self, _args, *_kwargs)
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 175, in get
self.list()
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 121, in wrapper
return func(self, _args, *kwargs)
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 590, in list
ui_config = config.motion_camera_dict_to_ui(local_config)
File "/usr/local/lib/python2.7/dist-packages/motioneye/config.py", line 929, in motion_camera_dict_to_ui
'video_streaming': not data['stream_localhost'],
KeyError: 'stream_localhost'
2015-09-13 23:25:35: [motioneye] ERROR: 500 GET /config/list/?=1442179535568&_username=admin&_signature=8628f341bfbc29406fe41b04ce2563d0e3f407f6 (127.0.0.1) 12.75ms
2015-09-13 23:27:03: [motioneye] INFO: adding new camera with id 8...
2015-09-13 23:27:10: [motioneye] ERROR: 'stream_localhost'
Traceback (most recent call last):
File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1369, in _stack_context_handle_exception
raise_exc_info((type, value, traceback))
File "/usr/local/lib/python2.7/dist-packages/tornado/web.py", line 1572, in wrapper
result = method(self, _args, *_kwargs)
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 175, in get
self.list()
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 121, in wrapper
return func(self, _args, *kwargs)
File "/usr/local/lib/python2.7/dist-packages/motioneye/handlers.py", line 590, in list
ui_config = config.motion_camera_dict_to_ui(local_config)
File "/usr/local/lib/python2.7/dist-packages/motioneye/config.py", line 929, in motion_camera_dict_to_ui
'video_streaming': not data['stream_localhost'],
KeyError: 'stream_localhost'
2015-09-13 23:27:10: [motioneye] ERROR: 500 GET /config/list/?=1442179629052&_username=admin&_signature=5715499591c41e3d0e41483e828611078ffaee4f (127.0.0.1) 11.67ms
2015-09-13 23:33:24: [motioneye] INFO: interrupt signal received, shutting down...
2015-09-13 23:33:24: [motioneye] INFO: server stopped
2015-09-13 23:33:27: [motioneye] INFO: motion stopped
2015-09-13 23:33:27: [motioneye] INFO: bye!
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 104] Connection reset by peer
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 104] Connection reset by peer
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 104] Connection reset by peer
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 104] Connection reset by peer
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 104] Connection reset by peer
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 104] Connection reset by peer
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 111] Connection refused
2015-09-13 23:33:27: [relayevent] ERROR: failed to relay event: [Errno socket error] [Errno 111] Connection refused
2015-09-13 23:33:45: [motioneye] INFO: hello! this is motionEye server 0.27.2
2015-09-13 23:33:45: [motioneye] INFO: motion not installed
The text was updated successfully, but these errors were encountered: