Restarting DomotiGa automatically

[RDNZL]

Ok, I have changed ServerStats.module so it catches the system errors before stopping, it now logs them to the logfile.
Can you update your file with the latest from svn and let me know?
For the record these errors have nothing direct to do with rrdtool.
You get the error on a simple EXEC cat /proc/loadavg to get the contents of that file in a string to parse.

[Andy_Burn]

Good man!
Thanks Ron
I'll update the code, probably in a couple of days since I have other commitments.
Cheers....

[Andy_Burn]

Ron,
The code is much more stable now.
Last night, it recorded 6+hrs of errors like:
2011/02/02 06:35:41 ERROR: System error. Too many open files at ServerStats.UpdateRRDs.88
2011/02/02 06:36:41 ERROR: System error. Too many open files at ServerStats.UpdateRRDs.88

It didnt update sensors using RRD for graphing, however.... it didnt crash!!

Thanks,
Andy

[RDNZL]

Did you only update domotiga code?

Or did you also do the ulimit changes to your server?
If not pls do so we can find out how to solve it...
I'm also very interested in the lsof output I described above when you get these errors...

[j.hoekstra]

I don't know if it's better to make a new post or replying here but here goes.
I've been having memory-erros every now and again causing domotiga to stop, it ran out of memory on the serverstats module or just checking gmail, to counter the problem I thought I'd add some more memory to the system making it a total of nearly 4 GB(onboard video), however it seems that either Gambas or domotiga are just slurping more memory now, this morning it was just below a GB and now it's getting close to 1200M.
When I stop domotiga it goes back down to normal levels and it takes a couple of days before it gets to this level again.

Is anyone else experiencing this as well?
I'm in the process of rebuilding Gambas with latest SVN now to see if that helps, however having just the ide in the background it doesn't produce these high numbers...

[RDNZL]

Supplying relevant information is more important than the subject of a post.
Without it it's hard to fix, more over because I don't have any memory problems at all, running 1,5 week in a row, before I restart it because of dev changes.

Some are:
Which OS are you running?
Which revision of DomotiGa?
Which version of Gambas?
DomotiGa GUI or Server?
How many graphs, which poll interval set?
etc....

[j.hoekstra]

Ubuntu Lucid, default updated kernel
Domotiga GUI-version 0.1.194(svn rev. 540)
Gambas 2.22(now svn rev. 3572 before rev 3431)
No graphing set, no serverstats anymore and no rrd.
No polling as far as I know.

I have updated gambas to latest and sofar res mem seems to be stable around 140M with virtual just over 400, will check if it raises over the next few days. Are there any tools I could use to see if there's memory leaking and if so where?

[RDNZL]

Ok thanks.
Look at domotiga.nls debugging page and how to run valgrind.
But I doubt if you see leakage of external prgs too.