Closed mbethke closed 8 years ago
Can you capture its output or does it fail silently?
Sorry, my bad: it boiled down to a permission problem in the config directory that I didn't know it needed to write to every time. It actually failed with "permission denied" but I'd been too thick to capture the output ...
I'm trying to run this as a message delivery agent from Icinga. Cut down a little, this is the script I'm running as a notification command:
When I set the variables and run it from an interactive shell, it works fine. It also works when running Icinga in the forground for debugging. However, it fails to do anything when running from a daemonized Icinga. However, it's not the controlling terminal alone that causes it to fail; as a non-interactive command via ssh it doesn't present any problem either.
I've tried various workarounds like running textsecure using
script
andunbuffer
to fake a terminal, trying to persuade bash it's interactive withset -m
, but to no avail. Sorry I don't have enough of a clue about Go to go hunting for the problem myself yet.