Skip to content
This repository has been archived by the owner on Nov 9, 2022. It is now read-only.

Troubleshooting

Jump to bottom
David Cassel edited this page Sep 22, 2015 · 5 revisions

General troubleshooting notes.

When the Deployer doesn't work the way you expect, a good place to start is adding "-v" (verbose). That should give you more information about what happens, making it easier to debug.

Replacement

  • In deploy/build.properties, I have app-port and I set up app-port-admin for a second HTTP server. I added the HTTP server XML to deploy/ml-config.xml, but the replacement isn't working right. In @ml.app-port-admin, the replacement script is only seeing "@ml.app-port", so I end up with 8123-admin. What gives?

The replacement script is not greedy -- it replaces the first string it finds that matches a variable. Workaround: instead of setting "app-port-admin", set "admin-app-port".

Deploy Modules failed

Bootstrap worked fine, but when I run deploy modules I this:

Roxy::Http : request failure count: 1, exception: #<Errno::ECONNABORTED: An established connection was aborted by the software in your host machine.>

Bootstrap and deploy use different ports. Most likely, the XCC port you specified in build.properties is blocked by a firewall. Check the firewall configuration to see whether the ports for your XCC and HTTP app servers are both open. If the XCC port is blocked and won't be opened, you'll need to push the project to the server and deploy from there.

Windows issues

Filenames with uncommon characters

Some people have had issues loading files with Japanese Kanji in the filename on Windows (10) environments with (US) English language settings.

Solution for Windows 10:

  1. Type Region in the start menu. If that doesn't work navigate to Control Panel\All Control Panel Items\Language\Advanced settings and then press "Apply language settings for to the welcome screen ...."
  2. Under Language for non-Unicode programs press Change system locale...
  3. Select the language of the filenames causing the ingestion issue. Note this will cause require a restart and afterwards the command prompt may show weird characters instead of the standard \
  4. Attempt to reload content. If you get a 400 error about a blank file then you may have picked the wrong language. If the load fails for another reason try starting command prompt by running cmd /u

Ruby SSL

Roxy will use HTTPS were appropriate. If your Ruby was not compiled with SSL, you'll see an error like this one:

$ ./ml dev bootstrap
/usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require': cannot load such file -- openssl (LoadError)
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /usr/local/lib/ruby/2.2.0/net/https.rb:22:in `<top (required)>'
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /root/Roxy/deploy/lib/RoxyHttp.rb:23:in `<top (required)>'
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /root/Roxy/deploy/lib/server_config.rb:21:in `<top (required)>'
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from /usr/local/lib/ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in `require'
    from deploy/lib/ml.rb:17:in `<main>'

openssl is used by the "net/https" Ruby gem. If you see this error, the solution is to use a Ruby with openssl compiled into it.

Clone this wiki locally