IO Error on opening Server Log (Solved)

I have a Problem on which i can’t get my head around.

When i want to look at the Server Logs from my Client, i get an IO Error in the Client.
grafik
The Logfile on the server on the other hand doesn’t show anything about this problem.


but is also quite empty in general, basically nothing from the server activity is logged, despite having all the logs on:

grafik

My server runs on Centos7, no SeLinux, Server uses a MariaDB as DB Backend.

The Configfile is:

# cat ts3server.ini 
voice_port=9987
voice_ip=0.0.0.0
licensepath=
filetransfer_port=30033
filetransfer_ip=0.0.0.0
query_port=10011
query_ip=127.0.0.1
query_ip_whitelist=query_ip_whitelist.txt
query_ip_blacklist=query_ip_blacklist.txt
dbplugin=ts3db_mariadb
dbpluginparameter=ts3db_mariadb.ini
dbsqlpath=sql/
dbsqlcreatepath=create_mariadb/
dbconnections=10
logpath=logs
logquerycommands=1
dbclientkeepdays=90
logappend=0
machine_id=1
license_accepted=1

Does anyone know why the server logs almost nothing and the client can’t display it?

The logs folder does not exist or user who runs the server has no access to read the logs.

Please never install or run the server with the ROOT account!

1 Like

Thanks for the answer.
I Posted the output of the log file, therefore the logfile and the directory exist:

# ls -lisah logs/
insgesamt 136K
131252 4,0K drwx------  2 ts3 ts3 4,0K 27. Feb 14:17 .
130792 4,0K drwxr-xr-x 10 ts3 ts3 4,0K 16. Mär 10:15 ..
131254 128K -rw-r--r--  1 ts3 ts3 121K 16. Mär 13:47 ts3server_0.log

Also, the server runs under its own user (ts3)

# p s aux | grep ts3
root      6592  0.0  0.0 112724   960 pts/1    S+   10:56   0:00 grep --color=auto ts3
ts3      18008  1.9  0.5 1353612 22136 ?       Ssl  Jan16 1728:45 ./ts3server inifile=ts3server.ini

By the way, if i write ps together in the codeblock i get a 403 forbidden error here in the forum :thinking:

There is only log 0 in your output. There should be at least one with another number at the end.

Are you sure the permissions are right?
Is the owner of the whole server and sub folder also ts3?

1 Like

So,

i am not sure if this solved the issue, but.

i added the write permission for the ts3 group to the logdirectory (so 775) and restarted the server, and now it wrote the files. (No idea if the change in permissions or the restart solved the issue)

1 Like