[vz-users] VZCompress

[Andreas Goetz]

Hallo Thomas,

On Wed, Apr 22, 2015 at 9:46 AM, Heine.thomas at online.de <
Heine.thomas at online.de> wrote:

>  Hallo,
>
> Wo und wie muss ich das machen, wenn ich es von Hand einstellen will?
>

Warum willst Du unbedingt den komplizierten Weg nehmen? Warum nicht einfach
den installer? Hast Du es versucht?


> Bin leider noch nicht all zu lange dabei und noch in der "Lernphase"
>
> Danke für die Mühe
>
> Thomas
>
> Viele Grüße,
Andreas


>
>
> Am 22.04.2015 um 09:32 schrieb Andreas Goetz:
>
>   > string(63) "DELETE command denied to user 'vz'@'localhost' for table
> 'data'"
>
>  Dein vz User hat keine DELETE Rechte -> Installationsskript nochmal
> laufen lassen und die Option für die Rechte dabei auswählen. Oder von Hand
> auf der DB vergeben (Windows: z.B. MySQL Workbench).
>
>  Viele Grüße,
>  Andreas
>
>
> On Wed, Apr 22, 2015 at 9:27 AM, Heine.thomas at online.de <
> Heine.thomas at online.de> wrote:
>
>>  Hallo,
>>
>> Es liegen seit Anfang April etwa 4,3 Mio Datensätze (ca.350MB) vor.
>> Ich denkejedoch, dass noch nichts da ist, was älter als 30 Tage ist.
>> Aber es gibt genügend,was älter als eine Woche ist (Reduzierung auf 1
>> Datensatz/sek.).
>>
>> hab jetzt mal folgende Reduzierung eingertagen:
>>
>> (7*24*60*60) => 2, //Older than 7 Days Datapoint per 2 sekunde
>> (30*24*60*60) => 30, //Older than 30 Days Datapoint per 30 sek
>> (6*30*24*60*60) => (1*60), //Older than 6 Month Datapoint per 1 Minutes
>> (365*24*60*60) => (3*60), //Older than 1 Year Datapoint per 3 Minutes
>>
>>
>>  Hier das Ergebnis:
>>
>> 04/22/15 09:23:52 - Processing Sensor ID 1...
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:52 and 04/15/15 09:23:52 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:52 and 03/23/15 08:23:52 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:52 and 10/24/14 09:23:52 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:52 and 04/22/14 09:23:52 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:52 - Processing Sensor ID 2...
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:52 and 04/15/15 09:23:52 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:52 and 03/23/15 08:23:52 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:52 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:52 and 10/24/14 09:23:52 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:52 and 04/22/14 09:23:52 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 3...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 4...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 5...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 6...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 7...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 8...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 9...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 10...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 11...
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 03/23/15 08:23:53 and 04/15/15 09:23:53 using a 2 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 10/24/14 09:23:53 and 03/23/15 08:23:53 using a 30 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/14 09:23:53 and 10/24/14 09:23:53 using a 60 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 -   Skipping compression pass for datapoints between
>> 04/22/15 09:23:53 and 04/22/14 09:23:53 using a 180 second timeframe: No
>> Datapoints found
>> 04/22/15 09:23:53 - Processing Sensor ID 12...
>> 04/22/15 09:23:53 -   Compressing datapoints between 04/01/15 18:19:24
>> and 04/15/15 09:23:51 using a 2 second timeframe
>> 04/22/15 09:23:53 -     Processing: 04/01/15 18:19:26 - 04/01/15 18:19:28
>> (0%)...                    array(3) {
>>   [0]=>
>>   string(5) "42000"
>>   [1]=>
>>   int(1142)
>>   [2]=>
>>   string(63) "DELETE command denied to user 'vz'@'localhost' for table
>> 'data'"
>> }
>> PHP Fatal error:  SQL FAILURE in /home/pi/
>> volkszaehler.org/misc/tools/vzcompress2.php on line 220
>>
>> Was hab ich falsch gemacht????
>>
>> Danke Gruß Thomas
>>
>>
>>
>> Am 22.04.2015 um 08:02 schrieb Andreas Götz:
>>
>> In welcher Auflösung liegen Deine Daten denn vor bzw. wieviele Einträge
>> pro Kanal hast Du in welchem Zeitraum? Sieht aus als hätte vzcompress
>> nichts gefunden...
>>
>>  Viele Grüße, Andreas
>>
>>
>>
>> Am 22.04.2015 um 06:58 schrieb "Heine.thomas at online.de" <
>> Heine.thomas at online.de>:
>>
>>   Hallo zusammen,
>>
>> hab das VZCompress einmalig durchlaufen lassen (hat etwa 17 Stunden
>> gedauert, wie ihr seht). Mit folgendem Ergebniss:
>>
>> ...
>> ...
>> ...
>> 04/22/15 06:42:16 -     Processing: 04/15/15 02:14:21 - 04/15/15 02:14:22
>> (100%)...
>> 04/22/15 06:42:16 -     Processing: 04/15/15 02:14:22 - 04/15/15 02:14:23
>> (100%)...
>> 04/22/15 06:42:16 -     Processing: 04/15/15 02:14:23 - 04/15/15 02:14:24
>> (100%)...
>> 04/22/15 06:42:16 -     Removed 0 Datapoints in *16071*
>> Seconds.
>>
>> 04/22/15 06:42:16 -   Skipping compression pass for datapoints between
>> 10/24/14 02:14:25 and
>> 03/23/15 01:14:25 using a 20 second timeframe: No Datapoints found
>> 04/22/15 06:42:16 -   Skipping compression pass for datapoints between
>> 04/22/14 02:14:25 and
>> 10/24/14 02:14:25 using a 60 second timeframe: No Datapoints found
>> 04/22/15 06:42:16 -   Skipping compression pass for datapoints between
>> 04/22/15 02:14:25 and
>> 04/22/14 02:14:25 using a 180 second timeframe: No Datapoints found
>> 04/22/15 06:42:16 - Done. Purged  Datapoints from 16 Channels in *59200*
>> Seconds
>>
>>
>> Irgendwie stimmt das aber nicht mit meiner Configuration überein, oder?
>> In meinem Script steht folgendes:
>>
>> (7*24*60*60) => (1*1), //Older than 7 Days Datapoint per 1 sekunde
>> (30*24*60*60) => (5*6), //Older than 30 Days Datapoint per 30 sek
>> (6*30*24*60*60) => (1*60), //Older than 6 Month Datapoint per 1 Minutes
>> (365*24*60*60) => (3*60), //Older than 1 Year Datapoint per 3 Minutes
>>
>> wo hab ich den Fehler gemacht?
>>
>> Danke Gruß Thomas
>>
>>
>>
>> Am 02.04.2015 um 10:35 schrieb Thomas Heine:
>>
>>  Hallo,
>> ich muss die Datenmenge meines Volkszählers verkleinern.
>> Würde das gerne mit vzcompress machen.
>> Ein Messpunkt/minute ist mir aber zu wenig.
>> Wie soll ich das skript abändern?
>> Ursprüngliches skript:
>> (7*24*60*60) => (1*60), //Older than 7 Days Datapoint per 1 Minute
>> (30*24*60*60) => (5*60), //Older than 30 Days Datapoint per 5 Minutes
>> (6*30*24*60*60) => (15*60), //Older than 6 Month Datapoint per 15 Minutes
>> (365*24*60*60) => (30*60), //Older than 1 Year Datapoint per 30 Minutes
>>
>> Mein script:
>> (7*24*60*60) => (1*1), //Older than 7 Days Datapoint per 1 sekunde
>> (30*24*60*60) => (5*6), //Older than 30 Days Datapoint per 30 sek
>> (6*30*24*60*60) => (1*60), //Older than 6 Month Datapoint per 1 Minutes
>> (365*24*60*60) => (3*60), //Older than 1 Year Datapoint per 3 Minutes
>>
>> würde das so klappen?
>> Kann ich das skript irgendwie einmalig aufrufen? oder macht es sinn, es
>> in eine crontab zu schreiben?
>>
>> Danke für die Hilfe!
>> Gruß
>> Thomas
>>
>>
>>
>>
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://demo.volkszaehler.org/pipermail/volkszaehler-users/attachments/20150422/e776f2c0/attachment-0001.html>