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

Integer conversion errors in 32-bit builds #2314

Closed
zwass opened this issue Oct 5, 2020 · 6 comments · Fixed by #2315
Closed

Integer conversion errors in 32-bit builds #2314

zwass opened this issue Oct 5, 2020 · 6 comments · Fixed by #2315

Comments

@zwass
Copy link
Contributor

zwass commented Oct 5, 2020

@kevensen reported in #2297 (comment) an issue with hosts enrolling.

Looking at the error message in #2297 (comment), failed to ingest result: ingesting query kolide_detail_query_system_info: strconv.Atoi: parsing \"67314212864\": value out of range, it seems that the issue comes from parsing the string to a 32 bit integer.

This implies - but we are waiting for confirmation - that the user has a 32 bit build of Fleet.

We need to understand how/why folks are running 32 bit builds of the Fleet server, and then choose a course of action:

  1. Decide and document that Fleet expects a 64 bit build.

  2. Ensure that int64 types and conversions are used explicitly anywhere this is necessary.

@zwass
Copy link
Contributor Author

zwass commented Oct 5, 2020

@kevensen confirmed that they are running a 32 bit build: #2297 (comment)

@zwass
Copy link
Contributor Author

zwass commented Oct 5, 2020

@kevensen want to pull down #2315 and see if it resolves your issue? I'm curious if anything else will come up.

@kevensen
Copy link

kevensen commented Oct 5, 2020

Sure thing. I can try in a little bit.

@kevensen
Copy link

kevensen commented Oct 5, 2020

Well, the host info is populated now and I do not see any issues with the atoi.

@kevensen
Copy link

kevensen commented Oct 5, 2020

I've added other hosts and am observing the desired behavior.

@zwass
Copy link
Contributor Author

zwass commented Oct 6, 2020

Thank you for testing that out! Let me know if any other issues come up.

zwass added a commit that referenced this issue Oct 6, 2020
Addresses an error when Fleet is compiled for a 32-bit architecture.

May not be comprehensive of all related errors.

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

Successfully merging a pull request may close this issue.

2 participants