This is yet more puzzlement about a large and almost-completely-undocumented Perl application I'm working on.
There's a cron-like process which runs constantly, polling for jobs. When it gets a job, it instantiates one of various modules (depending on the job type) and runs some processes.
My current puzzle is this. In some of the modules, to figure out what's happening, I can put pretty crude logging along the lines of:
use Data::Dumper; open(LOG,'>>','/some/log/file.log') or die "can't log"; print LOG 'Some object: ' . Dumper($some_object); close(LOG);
I'm aware this is far from ideal but it should work, right?
But in some of the modules, when I add this, I get no output at all. It doesn't die, it doesn't fail, the operation concludes. In others it works and I get output. There's definitely nothing wrong with the logfile, its location and permissions etc. all allow it to be written to.
The modules which apparently can't do output are mostly ones to do with an API which fetches JSON from AWS.
Where can I start looking to figure out why this would be?
In reply to Why can't some of my modules do log output to a file? by LittleJack
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |