You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a developer I would like procserv log files to be reliably created with correct permissions / created with permissions that can't be seen as the file is locked.
On many instruments, particularly (but not exclusively) at the time of starting the IBEX server, the procserv log files can be created with invalid permissions. The symptoms are that:
Right click -> properties -> permissions is unable to show file permissions correctly
dir /q reports ... as the file owner rather than an actual username
The files are not readable by anyone (including admin)
Although this is happening on most instruments, it is not happening on dev or test machines. This ticket is to find a reliable way to reproduce the problem, ideally without an instrument machine, so that we can investigate/fix it.
Although this was noticed in the context of log rotation, it's actually a more general problem as it would prevent us from looking at these log files to diagnose a problem.
How & Where?
procServ is in EPICS-tools.
Reproducible (Yes/No)?
No: finding a way to reproduce this reliably is part of this issue.
Acceptance Criteria
Documented reliable way to trigger this issue
Either:
Issue fixed
or
Follow-up issue created & proposed to fix
How to Review
Check that you can reliably reproduce this issue.
planning 82:00 2024/10/31
The text was updated successfully, but these errors were encountered:
Tom-Willemsen
changed the title
ProcServ: reproduce issue with "bad" permissions
ProcServ: reproduce issue with "bad"/"locked" permissions
Oct 31, 2024
Issue Description
As a developer I would like procserv log files to be reliably created with correct permissions / created with permissions that can't be seen as the file is locked.
On many instruments, particularly (but not exclusively) at the time of starting the IBEX server, the procserv log files can be created with invalid permissions. The symptoms are that:
dir /q
reports...
as the file owner rather than an actual usernameAlthough this is happening on most instruments, it is not happening on dev or test machines. This ticket is to find a reliable way to reproduce the problem, ideally without an instrument machine, so that we can investigate/fix it.
Although this was noticed in the context of log rotation, it's actually a more general problem as it would prevent us from looking at these log files to diagnose a problem.
How & Where?
procServ is in
EPICS-tools
.Reproducible (Yes/No)?
No: finding a way to reproduce this reliably is part of this issue.
Acceptance Criteria
Either:
or
How to Review
Check that you can reliably reproduce this issue.
planning 82:00 2024/10/31
The text was updated successfully, but these errors were encountered: