Title
#kolide
d

darren

09/23/2020, 3:30 PM
I'm trying to upgrade from 2.6.0 to 3.1.0 and I'm getting authentication errors for http and service components. Has anyone else come across this when upgrading from v2 to v3? If i roll back to version 2.6.0 everything works fine. Also the below error.
{
  "component": "http",
  "err": "authentication error: missing node key",
  "ts": "2020-09-23T15:18:39.879218643Z"
}
zwass

zwass

09/23/2020, 4:17 PM
Are you certain those errors are only happening on 3.1.0? I can't think of anything that changed that would cause these errors. It indicates that requests from osquery agents do not include the node key used for authentication.
d

darren

09/23/2020, 4:18 PM
yep, only happening on 3.0.0 and 3.1.0, if I roll back to any instance of version 2 everything works perfectly again
4:20 PM
Once restarted if I try and load the hosts section of the web interface I get a 500 error
zwass

zwass

09/23/2020, 4:29 PM
Did you run the db migrations?
d

darren

09/23/2020, 4:31 PM
yup
4:31 PM
i'll run them again
zwass

zwass

09/23/2020, 4:35 PM
When you were downgrading to 2.6.0 were you restoring from a backup? Because 2.6.0 should stop working after the migrations run.
d

darren

09/23/2020, 4:36 PM
just realised it's trying to do local migrations. Our DB is an RDS instance in AWS
zwass

zwass

09/23/2020, 4:37 PM
Pass the same env vars/config file/flags as the serve command and it will connect to the same DB.
4:37 PM
I think this should sort your issue.
4:37 PM
You'll probably find warnings in your logs that there are migrations that have not run.
4:37 PM
Not sure why it would have resulted in the particular error you saw though.
d

darren

09/23/2020, 4:37 PM
okay will give it a go
4:40 PM
@zwass that has fixed it! thanks. Will update my chef cookbook to add a migration step 🙂
zwass

zwass

09/23/2020, 4:41 PM
Glad to hear it 🍻