neutron-server and keystone start to write logs into wrong file
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Invalid
|
Medium
|
Fuel Library (Deprecated) | ||
6.0.x |
Won't Fix
|
High
|
MOS Maintenance | ||
6.1.x |
Fix Released
|
Critical
|
Alexey Stupnikov | ||
7.0.x |
Invalid
|
High
|
Alexey Stupnikov | ||
8.0.x |
Invalid
|
Medium
|
Fuel Library (Deprecated) |
Bug Description
Fuel 6.0, neutron+vlan, ceph, Ubuntu
neutron-server and keystone start to write logs into wrong file
When Customer try to free space on disk he erase some .log files from /var/log/upstart folder on controller nodes.
After it neutron-server, neutron-dhcp, keystone services start to write logs into neutron-
Due to absence of the .log files, fuel-logrotate does not rotate .log.1 files and Customer reach full disk problem - cluster become inoperable.
Workaround:
For any logs into /var/log/upstart folder check that *.log file exist and services put data into it.
If the file do not exist or not using by related service (service can write logs onto *.log.1 file) please make next steps:
1 ensure that you have enough free space for log rotation
2 create fake log file with size more than 100M (let it be 120M and for example glance-api.log into /var/log/upstart folder)
fallocate -l 120M /var/log/
3 wait untill fuel-logrotate will be triggered by crone and fake log file will be rotated (glance-api.log -> glance-api.log.1, and system 4 will create new glance-api.log and start to put data there)
4 remove rotated fake log to free disk space (for example rm -f /var/log/
5 proceed with another log
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
summary: |
- neutron-server and keystone start to wright logs into wrong file + neutron-server and keystone start to write logs into wrong file |
description: | updated |
Changed in fuel: | |
milestone: | none → 6.0-updates |
importance: | Undecided → Medium |
tags: | added: area-library |
tags: | added: ct1 |
Changed in fuel: | |
status: | Confirmed → Invalid |
tags: | added: on-verification |
High due to customer-found