• If you need help or want to discuss things, you now can also join us on our Discord Server!
  • A first preview of the unlimited version of SinusBot can be found in the Upcoming Changes thread. A version for Windows will follow, but we don't have a release date, yet.

Full config file?

Status
Not open for further replies.

Crash129

Member
On my last sinusbot installation I had a huge config file and on my second installation I only have 3 lines... Where can I get the full config file?
 

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
The config will be generated on first start.

Yesterday I had a user with the same problem, the bot has not generated the config.
Have you started the bot once?
 

Crash129

Member
The config will be generated on first start.

Yesterday I had a user with the same problem, the bot has not generated the config.
Have you started the bot once?

I started the bot once as root, once as normal user and once with screen as normal user. Still only have a 3 line config.
 

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
Mhm, that seems its a bug...
Moment, i give you a config as work a round.
 

Xuxe

Containerholic
Staff member
is awesome!
V.I.P.
Contributor
Insider
TS3Path = "/home/xuxe/sinusbot/TeamSpeak3-Client-linux_amd64/ts3client_linux_amd64"
ListenHost = "0.0.0.0"
DataDir = ""
ListenPort = 8087
LocalPlayback = false
EnableLocalFS = false
LogLevel = 3
EnableProfiler = false
YoutubeDLPath = ""
EnableDebugConsole = false
UploadLimit = 83886080
RunAsUser = 0
RunAsGroup = 0
InstanceActionLimit = 6
UseSSL = false
SSLKeyFile = ""
SSLCertFile = ""
Hostname = ""
MTU = 1500
SampleInterval = 100
StartVNC = false
EnableWebStream = false
LogFile = ""
LicenseKey = ""
EnableAloneMode = false
DisableLocalXServer = false
DebugLocalXServer = false

[StreamRewrites]




Do not forget to make your changes.
 

flyth

is reticulating splines
Staff member
Developer
Contributor
I started the bot once as root, once as normal user and once with screen as normal user. Still only have a 3 line config.
This is HIGHLY problematic. The bot user needs to own EVERY file in the data-directory and the directory as well. If you run the bot for the first time as root, it will create those directories with root-permissions which might later prevent the bot user from writing in there. The same applies to the config.ini.

Please run
Code:
chown -R botuser:botgroup /path/to/your/bot/data
chown botuser:botgroup /path/to/your/bot/config.ini
to fix the permissions - change the parameters to fit your installation - botgroup is most likely the same as botuser.

[faq=18][/faq]
 
Last edited:
Status
Not open for further replies.
Top