crowsnest issues? logs says all ok...but then fails
Turned on my machine this evening (after the piano wire short (see #imverysmart) neither webcam is working.
So I checked the powered hub they're plugged into...no problems as my TFT touch is plug in there to swapped plugs around all sockets working..
So I swapped out the cams for known good units. command line ls by-dev finds the cam no problem (see screen cap)
attached is the crowsnest log (deletes, runs fresh each boot) all is good...then neither starts (see last couple lines in the log says failed
so checked the v3 -> v4 crowsnest update page.... edited boot/config.txt to comment out start cam and startx as directed...didn't change anything. I've also deleted and tried to re-config my cams via the mainsail interface (as well as directly editing crosenest.conf
So my Q.... where do I look next, and any WAGs as to why they both just dropped out, and absolutely nothing else in the VC500 is not working as expected. lost here....
10 Replies
just renamed the old crowsnest folder...and did a complete re-install/build of crowsnest v4.
Got one camera back...but not via webrtc.... only one is responding to good old fashioned mpeg streaming.
Everything is up to date as far as I can tell. WHAT could be the interaction stopping RatOS or mainsail or what ever from allowing webrtc to integrate/execute as designed???
with orig cams back in place
Rosanna-dana-dana quote.... Never mind.
was actually a a mainsail issue .
they're back with webrtc
So solved? I noticed the URL you were using for WebRTC is wrong.
in the above two pics..yep second pic was wrong screen cap posted that was (attempt to ) showing the cam worked (under mpeg streaming) ..just couldn't get it to show up again via the previously working webrtc .every option tried...just posted wrong test scenerio 😜 current is back to a working webrtc for BOTH cams
Excellent 👌