11/23/2023 0 Comments Teamspeak 3 server setup![]() Would that be caused by not having used that -r switch?Īh, not sure how I forgot this part, I suppose the most important part, here's the error I get when attempting to run the start teamspeak3-server_linux_amd64]$. I was still able to use su tsdaemon, and get to my home directory to manually launch the script/server again, but the cron job didn't pick it up. However, and this may play into what you're saying with the system user, I attempted to reboot the server this morning, and when it came back up it doesn't look like the cron job worked. ![]() Using that I was able to go in and start the server with that script, and pull tsdaemon out of the sudoers file. I did get this issue working last night though by using the -R switch on my chown command. When I created the account I did not use the -r switch. ![]() ![]() That's a good question, and one I had too, I'm not sure who user 1000 is, it's definitely not one I had created, I assumed it was some sort of system account. If you don't, it will end up in the space controlled by LDAP and get wiped on every reboot. So who is user 1000? Are you using "useradd" to add your tsdaemon user? If so you must use the -r switch to create it as a system user. rw-r-r- 1 root root 1024 Aug 15 17:07 ts3server.sqlitedb rw-r-r- 1 root root 0 Aug 15 17:07 query_ip_blacklist.txt I'm not yet super well versed in linux permissions systems, but here's the output of my ls -al on the folder:ĭrwxrwxr-x 9 tsdaemon 1000 4096 Aug 15 17:16. What do I need to do to give my daemon user the proper permissions to successfully run that start script? My cron job is just going to /home/tsdaemon/teamspeak3-server_linux-amd64/ts3server_startscript.sh start Ultimately I want to get this setup to start on reboot automatically by adding a cronjob, but if it can't start by manually running the start script, I don't have a ton of faith in that cronjob working. Switched back to my daemon user and attempted the start script again, still no luck. So I tried backing out again, and changing the owner of the directory to my tsdaemon user (chown tsdaemon /home/tsdaemon/teamspeak_directory_here). Next I went into the freshly unzipped folder and tried to run the start script, again issues with permission denied, so I ran it as sudo, success. Tried again, and I didn't have bzip installed, so I installed bzip, and got my package unzipped. So I backed out and added the daemon account to my sudoers file, just to get the setup done. Once it was down I attempted to tar xvfj the file (it was a bz2 zip), doing that returned an error that said no permission allowed. I started by creating the user "tsdaemon", adding the password, then downloading the server file for linux for the website into the "/home/tsdaemon" directory. Now, in the name of security, I've decided to try and set it up as it's own little daemon user, but I'm running into issues. Previously I had done this as root, and just had it running as root every time the box would reboot, or go down. I'm currently trying to setup a teamspeak 3 server. I recently installed 7.2, and I'm getting it all set back up to my previous setup.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |