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

"Potential split boundary" log message should be suppressed by "netcam_tolerant_check" #36

Open
dmak opened this issue Jan 20, 2016 · 5 comments

Comments

@dmak
Copy link

dmak commented Jan 20, 2016

In my logs I see a lot of messages like this (approx 2 messages per second):

netcam_init_jpeg: no new pic, no signal rcvd
netcam_read_html_jpeg: Potential split boundary - 1447 chars flushed, 1 re-positioned

I have the option netcam_tolerant_check on in my config – assuming that should have suppressed these messages.
Additional info: camera Foscam FI8918W configured via netcam_url.

@fpytloun
Copy link

fpytloun commented Oct 20, 2016

I am facing similar issue:

[1] [NTC] [NET] netcam_read_html_jpeg: Potential split boundary - 4095 chars flushed, 1 re-positioned

Using motion with netcam_url on localhost stream of uv4l with raspicam driver on Raspberry Pi 3
Setting netcam_tolerant_check didn't suppress that message.

@n8foo
Copy link

n8foo commented Nov 25, 2016

Seeing the same issue on localhost stream of uv4l-raspicam on RPI3

@PaskoMoto
Copy link

Hi.
Any news about this issue?
I'm using two netcams, but only one is generating this flooding.
Thanks in advance.
Regards.

@tosiara
Copy link

tosiara commented Jun 24, 2017

This is outdated repo, nobody is watching issues here
Use current official fork @Motion-Project

@PaskoMoto
Copy link

PaskoMoto commented Jun 24, 2017

Hi.
Just for future references:
I got rid of these messaging flooding by using:
log_level 5
inside my .conf file
Hopefully I'm not missing many important messages.
Regards.

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

5 participants