-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
Cannot boot after a crash - data is effectively lost now #904
Comments
@mattheworiordan Just out of curiosity, how much memory is available to the process? I ran into an instance recently where insufficient memory (1GB) caused repeated crashes on startup. Moving it to a larger VM fixed the issue. |
@toddboom 3.7GB on the machine, and no limits as far as I can tell. The problem is not that it was crashing, the process did not exit, it just never proceeded and never presented any errors. |
What happens if you start Influx in a console interactively? Wondering if On Wed, Sep 3, 2014 at 11:00 PM, mattheworiordan notifications@github.com
|
@pauldix in my ticket you will see I included the output from a console session as well as the output from the log file |
Hi @mattheworiordan, let me rephrase the issue to make sure I understand it correctly. Whenever you bring up the node, the daemon just hangs with the given output in the log. Assuming that the service doesn't die and just hangs, I think this issue is due to the raft node trying to change its address. Specifically the lilne below is what's causing the issue:
The node is trying to change its hotsname from |
duplicate of #914 |
After running a join query that caused InfluxDB to crash, I am now unable to start up my InfluxDB database. This is pretty worrying as I have recently started using InfluxDB to store data that we cannot discard, and I am no longer able to recover this data. This happened once before, but I suspect it was a one off, but clearly it's not. I am running InfluxDB 0.8 on Ubuntu 14.04 in a Docker LXC container.
Any advice on what steps I could take to recover my data and InfluxDB would be appreciated.
As you can see from my InfluxDB log below, the server starts up, detects shards, and then never makes the admin or REST interface available.
In the console of the InfluxDB process
In my log file
The text was updated successfully, but these errors were encountered: