Post

Replies

Boosts

Views

Activity

iTMSTransporter 3.3.0 Linux failing on start with "com.apple.transporter.launcher.util.FileUtil.logger" is null
I am running the iTMS Transporter on a OL7 k8s pod. The issue appeared when I have set the read-only filesystem. Trace: Exception in thread "main" java.lang.ExceptionInInitializerError at com.apple.transporter.launcher.Application.start(Application.java:120) at com.apple.transporter.launcher.Application.main(Application.java:766) Caused by: java.lang.NullPointerException: Cannot invoke "com.apple.transporter.launcher.api.LaunchLogger.warn(String)" because "com.apple.transporter.launcher.util.FileUtil.logger" is null at com.apple.transporter.launcher.util.FileUtil.logWarning(FileUtil.java:151) at com.apple.transporter.launcher.util.FileUtil.userHomeDirectory(FileUtil.java:110) at com.apple.transporter.launcher.util.FileUtil.localConfigHome0(FileUtil.java:188) at com.apple.transporter.launcher.util.FileUtil.(FileUtil.java:25) ... 2 more I have to have the pod filesystem read-only it is a security compliance requirement, so I need to find a solution for this issue. Before setting the the FS to read-only everything was working perfectly. Apparently iTMS Transporter lost access to some locations on the pod. What folders should be accessible (writable) got the iTMS Transporter?
0
0
212
Oct ’24