radosgw doesn't start a new log on SIGHUP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
High
|
MOS Ceph | ||
5.1.x |
Invalid
|
High
|
MOS Maintenance | ||
6.0.x |
Invalid
|
High
|
MOS Maintenance | ||
6.1.x |
Invalid
|
High
|
MOS Maintenance | ||
7.0.x |
Invalid
|
High
|
MOS Ceph |
Bug Description
Hi,
radosgw service doesn't produce a new log after logrotation. After investigation I found that SIGHUP doesn't work proplerly. The issue is present on CentOS (Ubuntu is not affected). Here is a way how to reproduce
root@node-1:~# lsof -p `pgrep radosgw` | grep ceph-client.
radosgw 19420 root 3w REG 252,0 45554 146958 /var/log/
As you can see file is present. Ok. let's delete it. that's what usually logrotate does
root@node-1:~# lsof -p `pgrep radosgw` | grep ceph-client.
radosgw 19420 root 3w REG 252,0 120611 146958 /var/log/
file has been marked as deleted. Ok. let's send a SIGHUP
root@node-1:~# lsof -p `pgrep radosgw` | grep ceph-client.
as we can see radosgw didn't start writing logs to a new file
Changed in fuel: | |
importance: | Undecided → High |
assignee: | nobody → MOS Linux (mos-linux) |
milestone: | none → 6.1 |
Changed in fuel: | |
status: | Invalid → Confirmed |
tags: | added: customer-found |
no longer affects: | fuel/6.0.x |
no longer affects: | fuel/5.1.x |
no longer affects: | fuel/5.0.x |
tags: | added: known-issue |
radosgw works from root user in Ubuntu, while it uses apache under CentOS - which has no rights to write to /var/log/radosgw folder.