-
Notifications
You must be signed in to change notification settings - Fork 63
Troubleshooting
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.
- 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".
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.