[
https://issues.apache.org/jira/browse/JENA-2239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17468623#comment-17468623
]
Andy Seaborne commented on JENA-2239:
-------------------------------------
Thanks [~andr...@kth.se] -- yes, these are the logging output if
log4j2.properties isn't found. Placing a copy where you run `fuseki-server`
I'm not a mac user but there something about that script that looks odd - some
of it is relate to the war file. e.g FUSEKI_LOGS and var/"log/fuseki"
The fuseki-server script of 4.3.2 should run better when it has no
log4j2.properties but it (the fuseki-server script) mishandles the setup. (This
is not mac related - happens on Linux). Recorded as JENA-2240
Workaround: run with the LOGGING environment variable to some spaces (one or
more):
{noformat}
env LOGGING=" " ./fuseki-server --mem /ds
{noformat}
It should then look like:
{noformat}
2022-01-04 13:10:37] Server INFO Apache Jena Fuseki 4.3.2
[2022-01-04 13:10:37] Config INFO FUSEKI_HOME=/home/afs/tmp/Fuseki/.
[2022-01-04 13:10:37] Config INFO FUSEKI_BASE=/home/afs/tmp/Fuseki/run
[2022-01-04 13:10:37] Config INFO Shiro file:
file:///home/afs/tmp/Fuseki/run/shiro.ini
[2022-01-04 13:10:38] Config INFO Template file: templates/config-mem
[2022-01-04 13:10:38] Server INFO Database: in-memory
[2022-01-04 13:10:38] Server INFO Path = /ds
[2022-01-04 13:10:38] Server INFO System
[2022-01-04 13:10:38] Server INFO Memory: 4.0 GiB
[2022-01-04 13:10:38] Server INFO Java: 17.0.1
[2022-01-04 13:10:38] Server INFO OS: Linux 5.13.0-22-generic amd64
[2022-01-04 13:10:38] Server INFO PID: 117624
[2022-01-04 13:10:38] Server INFO Started 2022/01/04 13:10:38 GMT on port
3030
[2022-01-04 13:11:20] Fuseki INFO [1] GET
http://localhost:3030/ds?query=ASK%7B%7D
[2022-01-04 13:11:20] Fuseki INFO [1] Query = ASK{}
[2022-01-04 13:11:20] Fuseki INFO [1] 200 OK (17 ms)
. . .
{noformat}
> fuseki-server does not show logs upon startup
> ---------------------------------------------
>
> Key: JENA-2239
> URL: https://issues.apache.org/jira/browse/JENA-2239
> Project: Apache Jena
> Issue Type: Bug
> Components: Fuseki
> Affects Versions: Jena 4.3.2
> Environment: OS: macOS Big Sur version 11.6
> Java: openjdk 11.0.10 2021-01-19
> Reporter: Kelvin Qian
> Priority: Minor
>
> h3. Current Behavior
> When executing the `fuseki-server` command, e.g.:
> {code:java}
> fuseki-server --mem /ds{code}
> the following message appears:
> {code:java}
> ERROR StatusLogger Reconfiguration failed: No configuration found for
> '42110406' at 'null' in 'null'{code}
> The server itself still works as normal, but that fact is not obvious given
> the error message, and it is very annoying to not have the visual
> confirmation of logging.
> h3. Expected Behavior
> In contrast, version 4.2.0 did had logging output upon startup without any
> special configuration, i.e. _this_ is what _should_ output upon startup:
> {code:java}
> 14:37:14 INFO Server :: jetty-10.0.6; built: 2021-06-29T15:28:56.259Z;
> git: 37e7731b4b142a882d73974ff3bec78d621bd674; jvm 17+0
> 14:37:14 INFO StandardDescriptorProcessor :: NO JSP Support for /, did not
> find org.eclipse.jetty.jsp.JettyJspServlet
> 14:37:14 INFO DefaultSessionIdManager :: Session workerName=node0
> 14:37:14 INFO org_apache_jena_fuseki_Servlet :: Initializing Shiro
> environment
> 14:37:14 INFO EnvironmentLoader :: Starting Shiro environment initialization.
> 14:37:14 WARN IniRealm :: Users or Roles are already populated.
> Configured Ini instance will be ignored.
> 14:37:14 INFO EnvironmentLoader :: Shiro environment initialized in 159 ms.
> 14:37:15 INFO ContextHandler :: Started
> o.e.j.w.WebAppContext@1c3259fa{Apache Jena Fuseki
> Server,/,file:///usr/local/Cellar/fuseki/4.2.0/libexec/webapp/,AVAILABLE}
> 14:37:15 INFO AbstractConnector :: Started
> ServerConnector@4152d38d{HTTP/1.1, (http/1.1)}{0.0.0.0:3030}
> 14:37:15 INFO Server :: Started Server@2d8f2f3a{STARTING}[10.0.6,sto=0]
> @2266ms{code}
> h3. Additional Notes
> Fuseki was installed via Homebrew using the command
> {code:java}
> brew install fuseki{code}
> I was able to have this issue be replicated my coworker's machine as well
> (which is also a Mac that is running Java 11+), indicating that this issue is
> likely not unique to this environment.
> I tested this both without a log4j2.properties file in the current directory
> and with one, using the sample file from this webpage:
> [https://howtodoinjava.com/log4j2/log4j2-properties-example/.|https://howtodoinjava.com/log4j2/log4j2-properties-example/]
> In both cases, the error message appears.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
