[
https://issues.apache.org/jira/browse/SLING-9780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17205421#comment-17205421
]
Hans-Peter Stoerr commented on SLING-9780:
------------------------------------------
Thank you for your prompt answer!
Very strange. This is only about system/console/logs - system/console/slinglog
works perfectly, as does the launcher/log/error.log . I tried it again on a
Linux machine with a Sling Starter built from the same commit as you, and still
I get in system/console/log a message "Log Service is not installed/running."
Compare the screenshot I'll attach.
{code}
> uname -a
Linux (XXX) 3.10.0-1062.18.1.el7.x86_64 #1 SMP Tue Mar 17 23:49:17 UTC 2020
x86_64 x86_64 x86_64 GNU/Linux
> java -version
openjdk version "11.0.6" 2020-01-14 LTS
OpenJDK Runtime Environment 18.9 (build 11.0.6+10-LTS)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.6+10-LTS, mixed mode, sharing)
> java -jar org.apache.sling.feature.launcher.jar -f feature-oak_tar.json -D
> org.osgi.service.http.port=12345 >& stdout.log
{code}
If I have a look at the org.apache.sling.commons.logservice bundle in the OSGI
Bundles listing, it's noticeable that there are no services exported from that
bundle - see the screenshot attached; I'll also attach a screenshot from
Starter version 11 with the 1.0.6 version, where you can see the LogService
exported.
Would it help if I attach the stdout.log and launcher/logs/error.log?
> Sling Starter 12: OSGI Log Service does not work properly
> ---------------------------------------------------------
>
> Key: SLING-9780
> URL: https://issues.apache.org/jira/browse/SLING-9780
> Project: Sling
> Issue Type: Bug
> Components: Starter
> Affects Versions: Starter 12
> Environment: Java 11 and 13 on MacOS
> Reporter: Hans-Peter Stoerr
> Priority: Minor
>
> In the current Sling Starter 12 snapshot the OSGI Log Service does not work
> properly. This has the effect that in the console at OSGI / Log Service
> [http://localhost:8080/system/console/logs] there is only the display "Log
> Service is not installed/running." and messages from OSGI (such as errors in
> activation methods) are inconveniently logged to stdout instead of the
> configured logfiles like error.log, which gave me some headache until I
> noticed that. :) Both the console plugin and the logging to error.log do
> work properly in version 11.
> This is in spite of the bundle org.apache.sling.commons.logservice being
> active. I tried downgrading it from the currently included 1.1.0 to 1.0.6,
> which works in the version 11 of the Sling Starter, but this doesn't help. So
> I guess it's some kind of configuration problem.
> Thanks so much for your amazing work!
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
