Thanks, Andy, you were right, it was an open file issue (even after fuseki exited). lsof shows
rsyslogd 1075 root 8w REG 253,0 7727536209 409179840 /var/log/fuseki/stderrout.7.log (deleted) in:imjour 1075 1481 root 8w REG 253,0 7727536209 409179840 /var/log/fuseki/stderrout.7.log (deleted) rs:main 1075 1495 root 8w REG 253,0 7727536209 409179840 /var/log/fuseki/stderrout.7.log (deleted) so rsyslogd held a link to the renamed and then gzipped file. As it turned out, the reason for that were the remains of an unsuccessful attempt to manage the log with rsyslogd some years ago. These removed, it works straightforward as you described it. I'll give the log4j appenders a try for management. Thank you again for the helpful hints! Cheers, Joachim > -----Ursprüngliche Nachricht----- > Von: Andy Seaborne [mailto:[email protected]] > Gesendet: Dienstag, 19. Oktober 2021 17:39 > An: [email protected] > Betreff: Re: gziped stderrout.log not started anew > > Hi Joachim, > > When you say "stopped" do you the server is not running or only paused? > > The usual script sends output to a file that is created by the shell. > > If the server is paused, and continued, the file is still open but no > longer accessible from the filesystem. > > If it exited and restarted, I don't why the file isn't there because the > script does "&> stderrout.log". > > Fuseki uses log4j2 - If you want e.g. a rolling file appender, that the > place to set it up. It looks for log4j2.properties in the server current > working directory before using the built-in settings. > > Also - the situation happens with regular Tomcat so advice (inc > StackOverflow) applies. > > Andy > > > On 19/10/2021 13:51, Neubert, Joachim wrote: > > When, with a stopped Fuseki, I gzip and rename the stderrout.log file, it is > not created anew with the next fuseki start. > > > > When I create an empty stderrout.log manually, and make it belong to > fuseki:fuseki, the file remains empty, while apparently the log entries are > written to the system log (journalctl - CentOs 7.9, SElinux disabled). > > > > Does anybody know how to get Fuseki/Jetty to accept the newly created log > file? (and perhaps, how this can happen in the first place?) > > > > Help is much appreciated! > > > > Cheers, Joachim > > -- > > Joachim Neubert > > > > ZBW - Leibniz Information Centre for Economics > > Neuer Jungfernstieg 21 > > 20354 Hamburg > > Phone +49-40-42834-462 > > > >
