Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Syslog cluttered with loglines containing two numbers in Influx 1.7.7 OSS Debian 8 #14265

Closed
BerndWi opened this issue Jul 5, 2019 · 5 comments
Labels
Milestone

Comments

@BerndWi
Copy link

BerndWi commented Jul 5, 2019

Hi,

we have upgraded to influxdb 1.7.7 on Debian 8 from your repositories.
After starting the new version, we get more than 8000 loglines per second of just two numbers. It seems that a debug output hasn't been stripped before this release.

The lines look like the following:

Jul 5 09:47:54 influx3 influxd[160290]: 1674 1674 Jul 5 09:47:54 influx3 influxd[160290]: 2510 2510 Jul 5 09:47:54 influx3 influxd[160290]: 1650 1650 Jul 5 09:47:54 influx3 influxd[160290]: 2474 2474 Jul 5 09:47:54 influx3 influxd[160290]: 1650 1650 Jul 5 09:47:54 influx3 influxd[160290]: 2474 2474
Has anyone else seen this behaviour? I couldn't find anything in the config where debug logs are enabled.

Best regards,
Bernd

@mark-rushakoff
Copy link
Contributor

Thanks for raising this issue @BerndWi. You're right, I looked at the diff between v1.7.6 and v1.7.7, and I noticed this line:

fmt.Println(srcSz64, srcSz)

Looks like that was introduced to the 1.7 line in #14083. Same fmt.Println was included in the 1.8 line PR #13699.

I don't think there's any simple way we can turn that off without cutting a v1.7.8 release. I think in (almost?) all cases the numbers will be the same, so you could grep out the lines with grep -v -E '^([[:digit:]]+) \1$' in the meantime.

I'll raise this with the product team so that we can get this prioritized in a release asap.

@russorat
Copy link
Contributor

this fix is in 1.7.8 which is in rc0 at the moment.

@JNCone
Copy link

JNCone commented Nov 7, 2019

Hi,
are there any config changes needed? I updated to 1.7.9 and I still have this behavior in my logfiles.

best
Chris

@russorat
Copy link
Contributor

russorat commented Nov 8, 2019

@JNCone thanks! that specific line is definitely not in the 1.7.9 code, so either the message is coming from somewhere else or you are still running an older version of InfluxDB. Can you confirm it's not the latter and then we can reopen this issue?

@JNCone
Copy link

JNCone commented Nov 8, 2019

@russorat thanks for fast answer! It was a mistake from my side, I didn't restart the process after the upgrade. No more messages since the restart, so all good. Thanks a lot.

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

No branches or pull requests

4 participants