The Vera Community forums have moved!

General => General => Topic started by: jackpot on May 26, 2011, 02:58:05 pm

Title: Vera Memory
Post by: jackpot on May 26, 2011, 02:58:05 pm
Was just thinking about the minimal memory available in VERA. Since it has USB ports and is already using it to store logs to a memory stick one would think that some of the non essential files could be stored on another memory stick to allow more internal memory to be used for other more important things.
Just thinking.....
Title: Re: Vera Memory
Post by: JOD on May 26, 2011, 03:49:49 pm
It's not just the logging that's the issue, when the logs are zipped and sent to MCV there is also a CPU limitation. The biggger the log file the more demand is put on the CPU.
Personally, I would like the option to disable logging.
Anyone know if that's possible?

JOD.
Title: Re: Vera Memory
Post by: Henk on May 26, 2011, 04:01:16 pm
@JOD

My settings are reflected by hte screenshot.
Since i have a usb flashdrive attached to vera that stores the logs and i have disables all remote logging to MCV
i think that is what you mean?

Henk
Title: Re: Vera Memory
Post by: JOD on May 26, 2011, 04:16:39 pm
@Henk,

I have the same settings as you. Watching a "top" session I can see that when my logs reach ~20MB (I think this is when the zipping occurs) my %MEM increases to 68% and my CPU: sys jumps to 90%+ and Vera gets unresponsive for a while until that logging space is freed up (uploaded or dumped) occasionally (often) Vera can't process this zipping or uploading fast enough and she will reboot or things cascade out of control and she cant recover and then I have to do a manual reboot.

JOD.
Title: Re: Vera Memory
Post by: Henk on May 26, 2011, 04:27:15 pm
@Henk,

I have the same settings as you. Watching a "top" session I can see that when my logs reach ~20MB (I think this is when the zipping occurs) my %MEM increases to 68% and my CPU: sys jumps to 90%+ and Vera gets unresponsive for a while until that logging space is freed up (uploaded or dumped) occasionally (often) Vera can't process this zipping or uploading fast enough and she will reboot or things cascade out of control and she cant recover and then I have to do a manual reboot.

JOD.


Caused by your elaborate network with many devices? because my log should do the same in time, but i havent seen the behavious you describe
Title: Re: Vera Memory
Post by: JOD on May 26, 2011, 04:39:52 pm
Don't get side tracked...There is nothing elaborate, just devices and scenes.
But anyway..Logging could be called CLOGGING (no disrespect)
The logging appears to be clogging my system.

Does logging do ME any good?
I would like the option to disable it.

JOD.
Title: Re: Vera Memory
Post by: oTi@ on May 26, 2011, 04:42:21 pm
Anyone know if that's possible?
You can manually manipulate what gets logged. And I'm guessing that by specifying a non-existent log level, you effectively can have it log nothing and thus prevent/slow down the rotations.
Title: Re: Vera Memory
Post by: Henk on May 26, 2011, 04:45:56 pm
Don't get side tracked...There is nothing elaborate, just devices and scenes.
But anyway..Logging could be called CLOGGING (no disrespect)
The logging appears to be clogging my system.

Does logging do ME any good?
I would like the option to disable it.

JOD.


Didnt mean to get you sidetracked, just thinking WHY your logging is so heavy, thus exploring options what could prevent "clogging" as you state

@ oTi, manually edit what gets logged? how would that work?
Title: Re: Vera Memory
Post by: oTi@ on May 26, 2011, 04:48:23 pm
@ oTi, manually edit what gets logged? how would that work?
PM sent to @JOD, for experiment; for now. (My log file is currently 0 bytes.)
Title: Re: Vera Memory
Post by: JOD on May 26, 2011, 04:57:36 pm
@ oTi, manually edit what gets logged? how would that work?
PM sent to @JOD, for experiment; for now. (My log file is currently 0 bytes.)
Sweet. Did your Vera slowdowns disappear?

JOD.
Title: Re: Vera Memory
Post by: shady on May 26, 2011, 07:06:27 pm
I am having issues which I think might be memory related, basically it boils down to inconsistent scene activation or an unresponsive Vera, which occurs once every ten days or so.  Of course, I try enabling Verbose Logging (because I am on USB) and Locking it to try and help when I submit a ticket, but Vera ends up unresponsive so I can't submit a ticket.  So I'm with you guys, that I'd like to try killing Support Logs all together and see if that helps.  I'd still want logs for the Schlage Locks etc, of course.
Title: Re: Vera Memory
Post by: jackpot on May 26, 2011, 08:26:57 pm
So it sounds like the logging can be disabled somehow?
How would it be done?
Title: Re: Vera Memory
Post by: mcvflorin on May 27, 2011, 05:48:48 am
So it sounds like the logging can be disabled somehow?
How would it be done?

http://wiki.micasaverde.com/index.php/Luup_Loglevels

Set LogLevels = 1 to log only critical messages. This reduces the number of messages logged. Also, as it has been stated, set it to an invalid log level and see if any message is logged.
Title: Re: Vera Memory
Post by: jackpot on May 27, 2011, 02:28:21 pm
Thanks for the help mcvflorin , I will give it a try !
Title: Re: Vera Memory
Post by: Henk on May 29, 2011, 03:36:54 pm
@ oTi, manually edit what gets logged? how would that work?
PM sent to @JOD, for experiment; for now. (My log file is currently 0 bytes.)
Sweet. Did your Vera slowdowns disappear?

JOD.

You needed a HOWTO on this JOD?
Title: Re: Vera Memory
Post by: oTi@ on May 29, 2011, 04:12:47 pm
PM sent to @JOD, for experiment; for now. (My log file is currently 0 bytes.)
You needed a HOWTO on this JOD?
:) The HowTo was in the PM, for testing.
Title: Re: Vera Memory
Post by: Henk on May 29, 2011, 04:16:27 pm
PM sent to @JOD, for experiment; for now. (My log file is currently 0 bytes.)
You needed a HOWTO on this JOD?
:) The HowTo was in the PM, for testing.

So how will we all benefit :D
Title: Re: Vera Memory
Post by: JOD on May 31, 2011, 08:07:33 pm
Quote
So how will we all benefit
Still testing. These are my current settings with Verbose logging off and an uptime of 2 days 20hrs.

LogLevels = 1,2,3,4,5,6,7,8,9,50 NOW= 1
ImmediatelyFlushLog=0
LogUPnP = 0
#Number of log files to keep
NumberOfCopies= 10 NOW=5
#rotation interval in seconds of log files
RotationInterval= 15 * 60

#Store logs on mcv server at rotation
ArchiveLogsOnServer=1 NOW= 0 (I'm hoping this eliminates the lockups during rotations)

JOD.
Title: Re: Vera Memory
Post by: Henk on June 01, 2011, 06:42:01 am
@JOD

Great..uptime 2 days sounds promising! Better still, you havent killed loggin indefinite, just reduced the log load. Keep us posted on your experiences!

Ill try and combine your info with the remark @mcvflorin made and create a preliminary HOWTO.

I could use input/reviewinfo from you and @oTI@ once ive posted it to make sure its accurate and not too dangerous for users.
Title: Re: Vera Memory
Post by: JOD on June 01, 2011, 09:30:00 am
Bah humbug.
Uptime is now 4hrs 20 mins so it's still rebooting.  :-\
This puts it around 5:00am my time, at least it didnt interfere with any of my timed events.
Maybe the best thing is just to schedule nightly reboots to avoid lockups or slowdowns during system usage during the day?

I'm going to set everything to -0- and see what happens for now.
oTi@, what's your experience?

JOD.

Title: Re: Vera Memory
Post by: oTi@ on June 01, 2011, 09:36:26 am
General note: I feel the stuff discussed here (USB logging, log level changes, low resources, etc.) is essential to very few (known) users. Please don't draw the conclusion that one must enable USB logging and must change the configuration files to have a stable Vera with .1245.

I'm going to set everything to -0- and see what happens for now.
@JOD, set it to 101 (or some other log level that doesn't appear to exist); that will effectively stop logging to LuaUPnP. Still some chatter ends up in there, perhaps from start-up etc., but it's very little.

I'd have to check the script again, but I think log rotation is time driven (not just size) as well.

I'm still looking to get you a modified script / bigger partition.

Title: Re: Vera Memory
Post by: JOD on June 01, 2011, 09:49:15 am
set it to 101 (or some other log level that doesn't appear to exist
OK.

Quote
I'd have to check the script again, but I think log rotation is time driven (not just size) as well.
#rotation interval in seconds of log files
RotationInterval= 15 * 60
Question. If this is not a rotation / USB issue, maybe it's more of an internal memory issue? A reboot always brings a slow system back to full speed and that would only clear the internal memory.

I'm going to keep a "top" session active and log the output for the next couple of days.
*Edit. the "top" dosen't give me a time stamp, anything else I can run?

JOD.
Title: Re: Vera Memory
Post by: oTi@ on June 01, 2011, 10:07:00 am
#rotation interval in seconds of log files
RotationInterval= 15 * 60
That's the interval for forced rotations, I believe. Normally, a rotation will happen at least every 12 hours.

PM sent.
Title: Re: Vera Memory
Post by: JOD on June 01, 2011, 10:20:06 am
PM sent.
MCV must be screening your PM's, or maybe you've reached your quota?  Nothing received yet.

*Edit. I finally got it. It has a big "CENSORED" stamp across it.  ;D

JOD.