won't fix Autostart with Windows?

[Spider]

Hey guys.

So i installed sinusbot yesterday without any problems on my Windows Server (2016,Datacenter). I normaly use nssm for dealing with service autostart/stop so i tried using nssm for sinusbot but unfortunatly sinusbot crashes once the service starts running. Are there any parameters needed to run sinusbot as a service?

 

[mxschmitt]

unfortunatly sinusbot crashes o

Can you show us logs?

 

[irgendwr]

Why don't you just put the shortcut to the Sinusbot in the autostart folder?

 

[Spider]

Can you show us logs?

Here you go https://pastebin.com/FzYTHSAq

While looking through the logs it was pretty obvious that the service seems to be in a constant start/stop loop. Confirmed this in task manager.

Why don't you just put the shortcut so the Sinusbot in the autostart folder?

Unfortunately if i do this the program would only start after i logged on (via RDP). Kinda beats it's purpose then.

 

[irgendwr]

Unfortunately if i do this the program would only start after i logged on (via RDP). Kinda beats it's purpose then.

Ah, right.

Here you go https://pastebin.com/FzYTHSAq
While looking through the logs it was pretty obvious that the service seems to be in a constant start/stop loop. Confirmed this in task manager.

Seems to be unable to talk to the teamspeak client in any way, so TS could be the problem (maybe because there is no screen session initialized? I don't think the client can run headless by itself.)
The looping is caused by nssm.

 

[Spider]

Well if i manually start Sinusbot there isn't a problem. I also tried starting the service while being connected via RDP however the results are the same. Either sinusbot is crashing and nssm is automaticly trying to start it again or sinusbot isnt crashing and windows service manager craps on it for some reason.