Bug was verified and the latest Trains Server docker image for 0.15.0 was updated with a fix. Fix will be officially released in Trains Server version 0.15.1
Yeah, creating fixed users is protected so that the server will still run, but it's a relatively small piece of code, and the only way for such an error to be raised seems to be related to a "surprising" dict key received from the configuration
It really seems like an issue with the configuration file - would you like to send me the configuration file (with sensitive info removed) in a PM?
JIC - trains still works after that, it's just that the new user is not added and hence is not able to login
BTW - if you remove this new user and revert the configuration to the old fixed users list? Do you still get the error?
The error seems to indicate this happens even before the server tires to access the DB for this fixed user
Can I see some more context from the log? A little before the error?
maybe db somehow got corrupted ot smth like this? I'm clueless
From the error, it looks like some of the user details contains the keys "key" and "secret"... but I don't see it
{
username: "username"
password: "password"
name: "John Doe"
},
Can you share the new user's definition (I just want to see the structure, actual values don't matter)?
Hi DilapidatedDucks58 , what server version are you using?
[2020-06-09 16:03:19,851] [8] [ERROR] [trains.mongo.initialize] Failed creating fixed user John Doe: 'key'