Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escaping: Escape characters +-&|!(){}[]^"~*?:\ with \, e.g. \+
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
Answered
Hey Guys The First Time I'M Seeing This Behavior I'M Adding A New User To /Opt/Trains/Config/Apiserver.Conf And Restarting The Containers. All Old Users Are Able To Log In, But Not The New One (Invalid User/Password Combination). Any Ideas?

hey guys
the first time I'm seeing this behavior
I'm adding a new user to /opt/trains/config/apiserver.conf and restarting the containers. all old users are able to log in, but not the new one (Invalid User/Password combination). any ideas?

  
  
Posted 3 years ago
Votes Newest

Answers 14


Can you share the new user's definition (I just want to see the structure, actual values don't matter)?

  
  
Posted 3 years ago

{
username: "username"
password: "password"
name: "John Doe"
},

  
  
Posted 3 years ago

Hi DilapidatedDucks58 , what server version are you using?

  
  
Posted 3 years ago

0.15.0

  
  
Posted 3 years ago

[2020-06-09 16:03:19,851] [8] [ERROR] [trains.mongo.initialize] Failed creating fixed user John Doe: 'key'

  
  
Posted 3 years ago

From the error, it looks like some of the user details contains the keys "key" and "secret"... but I don't see it

  
  
Posted 3 years ago

Can I see some more context from the log? A little before the error?

  
  
Posted 3 years ago

maybe db somehow got corrupted ot smth like this? I'm clueless

  
  
Posted 3 years ago

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

  
  
Posted 3 years ago

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

  
  
Posted 3 years ago

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?

  
  
Posted 3 years ago

BTW - if you remove this new user and revert the configuration to the old fixed users list? Do you still get the error?

  
  
Posted 3 years ago

JIC - trains still works after that, it's just that the new user is not added and hence is not able to login

  
  
Posted 3 years ago

The error seems to indicate this happens even before the server tires to access the DB for this fixed user

  
  
Posted 3 years ago
673 Views
14 Answers
3 years ago
one year ago
Tags