izZiManiA Posted February 4, 2021 Share Posted February 4, 2021 19 minutes ago, jcsnider said: Désolé pour la réponse très tardive, mais nous venons de régler cela nous-mêmes. La commande de lancement doit être: Sans l'ensemble LD_LIBRARY_PATH, il ne trouvera pas la bibliothèque sqlite que le serveur extrait pour une raison quelconque. I just tried it personally but I still have the problem with sqlite Log1 Log2 Link to comment Share on other sites More sharing options...
Habib Posted August 9, 2021 Share Posted August 9, 2021 Hi guys! Whenever I close my terminal, after some time, in my VM, the server closes. Any tips on how to keep it alive and running? ------- I figured it out, using "Screen". just get it and it's easy, if someone needs help: install GNU screen: apt-get update apt-get upgrade apt-get install screen type "screen". this will open up a new screen run the process to get the server up type: Ctrl + A, and then Ctrl + D. This will detach your screen session but leave your processes running feel free to close the SSH terminal. whenever you feel like it, come back to your terminal, and type screen -r to resume your previously detached session. to kill all detached screens, run: screen -ls | grep pts | cut -d. -f1 | awk '{print $1}' | xargs kill Link to comment Share on other sites More sharing options...
Talikan Posted August 9, 2021 Share Posted August 9, 2021 9 hours ago, Habib said: Hi guys! Whenever I close my terminal, after some time, in my VM, the server closes. Any tips on how to keep it alive and running? ------- I figured it out, using "Screen". just get it and it's easy, if someone needs help: install GNU screen: apt-get update apt-get upgrade apt-get install screen type "screen". this will open up a new screen run the process to get the server up type: Ctrl + A, and then Ctrl + D. This will detach your screen session but leave your processes running feel free to close the SSH terminal. whenever you feel like it, come back to your terminal, and type screen -r to resume your previously detached session. to kill all detached screens, run: screen -ls | grep pts | cut -d. -f1 | awk '{print $1}' | xargs kill Or "Tmux" If your leave, the session continue =) Link to comment Share on other sites More sharing options...
Habib Posted August 12, 2021 Share Posted August 12, 2021 Cool! There's any way to restart the server through the server terminal itself? Like a reboot command. Link to comment Share on other sites More sharing options...
Talikan Posted August 14, 2021 Share Posted August 14, 2021 Yes with "reboot" Scaly 1 Link to comment Share on other sites More sharing options...
Scaly Posted August 14, 2021 Share Posted August 14, 2021 On 8/12/2021 at 7:53 PM, Habib said: Cool! There's any way to restart the server through the server terminal itself? Like a reboot command. Linux person here. What type of unix OS are you using? Link to comment Share on other sites More sharing options...
Oddly Posted August 17, 2021 Share Posted August 17, 2021 On 8/12/2021 at 7:53 PM, Habib said: Cool! There's any way to restart the server through the server terminal itself? Like a reboot command. Most linux systems (not all) use systemd to manage services. This can ensure persistence of your server so if it crashes, it will automatically be restarted, you can also use systemd to ensure the service runs under a certain user so the app is limited to certain permissions, and restricted to their own environments within linux. Systemd allows us to manage services as well with console commands like `sudo systemctl stop <service>` `sudo systemctl start <service>` `sudo systemctl restart <service>` `sudo systemctl enable <service>` - ensures if the system restarts, the service is started back up automatically on boot. `sudo systemctl disable <service>` `sudo systemctl status <service>` - check whether a service is successfully started and running Assuming you are using a debian based distribution such as ubuntu, I garuntee your system is likely using systemctl. I use Manjaro linux which is arch based and it uses systemctl too. Here is a link for setting up services using systemd to sort of point you in the right direction. I'm sure you can find a tutorial that suits your distribution best.https://medium.com/@benmorel/creating-a-linux-service-with-systemd-611b5c8b91d6 Systemd also uses journald for logging, so any errors your service throws will be output into your system's journal. I recommend reading a bit up on how that works and what other capabilities systemd holds Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now