Server historical data space problem?
Some users and me seem to have lost H records early during the last 24-48 hours. I.e. my RT-PWR-Batt* logs currently can only be fetched for the last 3 hours instead of 24. Is there a storage space problem on the server? Regards, Michael -- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
Disk space is ok at the moment, and I haven't seen any issue. Can you eMail me your vehicle ID, and time of the problem? I'll have a look in the logs. Regards, Mark. On 18 Jun, 2014, at 5:18 am, Michael Balzer <dexter@expeedo.de> wrote:
Some users and me seem to have lost H records early during the last 24-48 hours.
I.e. my RT-PWR-Batt* logs currently can only be fetched for the last 3 hours instead of 24.
Is there a storage space problem on the server?
Regards, Michael
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Turns out the issue was expiring data records. OVMS is slightly unusual in that it allows the client to determine retention time of historical data. When the data record is submitted to the server, it includes an expire-after-seconds field set by the client submitting the record. Within reason, the server will retain the records for that time. The RT-PWR-Batt logs are tagged for 24 hour retention. Regards, Mark. On 18 Jun, 2014, at 8:22 am, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Disk space is ok at the moment, and I haven't seen any issue.
Can you eMail me your vehicle ID, and time of the problem? I'll have a look in the logs.
Regards, Mark.
On 18 Jun, 2014, at 5:18 am, Michael Balzer <dexter@expeedo.de> wrote:
Some users and me seem to have lost H records early during the last 24-48 hours.
I.e. my RT-PWR-Batt* logs currently can only be fetched for the last 3 hours instead of 24.
Is there a storage space problem on the server?
Regards, Michael
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
I guess that means I should be running my script that downloads and archives all of the records twice per day. Tom -----Original Message----- From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Wednesday, June 18, 2014 at 6:47 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Server historical data space problem?
Turns out the issue was expiring data records.
OVMS is slightly unusual in that it allows the client to determine retention time of historical data. When the data record is submitted to the server, it includes an expire-after-seconds field set by the client submitting the record. Within reason, the server will retain the records for that time.
The RT-PWR-Batt logs are tagged for 24 hour retention.
Regards, Mark.
On 18 Jun, 2014, at 8:22 am, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Disk space is ok at the moment, and I haven't seen any issue.
Can you eMail me your vehicle ID, and time of the problem? I'll have a look in the logs.
Regards, Mark.
On 18 Jun, 2014, at 5:18 am, Michael Balzer <dexter@expeedo.de> wrote:
Some users and me seem to have lost H records early during the last 24-48 hours.
I.e. my RT-PWR-Batt* logs currently can only be fetched for the last 3 hours instead of 24.
Is there a storage space problem on the server?
Regards, Michael
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Tom , Do you mind sharing that script? Nikolay On Thursday, June 19, 2014 7:07 PM, Tom Saxton <tom@idleloop.com> wrote: I guess that means I should be running my script that downloads and archives all of the records twice per day. Tom -----Original Message----- From: Mark Webb-Johnson <mark@webb-johnson.net> Reply-To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Date: Wednesday, June 18, 2014 at 6:47 PM To: OVMS Developers <ovmsdev@lists.teslaclub.hk> Subject: Re: [Ovmsdev] Server historical data space problem?
Turns out the issue was expiring data records.
OVMS is slightly unusual in that it allows the client to determine retention time of historical data. When the data record is submitted to the server, it includes an expire-after-seconds field set by the client submitting the record. Within reason, the server will retain the records for that time.
The RT-PWR-Batt logs are tagged for 24 hour retention.
Regards, Mark.
On 18 Jun, 2014, at 8:22 am, Mark Webb-Johnson <mark@webb-johnson.net> wrote:
Disk space is ok at the moment, and I haven't seen any issue.
Can you eMail me your vehicle ID, and time of the problem? I'll have a look in the logs.
Regards, Mark.
On 18 Jun, 2014, at 5:18 am, Michael Balzer <dexter@expeedo.de> wrote:
Some users and me seem to have lost H records early during the last 24-48 hours.
I.e. my RT-PWR-Batt* logs currently can only be fetched for the last 3 hours instead of 24.
Is there a storage space problem on the server?
Regards, Michael
-- Michael Balzer * Paradestr. 8 * D-42107 Wuppertal Fon 0202 / 272 2201 * Handy 0176 / 206 989 26
<dexter.vcf>_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
_______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
Hi Nikolay, I've attached a zip archive with three files. I changed the file extension for email servers that filter out zip archives, so you'll need to change .piz to .zip then unpack the archive. The three files are: ovms.pl - A Perl script that will download and display the most recent charge status, the drive logs, the charge logs and/or the server's message history. The records are decoded and shown in a slightly more human readable form. Command line arguments determine which items it downloads. It always gets the more recent charge status. To get the others, put drive, charge or server on the command line. This script is just for displaying the OVMS data, it doesn't store anything. Before using the script, you'll need to fill in your account and vehicle info at the top of the file. ovms-log-archive.pl - This is the one that downloads all of the info and dumps it out to text files. Again, it needs to be customized with your account and vehicle info. It dumps all of the charge and drive logs into one file (in ascending time order) and all of the stored messages to another. The messages are saved in their raw format, no formatting is done. I have this one set up to run once every 12 hours. com.idleloop.ovms-logs.plist - If you'll be running the log archive script on OS X, this Launch Control script will set up the automation. You'll want to open this file in a text editor and customize the three paths, then copy it to ~/Library/LaunchAgents. From that directory, run this command to enable the automation: launchctl load -w com.idleloop.ovms-logs.plist Tom On 6/20/14, 1:11 PM, "Nikolay Shishkov" <nshishkov@yahoo.com> wrote: Hi Tom , Do you mind sharing that script? Nikolay On Thursday, June 19, 2014 7:07 PM, Tom Saxton <tom@idleloop.com> wrote: I guess that means I should be running my script that downloads and archives all of the records twice per day. Tom
Thanks Tom! On Saturday, June 21, 2014 12:07 AM, Tom Saxton <tom@idleloop.com> wrote: Hi Nikolay, I've attached a zip archive with three files. I changed the file extension for email servers that filter out zip archives, so you'll need to change .piz to .zip then unpack the archive. The three files are: ovms.pl - A Perl script that will download and display the most recent charge status, the drive logs, the charge logs and/or the server's message history. The records are decoded and shown in a slightly more human readable form. Command line arguments determine which items it downloads. It always gets the more recent charge status. To get the others, put drive, charge or server on the command line. This script is just for displaying the OVMS data, it doesn't store anything. Before using the script, you'll need to fill in your account and vehicle info at the top of the file. ovms-log-archive.pl - This is the one that downloads all of the info and dumps it out to text files. Again, it needs to be customized with your account and vehicle info. It dumps all of the charge and drive logs into one file (in ascending time order) and all of the stored messages to another. The messages are saved in their raw format, no formatting is done. I have this one set up to run once every 12 hours. com.idleloop.ovms-logs.plist - If you'll be running the log archive script on OS X, this Launch Control script will set up the automation. You'll want to open this file in a text editor and customize the three paths, then copy it to ~/Library/LaunchAgents. From that directory, run this command to enable the automation: launchctl load -w com.idleloop.ovms-logs.plist Tom On 6/20/14, 1:11 PM, "Nikolay Shishkov" <nshishkov@yahoo.com> wrote: Hi Tom , Do you mind sharing that script? Nikolay On Thursday, June 19, 2014 7:07 PM, Tom Saxton <tom@idleloop.com> wrote: I guess that means I should be running my script that downloads and archives all of the records twice per day. Tom _______________________________________________ OvmsDev mailing list OvmsDev@lists.teslaclub.hk http://lists.teslaclub.hk/mailman/listinfo/ovmsdev
participants (4)
-
Mark Webb-Johnson -
Michael Balzer -
Nikolay Shishkov -
Tom Saxton