karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Caspar MacRae (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (KARAF-230) 2.1.0 Wrapper doesn't work and if hacked no SSH
Date Mon, 27 Sep 2010 23:56:33 GMT

     [ https://issues.apache.org/jira/browse/KARAF-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Caspar MacRae resolved KARAF-230.
---------------------------------

    Fix Version/s: 2.1.0
       Resolution: Not A Problem

Not an issue with release, provided configured correctly.

> 2.1.0 Wrapper doesn't work and if hacked no SSH
> -----------------------------------------------
>
>                 Key: KARAF-230
>                 URL: https://issues.apache.org/jira/browse/KARAF-230
>             Project: Karaf
>          Issue Type: Bug
>    Affects Versions: 2.1.0
>         Environment: Ubuntu x86_64
>            Reporter: Caspar MacRae
>             Fix For: 2.1.0
>
>
> I had the same issue in 2.0.0.
> wget http://www.mirrorservice.org/sites/ftp.apache.org//karaf/2.1.0/apache-karaf-2.1.0.tar.gz
> tar -xvzf apache-karaf-2.1.0.tar.gz 
> cd apache-karaf-2.1.0/
> JAVA_HOME=/usr/lib/jvm/java-6-sun/ && export JAVA_HOME
> ./bin/karaf 
> karaf> features:install wrapper
> karaf> wrapper:install 
> karaf> shutdown
> ./bin/karaf-service start    ## Note, no variation of paths works
> Error message:  "542: /srv/gather/karaf/bin/karaf-wrapper: not found"
> The workaround isn't hard (download and replace relevant files from http://wrapper.tanukisoftware.com),
but it is a somewhat pointless endeavour as I cannot then access it via SSH (but can access
via SSH when just running the bin/karaf script)
> I followed these links for adding and bootstapping bouncycastle:
> http://fusesource.com/forums/thread.jspa?messageID=7395
> http://felix.apache.org/site/65-deploying-security-providers.html
> But still no joy wrt wrapper and SSH.
> I'm using the karaf instance as an ActiveMQ (blueprint) broker host, with camel-quartz
and it is setup with a failover instance using simple file lock (all working fine without
exception)

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message