I'm seeing some errors from apache2 that look like:
(36)File name too long: [client <redacted>] AH00036: access to /short/path?really=long&query=string failed (filesystem path '/srv/my-site/short/path?really=long&query=string')
Why is apache including the query string in the filesystem path, and how do I get it to stop doing that?
My apache2 service has PrivateTmp=true. When the service first starts it works fine, but after a few days, writing to /tmp fails with "no such file or directory". To debug I've tried running nsenter -t <apache-pid> -m bash and I've confirmed that /tmp exists, but mkdir /tmp/test fails with "no such file or directory". I'd rather not remove the PrivateTmp=true directive.
If I restart the service it starts working again.
The mount line for /tmp inside says it is mounted to /dev/nvme0n1 which seems odd to me, but that is the case both when /tmp is working immediately after starting the service and when it is not writable.
Anyone know why /tmp suddenly becomes unwritable?
I need to schedule a command to run at a certain time in the future. systemd-run with the --on-calendar option seems like it can do that, except that it seems the service is only stored ephemerally and is lost if the host reboots. And in this case the host will certainly reboot before I need to the command to run.
I know I could manually write service and timer files, but that is a little less convenient than using systemd-run for a one-off task, and I need to go back and clean up the service files aftewards. Is there a way to tell systemd-run to persist the job across reboots?