Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
pid file not properly overwritten #3425
I had an instance running on a server, and the PID file had a 5-digit process ID in it. I did a restart, and the new process ID was 4-digits, but the file sitll had the 5th digit from the prior process.
When writing the pid file, it should truncate it first if it already exists.
Running elasticsearch 0.90.0 on FreeBSD.
can you please provide more information. how you did this? I just tried the following (under Mac OS):
In my case the truncation works flawlessly (there is no check in elasticsearch if the pid file already exists). Anything you did different with the exception of your operating system? I am wondering if the sigar library is completely supported under freebsd, but judging from the official documentation it looks like it.
Your example shows the PID both of length 5.
echo aaaaaaaaaa > /tmp/pid
then run your test.
Here is what it looks like to me:
[root@logger]# /usr/local/etc/rc.d/elasticsearch start
Basically, if the pid assigned to elastic search is 5 digits long, and then
So if the first PID is 12345 and the second pid is 4321, what will be in
On FreeBSD, the PIDs are not necessarily monotonically increasing, so this
On Fri, Aug 2, 2013 at 3:05 AM, Alexander Reelsen