Error, ERROR: Not enough space in stream buffer

[KiwiHC16]

Hi All,
After a day or so, I start to have messages in OZ...log file:
Error, ERROR: Not enough space in stream buffer
open-zwave-control-panel run on a raspberry pi platform. I tried with Raspian Wheezy and Jessie with same issue.
I tried with r736, r886, r 929, r1014 and the last git version of open-zwave, same issue.
I tried with few version of openzwave-control-panel, still same issue.
I did not find any good chat around this issue on the net.
What is very surprising is that I never faced this issue in the past. After a crash of the raspberry pi , I did a complete re-installation and since I have this issue.
I think also that after sometime the ozcwp crash. I have activated core dump today. Let see if I get a core tomorrow.
The error message is in the Stream.cpp file from openzwave.
Any idea where to start to progress on the trouble shooting ?
Any workaround ?
Thanks.

[Fishwaldo]

Is your rpi heavily loaded? That message indicates that we are generating messages faster than we can send to the serial port. 

Sent from my iPhone

On 16 Oct 2015, at 7:21 PM, Ben <notifications@github.com mailto:notifications@github.com > wrote:

Hi All,
After a day or so, I start to have messages in OZ...log file:
Error, ERROR: Not enough space in stream buffer
open-zwave-control-panel run on a raspberry pi platform. I tried with Raspian Wheezy and Jessie with same issue.
I tried with r736, r886, r 929, r1014 and the last git version of open-zwave, same issue.
I tried with few version of openzwave-control-panel, still same issue.
I did not find any good chat around this issue on the net.
What is very surprising is that I never faced this issue in the past. After a crash of the raspberry pi , I did a complete re-installation and since I have this issue.
I think also that after sometime the ozcwp crash. I have activated core dump today. Let see if I get a core tomorrow.
The error message is in the Stream.cpp file from openzwave.
Any idea where to start to progress on the trouble shooting ?
Any workaround ?
Thanks.

—
Reply to this email directly or view it on GitHub.

[KiwiHC16]

Thanks for this indication.
I have this error message again this morning. It’s in the log every second.
But I saw that a personal client process crashed. So I guess the issue is on my side. I transferred this discussion to the google group. This issue could be closed as there is no issue on openzwave as far as I can see.

[vibr77-zz]

I have exactly the same issue, but i do not have any process that have crashed
How to debug the root cause of this ?

thanks
Vincent

[openzwave-dev-watcher]

To give more information about the contexte

I am running the version 1.3.482 of the openzwave library
I do not have any issue for months
My hardware is raspberry

few days ago i had alarm that has been triggered from on device (without
being able to identify which one) and i have my fibaro switch device that
were flipping from on to off. But nothing in the OZW log file...
And now i get this error with no space left on stream buffer.

How do I can debug what is happening ?

On Wednesday, December 2, 2015 at 11:06:48 AM UTC+1, MisterV wrote:

I have exactly the same issue, but i do not have any process that have
crashed
How to debug the root cause of this ?

thanks
Vincent

—
Reply to this email directly or view it on GitHub
#673 (comment)
.

[openzwave-dev-watcher]

I have tested with the last version openzwave and after 24h i have one more
time the same issue...
Help plz
Vincent

On Wednesday, December 2, 2015 at 11:06:48 AM UTC+1, MisterV wrote:

I have exactly the same issue, but i do not have any process that have
crashed
How to debug the root cause of this ?

thanks
Vincent

—
Reply to this email directly or view it on GitHub
#673 (comment)
.

[openzwave-dev-watcher]

As far as I can tell, this is a OS issue and not anything related to OZW per say.

The error occurs if the Serial Port Buffers get full. The buffers are controlled by the Operating system and not OZW. It basically means it the OS can’t send messages to the Serial port (fast enough) so a heavily loaded system or other issue could be the cause.

From: openzwave@googlegroups.com on behalf of Vincent Besson vincent@besson.be
Reply-To: openzwave@googlegroups.com
Date: Thursday, 3 December 2015 at 10:18 PM
To: OpenZWave openzwave@googlegroups.com
Cc: open-zwave@noreply.github.com, reply@reply.github.com, notifications@github.com
Subject: [openzwave] Re: [open-zwave] Error, ERROR: Not enough space in stream buffer (#673)

I have tested with the last version openzwave and after 24h i have one more time the same issue...
Help plz
Vincent

On Wednesday, December 2, 2015 at 11:06:48 AM UTC+1, MisterV wrote:
I have exactly the same issue, but i do not have any process that have crashed
How to debug the root cause of this ?

thanks
Vincent

—
Reply to this email directly or view it on GitHub.

You received this message because you are subscribed to the Google Groups "OpenZWave" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openzwave+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[jonferreira]

@openzwave-dev-watcher I've been battling with this problem for a couple of weeks now, running 1.4-2888-g54682370-dirty on domoticz.

I just can't see how it's can possibly be a "OS issue" caused by a "heavily loaded system", given that this a RPI running just Domo and node-red and the problem happens overnight when nothing but power reports happen, etc

RPI CPU averages at 5% and memory at 40%.