Virtual server manager is unable to create file transfer dirs

[Robidu]

Greetings!

One issue resolved, one issue cropped up...

Now MySQL is fired up and initialized correctly, but now the virtual server manager refuses to correctly initialize.
I have installed the daemon in /usr/local/teamspeak and I'm launching by a start script that resides in /etc/init.d, however, for some reason the "files" directory won't be created.
I have set all files/dirs concerning TS to uid/gid root/teamspeak, with all files and dirs set to the permissions 0750 (except for /usr/local/teamspeak and /usr/local/teamspeak/logs, which have 0770).

Here's the dir listing:

drwxrwx---  7 root teamspeak    4096 11. Mai 09:32 .
drwxr-xr-x 14 root root         4096 11. Mai 01:07 ..
drwxr-x---  2 root teamspeak    4096 11. Mai 08:52 doc
-rwxr-x---  1 root teamspeak  217096 11. Mai 01:09 libts3db_mysql.so
-rwxr-x---  1 root teamspeak 1056280 11. Mai 01:09 libts3db_sqlite3.so
drwxrwx---  2 root teamspeak    4096 11. Mai 10:54 logs
drwxr-x---  2 root teamspeak    4096 11. Mai 01:08 serverquerydocs
drwxr-x---  4 root teamspeak    4096 11. Mai 01:08 sql
-rw-r-----  1 root teamspeak      98 11. Mai 08:21 ts3db_mysql.ini
-rw-r-----  1 root teamspeak     475 11. Mai 09:14 ts3.ini
-rwxr-x---  1 root teamspeak 5447240 11. Mai 01:08 ts3server_linux_amd64
drwxr-x---  2 root teamspeak    4096 11. Mai 10:37 tsdns

TS is correctly generating its logs in /usr/local/teamspeak/logs, and stdout and stderr are redirected by startproc to /var/log/teamspeak3.

Finally, this is what winds up in the log file:

2012-05-11 09:03:00.922571|INFO    |ServerLibPriv |   | TeamSpeak 3 Server 3.0.5 (2012-04-23 04:46:12)
2012-05-11 09:03:00.924375|INFO    |DatabaseQuery |   | dbPlugin name:    MySQL plugin, (c)TeamSpeak Systems GmbH
2012-05-11 09:03:00.924454|INFO    |DatabaseQuery |   | dbPlugin version: 1
2012-05-11 09:03:00.947070|WARNING |Accounting    |   | Unable to find valid license key, falling back to limited functionality
2012-05-11 09:03:01.461867|CRITICAL|VirtualSvrMgr |   | unable to start filemanager, while creating directory : files failed

Furthermore, here's my ts3.ini:

machine_id=
default_voice_port=9987
voice_ip=0.0.0.0
licensepath=
filetransfer_port=30033
filetransfer_ip=0.0.0.0
query_port=10011
query_ip=0.0.0.0
query_ip_whitelist=query_ip_whitelist.txt
query_ip_blacklist=query_ip_blacklist.txt
dbplugin=ts3db_mysql
dbpluginparameter=/usr/local/teamspeak/ts3db_mysql.ini
dbsqlpath=/usr/local/teamspeak/sql/
dbsqlcreatepath=create_mysql
dbconnections=10
logpath=/usr/local/teamspeak/logs
logquerycommands=0
dbclientkeepdays=30
logappend=0

Any help would be greatly appreciated since I already have searched the forum, but I haven't found a feasible solution so far.

I have also attempted to set everything to uid/gid teamspeak/teamspeak, but that wouldn't work, either...

[dante696]

Please try this.
Edit your server.ini and add your server ip, for filetransfer.

Please check, that the folder "\files\virtualserver_x" do exist
And are you 100 sure, that the server is allowed, to write any files?

[Robidu]

Please try this.
Edit your server.ini and add your server ip, for filetransfer.

According to server_quickstart.txt this is the address at which file transfers from the clients arrive, so setting this just won't do. Since the IP address is 0.0.0.0, any address is allowed for incoming file transfers - and furthermore, the server doesn't have to do TCP/IP when writing to local disk space.

Please try this.
Please check, that the folder "\files\virtualserver_x" do exist
And are you 100 sure, that the server is allowed, to write any files?

Absolutely. /usr/local/teamspeak is uid/gid root/teamspeak and both user and group writable. Furthermore, the uid teamspeak belongs to the group teamspeak, which automatically enables any group access modes if the uids don't match.
Also, when the directories in question don't exist, the client is supposed to create them on its own - however, this doesn't happen for some reason.
And I have also cded to /usr/local/teamspeak in the startup script so that shouldn't be a problem, either...

Btw.: A small wrapper script managed to get rid of this issue. Somehow cding to another directory isn't carried over by startproc, and the pwd seems to be reset to somewhere else - but with running the wrapper, I managed to do the cd. Now the server starts up just as expected.