Data.Binary.Get.runGetState at position 296: demandInput: not enough bytes
Joachim Breitner
mail at joachim-breitner.de
Thu Oct 31 10:14:56 CET 2013
Dear Henk,
Am Donnerstag, den 31.10.2013, 10:10 +0100 schrieb Henk te Sligte:
> Does arbtt-recover go through? What does it print?
>
>
> arbtt-recover goes through but I remember having errors as well when
> working with a larger log file. I might be wrong though, I'm not sure
> about this. In this case, I don't get errors:
> henk at linux-lu3t:~> arbtt-recover
> Found header, continuing... (38513 bytes to go)
Interesting; why does arbtt-recover not mention the errors?
> In this case I don't get errors after renaming capture.log.recovered
> to capture.log. I'm definitely sure I did get the demandInput: not
> enough bytes error before with a larger log file.
> henk at linux-lu3t:~/.arbtt> mv capture.log capture.old
> henk at linux-lu3t:~/.arbtt> mv capture.log.recovered capture.log
> henk at linux-lu3t:~/.arbtt> arbtt-stats
> Total time per
> tag
> ==================
> Tag_|_Time_|_Percentage_
Are there really no tags listed output, or did you cut it of from the
log?
> (in case you were wondering why I didn't use --logfile:)
> henk at linux-lu3t:~> arbtt-stats
> --logfile=~/.arbtt/capture.log.recovered
> arbtt-stats: ~/.arbtt/capture.log.recovered: openBinaryFile: does not
> exist (No such file or directory)
This way, the bash does not resolve ~, try
--logfile ~/.arbtt/capture.log.recovered
or give a path without ~ (relative or absolute).
> When you remove the log file and start with a fresh file, does
> arbtt-stats immediately give the error message, or only after
> it has
> been running for a while?
>
>
> Yes, it starts immediately with the same error:
> henk at linux-lu3t:~/.arbtt> rm capture.log
> henk at linux-lu3t:~/.arbtt> (arbtt-capture &)
> henk at linux-lu3t:~/.arbtt> arbtt-stats
> arbtt-stats: Data.Binary.Get.runGetState at position 429: demandInput:
> not enough bytes
Weird. Can you send me such a minimal file that produces the error?
> Did you modify the sample rate?
>
>
> No, I have just the minimal categorize.cfg:
> henk at linux-lu3t:~/.arbtt> cat categorize.cfg
> {$idle > 60 ==> tag inactive}
The sample rate is passed to arbtt-capture as a parameter, but
obviously, you did not change that either.
Greetings,
Joachim
--
Joachim “nomeata” Breitner
mail at joachim-breitner.de • http://www.joachim-breitner.de/
Jabber: nomeata at joachim-breitner.de • GPG-Key: 0x4743206C
Debian Developer: nomeata at debian.org
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <https://lists.nomeata.de/pipermail/arbtt/attachments/20131031/78efe431/attachment.asc>
More information about the arbtt
mailing list