Pending TeaSpeak has different behaviour on 'logview'

eduardoroeder · Feb 28, 2020

Using plain logview sq command in TeaSpeak has different behaviour as in Tea*Speak.

Sending plain 'logview':
TeaSpeak:

http://imgur.com/oL6btEb

Tea*Speak:

http://imgur.com/whuIJr8

Sending "logview lines=30":
TeaSpeak:

http://imgur.com/qyDrfpM

Tea*Speak:

http://imgur.com/oH6MMkt

Sending "logview instance=0 begin_pos=0 lines=100":
TeaSpeak:

http://imgur.com/9WMU6RD

Tea*Speak: https://i.imgur.com/aK5v59b.png

Both servers has the same logging options: https://i.imgur.com/x4UXEsR.png

Can't open the log from TeaSpeak in YaTQA and neither at TS3 client also.

BIOS · Feb 28, 2020

in YaTQA it currently not works and ts3 client is not supported....
Tea*Speak has her own logfile system.

eduardoroeder · Feb 28, 2020

So how can one read the log even with simple ServerQuery commands?

---- Automatically Merged Double Post ----

It should behave like the expected counterparts, specially when provisioning via interfaces (blesta, whcms, tsi, etc)

grepher76 · Feb 28, 2020

me too :

TeamSpeak3_Adapter_ServerQuery_Exception: sql empty result set in /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Adapter/ServerQuery/Reply.php:316 Stack trace: #0 /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Adapter/ServerQuery/Reply.php(88): TeamSpeak3_Adapter_ServerQuery_Reply->fetchError(Object(TeamSpeak3_Helper_String)) #1 /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Adapter/ServerQuery.php(140): TeamSpeak3_Adapter_ServerQuery_Reply->__construct(Array, 'logview lines=3...', Object(TeamSpeak3_Node_Host), true) #2 /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Node/Abstract.php(70): TeamSpeak3_Adapter_ServerQuery->request('logview lines=3...', true) #3 /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Node/Server.php(87): TeamSpeak3_Node_Abstract->request('logview lines=3...', true) #4 /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Node/Abstract.php(94): TeamSpeak3_Node_Server->request('logview lines=3...') #5 /var/www/clients/client0/web1/web/libraries/TeamSpeak3/Node/Server.php(2323): TeamSpeak3_Node_Abstract->execute('logview', Array) #6 /var/www/clients/client0/web1/web/panel/logs.php(26): TeamSpeak3_Node_Server->logView() #7 {main}

WolverinDEV · Feb 28, 2020

Works for me:

What are your config.yml options?

eduardoroeder · Feb 28, 2020

I'll take a look inside config.yaml, in the meantime, what's the expected to be inside?

WolverinDEV · Feb 28, 2020

There is a setting to set the log level.
TeaSpeak does not take the virtual server log settings into account, because TeaSpeak has in general another log system.

eduardoroeder · Feb 28, 2020

Code:

log:
  #Description:
  #  The log level within the log files
  #  Available types:
  #    0: Trace
  #    1: Debug
  #    2: Info
  #    3: Warn
  #    4: Error
  #    5: Critical
  #    6: Off
  #The value must be a positive numeric value between 0 and 6
  level: 3
  #Description:
  #  The log level within the TeaSpeak server terminal
  #  Available types:
  #    0: Trace
  #    1: Debug
  #    2: Info
  #    3: Warn
  #    4: Error
  #    5: Critical
  #    6: Off
  #The value must be a positive numeric value between 0 and 6
  terminal_level: 2
  #Description:
  #  Disable/enable ascii codes within the log file
  #The value must be a positive numeric value between 0 and 1
  colored: 0
  #Description:
  #  Virtual server log chunk size
  #The value must be a unsigned long between 0 and 65535
  vs_size: 0
  #Description:
  #  The log file path
  #The value must be a string
  path: logs/log_${time}(%Y-%m-%d_%H:%M:%S)_${group}.log

WolverinDEV · Feb 28, 2020

"level: 3" well if you have no warning within your log, logview will be empty as well

grepher76 · Feb 28, 2020

For me

Code:

log:
#Description:
# The log level within the log files
# Available types:
# 0: Trace
# 1: Debug
# 2: Info
# 3: Warn
# 4: Error
# 5: Critical
# 6: Off
#The value must be a positive numeric value between 0 and 6
level: 2
#Description:
# The log level within the TeaSpeak server terminal
# Available types:
# 0: Trace
# 1: Debug
# 2: Info
# 3: Warn
# 4: Error
# 5: Critical
# 6: Off
#The value must be a positive numeric value between 0 and 6
terminal_level: 2
#Description:
# Disable/enable ascii codes within the log file
#The value must be a positive numeric value between 0 and 1
colored: 0
#Description:
# Virtual server log chunk size
#The value must be a unsigned long between 0 and 65535
vs_size: 1
#Description:
# The log file path
#The value must be a string
path: logs/log_${time}(%Y-%m-%d_%H:%M:%S)_${group}.log

eduardoroeder · Feb 28, 2020

WolverinDEV said:
"level: 3" well if you have no warning within your log, logview will be empty as well

I'm pretty sure that this instances has warnings.... They are 2-3 months old. I'll switch the logging options after you update the talk power bug and try out.

In my opinion, you should allow the user to tweak what to show in log per instance. For some instances I don't mind to skip any kind of unproductive logs and just show permission changes. For others, like for testing new functions, I'd rather have full logs. Having full logs in production with instances of 600 slots (300-500 users constantly leaving and enter) will spam the logs pretty fast.

---- Automatically Merged Double Post ----

@WolverinDEV can't find 1.4.10 in the repo's....

eduardoroeder · Mar 12, 2020

@WolverinDEV this happens in 1.4.10 aswell. Does TeaSpeak creates a new log file for each instance like ts3? Or it's all in one file?

WolverinDEV · Mar 20, 2020

eduardoroeder said:
@WolverinDEV this happens in 1.4.10 aswell. Does TeaSpeak creates a new log file for each instance like ts3? Or it's all in one file?

Depends on your server settings.
If the
vs_size is 0 than all files are together, else every server has a different log file.

mkll11one · Mar 20, 2020

WolverinDEV said:
Depends on your server settings.
If the
vs_size is 0 than all files are together, else every server has a different log file.

@WolverinDEV
I did set vs_size 0 on my config.yml and "reload config" and tried to look "log" at (yatqa)

> grep: symbol lookup error: grep: undefined symbol: pcre_jit_stack_alloc

cat: write error: Broken pipe

WolverinDEV · Mar 20, 2020

1. The value is not reloadable.
2. Yes thats the error (I'm already aware of, it comes with the libnice dependency & prce)... But I don't really want to write a log reader :/

eduardoroeder · Mar 27, 2020

@WolverinDEV I've updated to the last 1.4.10 and still gives the same MySQL error. I've changed the vssize to bigger than 0 (actually ~16000) and even though it splits the server logs, it won't split between all instances. It only splits the core server log into the usual file and then the virtual instances to another file with group finishing in '0'. It should create a log file for each virtual indtance instead of putting them all into only one file.

WolverinDEV · Mar 27, 2020

Hey, set the vssize to 1 for example

ANd which MySQL error? May see the other thread within this forum

eduardoroeder · Mar 27, 2020

I meant "sql" not "MySQL" lol

The core problem within logview on yatqta on the main thread. I still can't see logs in YaTQA, even the server query command doesn't show.

REDOSS · Aug 15, 2020

// Closed

In TeaSpeak has implemented its own server logs.
Use the command logquery

Pending TeaSpeak has different behaviour on 'logview'

eduardoroeder

Fanatic member

BIOS

TeaSpeak Team

eduardoroeder

Fanatic member

grepher76

Well-known member

WolverinDEV

TeaSpeak Team

eduardoroeder

Fanatic member

WolverinDEV

TeaSpeak Team

eduardoroeder

Fanatic member

WolverinDEV

TeaSpeak Team

grepher76

Well-known member

eduardoroeder

Fanatic member

eduardoroeder

Fanatic member

WolverinDEV

TeaSpeak Team

mkll11one

TeaSpeak Team

WolverinDEV

TeaSpeak Team

eduardoroeder

Fanatic member

WolverinDEV

TeaSpeak Team

eduardoroeder

Fanatic member

REDOSS

TeaSpeak Team