[
http://jira.codehaus.org/browse/MRM-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262221#action_262221
]
Brett Porter commented on MRM-1467:
-----------------------------------
I haven't seen anyone else report these, though I can't see how you'd have
misconfigured it. On Solaris, it looks like the 'tr' command is the one not
working, on Linux I'm not sure why uname would do that.
You could workaround it by editing the archiva shell script to set the correct
WRAPPER_CMD.
> Archiva does not start up on Solaris 64-bit.
> --------------------------------------------
>
> Key: MRM-1467
> URL: http://jira.codehaus.org/browse/MRM-1467
> Project: Archiva
> Issue Type: Bug
> Affects Versions: 1.3.4
> Environment: SunOS unknown 5.10 Generic_138889-02 i86pc i386 i86pc
> Reporter: Andrew Stine
> Priority: Blocker
>
> Attempting to launch causes causes error:
> $ ./apache-archiva-1.3.4/bin/archiva console
> Bad string
> Bad string
> Bad string
> Bad string
> Unable to locate any of the following binaries:
> /export/home/astine/apache-archiva-1.3.4/bin/./wrapper---32
> /export/home/astine/apache-archiva-1.3.4/bin/./wrapper---64
> /export/home/astine/apache-archiva-1.3.4/bin/./wrapper
> necessary files appear to be missing or misnamed.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira