EL7.1 razor-server-1.0.0-1.el7 jboss throws an error with CentOS 7.1.1503

[Alan Crosswell]

Hi there,

I'm trying to run razor-server-1.0.0 on CentOS 7.1 and get this Jboss error when using the razor-server-1.0.0 rpm:

19:35:12,147 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS014613: Operation ("add") failed - address: ([
    ("socket-binding-group" => "standard-sockets"),
    ("socket-binding" => "http")
]) - failure description: "JBAS014688: Wrong type for port. Expected [EXPRESSION, INT] but was STRING"

19:35:57,024 ERROR [org.jboss.as] (Controller Boot Thread) JBAS015875: JBoss AS 7.2.x.slim.incremental.16 "Janus" started (with errors) in 49314ms - Started 148 of 225 services (1 services failed or missing dependencies, 75 services are passive or on-demand)

Building from the identical Vagrantfile (just changing the CentOS version) this works fine under CentOS-6.6.

CentOS 7 Versions:

CentOS Linux release 7.1.1503 (Core), followed by yum upgrade
razor-server-1.0.0-1.el7
razor-torquebox-3.1.1.9-1.el7.

CentOS 6 Versions:

CentOS release 6.6 (Final), followed by yum upgrade
razor-server-1.0.0-1.el6
razor-torquebox-3.1.1.9-1.el6

/a

-- 

[Scott McClellan]

Hi Alan,

The razor-server rpm sets down and uses the default standalone.xml file. It looks like there has been an upstream update to how that file is interpreted. Short-term, you can fix this issue by running this to find the file (as your path may vary):

`find / -name standalone.xml`

Then inside this file, replace: 

'${http.port:8080}'

to just:

'8080'

That should resolve it once razor-server is restarted. Long-term we need our packaging to manage this file, but we currently just use the default in FOSS. I have created RAZOR-629 to track the effort to make this change code-side.

Scott

--
You received this message because you are subscribed to the Google Groups "puppet-razor" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-razor...@googlegroups.com.
To post to this group, send email to puppet...@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-razor.
For more options, visit https://groups.google.com/d/optout.

--

Join us at PuppetConf 2015, October 5-9 in Portland, OR - http://2015.puppetconf.com.  

Register early to save 40%!

[Alan Crosswell]

Here's what I've done in my vagrant shell bootstrap for now:

rel=`facter operatingsystemmajrelease`

if [ ${rel} -eq 7 ];then

   # patch for upstream change in CentOS 7:                
   sudo sed -i.bak -e 's/\${http.port:8080}/8080/' /var/lib/razor-torquebox/configuration/standalone.xml
fi

Thanks for your help!

/a