You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@archiva.apache.org by "Leitch, Oblio" <Ob...@state.vt.us> on 2012/11/28 19:27:56 UTC
new user question
I'm trying to get Archiva setup on our dev box. I've unzipped the files and chmod +x'd the bin/archiva file. However, when I run it, I get
Unable to locate any of the following operational binaries:
/var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper-linux-power6(architected),altivecsupported-64
/var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper-linux-power6(architected),altivecsupported-32
/var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper
Maybe I don't have the right version?
Thanks,
Oblio
Re: new user question
Posted by Olivier Lamy <ol...@apache.org>.
2012/11/30 Leitch, Oblio <Ob...@state.vt.us>:
> The ARGS line is missing a replace:
> ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed 's/wrapper.app.parameter.[0-9]*=//' | sed "s#%ARCHIVA_BASE%#$ARCHIVA_BASE#" | tr '\n' ' '`
>
Thanks I hope it works.
More generally I think we could provide an auto executable jar for
ease archiva testing.
something like: java -jar archiva.jar
This could startup embeded tomcat and run the webapp.
> -----Original Message-----
> From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
> Sent: Thursday, November 29, 2012 6:32 PM
> To: users@archiva.apache.org
> Subject: Re: new user question
>
> Sorry, replace CONTINUUM_BASE with ARCHIVA_BASE in this example - they both use the same appassembler generated config.
>
> On 30/11/2012, at 10:30 AM, Brett Porter <br...@apache.org> wrote:
>
>> One option is to get a stock jetty download, and copy across our configuration & application files - then you'll have all their scripts.
>>
>> Alternatively here's a quick and dirty start script you could use to pull the info from wrapper.conf which should keep working with new versions:
>>
>> #!/bin/sh
>>
>> set -e
>>
>> (
>> cd `dirname $0`/..
>> if [ -z "$CONTINUUM_BASE" ]; then
>> CONTINUUM_BASE=.
>> fi
>>
>> REPO_DIR=lib
>> CP=`cat conf/wrapper.conf | grep ^wrapper.java.classpath.[0-9]*= | grep -v '.pom$' | sed 's/wrapper.java.classpath.[0-9]*=//' | sed "s#%REPO_DIR%#$REPO_DIR#" | tr '\n' ':' | sed 's/:$//'`
>> ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed 's/wrapper.app.parameter.[0-9]*=//' | tr '\n' ' '`
>> JVM_ARGS=`cat conf/wrapper.conf | egrep ^wrapper.java.additional.[0-9]*= | sed 's/wrapper.java.additional.[0-9]*=//' | sed "s#%CONTINUUM_BASE%#$CONTINUUM_BASE#" | tr '\n' ' '`
>> JVM_MINMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.minmemory= | sed 's/wrapper.java.minmemory=//'`
>> if [ ! -z "$JVM_MINMEM_ARG" ]; then
>> JVM_ARGS="-Xms${JVM_MINMEM_ARG}m $JVM_ARGS"
>> fi
>> JVM_MAXMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.maxmemory= | sed 's/wrapper.java.maxmemory=//'`
>> if [ ! -z "$JVM_MAXMEM_ARG" ]; then
>> JVM_ARGS="-Xmx${JVM_MAXMEM_ARG}m $JVM_ARGS"
>> fi
>> java -cp $CP $JVM_ARGS $ARGS
>> )
>>
>>
>> On 30/11/2012, at 12:41 AM, "Leitch, Oblio" <Ob...@state.vt.us> wrote:
>>
>>> Yeah, that sounds like a plan. I see that Jetty's included in the stand-alone version. How would I get that started?
>>>
>>> -----Original Message-----
>>> From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
>>> Sent: Wednesday, November 28, 2012 7:00 PM
>>> To: users@archiva.apache.org
>>> Subject: Re: new user question
>>>
>>> Another option is to deploy the WAR into your application server of choice. Perhaps we should have a wrapper-less startup script to do that with Jetty...
>>>
>>> - Brett
>>
>> --
>> Brett Porter
>> brett@apache.org
>> http://brettporter.wordpress.com/
>> http://au.linkedin.com/in/brettporter
>> http://twitter.com/brettporter
>>
>>
>>
>>
>>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
RE: new user question
Posted by "Leitch, Oblio" <Ob...@state.vt.us>.
The ARGS line is missing a replace:
ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed 's/wrapper.app.parameter.[0-9]*=//' | sed "s#%ARCHIVA_BASE%#$ARCHIVA_BASE#" | tr '\n' ' '`
-----Original Message-----
From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
Sent: Thursday, November 29, 2012 6:32 PM
To: users@archiva.apache.org
Subject: Re: new user question
Sorry, replace CONTINUUM_BASE with ARCHIVA_BASE in this example - they both use the same appassembler generated config.
On 30/11/2012, at 10:30 AM, Brett Porter <br...@apache.org> wrote:
> One option is to get a stock jetty download, and copy across our configuration & application files - then you'll have all their scripts.
>
> Alternatively here's a quick and dirty start script you could use to pull the info from wrapper.conf which should keep working with new versions:
>
> #!/bin/sh
>
> set -e
>
> (
> cd `dirname $0`/..
> if [ -z "$CONTINUUM_BASE" ]; then
> CONTINUUM_BASE=.
> fi
>
> REPO_DIR=lib
> CP=`cat conf/wrapper.conf | grep ^wrapper.java.classpath.[0-9]*= | grep -v '.pom$' | sed 's/wrapper.java.classpath.[0-9]*=//' | sed "s#%REPO_DIR%#$REPO_DIR#" | tr '\n' ':' | sed 's/:$//'`
> ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed 's/wrapper.app.parameter.[0-9]*=//' | tr '\n' ' '`
> JVM_ARGS=`cat conf/wrapper.conf | egrep ^wrapper.java.additional.[0-9]*= | sed 's/wrapper.java.additional.[0-9]*=//' | sed "s#%CONTINUUM_BASE%#$CONTINUUM_BASE#" | tr '\n' ' '`
> JVM_MINMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.minmemory= | sed 's/wrapper.java.minmemory=//'`
> if [ ! -z "$JVM_MINMEM_ARG" ]; then
> JVM_ARGS="-Xms${JVM_MINMEM_ARG}m $JVM_ARGS"
> fi
> JVM_MAXMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.maxmemory= | sed 's/wrapper.java.maxmemory=//'`
> if [ ! -z "$JVM_MAXMEM_ARG" ]; then
> JVM_ARGS="-Xmx${JVM_MAXMEM_ARG}m $JVM_ARGS"
> fi
> java -cp $CP $JVM_ARGS $ARGS
> )
>
>
> On 30/11/2012, at 12:41 AM, "Leitch, Oblio" <Ob...@state.vt.us> wrote:
>
>> Yeah, that sounds like a plan. I see that Jetty's included in the stand-alone version. How would I get that started?
>>
>> -----Original Message-----
>> From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
>> Sent: Wednesday, November 28, 2012 7:00 PM
>> To: users@archiva.apache.org
>> Subject: Re: new user question
>>
>> Another option is to deploy the WAR into your application server of choice. Perhaps we should have a wrapper-less startup script to do that with Jetty...
>>
>> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
Re: new user question
Posted by Brett Porter <br...@apache.org>.
Sorry, replace CONTINUUM_BASE with ARCHIVA_BASE in this example - they both use the same appassembler generated config.
On 30/11/2012, at 10:30 AM, Brett Porter <br...@apache.org> wrote:
> One option is to get a stock jetty download, and copy across our configuration & application files - then you'll have all their scripts.
>
> Alternatively here's a quick and dirty start script you could use to pull the info from wrapper.conf which should keep working with new versions:
>
> #!/bin/sh
>
> set -e
>
> (
> cd `dirname $0`/..
> if [ -z "$CONTINUUM_BASE" ]; then
> CONTINUUM_BASE=.
> fi
>
> REPO_DIR=lib
> CP=`cat conf/wrapper.conf | grep ^wrapper.java.classpath.[0-9]*= | grep -v '.pom$' | sed 's/wrapper.java.classpath.[0-9]*=//' | sed "s#%REPO_DIR%#$REPO_DIR#" | tr '\n' ':' | sed 's/:$//'`
> ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed 's/wrapper.app.parameter.[0-9]*=//' | tr '\n' ' '`
> JVM_ARGS=`cat conf/wrapper.conf | egrep ^wrapper.java.additional.[0-9]*= | sed 's/wrapper.java.additional.[0-9]*=//' | sed "s#%CONTINUUM_BASE%#$CONTINUUM_BASE#" | tr '\n' ' '`
> JVM_MINMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.minmemory= | sed 's/wrapper.java.minmemory=//'`
> if [ ! -z "$JVM_MINMEM_ARG" ]; then
> JVM_ARGS="-Xms${JVM_MINMEM_ARG}m $JVM_ARGS"
> fi
> JVM_MAXMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.maxmemory= | sed 's/wrapper.java.maxmemory=//'`
> if [ ! -z "$JVM_MAXMEM_ARG" ]; then
> JVM_ARGS="-Xmx${JVM_MAXMEM_ARG}m $JVM_ARGS"
> fi
> java -cp $CP $JVM_ARGS $ARGS
> )
>
>
> On 30/11/2012, at 12:41 AM, "Leitch, Oblio" <Ob...@state.vt.us> wrote:
>
>> Yeah, that sounds like a plan. I see that Jetty's included in the stand-alone version. How would I get that started?
>>
>> -----Original Message-----
>> From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
>> Sent: Wednesday, November 28, 2012 7:00 PM
>> To: users@archiva.apache.org
>> Subject: Re: new user question
>>
>> Another option is to deploy the WAR into your application server of choice. Perhaps we should have a wrapper-less startup script to do that with Jetty...
>>
>> - Brett
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
> http://au.linkedin.com/in/brettporter
> http://twitter.com/brettporter
>
>
>
>
>
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
Re: new user question
Posted by Brett Porter <br...@apache.org>.
One option is to get a stock jetty download, and copy across our configuration & application files - then you'll have all their scripts.
Alternatively here's a quick and dirty start script you could use to pull the info from wrapper.conf which should keep working with new versions:
#!/bin/sh
set -e
(
cd `dirname $0`/..
if [ -z "$CONTINUUM_BASE" ]; then
CONTINUUM_BASE=.
fi
REPO_DIR=lib
CP=`cat conf/wrapper.conf | grep ^wrapper.java.classpath.[0-9]*= | grep -v '.pom$' | sed 's/wrapper.java.classpath.[0-9]*=//' | sed "s#%REPO_DIR%#$REPO_DIR#" | tr '\n' ':' | sed 's/:$//'`
ARGS=`cat conf/wrapper.conf | grep ^wrapper.app.parameter.[0-9]*= | sed 's/wrapper.app.parameter.[0-9]*=//' | tr '\n' ' '`
JVM_ARGS=`cat conf/wrapper.conf | egrep ^wrapper.java.additional.[0-9]*= | sed 's/wrapper.java.additional.[0-9]*=//' | sed "s#%CONTINUUM_BASE%#$CONTINUUM_BASE#" | tr '\n' ' '`
JVM_MINMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.minmemory= | sed 's/wrapper.java.minmemory=//'`
if [ ! -z "$JVM_MINMEM_ARG" ]; then
JVM_ARGS="-Xms${JVM_MINMEM_ARG}m $JVM_ARGS"
fi
JVM_MAXMEM_ARG=`cat conf/wrapper.conf | egrep ^wrapper.java.maxmemory= | sed 's/wrapper.java.maxmemory=//'`
if [ ! -z "$JVM_MAXMEM_ARG" ]; then
JVM_ARGS="-Xmx${JVM_MAXMEM_ARG}m $JVM_ARGS"
fi
java -cp $CP $JVM_ARGS $ARGS
)
On 30/11/2012, at 12:41 AM, "Leitch, Oblio" <Ob...@state.vt.us> wrote:
> Yeah, that sounds like a plan. I see that Jetty's included in the stand-alone version. How would I get that started?
>
> -----Original Message-----
> From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
> Sent: Wednesday, November 28, 2012 7:00 PM
> To: users@archiva.apache.org
> Subject: Re: new user question
>
> Another option is to deploy the WAR into your application server of choice. Perhaps we should have a wrapper-less startup script to do that with Jetty...
>
> - Brett
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
RE: new user question
Posted by "Leitch, Oblio" <Ob...@state.vt.us>.
Yeah, that sounds like a plan. I see that Jetty's included in the stand-alone version. How would I get that started?
-----Original Message-----
From: Brett Porter [mailto:brett@porterclan.net] On Behalf Of Brett Porter
Sent: Wednesday, November 28, 2012 7:00 PM
To: users@archiva.apache.org
Subject: Re: new user question
Another option is to deploy the WAR into your application server of choice. Perhaps we should have a wrapper-less startup script to do that with Jetty...
- Brett
Re: new user question
Posted by Brett Porter <br...@apache.org>.
Another option is to deploy the WAR into your application server of choice. Perhaps we should have a wrapper-less startup script to do that with Jetty...
- Brett
On 29/11/2012, at 10:24 AM, Olivier Lamy <ol...@apache.org> wrote:
> 2012/11/28 Leitch, Oblio <Ob...@state.vt.us>:
>> I'm trying to get Archiva setup on our dev box. I've unzipped the files and chmod +x'd the bin/archiva file. However, when I run it, I get
>> Unable to locate any of the following operational binaries:
>> /var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper-linux-power6(architected),altivecsupported-64
>> /var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper-linux-power6(architected),altivecsupported-32
>> /var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper
>>
>> Maybe I don't have the right version?
>>
>> Thanks,
>> Oblio
>
> doh it looks we don't support your architecture
>
> $ARCHIVA_HOME directory where archiva is installed/unzipped
>
> Try
> $ARCHIVA_HOME/bin/./wrapper-macosx-universal-32
> $ARCHIVA_HOME/conf/wrapper.conf wrapper.syslog.ident=archiva
> wrapper.pidfile=$ARCHIVA_HOME/logs/archiva.pid
>
> see archiva script
> line with # Resolve the architecture
> there is a probably something we could add here to save you :-)
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
--
Brett Porter
brett@apache.org
http://brettporter.wordpress.com/
http://au.linkedin.com/in/brettporter
http://twitter.com/brettporter
Re: new user question
Posted by Olivier Lamy <ol...@apache.org>.
2012/11/28 Leitch, Oblio <Ob...@state.vt.us>:
> I'm trying to get Archiva setup on our dev box. I've unzipped the files and chmod +x'd the bin/archiva file. However, when I run it, I get
> Unable to locate any of the following operational binaries:
> /var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper-linux-power6(architected),altivecsupported-64
> /var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper-linux-power6(architected),altivecsupported-32
> /var/archiva/apache-archiva-js-1.4-M3/bin/./wrapper
>
> Maybe I don't have the right version?
>
> Thanks,
> Oblio
doh it looks we don't support your architecture
$ARCHIVA_HOME directory where archiva is installed/unzipped
Try
$ARCHIVA_HOME/bin/./wrapper-macosx-universal-32
$ARCHIVA_HOME/conf/wrapper.conf wrapper.syslog.ident=archiva
wrapper.pidfile=$ARCHIVA_HOME/logs/archiva.pid
see archiva script
line with # Resolve the architecture
there is a probably something we could add here to save you :-)
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy