karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Frédérik ROULEAU (JIRA) <j...@apache.org>
Subject [jira] [Commented] (KARAF-4690) Karaf client fails to load if not able to write to $KARAF_DATA/tmp
Date Mon, 19 Sep 2016 15:56:21 GMT

    [ https://issues.apache.org/jira/browse/KARAF-4690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15503843#comment-15503843

Frédérik ROULEAU commented on KARAF-4690:

This is caused by jansi upgrade implied by jline upgrade.
jansi tries to unjar a dynamic library into tmp dir. If the directory does not exist, init
Moving the tmp dir to system's tmp may also lead to problem as on common production system,
that directory is mounted with noexec flag, preventing also jansi to load its native library.

> Karaf client fails to load if not able to write to $KARAF_DATA/tmp
> ------------------------------------------------------------------
>                 Key: KARAF-4690
>                 URL: https://issues.apache.org/jira/browse/KARAF-4690
>             Project: Karaf
>          Issue Type: Bug
>          Components: karaf-core
>    Affects Versions: 4.0.6
>         Environment: Linux
>            Reporter: Adrian Baker
> Running the Karaf client seems to result in an attempted write to the $KARAF_DATA/tmp
directory (see https://github.com/fusesource/hawtjni/issues/27). If this fails, the client
won't load.
> {code}
> [vagrant@localhost data]$ /opt/karaf/bin/client
> Logging in as karaf
> 391 [sshd-SshClient[4445629]-nio2-thread-2] WARN org.apache.sshd.client.keyverifier.AcceptAllServerKeyVerifier
- Server at / presented unverified RSA key: 49:03:6e:ad:91:7d:c2:11:cb:86:84:73:b2:9e:e9:4b
> Could not load library. Reasons: [no jansi in java.library.path, Permission denied]
> {code}
> This write will fail if the user running the client script doesn't have write permission
to this directory, which occurs if you've installed karaf as one user, then use another user
to invoke the client script.
> I wonder if the standard default tmp directory is more appropriate for the client process.
> This appears to be a change from 4.0.4 -> 4.0.6.

This message was sent by Atlassian JIRA

View raw message