[tor-relays] AccountingMax 48 GBytes is not working

[Vasilis]

Hi,

Artur Pędziwilk:

>> From: teor2345 at gmail.com
>>
>> It is weird that your traffic figures are 5x the limit.
>> We should fix this bug.
>>
>> Do you know which traffic figure is correct?
>> (For example, from your provider's monitoring?)
>>
>> Did you intend to use the "max" AccountingRule or the "sum" rule?
>>
>> Does this issue occur after the first day as well?
> 
> The high value is correct from according to other source metrics of metrics.
> I intend to use the "max" as whatever comes first I wish to hibernate. The issue occur randomly with different values of data and different hours but just before hibernation the sum is that value + correct limit so it really seems like traffic over obfs4proxy.
> Not sure if it is correct to see that as a bug. I learn more, I leave that public relay without obfs4proxy and I run additional instance just as bridge relay with obfs4proxy and accounting enabled to check if counting is correct.

Great let us know if the issue persists and/or you can reproduce it to
the bridge relay that uses obfs4proxy as a ServerTransportPlugin.

Thanks for running an extra bridge. :)


Cheers,
~Vasilis
-- 
Fingerprint: 8FD5 CF5F 39FC 03EB B382 7470 5FBF 70B1 D126 0162
Pubkey: https://pgp.mit.edu/pks/lookup?op=get&search=0x5FBF70B1D1260162

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-relays/attachments/20171020/8a4a10bd/attachment.sig>