traffic.h2.db growing rapidily and consuming storage

[Complex-Nerd]

Hello

We are running nxcloud in a cluster and just recently the master node has rapidly increased storage to over 90%. On investigation the files traffic.h2.db, traffic.h2.db.old and traffic.db.old.mig are large in size. I stopped the services and tried deleting traffic.h2.db.old and traffic.h2.db.old.mig to gain some space back as these too are large in size (not growing anymore though) and retarted the service but although the service retstarts ok the server fails to resolve DNS and the web management page fails to load on the master node also. We retain 10 days of logs currently.

Can anyone tell me what the traffic.h2.db.old and tarffic.h2.db.old.mig are for and why deleting them might stop the master node for working?

Thanks

[support200]

It seems like they are needed for reindexing of the traffic DB. Delete all traffic related files.

rm traffic*

As a result, you will lose your 10 day traffic log but you will have the new traffic DB.

If you want to build a real business service, you should think about separating logging/reporting from your server using Graylog like tools

https://nxfilter.org/tutorial/h-gray...te-logging.php

Graylog supports remote API and you can fetch logging/reporting data from it and show it to your users. That's the best.

[Complex-Nerd]

Thanks I will give that a try and let you know how I get on.

I am in the process of working through the transistion for managing the logs through Graylog but struggling to get the R&D time to focus on it at the mo but it is on the list!

[Complex-Nerd]

Thanks support200 that did the trick, I deleted around 7 files of traffic*

traffic.h2.db
traffic.h2.db.old
traffic.h2.db.old.mig
traffic.lock.db
traffic.lock.old
traffci.trace.db
traffic.trace.db.old

Looking at the db folder now and I see the traffic.h2.db and traffic.lock.db have been recreated. Eitherway all looks healthy again now, thanks again.