Jump to content
TorGuard
  • 0
Sign in to follow this  
5673345

Ubuntu 16 LTS: Torguard Client Flooding System Log (bytecount)

Rate this question

Question

Hi there.

 

The Torguard linux client is flooding the system log with bytecount entries to feed the client's up-down statistics.

 

Here is an example:

Aug 15 19:46:01 linux gnome-session[1475]: [2017-08-15 19:46:01.454 CEST D] unknown:0, unknown - OpenVPN mgmt message:  ">BYTECOUNT:6473719204,267296721"
Aug 15 19:46:02 linux gnome-session[1475]: [2017-08-15 19:46:02.329 CEST D] unknown:0, unknown - OpenVPN mgmt message:  ">BYTECOUNT:6473719204,267296915"

As you can see, every second a new entry is added to the system log (/var/log/syslog).  This seems to be unnecessary and adds weight to system resources and it doesn't take long for the syslog to grow out of control making it less useful/manageable.

 

Where is the setting/option to lower the logging level or disable logging completely?  Also, perhaps it would be more useful if torguard had it's own log (e.g., /var/log/torguard.log)?

 

Many thanks.


 

Share this post


Link to post
Share on other sites

3 answers to this question

Recommended Posts

  • 0

Hi there.

 

The Torguard linux client is flooding the system log with bytecount entries to feed the client's up-down statistics.

 

Here is an example:

Aug 15 19:46:01 linux gnome-session[1475]: [2017-08-15 19:46:01.454 CEST D] unknown:0, unknown - OpenVPN mgmt message:  ">BYTECOUNT:6473719204,267296721"
Aug 15 19:46:02 linux gnome-session[1475]: [2017-08-15 19:46:02.329 CEST D] unknown:0, unknown - OpenVPN mgmt message:  ">BYTECOUNT:6473719204,267296915"

As you can see, every second a new entry is added to the system log (/var/log/syslog).  This seems to be unnecessary and adds weight to system resources and it doesn't take long for the syslog to grow out of control making it less useful/manageable.

 

Where is the setting/option to lower the logging level or disable logging completely?  Also, perhaps it would be more useful if torguard had it's own log (e.g., /var/log/torguard.log)?

 

Many thanks.

 

 

 

 

 

Thanks for reporting - we just let the log run out on stdout and do not actively log to syslog. Would not be surprised if this is due to systemd.

 

We will fix in next release.

 

Regards

Share this post


Link to post
Share on other sites
  • 0
On 8/17/2017 at 7:03 PM, Support said:

 

 

Thanks for reporting - we just let the log run out on stdout and do not actively log to syslog. Would not be surprised if this is due to systemd.

 

We will fix in next release.

 

Regards

 

I noticed in the latest release that the log has been neutralized, but is there a way to still see this information on some log file in case people like myself like to scan through them? Or maybe have it as an option that can be enabled/disabled?

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×