Open hallard opened 5 years ago
Yes, there is: {event_lifetime, 86400}
. The number means how many seconds is an event displayed before it gets deleted.
Looks like #601 I setup this parameter to 3600 and still have events from 2hours, could it be a localtime or timezone issue? I've purged both from web interface. Can we purge thru API until it's fixed?
this is really weird, will have a look
the API allows you to delete all entries in a table (that's what the purge buttons do). simply HTTP DELETE /api/events
, but be careful-- it deletes everything without any warning and any way to recover (that's why its not documented)
:( Il mer 27 mar 2019, 16:10 Petr Gotthard notifications@github.com ha scritto:
this is really weird, will have a look
the API allows you to delete all entries in a table (that's what the purge buttons do). simply HTTP DELETE /api/events, but be careful-- it deletes everything without any warning and any way to recover (that's why its not documented)
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/gotthardp/lorawan-server/issues/606#issuecomment-477201053, or mute the thread https://github.com/notifications/unsubscribe-auth/ABdhaoypjwuxc_03538mI6Rl2Kl6G4scks5va4n_gaJpZM4bgk5f .
@hallard To further debug this issue I made the following updates to the latest master:
{trim_interval, 3600}
to define how often (in seconds) is the database trimmed. Note that if you say {event_lifetime, 3600} and {trim_interval, 3600} your events will never be older than 2 (two!) hours.Using config:
following a list of config parameters to make sure nothing was misspelled not misplaced.@gotthardp Thanks, I'll try this one setting both to 1800 to see, but not today, we need to finalise production by the end of day
@gotthardp
Looks like still not working for RX frames
% amount of rxframes retained for each device/node
{retained_rxframes, 10},
% events duration on interface
{event_lifetime, 1800},
{trim_interval, 1800},
Frames pages 458 frames
Most recent before
Older before (2 days ago)
Events looks better despite the fact there are 3 old events but all other are fine
Concerning the events: please see the Last Occurred date. There are no old events.
Concerning the Frames: what you posted is not necessarily wrong, could you please (wait 1800 seconds after server start and then) filter out only one DevAddr? Is there a DevAddr that has more than a high number of old frames or not?
Hi,
It's possible to remove all received frames, removing rxframe.DLC and rxframe.DCD ? Can I remove this with loraserver running ??
What is the best procedure ? Because my rxframes page does not load......
Dear @gotthardp is it safe to remove rxframe.DLC and rxframe.DCD ? Or to configure retained_rxframes=0? Thank you for your reply.
We need to decrease database size, on multitech GW with lot of devices, sometime admin interface does not answer anymore until we delete the following files:
event.DLC
andevent.DCD
rxframe.DLC
andrxframe.DCD
LATEST.LOG
As asked in decrease database size #601 We understand we can use parameter
Is there something similar for events ?
Thansks