wildfly.service failed because a configured resource limit was exceeded

[epetter...@gmail.com]

when attempting to run wildfly server, the following error:

wildfly.service failed because a configured resource limit was exceeded

Windows machine running hyper-v

VM is CentOS7 minimal install

SELinux is disabled

user "wildfly" is in "wheel" group. chown's the wildfly folders and everything exactly as listed in the installation guide.

much appreciated if anyone has this error, to post that they also have it, or any solutions they came up with.

thank you.

[epetter...@gmail.com]

for any others having this issue - its because JBOSS_USER is not defined in the install script provided with wildfly-final-10.0.0.1

basically - the current wiki installation steps are broken. following them wont work in setting up a working installation.

I am therefor curious if anyone knows where a valid, functional, and updated (i2b2-1.7.09C and CentOS7) installation guide or install script is located?
How did all of you get your installs going?

Thanks.

[Mendis, Michael E.]

Hi,

 

I am looking at trying to make the install documents more accurate.   I did find this: https://community.i2b2.org/wiki/display/getstarted/2.4.2.3+Run+Wildfly+as+a+Linux+Service

 

Which at the bottom in Step 4 talks about setting the JBOSS_USER in the wildfly.conf to the user which owns the wildfly application.  Was this where you thought the install was broken?

 

Thanks

mike

 

From: <i2b2-ins...@googlegroups.com> on behalf of "epetter...@gmail.com" <epetter...@gmail.com>
Reply-To: "i2b2-ins...@googlegroups.com" <i2b2-ins...@googlegroups.com>
Date: Wednesday, November 7, 2018 at 1:59 PM
To: i2b2 Install Help <i2b2-ins...@googlegroups.com>
Subject: Re: wildfly.service failed because a configured resource limit was exceeded

 

        External Email - Use Caution        

--
You received this message because you are subscribed to the Google Groups "i2b2 Install Help" group.
To unsubscribe from this group and stop receiving emails from it, send an email to i2b2-install-h...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[epetter...@gmail.com]

Hi Mike

Yes i did follow those steps, but it isnt working.

The install script (wildfly-init-redhat.sh) needs to add:

JBOSS_USER=wildfly
export JBOSS_USER

To the top of the file preferably.

(wildfly = whatever username that will run it of course)

Then the install script works fine.

The line that causes this error is:

chown $JBOSS_USER $(dirname $JBOSS_PIDFILE) || true

Because JBOSS_USER is undefined in the script. Then the PIDFILE can never be created.

While we are on the topic of the install wiki....

The page you linked also has a few path errors:

Step 4 & 5 say "defaults" path rather than "default" (remove the "s")

EG:

cp wildfly.conf /etc/defaults/widlfly
open /etc/defaults/wildfly.conf

I'm assuming anyway?

Another issue with the wiki is the https cert is not working or expired. Every time I visit a page I get this warning:

Your connection is not private
Attackers might be trying to steal your information from community.i2b2.org (for example, passwords, messages, or credit cards). Learn more
NET::ERR_CERT_SYMANTEC_LEGACY
Warnings may be common while websites update their security. This should improve soon.

The navigation menu also wont load.

Are you in charge of the wiki?
I'd be happy to report issues in the install process and help improve it, if I can.

Thanks for the reply.

Best regards,

Efraim

[epetter...@gmail.com]

Also one more question: if running centos7 - are we supposed to use the /systemd/ install method for wildfly instead of the /init.d/ install method?

I was a bit confused by this.

The /systemd/ script is quite small. But init.d is for centos6 and systemd for 7....in the install wiki it doesnt even mention the systemd. I only found it when I unzipped and browsed the package and then wondered if that was why it wasnt working.

Thanks.