Anybody getting lots of messages like this in the error log since new firmware ?
01 01/17/18 14:32:25.129 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x706ba520>
Anybody getting lots of messages like this in the error log since new firmware ?
01 01/17/18 14:32:25.129 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x706ba520>
Someone sent me a log with that in it … I have never seen it before.
Hello guys,
We are already tracking this as we speak and I will come back with an official explanation/ETA/postmortem once we gather more data.
Hi
After upgrading to latest FW I am also receiving errors on Vera Edge:
“sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x746ce520>”
As well as:
“ZWaveNode::AddPollingCommand null in embedded for node 4 <0x768e2520>”
[quote=“Al2kas, post:4, topic:198295”]Hi
After upgrading to latest FW I am also receiving errors on Vera Edge:
“sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x746ce520>”
As well as:
“ZWaveNode::AddPollingCommand null in embedded for node 4 <0x768e2520>”[/quote]
I notice the same problem in the log. New since 1.7.3501 on my VeraPlus. Also this morning one of my PLEG actions (light out) did not work. Any suggestions?
[quote=“bruine01, post:5, topic:198295”][quote=“Al2kas, post:4, topic:198295”]Hi
After upgrading to latest FW I am also receiving errors on Vera Edge:
“sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x746ce520>”
As well as:
“ZWaveNode::AddPollingCommand null in embedded for node 4 <0x768e2520>”[/quote]
I notice the same problem in the log. New since 1.7.3501 on my VeraPlus. Also this morning one of my PLEG actions (light out) did not work. Any suggestions?[/quote]
Contact Support. Roll back…
Hello
In VeraPlus, I can confirm that this issue with getnameinfo are present at least from 7.024, 7025beta and 7.025
[quote=“Al2kas, post:7, topic:198295”]@Sammy2, thanks.
@bruine01, try to reboot Vera. That worked for me for now.[/quote]
Just did a reboot (sofware restart. No power cycle). Still pop’s up with sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo. Will do a power cycle now.
Same issue after a power cycle. Already send a mail to support.
I also observed this case on my veraplus in the last release: 1.7.3501
sbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfo <0x7081a520>
08 01/20/18 11:26:43.199 JobHandler_LuaUPnP::HandleActionRequest device: 31 service: urn:upnp-org:serviceId:Dimming1 action: SetLoadLevelTarget <0x7081a520>
I think that a new bug as appeared in this release because i’ve nerver observed it before.
[quote=“Sorin M., post:3, topic:198295”]Hello guys,
We are already tracking this as we speak and I will come back with an official explanation/ETA/postmortem once we gather more data.[/quote]
Hello , do you have news about this. this is litterally hammering my box with this log line several time per seconds sometime
Line 114077: 01 01/20/18 14:35:11.256 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114087: 01 01/20/18 14:35:11.268 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114097: 01 01/20/18 14:35:11.507 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114107: 01 01/20/18 14:35:11.520 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114117: 01 01/20/18 14:35:12.994 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114127: 01 01/20/18 14:35:13.008 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114138: 01 01/20/18 14:35:13.239 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114148: 01 01/20/18 14:35:13.269 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114167: 01 01/20/18 14:35:13.488 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114177: 01 01/20/18 14:35:13.522 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114187: 01 01/20/18 14:35:13.741 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114197: 01 01/20/18 14:35:13.784 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114207: 01 01/20/18 14:35:14.098 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114217: 01 01/20/18 14:35:14.296 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114240: 01 01/20/18 14:35:19.298 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114250: 01 01/20/18 14:35:19.309 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114260: 01 01/20/18 14:35:19.538 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114270: 01 01/20/18 14:35:19.551 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114297: 01 01/20/18 14:35:25.065 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114384: 01 01/20/18 14:35:25.663 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114402: 01 01/20/18 14:35:25.767 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114409: 01 01/20/18 14:35:25.883 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114502: 01 01/20/18 14:35:27.083 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114515: 01 01/20/18 14:35:30.416 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114525: 01 01/20/18 14:35:30.443 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114535: 01 01/20/18 14:35:30.964 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114545: 01 01/20/18 14:35:31.060 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x7030c520>
Line 114687: 01 01/20/18 14:35:38.639 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x749c5520>
Line 114739: 01 01/20/18 14:35:47.100 e[31;1msbrk JobHandler_LuaUPnP::HandleActionRequest Problem with getnameinfoe[0m <0x771c5520>
Still have this behavior this morning and impossible to move my roller shutter. Feedback from Vera asap is needed.
Is there any ticket already opened on this topic?
[quote=“jojoflyhigh, post:12, topic:198295”]Still have this behavior this morning and impossible to move my roller shutter. Feedback from Vera asap is needed.
Is there any ticket already opened on this topic?[/quote]
I loged a ticket but we should all do
the answer I got is not satisfactory from my standpoint because it ignores the fact I get tons per seconds of these
In regards to ?getnameinfo? this is a standard POSIX function and it?s used for logging so it?s not something vital and you can just ignore that message as it appears when the function returns a non-zero value.
I there any news on this topic. I have opened a ticket but still no feedback.
[quote=“jojoflyhigh, post:12, topic:198295”]Still have this behavior this morning and impossible to move my roller shutter. Feedback from Vera asap is needed.
Is there any ticket already opened on this topic?[/quote]
Hello Everyone,
To use the technical lingo of my fellow developers, this is standard POSIX information triggered by UPnP services in vera. It is used for logging only which is triggered when zero return value for getnameinfo() indicates successful completion; a non-zero return value indicates failure.
Should it be visible/have an output in the logs? Absolutely not. Does it affect any of the devices you mention here? No, it does not translate or affect the functionality of Vera or any devices on it.
A trivial task has been created in our bug tracker and it will be addressed in a future firmware update.
If you have any particular issues with your devices please make reference to those devices specifically and not this error specifically, for the most efficient Customer Care approach and solution.
Best Home Automation shopping experience. Shop at Ezlo!
© 2026 Ezlo Innovation, All Rights Reserved. Terms of Use | Privacy Policy | Forum Rules