If you are experiencing problems getting logs into the unRAID UI, here was a solution for me.
Fix logging in unRAID UI:
Started TS3 and got this mess in the log:
tail: cannot open 'ts3server_2016-09-14__22_35_20.912262_0.log' for reading: No such file or directory
tail: cannot open 'ts3server_2016-09-14__22_35_17.029256_0.log' for reading: No such file or directory
ls: write error: Broken pipe
tail: cannot open 'ts3server_2016-09-14__22_35_25.789968_0.log' for reading: No such file or directory
tail: cannot open 'ts3server_2016-09-14__22_35_20.912262_0.log' for reading: No such file or directory
ls: write error: Broken pipe
Well, that was pretty ugly. Let's get that fixed....connected to the docker and found the startup in /etc/services.d/teamspeak within there is a run file which has the following part a little broken:
exec \
s6-setuidgid abc tail -F -q --pid=$(cat /config/serverfiles/ts3server.pid) \
$(ls -t /config/serverfiles/logs | head -n 2)
The s6-setuidgid is similar to sudo -u abc -c <cmd> for those who are interested in the first tidbit. The problem was a simple oversight to the third line. ls -t /config/serverfiles/logs |head -n 2 lists the two latest files. The problem is the path to the file is not included in the listing. Changing the ls command to the following results output that appears to be desired:
ls -rt -1 /config/serverfiles/logs/*.log |head -n2
Logs in UI.
Cheers.