Skip to content
This repository has been archived by the owner on Jun 4, 2021. It is now read-only.

Common problems and solutions

Jump to bottom
Melissa edited this page Jan 5, 2015 · 26 revisions

API results only use localhost in the URL, breaking remote razor-client

The URL returned in the /api endpoints is actually generated at runtime based on the hostname you contact. This comes up from the Ruby Rack code, rather than anything we directly control. Generally speaking this tries to resolve your hostname correctly -- and the most common cause of trouble is an entry in /etc/hosts that leads to resolving your server as "localhost" rather than the expected FQDN. Check there first.

Multiple network cards for Redhat task

By default, the Redhat task does not allow multiple network cards. If this capability is needed, run this command, which will modify the kickstart template to add the two devices:

sed -i '/network.*/i\network --bootproto=dhcp --device=eth0\nnetwork --bootproto=dhcp --device=eth1' /opt/puppet/share/razor-server/tasks/redhat.task/kickstart.erb

Other tasks may have similar workarounds available.

Do not use Mac Disk Utility to extract Windows ISO image files

Using Mac Disk Utility to extract Windows ISO files will result in missing file, for example the SPWIZENG.DLL will not be created when extracting Windows 2012R2 ISO image file, the SPWIZENG.DLL file is needed for window setup.

There are many reasons to cause the failure 'Exec Format error' in iPXE boot with Razor, using Mac Disk Utility to extract Windows ISO image is one of them.

spec tests fail on various text related things

Check that your PostgreSQL database was created with the UTF-8 encoding, which we depend on in order to manage text strings correctly. Newer versions default to this, but older versions may default to a locale-specific encoding that will cause failures.

/bin/systemctl status razor-server.status -l error on Centos 7

After getting PostgreSQL and Razor Server installed, there may be an issue starting the razor-server service with systemd:

JBAS014775:    New missing/unsatisfied dependencies:
      service jboss.binding.http (missing) dependents: [service jboss.web.connector.http]

To address the issue, change the line <socket-binding name='http' port='${http.port:8080}'/> to <socket-binding name='http' port='8080'/> in /var/lib/razor-torquebox/configuration/standalone.xml. This has not been encountered on any other systems.

Clone this wiki locally