Info Viewer plugin - Log Viewer updated

[RexBeckett]

@tomgru,

Your problems are beginning to fit the profile for memory issues. Check in the log for messages like Failed to save user data and similar. If you are running a lot of plugins on a Vera Lite and/or you have a lot of files consuming your flash, it could cause some of your symptoms.

I also once had a rash of Info Viewer ajax error - possibly malformed XML received: Handler failed messages caused by logging to a defective USB stick.

[tomgru]

@tomgru,

Your problems are beginning to fit the profile for memory issues. Check in the log for messages like Failed to save user data and similar. If you are running a lot of plugins on a Vera Lite and/or you have a lot of files consuming your flash, it could cause some of your symptoms.

I also once had a rash of Info Viewer ajax error - possibly malformed XML received: Handler failed messages caused by logging to a defective USB stick.

Thanks..... i'll check into that.  Any idea how i would know if my USB stick is defective?

Screen shot of it setup attached.  Also attached some shots of memory usage, not sure what to make of it.  Sorry... noob still trying to figure this out!

One other edit... I see this in my logs, but not the other warning you suggested.

LOG_CHECK_MEMORY_LEAK pMem start 0x202e000 now 0x20b0000 last 0x202e000 leaked 532480 <0x2c005680>

[RexBeckett]

You are running very low on memory. I had a Vera Lite that got down to that level. It would restart whenever several things happened at the same time and configuration changes didn't stick because it couldn't save the updates.

Solution (1) was to uninstall a few unnecessary plugins and delete the files from /etc/cmh-ludl before reloading. This cleared enough memory to get it stable.

Solution (2) was to order a Vera3 and transfer the whole configuration across to it.

Vera peppers the log with notifications of memory leaks. I still get them on a stable system with plenty of available memory.

[tomgru]

You are running very low on memory. I had a Vera Lite that got down to that level. It would restart whenever several things happened at the same time and configuration changes didn't stick because it couldn't save the updates.

Solution (1) was to uninstall a few unnecessary plugins and delete the files from /etc/cmh-ludl before reloading. This cleared enough memory to get it stable.

Solution (2) was to order a Vera3 and transfer the whole configuration across to it.

Vera peppers the log with notifications of memory leaks. I still get them on a stable system with plenty of available memory.

That's what I was afraid of.  I just ordered a Vera3!

Of interesting note... I pulled the USB and now logging is better/more consistent.  Think you had that one figured out as well.  Tried a new one (that I had laying around, but it's stuck at "re-formatting drive". 

with the new Vera3, should I still use USB logging?

THanks for the help!!!!

[RexBeckett]

I have joined my esteemed colleague @akbooer in believing that logging to USB can sometimes cause more problems than it solves. Since I returned to logging to main memory, my Vera3 is more stable and I have more available memory (as reported by EventWatcher). It may be that logging to USB has advantages when memory is in short supply but I am not convinced that the reported gains are real.
 

[tomgru]

I have joined my esteemed colleague @akbooer in believing that logging to USB can sometimes cause more problems than it solves. Since I returned to logging to main memory, my Vera3 is more stable and I have more available memory (as reported by EventWatcher). It may be that logging to USB has advantages when memory is in short supply but I am not convinced that the reported gains are real.

OK... thanks again for support.  also following your instructions for upgrading tomorrow!!!

[RexBeckett]

also following your instructions for upgrading tomorrow!!!

Good luck with that. Don't let your new Vera3 upgrade to UI7. If it does it automatically, contact support and have them remove the suicidal flag.

[tomgru]

also following your instructions for upgrading tomorrow!!!

Good luck with that. Don't let your new Vera3 upgrade to UI7. If it does it automatically, contact support and have them remove the suicidal flag.

My plan is to definitely stay with U15.  Will it try to move me automatically?

[RexBeckett]

My plan is to definitely stay with U15.  Will it try to move me automatically?

Apparently some units are shipped with a flag set that causes them to upgrade automatically. When the owners have re-installed UI5, the flag continues to download UI7. Support can remove the flag. If you are lucky, you will get an old-stock unit and avoid the problem.
 

[AgileHumor]

I have joined my esteemed colleague @akbooer in believing that logging to USB can sometimes cause more problems than it solves. Since I returned to logging to main memory, my Vera3 is more stable and I have more available memory (as reported by EventWatcher). It may be that logging to USB has advantages when memory is in short supply but I am not convinced that the reported gains are real.
 

I also log locally and have noticed greater stability.

[tomgru]

I have joined my esteemed colleague @akbooer in believing that logging to USB can sometimes cause more problems than it solves. Since I returned to logging to main memory, my Vera3 is more stable and I have more available memory (as reported by EventWatcher). It may be that logging to USB has advantages when memory is in short supply but I am not convinced that the reported gains are real.
 

I also log locally and have noticed greater stability.

Thanks... upgrade went smoothly.

For logging locally... with the Vera3, do you turn on verbose logging?

[AgileHumor]

Not unless I'm debugging.  Actually, if you don't click the "lock levels" check box, verbose is turned off after a set period.

[oTi@]

Apparently some units are shipped with a flag set that causes them to upgrade automatically. When the owners have re-installed UI5, the flag continues to download UI7. Support can remove the flag.

Affirmative. As said on other threads, just start a chat with support and the flag may get disabled within 5 minutes; even on the weekends (or at least on Saturday).

[mda]

Sorry for the dumb question, but how to i setup info viewer's log viewer pattern to display multiple log levels?

When i grep the logs via ssh and want to, for example, find all entries that start with 01 or 50 i just grep '^01\|^50'

but i can not figure out the equivalent pattern in lua for info viewer despite reading as much as could.

Can anyone help a poor lua-impaired guy out?

Thanks !

[gengen]

First of all, the definitive source for documentation on Lua patterns is http://www.lua.org/manual/5.1/manual.html#5.4.1

Unfortunately, Lua patterns do not contain the | operator. The best thing you can try is something like ^[05][10] which would also find 51 but that's better than nothing.