Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v0.0.41-alpha.2 - No services - No web services - No streaming #98

Open
jangliss opened this issue Dec 31, 2022 · 13 comments
Open

v0.0.41-alpha.2 - No services - No web services - No streaming #98

jangliss opened this issue Dec 31, 2022 · 13 comments

Comments

@jangliss
Copy link

0.0.41-alpha.2 - No services running - No stream - No web interface

Finding I'm hitting several issues, not sure if it's caused by a bad flash, or other issues. Using Wyzecam V2, flashed using 0.041-alpha.2, none of the documented ports are responding, for example not being able to see the stream, connect to rtsp, or even get a webpage to open.

# cat /etc/VERSION 
3e9737c

# grep -v "^#" /etc/openmiko.conf 
ENABLE_API=1
ENABLE_MJPEG_OVER_HTTP=1
MJPEG_FPS=15
ENABLE_AUTONIGHT=1
WIFI_MODULE=8189fs

# netstat -ane
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address           Foreign Address         State       
tcp        0      0 0.0.0.0:80              0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:8081            0.0.0.0:*               LISTEN      
tcp        0      0 0.0.0.0:22              0.0.0.0:*               LISTEN      
tcp        0    448 192.168.35.97:22        192.168.35.20:60304     ESTABLISHED 
netstat: /proc/net/tcp6: No such file or directory
netstat: /proc/net/udp6: No such file or directory
netstat: /proc/net/raw6: No such file or directory
Active UNIX domain sockets (servers and established)
Proto RefCnt Flags       Type       State         I-Node Path
unix  2      [ ACC ]     STREAM     LISTENING      13908 /tmp/dropbear-7b604193/auth-11f8960a-9
unix  2      [ ]         DGRAM                       601 /var/run/wpa_supplicant/wlan0
unix  6      [ ]         DGRAM                       459 /dev/log
unix  2      [ ]         DGRAM                       478 
unix  2      [ ]         DGRAM                       771 
unix  2      [ ]         DGRAM                       468 
unix  2      [ ]         DGRAM                       619 

I don't see port 8080 listening, nor 8554.

Video capture is running.

# ps aux | grep video
16613 root       0:39 /usr/bin/videocapture /etc/videocapture_settings.json

# tail /var/log/videocapture.log
2022-12-31 01:01:23 INFO  /openmiko/build/buildroot-2016.02/output/build/ingenic_videocap-86c1576153c6897f0c3e5b350a9f963363d69161/src/capture.c:1047: Current FPS: 25.00 / Channel 0
2022-12-31 01:01:31 INFO  /openmiko/build/buildroot-2016.02/output/build/ingenic_videocap-86c1576153c6897f0c3e5b350a9f963363d69161/src/capture.c:1047: Current FPS: 25.00 / Channel 0

mjpg_streamer is not...

# ps aux | grep mjpg
24831 root       0:00 grep mjpg

What's odd here is that if I look in /etc/init.d/S70mjpg_streamer it references /dev/video4 which I don't have.

# ls /dev/video*
/dev/video0  /dev/video1  /dev/video2  /dev/video3

If I try to start it, it says it starts OK, which isn't true, I think the exit status isn't evaluating properly...

# /etc/init.d/S70mjpg_streamer start
Starting mjpg_streamer (15 fps): OK
# ps aux | grep mjpg
25515 root       0:00 grep mjpg

If I downgrade to 0.0.40 with the same contents on the SD card, everything works fine.

@tachang
Copy link
Member

tachang commented Dec 31, 2022

I think it might be some bug with the alpha version.

@jangliss
Copy link
Author

I suspect possibly the same. Maybe the kernel/uboot isn't loading the drivers for the chipset for some reason. I reflashed using the same sdcard and configs a few more times, and it popped up working.

@DannySauval
Copy link

DannySauval commented Jan 5, 2023

Same on my side, which is weird because it worked flawlessly for a few weeks, but crashed about a week ago. SSH works but no stream.
I installed the 0.40 version which seems to work. Hopefully I’ll find the time to work on the firmware someday.

@valantur
Copy link

/var/log/messages shows these on all my Wyze V2 experiencing this same issue:

Dec 31 16:00:28 openmiko kern.warn kernel: [ 6.752511] FAT-fs (mmcblk0p1): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
Dec 31 16:00:28 openmiko kern.err kernel: [ 28.009585] FAT-fs (mmcblk0p1): error, clusters badly computed (10 != 9)
Dec 31 16:00:28 openmiko kern.err kernel: [ 28.023277] FAT-fs (mmcblk0p1): Filesystem has been set read-only

Could the SDCARD being remounted RO be related? fsck.auto is not installed so I can't fix the partition.

@martinbutt
Copy link
Contributor

@valantur there is a precompiled fsck binary here that you can use to manually fix the issue.

@nosoop
Copy link

nosoop commented Feb 11, 2023

Not sure about the web interface but v4l2rtspserver doesn't consistently start for whatever reason; found that out when I was reloading the service after making modifications to videocapture_settings.json.

Had to run the following commands whenever that happened:

# restart - sometimes v4l2rtspserver doesn't load properly; you will see messages related to VIDIOC_REQBUFS and the like when it succeeds
/etc/init.d/S60camera restart

# restart night mode handling
/etc/init.d/S75autonight restart

@NearlyWas
Copy link

v4l2rtspserver doesnt start for me, either. All other services are ok.
@nosoop 's tip worked: /etc/init.d/S60camera restart
[0.041-alpha.2, Wizecam V2]

@whitewhidow
Copy link

i have the same issue i tried with v0.0.40

i can ssh into the v2, but no webpage, or stream, or antyhing is available :/

i tried the above, but it did not help ? anyone able to assist?

@carefulcomputer
Copy link

same issue.

@whitewhidow
Copy link

whitewhidow commented Feb 18, 2023

for me, it DOES now work with v0.0.40, but the issue was the following:

i had first installed v0.0.41-alpha.2, which did not work.
Then i installed v0.0.40, and it also did not work, but then i noticed the following: even after flashing back to original firmware and fashing back to v0.0.40, it connected to my wifi, without me putting a new wpa_supplicant file !!
Which lead me to realise that it was still using previous config files from v0.0.41-alpha.2 !!!

So i did a reset, by holding the reset button for 5 seconds, which makes it clear all config files, it then dropped from my network, as it no longer had a wifi config, i then replaced the wifi config, and now it works fine on v0.0.40

@carefulcomputer
Copy link

@whitewhidow , didn't work for me. I am on 24ca9d2 (.40) , wiped all settings and still did not work. Maybe I am not doing things in right other. Here is what I gathered from your post..

  1. While SD card is out, and camera is on , hold reset button for 5 seconds to wipe existing config.
  2. On SD card put only config/overlay/etc/wpa_supplicant.conf
  3. Turn camera off and put sdcard in.
  4. Restart camera

Is that it ?

@martinbutt
Copy link
Contributor

@carefulcomputer you should reformat or fsck the SD card too.

I decided to merge together all of my changes from the last six months and release them for testing. This should address the issue that it stops working after a while. Testing is appreciated, and you can file an issue in that repo if you have any problems.

@richarddirocco
Copy link

richarddirocco commented Feb 21, 2023

I updated to the new release and still have the same problem. Sometimes I can manually start the RTSP server using /etc/init.d/S60camera start but other times, I get an error:

/etc/init.d/S60camera start
Adding necessary camera modules
root: Determined image sensor model as jxf22
insmod: can't insert '/lib/modules/3.10.14/kernel/drivers/media/platform/sensors/jxf22/sensor_jxf22.ko': File exists
c
c
c
Tue Feb 21 20:09:07 UTC 2023 - nightmode off
c
c
c
c
Audio is set to disabled in openmiko.conf. Skipping starting ffmpeg
Setting up 4 v4l2loopback device(s)
root: Starting video frame capture process
root: Starting v4l2rtspserver
VIDIOC_REQBUFS: Inappropriate ioctl for device
VIDIOC_STREAMOFF: Inappropriate ioctl for device
VIDIOC_REQBUFS: Inappropriate ioctl for device
VIDIOC_REQBUFS: Inappropriate ioctl for device
VIDIOC_STREAMOFF: Inappropriate ioctl for device
VIDIOC_REQBUFS: Inappropriate ioctl for device
VIDIOC_REQBUFS: Inappropriate ioctl for device
VIDIOC_STREAMOFF: Inappropriate ioctl for device
VIDIOC_REQBUFS: Inappropriate ioctl for device
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc

I'm not using a SWAP file. Memory seems almost full when it doesn't start at boot. Here's the output from cat /proc/meminfo on a boot where the v412rtspserver didn't start but did run after issuing /etc/init.d/S60camera start .

MemTotal: 91844 kB
MemFree: 11996 kB
Buffers: 432 kB
Cached: 7204 kB
SwapCached: 0 kB
Active: 7064 kB
Inactive: 5780 kB
Active(anon): 5244 kB
Inactive(anon): 44 kB
Active(file): 1820 kB
Inactive(file): 5736 kB
Unevictable: 0 kB
Mlocked: 0 kB
SwapTotal: 0 kB
SwapFree: 0 kB
Dirty: 28 kB
Writeback: 0 kB
AnonPages: 5228 kB
Mapped: 11032 kB
Shmem: 80 kB
Slab: 4256 kB
SReclaimable: 1508 kB
SUnreclaim: 2748 kB
KernelStack: 584 kB
PageTables: 376 kB
NFS_Unstable: 0 kB
Bounce: 0 kB
WritebackTmp: 0 kB
CommitLimit: 45920 kB
Committed_AS: 82796 kB
VmallocTotal: 1048372 kB
VmallocUsed: 37416 kB
VmallocChunk: 1008376 kB

Edit: Tested with a SWAP file on the SD card. Was able to reboot the camera 6 times and the RTSP server started each time without issue. So my issue seems to be insufficient memory without a swap file.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants