Skip to content
This repository has been archived by the owner on Dec 15, 2020. It is now read-only.

Fleet producing 500 Error #2295

Closed
anelshaer opened this issue Sep 2, 2020 · 5 comments
Closed

Fleet producing 500 Error #2295

anelshaer opened this issue Sep 2, 2020 · 5 comments

Comments

@anelshaer
Copy link

What version of fleet are you using (fleet version --full)?

v3.1.0

What operating system are you using?

CentOS

What did you do?

Deployed V3.1.0 for testing. after 2 days of working fine. i added KOLIDE_LOGGING_DEBUG and after i deployed fleet i got 500 error and still.

What did you expect to see?

i was expecting to get more logging. my objective was to enable access logging and if there is logging around running any osquery logs.

What did you see instead?

Uh oh! Error 500

{"component":"service","err":"list hosts: missing destination name primary_ip in *[]*kolide.Host","method":"ListHosts","took":"577.005µs","ts":"2020-09-02T11:19:04.701414231Z"}
{"component":"service","err":"selecting labels: missing destination name label_membership_type in *[]*kolide.Label","method":"ListLabels","took":"445.206µs","ts":"2020-09-02T11:19:04.702462612Z"}
{"component":"service","err":"getting enroll secret: selecting app config: missing destination name additional_queries in *kolide.AppConfig","ip_addr":"10.10.10.141:54638","method":"EnrollAgent","took":"786.318µs","ts":"2020-09-02T11:20:37.334139037Z","x_for_ip_addr":""}

@zwass
Copy link
Contributor

zwass commented Sep 17, 2020

It looks like you may have unintentionally redeployed the older version of Fleet here? That's what these missing destination name errors suggest to me.

@anelshaer
Copy link
Author

i'm not getting the 500 error now after redeploying. but i not seeing any kind of logs for different resources being accessed. or admin modification, query ran. does fleet have this kind of logs or it should be created as a feature request??.
thanks a lot Zwass.

@zwass
Copy link
Contributor

zwass commented Sep 25, 2020

Glad it worked for you!

Yes, those logs go to the Fleet server's stderr.

@zwass zwass closed this as completed Sep 25, 2020
@anelshaer
Copy link
Author

anelshaer commented Sep 25, 2020 via email

@zwass
Copy link
Contributor

zwass commented Sep 25, 2020

Yes, those logs go to stderr.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants