Hi, I’m building Collabora Online from source in a Docker container (Ubuntu 24.04) and encountered an issue where the compiled coolwsd binary gets deleted during the build process.
What happened:
make -j$(nproc)compilescoolwsdsuccessfully- During
setup-wsd, the Makefile runs:./coolwsd --cleanup || rm -f ./coolwsd - The cleanup command fails with error: “Null pointer: strategy”
- The binary gets deleted as a result
What I found:
The issue seems related to the logging configuration in coolwsd.xml.in:
<property name="rotation" desc="Log file rotation strategy. See Poco FileChannel.">never</property>
When rotation=never, Poco FileChannel appears to fail during initialization, causing the cleanup to fail.
My workaround:
I changed the rotation value to daily in coolwsd.xml.in:
<property name="rotation" desc="Log file rotation strategy. See Poco FileChannel.">daily</property>
After this change, cleanup succeeds and the binary is preserved.
My questions:
- Is
rotation=neversupposed to be a valid configuration value? - If not, should the default template use a different value?
- Is there a better way to handle this, or is my workaround the correct approach?
I’m new to Collabora development, so I’d appreciate any guidance. The Makefile’s cleanup mechanism (lines 534-540) seems designed to protect CI environments, but it’s confusing when a configuration issue triggers binary deletion.
Thanks for your help!