I have done a clean VMWare installation with Ubuntu Server and only Emoncms and its dependencies.
I have played around some but now I noticed that Vmware guest don't have any free disk and after digging down I find this
root@emoncms:/var/lib/timestore# du -sh * 3,4M 0000000000000005_0_.dat 8,0K 0000000000000005_1_.dat 4,0K 0000000000000005_2_.dat 4,0K 0000000000000005_3_.dat 4,0K 0000000000000005_4_.dat 4,0K 0000000000000005_5_.dat 4,0K 0000000000000005.tsdb 72K 0000000000000006_0_.dat 4,0K 0000000000000006_1_.dat 4,0K 0000000000000006_2_.dat 4,0K 0000000000000006_3_.dat 4,0K 0000000000000006_4_.dat 4,0K 0000000000000006_5_.dat 4,0K 0000000000000006.tsdb 17G 0000000000000007_0_.dat 8,0K 0000000000000007_1_.dat 4,0K 0000000000000007_2_.dat 4,0K 0000000000000007_3_.dat 4,0K 0000000000000007_4_.dat 4,0K 0000000000000007_5_.dat 4,0K 0000000000000007.tsdb 72K 0000000000000008_0_.dat 4,0K 0000000000000008_1_.dat 4,0K 0000000000000008_2_.dat 4,0K 0000000000000008_3_.dat 4,0K 0000000000000008_4_.dat 4,0K 0000000000000008_5_.dat 4,0K 0000000000000008.tsdb 4,0K adminkey.txt
Why and what have happened??
Re: Huge disk usage...
Ah!, I thought I had added the check for the condition that creates this error to the master emoncms repository but I had not, I had only updated the current development branch (redismetadata). Timestore will do that if you give it incorrect dates, its quite a serious bug that should have a check within timestore but the redismetadata branch checks for this within emoncms.
You might want to delete that file and upgrade to the redismetadata branch and I will try and merge the redismetadata branch into master in the next few days.
Re: Huge disk usage...
Ok, thanks and good you are into it :)
I think it started when I added the time argument. I receive XML dateTime as string e.g. "2013-12-04T18:32:28.16" and convert that to milliseconds from 1/1 1970 and use that so I am a bit curious what you mean by "Timestore will do that if you give it incorrect dates"
What is a incorrect date in this case?
Isn't a correct date milliseconds from 1/1 1970?!
EDIT: Correct myself, it's unix time == seconds (not millis) since 1/1 1970. I sent millis when this happend
Re: Huge disk usage...
I tested to upgrade to the branch but discovered dependencies to Redis etc so I fixed my bug to send unix times instead.