[Xymon] reopen_file: Cannot open new file: Permission denied

[J.C. Cleaver]

(Top posting due to encoding strangeness)

Hi Ian,

Unfortunately, the routine which calls this is used in a number of
different locations so it might be hard to track down w/o more detail.
Approximately what interval does the message occur on when you leave the
session open?

The bulk of the calls to this IIRC are dealing with log file output, and
usually involve reopening both stdout and stderr, so it's most likely log
related. Even in 4.3.17, xymonlaunch should be redirecting the stderr
output to a designated LOGFILE entry in tasks.cfg and/or clientlaunch.cfg;
I'd check either of those for any non-disabled tasks that don't have a
LOGFILE entry and add one in. That should either a) solve the problem, or
b) redirect the re-open error into an appropriate destination, since the
initial reopen is done by xymonlaunch prior to forking.


HTH,

-jc


On Wed, June 8, 2016 9:04 am, Ian Diddams wrote:
> When my xymon 4.3.17 server starts up, it runs fine and does irt job as
> expected...
> ... Â except that if I leave the session open that I started it on I see
> periodically this line repeated twice
>
> "reopen_file: Cannot open new file: Permission denied"
> I can;t work out what file it is trying to re-open and why therefore find
> out why its permissions are wrong.
> I've had a shufti at the ..../server  folder and nothing is leaping out
> as the "wrong" ownership ... Â what I do see is then
> ...../server/www/snap, Â ....server/wwww/rep have a group ownership of
> apache and everything below it is apache:apache but that is presumably
> tied up with the apache web server that presents xymon to the world so not
> likely to be it presumably.
>
> the only other place I thouht of was /var/logs/xymon but the user can
> create a new file OK in there.
>
> Anyone any pointers to where to start looking? Â or to start investigating
> further?