Issue Type: Bug Bug
Affects Versions: 1.3
Assignee: Unassigned
Created: 22/May/13 9:18 AM
Description:

After updating the AppAssembler plugin from 1.2.2 to 1.3 (no other changes, we've just tested it), the service fails to start after starting / rebooting the operating system. Interestingly, 'sudo service xxx start' keeps working like a charm, so the problem is limited to starting via runlevels.

The problem is that the path of the symlinked start script (/etc/init.d/) is taken as the base directory instead of the actual location (/opt/xxx/bin/). Thus we get the following error message in /opt/xxx/bin/wrapper.log (instead of /opt/xxx/logs/wrapper.log):
FATAL | wrapper | 2013/05/22 13:08:57 | Unable to resolve the full path of the configuration file, /etc/conf/wrapper.conf: No such file or directory

Explicitly setting the base directory in /opt/xxx/bin/xxx with 'BASEDIR="/opt/as2receiver"' resolves the issue. Also explicitly starting the service in crontab via '@reboot /etc/init.d/xxx' works.

We've also diffed /opt/xxx/bin/xxx between version 1.2.2 and 1.3 of AppAssembler and couldn't find any difference.

We're happy to test any suggestions and are reverting back to 1.2.2 for the moment.

Thanks for looking into this,
Philipp

Environment: Ubuntu 12.04 and 13.04
Project: Mojo AppAssembler Plugin
Priority: Major Major
Reporter: Philipp Krenn
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
--------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email

Reply via email to