-
Notifications
You must be signed in to change notification settings - Fork 3
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 get new version of boxfuse to use -healthcheck=false anymore. The ELB never gets into a state that allows the project to run #268
Comments
This really looks like a bug. Why? Because I can get healthchecks working inside of AWS ELB TCP:80 BUT, boxfuse is looking for HTTP 200 at / on port 80. I cannot get HTTP port 80 / to work inside of AWS ELB, thus boxfuse does not see the ELB go into a healthy state, So, How do I force boxfuse to use TCP 80 vs HTTP???? HERE IS SUPPORTING Debugging logging: 13:55:47.784 Destroying Launch Template xxxxxxxx ... |
@axelfontaine Please do respond this is a production system that needs to be updated. Thank you |
Passing If your ELB already exists and you don't want to destroy it and have it recreated, you can safely update it's healthcheck configuration in the AWS console. That update then won't be overridden by subsequent deploys. |
The elb is set to tcp:80 it passes last build and is running smoothly.
The issue is in the healthchecks.path I cannot set to tcp:80 as they fail
during deployment and I cannot set the -healthcheck.path=tcp and I cannot
pass as you state -healthcheck=false as that produces error. I have
reported the debugging in a post on GitHub.
There is a bug in your current build that does not allow
-healthcheck=false. Please check your code.
…On Wed, Apr 27, 2022 at 12:33 AM Axel Fontaine ***@***.***> wrote:
Passing -healthcheck=false does indeed set the ELB healthcheck config to
TCP:80 instead of HTTP:80, but only when the ELB is initially created.
If your ELB already exists and you don't want to destroy it and have it
recreated, you can safely update it's healthcheck configuration in the AWS
console. That update then won't be overridden by subsequent deploys.
—
Reply to this email directly, view it on GitHub
<#268 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCI4HXDG5MFK364QTBFH5LVHDGSHANCNFSM5UCUIIFQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
LEGAL DISCLAIMER: The contents of this e-mail and any attachments are
strictly confidential and they may not be used or disclosed by someone who
is not a named recipient. If you have received this email in error please
notify the sender by replying to this email inserting the word
"misdirected" as the message and delete this e-mail from your system.
|
The actual healthcheck is performed by the ELB itself, and that appears to be failing. Make sure your application responds properly to the ELB request and things should work smoothly again. |
Hi Axel,
I'm sorry but you have a bug in the new build.
That is what I'm trying to communicate with you, but failing earlier.
The ELB is just fine and healthchecks are 100% ok with build 7.11.31 and is
running fine for the last 4 months.
[image: Screen Shot 2022-04-30 at 5.20.28 PM.png]
[image: Screen Shot 2022-04-30 at 5.20.43 PM.png]
[image: Screen Shot 2022-04-30 at 5.20.05 PM.png]
The issue is that I updated boxfuse to the newest version :
boxfuse -version
CloudCaptain Client (previously called Boxfuse) v.1.35.2.1525
Copyright 2022 Axel Fontaine Labs GmbH. All rights reserved.
Now I cannot use the parameter -healthchecks=false anymore. It always fails
the healthchecks now.
…--
Noel Grover
*Founder & CEO, VoiceIt*
612-423-9015
voiceit.io
LEGAL DISCLAIMER: The contents of this e-mail and any attachments
are strictly confidential and they may not be used or disclosed by someone
who is not a named recipient. If you have received this email in error
please notify the sender by replying to this email inserting the word
"misdirected" as the message and delete this e-mail from your system.
On Thu, Apr 28, 2022 at 3:41 AM Axel Fontaine ***@***.***> wrote:
The actual healthcheck is performed by the ELB itself, and that appears to
be failing. Make sure your application responds properly to the ELB request
and things should work smoothly again.
—
Reply to this email directly, view it on GitHub
<#268 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACCI4HROTRFCNT563H35OMTVHJFLBANCNFSM5UCUIIFQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
LEGAL DISCLAIMER: The contents of this e-mail and any attachments are
strictly confidential and they may not be used or disclosed by someone who
is not a named recipient. If you have received this email in error please
notify the sender by replying to this email inserting the word
"misdirected" as the message and delete this e-mail from your system.
|
I have to keep the current ELB and it not failing checks on TCP:80 it's running build 7.11.31 from 4 months ago. The issues is I cannot use the same -healthcheck=false with newest build 7.11.32 It fails everytime with -healthcheck=false |
boxfuse run /Users/noel/development/deploy/voiceitapi1webonly-7.11.32.war -env=voiceitprod -jvm.args="-Dfile.encoding=UTF-8 -Dnet -XX:+UseConcMarkSweepGC" -healthcheck=false -X -securitygroup=sg-fbf4d386 17:34:36.436 Unable to read cached account data for offline use: java.lang.ClassCastException -> java.util.LinkedHashMap cannot be cast to java.util.List 17:34:36.501 Account:xxxx Again this fails healthchecks, when it's not suppose to be checking.... |
17:46:10.944 WARNING: Run failed: Time out: ELB failed to put instances in service within 300 seconds Again the current ELB is passing on TCP:80 not HTTP 200 at / on port 80. So there is a bug in current boxfuse and having to revert to backup version |
Requesting system reboot =>
20:28:40.882 i-xxxxxxx -> i-xxxxxxx => [ 20.087872] reboot: Restarting system
20:29:28.689 Destroying all Instances in Auto Scaling Group xxxxxxx ...
20:29:43.497 Auto Scaling Group: i-003xxxxxxx [Terminating]
20:30:44.249 Destroying Auto Scaling Group xxxxx ...
20:30:50.990 Destroying Launch Template xxxxxxx ...
20:30:50.990 WARNING: Run failed: Time out: ELB failed to put instances in service within 300 seconds
=> check the instance logs
=> ensure your application responds with an HTTP 200 at / on port 80
=> ensure the healthcheck configuration (healthcheck.port, healthcheck.path, healthcheck.timeout) is correct
20:30:51.000 ERROR: Running xxxxxxxx failed!
com.boxfuse.base.exception.BoxfuseException: Running xxxxxxxxxxxxxxxx failed!
at com.boxfuse.client.core.Boxfuse.run(Boxfuse.java:655)
at com.boxfuse.client.commandline.Main.run(Main.java:325)
at com.boxfuse.client.commandline.Main.main(Main.java:133)
The text was updated successfully, but these errors were encountered: