Bug Report: Payara 5.2021.2 *does not start* / FISH-1297 #5192
Assignees
Labels
Status: Accepted
Confirmed defect or accepted improvement to implement, issue has been escalated to Platform Dev
Type: Bug
Label issue as a bug defect
Comments
|
There is not much to go on here. Can you paste the stack trace? |
|
Here is a sample of what I see when it fails: |
|
From what I can see, this is an issue with network not being configured properly. |
|
This behavior can probably be improved thought to make it more lenient to network configurations though. |
|
On that machine, if I 'ping localhost', it happily reports successful results hitting '127.0.0.1'. I also see in the /etc/hosts, that it has entries there for: And, there is a single non-loopback IP interface functional here too, via I do notice that the single actual interface only has an IPv4 address. I wonder if not having an available IPv6 address is contributing here? |
|
Can you paste complete output of “ifconfig -a” ? |
lprimak
added
the
Status: Accepted
|
here you go. The only change I have made is to tweak the IP address details of venet0:0. Everything else is exactly as it is. |
|
I have been able now to get it to start, but, in order to do that, I have to modify domain.xml so that the hazelcast config is disabled entirely. I have not yet found a way to have hazelcast enabled, and for it to start. |
|
I did also try adding to domain.xml: but this did not make any difference. |
|
Ah, the issue is that the only true (non-localhost) network is |
|
Hmmm. Yeah, this is a 'VPS' (virtual machine) on a hosting provider, so, it only has whatever it has. I imagine this would be a very common situation these days with hosted virtual machines. |
|
Apparently not. First time anyone has seen this. |
|
Ok. Well, I guess this has highlighted some kind of deficiency in the testing scenarios. I appreciate the effort in getting a fix out for it. |
|
Which provider are you using? This is certainly not the case with AWS or Azure. |
|
This particular one is on 'myhosting.com', but, let me check one of my other providers, and see what it looks like there too. |
|
Hmmm. Yeah, another VPS provider I have, has interfaces that appear like non-virtual interfaces, I suppose: |
|
any word of a fix? |
AlanRoth
changed the title
|
Cool. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
After creating a domain using
asadmin create-domain das, trying to start it withasadmin start-domain dasFAILS miserably.The same result happens using the latest JDK 8 from Oracle, and the latest Zulu JDK 11.
Running on Centos 6.8 x86.
Expected Outcome
The domain should start.
Current Outcome
The domain fails to start and the output contains stack trace details.
Steps to reproduce
unpack the downloaded payara distribution zip file
configure payara5/glassfish/config/asenv.conf with AS_JAVA having location of java folder
navigate to payara5/glassfish/bin folder
issue command: ./asadmin create-domain das
issue command: ./asadmin start-domain das
see error output instead of result message indicating success.
In contrast, payara-5-2020.4.zip works just fine.
Environment
The text was updated successfully, but these errors were encountered: