Recurring error about "toolbox.js"

Community Playground General Discussions
1

I see this recurring entry in the logs:

02      12/22/12 13:00:20.990   luvd_get_info mg conn can't read /etc/cmh-ludl//toolbox.js or /etc/cmh-lu//toolbox.js from filename /toolbox.js pPtrFile (null) <0x2e50d680>

It’s always been there, so might be benign, but I wasn’t able to find it in a forum search or explanation for how I might resolve it.

What does this entry mean? Should there be a /toolbox.js?
I logged in, and there is no file called “toolbox.js” in the entire system. Where is it being referenced from (luvd_get_info)?

2

I get this error as well.

3

Thanks thetonyg… I’m relieved to hear it’s not something I did.

I tried creating an empty file called /etc/cmh-ludl/toolbox.js, and that seems to have made the error go away. I’ll see if it has side effects.

4

Yah, the error is a bit annoying, but like you said, it seems benign. Maybe it’ll get resolved in the next firmware :slight_smile:

5

Happy to report that a dummy file seems to have calmed it down, with no ill effects.

SSH into the Vera and run:

touch /etc/cmh-ludl/toolbox.js

That’s all it takes.

6

Hi,

I installed firmware version: 1.5.622 [url=http://forum.micasaverde.com/index.php/topic,13956.0.html]http://forum.micasaverde.com/index.php/topic,13956.0.html[/url]and still get the same error:

 luvd_get_info mg conn can't read /etc/cmh-ludl//toolbox.js or /etc/cmh-lu//toolbox.js from filename /toolbox.js pPtrFile (null)

I therefore used GroundLoop’s hint for a dummy file and all these errors in my log dissapeared. @GroundLoop Thanks!

Is this bug created by a plugin or a bug in the firmware?

7

It’s from the firmware …
It’s probably something that the developers uses inside MCV.

An empty file works … or you can add your own javascript patches there …