Hello,
Does anybody have a suggestion why, for Servoy 2024.3.2 on a Linux server, the servoy_log.txt is created but is not updated? It stays at 0B.
tomcat user has R and W rights on the file.
I think it is something in the war because an older 2022.3.5 instance updates it’s corresponding servoy_log.txt, but i don’t know where to look.
I don’t have much Linux experience, any suggestion is appreciated.
Thank you,
You should get the tomcat logs in /var/log/tomcat9/catalina.out do you see any messages there that relate to the logging?
If you build the war, do you set the ServoyHome directory correctly? You can set this in the export, either in the exporter or via the parameter “-userHomeDirectory”.
Alternatively you can set the ServoyHome in the Tomcat-Startup in /usr/share/tomcat9/bin/setenv.sh:
export CATALINA_OPTS="$CATALINA_OPTS -XX:+UseG1GC"
export CATALINA_OPTS="$CATALINA_OPTS -XX:+DisableExplicitGC"
[...]
export CATALINA_OPTS="$CATALINA_OPTS -DSERVOY_USER_HOME=/home/ServoyHome"
Tomcat runs without this file, so it’s not necessarily there, you should look where the tomcat on your system (lbs_release -a tells you what distribution you are running) expects this file and create/edit it there.
But for starters, check your war export and the catalina.out for more information, that’s the faster route.
Hi Robert,
Thank you for your suggestions.
In catalina.out i see no errors or warnings, just an info which i understand typically appears during Tomcat startup and can be safely ignored:
org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs.
Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them.
Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
in the war the ServoyHome directory is:
servoy.user.home=/var/lib/tomcat9/tomcat_home
Which I assume is correct because it creates the file:
/var/lib/tomcat9/tomcat_home/.servoy/server/myInstance/servoy_log.txt
just not updates it.
An upgrade to Java 21.0.2+13-Ubuntu-122.04.1 did not fix it…