Tim
05/13/2019, 3:57 PMzwass
Tim
05/13/2019, 4:11 PMzwass
Tim
06/06/2019, 10:51 PMzwass
Tim
06/26/2019, 10:46 PMmysql> select id,created_at from hosts count ;
+---------+---------------------+
| id | created_at |
+---------+---------------------+
| 9 | 2019-04-12 22:19:06 |
| 171 | 2019-05-09 17:39:30 |
| 224 | 2019-05-09 17:42:14 |
| 226 | 2019-05-09 17:42:14 |
| 228 | 2019-05-09 17:42:16 |
| 251 | 2019-05-09 17:43:22 |
| 254 | 2019-05-09 17:43:25 |
| 264 | 2019-05-09 17:43:34 |
| 794 | 2019-05-09 18:11:26 |
| 33727 | 2019-05-10 15:14:35 |
| 33734 | 2019-05-10 15:14:46 |
| 33735 | 2019-05-10 15:14:46 |
| 33742 | 2019-05-10 15:14:55 |
| 143650 | 2019-05-13 13:09:00 |
| 171565 | 2019-05-13 19:02:03 |
zwass
Tim
06/28/2019, 4:15 PM1561764009535540,kolide-osquery,kolide_user,10.179.135.46,528065,2686921774,QUERY,kolide,'INSERT INTO hosts ( detail_update_time, osquery_host_id, seen_time, node_key ) VALUES (?, ?, ?, ?) ON DUPLICATE KEY UPDATE node_key = VALUES(node_key), deleted = FALSE',0
Fleet is making a ton of INSERTs and queries constantly, pretty sure this is not intended behavior. I have full log files I can send if you'd like.{
"component": "http",
"err": "authentication error: invalid node key: WTf9lH6ZQFe310M49TMlZi+GE/T2fsPS",
"ts": "2019-06-29T00:54:18.454937871Z"
}
From what I could find in the documentation and your previous conversations in Slack, the node key is assigned to a host by the server after a valid enroll secret is provided. What could be causing the node key to be invalid?