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

Failure to run on Windows #6223

Closed
mvadu opened this issue Apr 5, 2016 · 3 comments · Fixed by #6224
Closed

Failure to run on Windows #6223

mvadu opened this issue Apr 5, 2016 · 3 comments · Fixed by #6224
Milestone

Comments

@mvadu
Copy link
Contributor

mvadu commented Apr 5, 2016

This is a repeating pattern with InfluxDB, every now and then a PR will introduce a os.rename which breaks the Windows compatibility due to the way OS works. Latest example being a961ff9 broke the Windows version as it removed the f.Close() and tried to rename.

Now we are getting

[monitor] 2016/04/05 23:12:55 failed to create retention policy 'monitor', failed to create internal storage: rename influxdb\meta\meta.dbtmp influxdb\meta\meta.db: The process cannot access the file because it is being used by another process.
[monitor] 2016/04/05 23:12:55 failed to store statistics: rename influxdb\meta\meta.dbtmp influxdb\meta\meta.db: The process cannot access the file because it is being used by another process.
[monitor] 2016/04/05 23:13:05 failed to create retention policy 'monitor', failed to create internal storage: rename influxdb\meta\meta.dbtmp influxdb\meta\meta.db: The process cannot access the file because it is being used by another process.
@mvadu mvadu mentioned this issue Apr 5, 2016
4 tasks
@mvadu
Copy link
Contributor Author

mvadu commented Apr 5, 2016

If mods are okay, I would like to keep this issue open as its a reoccurring issue with Influx due to the nature of the project, and its heavy *nix orientation.

@gunnaraasen
Copy link
Member

Sounds like this would be best solved by running continuous integration tests on Windows builds.

@joelegasse
Copy link
Contributor

I do not think keeping this issue open will solve anything. We already have #5359 to track windows support. Windows is still not officially supported, so until that time, we'll have to rely on bug reports like this when changes cause issues due to quirks in windows.

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

Successfully merging a pull request may close this issue.

4 participants