accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Resolved] (ACCUMULO-3952) bin/accumulo should verify log4j.jar was found
Date Wed, 05 Aug 2015 16:40:04 GMT


Josh Elser resolved ACCUMULO-3952.
    Resolution: Fixed

Apologies for the extra commits. I forgot to add this to 1.6 and 1.7 before pushing.

1.6 does *not* contain the extra check against {{CLASSPATH}} because the support (that was
apparently sneakily added in ACCUMULO-3685) does not exist in that branch. 1.7 and 1.8 contain
the fix as outlined.

Regarding the slf4j, I misspoke previously. We pull these jars from our installation directly,
not from elsewhere, so I did not have to add a check for them (someone goofed up the tarball
if they don't exist).

> bin/accumulo should verify log4j.jar was found
> ----------------------------------------------
>                 Key: ACCUMULO-3952
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: scripts
>    Affects Versions: 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.7.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>             Fix For: 1.6.4, 1.7.1, 1.8.0
>          Time Spent: 40m
>  Remaining Estimate: 0h
> Just spent a few hours trying to wrangle this one down. Ambari was failing to start all
Accumulo components. After digging in, I realized that when Ambari was invoking {{accumulo}},
it was failing to find the log4j jar.
> It turns out this was a deployment issue where the home directory for the {{accumulo}}
user was never created and the find command failed:
> {noformat}
> find: cannot stat current directory: Permission denied
> {noformat}
> Sadly, I couldn't find this error until I manually edited the accumulo script to remove
the {{2>/dev/null}} redirect. We should have been able to realize that we never found the
log4j jar and then clearly printed an error and exited instead of leading me on a goosechase
by silently proceeding.
> Same goes for the slf4j jars.

This message was sent by Atlassian JIRA

View raw message