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

[Help] InfluxDB can't run on container's restart #575

Open
jpbaril opened this issue Feb 15, 2024 · 1 comment
Open

[Help] InfluxDB can't run on container's restart #575

jpbaril opened this issue Feb 15, 2024 · 1 comment

Comments

@jpbaril
Copy link

jpbaril commented Feb 15, 2024

Hi,

I have Scrutiny running like in example.hubspoke.docker-compose.yml

I can start this stack and it works. But if I stop the stack and try to restart it, it will not work.
Both influxdb and scrutiny master-web always fail to start.

influxdb logs say: "find: failed to read file names from file system at or below '/var/lib/influxdb2': No such file or directory"

I don't understand why because that directory is mounted on the host and contains files. Permissions and ownership did not change on host between first run and and tentative second run.

I never had such weird issue with any Docker container.
Thanks

@jpbaril
Copy link
Author

jpbaril commented Feb 15, 2024

In the interim I now use the image master-omnibus instead even though I don't need to collector part and it works.

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

No branches or pull requests

1 participant