| 2016-09-22 18:26:12 |
Maksym Strukov |
bug |
|
|
added bug |
| 2016-09-22 18:28:13 |
Dmitry Sutyagin |
fuel: assignee |
|
Timmy Development Team (timmy-core) |
|
| 2016-09-22 18:44:36 |
Dmitry Sutyagin |
fuel: status |
New |
In Progress |
|
| 2016-09-23 08:25:46 |
Vitaly Sedelnik |
tags |
|
non-release |
|
| 2016-09-23 08:58:58 |
Dmitry Sutyagin |
fuel: status |
In Progress |
Fix Committed |
|
| 2016-09-23 09:33:39 |
Vitaly Sedelnik |
fuel: status |
Fix Committed |
In Progress |
|
| 2016-09-23 09:34:20 |
Vitaly Sedelnik |
tags |
non-release |
|
|
| 2016-09-23 09:34:39 |
Vitaly Sedelnik |
fuel: assignee |
Timmy Development Team (timmy-core) |
Maksym Strukov (unbelll) |
|
| 2016-09-23 09:34:46 |
Vitaly Sedelnik |
fuel: status |
In Progress |
Incomplete |
|
| 2016-09-23 09:37:43 |
Maksym Strukov |
description |
[root@fuel dump]# timmy --logs --days 3 --dest-file /var/dump/fuel-snapshot-2016-09-22_10-21-53/config.tar.gz --log-file /var/log/timmy.log
Initializing node data: done
Calculating logs size: done
Total logs size to collect before compression: 334176MB.
Compressed logs will take less space.
Log collection period: 3 days.
Checking free space: done
[root@fuel dump]# echo $?
0
[root@fuel dump]# ls fuel-snapshot-2016-09-22_10-21-53/
...
2016-09-22 18:13:07,356 INFO: nodes: is_enough_space(): logsize: 334291MB * 1.05, free space: 57770MB
2016-09-22 18:13:07,356 ERROR: nodes: is_enough_space(): Not enough space in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", logsize: 334291MB * 1.05, available: 57770MB. Decrease logs_size_coefficient config parameter (--logs-coeff CLI parameter) or free up space.
2016-09-22 18:13:07,356 ERROR: cli: main(): Not enough space for logs in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", exiting.
Environment:
[root@fuel dump]# timmy -V
1.20.3 |
Steps:
0. Master node /var partition should be small, to run into 'not enough space' when collecting logs. On my env /var has ~50gb free space, and log snapshot need ~334gb
1. cd /var/dump
2. fuel snapshot
Actual result:
Fuel create empty log snapshot:
[root@fuel dump]# fuel snapshot
Generating dump...
Downloading: http://10.20.0.2:8000/api/dump/fuel-snapshot-2016-09-22_10-21-53.tar Bytes: 10240
[==============================================================================]()
[root@fuel dump]# ls -hal
total 20K
drwxr-xr-x. 2 root root 4.0K Sep 22 10:22 .
drwxr-xr-x. 25 root root 4.0K Sep 21 13:47 ..
-rw-r--r--. 1 root root 10K Sep 22 10:22 fuel-snapshot-2016-09-22_10-21-53.tar
I re-run timmy directly with same command as Fuel did:
[root@fuel dump]# timmy --logs --days 3 --dest-file /var/dump/fuel-snapshot-2016-09-22_10-21-53/config.tar.gz --log-file /var/log/timmy.log
Initializing node data: done
Calculating logs size: done
Total logs size to collect before compression: 334176MB.
Compressed logs will take less space.
Log collection period: 3 days.
Checking free space: done
And checking exit code:
[root@fuel dump]# echo $?
0
[root@fuel dump]# ls fuel-snapshot-2016-09-22_10-21-53/
...
2016-09-22 18:13:07,356 INFO: nodes: is_enough_space(): logsize: 334291MB * 1.05, free space: 57770MB
2016-09-22 18:13:07,356 ERROR: nodes: is_enough_space(): Not enough space in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", logsize: 334291MB * 1.05, available: 57770MB. Decrease logs_size_coefficient config parameter (--logs-coeff CLI parameter) or free up space.
2016-09-22 18:13:07,356 ERROR: cli: main(): Not enough space for logs in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", exiting.
Root problem is that Timmy return exit code 0 when out of free space and can't gather logs.
Fuel receive timmy exit code == 0 and creating empty tar file which return to User.
Environment:
[root@fuel dump]# timmy -V
1.20.3 |
|
| 2016-09-23 09:54:55 |
Maksym Strukov |
description |
Steps:
0. Master node /var partition should be small, to run into 'not enough space' when collecting logs. On my env /var has ~50gb free space, and log snapshot need ~334gb
1. cd /var/dump
2. fuel snapshot
Actual result:
Fuel create empty log snapshot:
[root@fuel dump]# fuel snapshot
Generating dump...
Downloading: http://10.20.0.2:8000/api/dump/fuel-snapshot-2016-09-22_10-21-53.tar Bytes: 10240
[==============================================================================]()
[root@fuel dump]# ls -hal
total 20K
drwxr-xr-x. 2 root root 4.0K Sep 22 10:22 .
drwxr-xr-x. 25 root root 4.0K Sep 21 13:47 ..
-rw-r--r--. 1 root root 10K Sep 22 10:22 fuel-snapshot-2016-09-22_10-21-53.tar
I re-run timmy directly with same command as Fuel did:
[root@fuel dump]# timmy --logs --days 3 --dest-file /var/dump/fuel-snapshot-2016-09-22_10-21-53/config.tar.gz --log-file /var/log/timmy.log
Initializing node data: done
Calculating logs size: done
Total logs size to collect before compression: 334176MB.
Compressed logs will take less space.
Log collection period: 3 days.
Checking free space: done
And checking exit code:
[root@fuel dump]# echo $?
0
[root@fuel dump]# ls fuel-snapshot-2016-09-22_10-21-53/
...
2016-09-22 18:13:07,356 INFO: nodes: is_enough_space(): logsize: 334291MB * 1.05, free space: 57770MB
2016-09-22 18:13:07,356 ERROR: nodes: is_enough_space(): Not enough space in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", logsize: 334291MB * 1.05, available: 57770MB. Decrease logs_size_coefficient config parameter (--logs-coeff CLI parameter) or free up space.
2016-09-22 18:13:07,356 ERROR: cli: main(): Not enough space for logs in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", exiting.
Root problem is that Timmy return exit code 0 when out of free space and can't gather logs.
Fuel receive timmy exit code == 0 and creating empty tar file which return to User.
Environment:
[root@fuel dump]# timmy -V
1.20.3 |
Steps:
0. Master node /var partition should be small, to run into 'not enough space' when collecting logs. On my env /var has ~50gb free space, and log snapshot need ~334gb
1. cd /var/dump
2. fuel snapshot
Actual result:
Fuel create empty log snapshot:
[root@fuel dump]# fuel snapshot
Generating dump...
Downloading: http://10.20.0.2:8000/api/dump/fuel-snapshot-2016-09-22_10-21-53.tar Bytes: 10240
[==============================================================================]()
[root@fuel dump]# ls -hal
total 20K
drwxr-xr-x. 2 root root 4.0K Sep 22 10:22 .
drwxr-xr-x. 25 root root 4.0K Sep 21 13:47 ..
-rw-r--r--. 1 root root 10K Sep 22 10:22 fuel-snapshot-2016-09-22_10-21-53.tar
I re-run timmy directly with same command as Fuel did:
[root@fuel dump]# timmy --logs --days 3 --dest-file /var/dump/fuel-snapshot-2016-09-22_10-21-53/config.tar.gz --log-file /var/log/timmy.log
Initializing node data: done
Calculating logs size: done
Total logs size to collect before compression: 334176MB.
Compressed logs will take less space.
Log collection period: 3 days.
Checking free space: done
And checking exit code:
[root@fuel dump]# echo $?
0
[root@fuel dump]# ls fuel-snapshot-2016-09-22_10-21-53/
...
2016-09-22 18:13:07,356 INFO: nodes: is_enough_space(): logsize: 334291MB * 1.05, free space: 57770MB
2016-09-22 18:13:07,356 ERROR: nodes: is_enough_space(): Not enough space in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", logsize: 334291MB * 1.05, available: 57770MB. Decrease logs_size_coefficient config parameter (--logs-coeff CLI parameter) or free up space.
2016-09-22 18:13:07,356 ERROR: cli: main(): Not enough space for logs in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", exiting.
Root problem is that Timmy return exit code 0 when out of free space and can't gather logs.
Fuel receive timmy exit code == 0 and creating empty tar file which return to User.
By default /var partition allocate 40% from master node HDD size
Workaround:
None
Environment:
[root@fuel dump]# timmy -V
1.20.3
Master node has HDD 500 gb with /var partition 185 GB
Cluster has 200 nodes, deployed and lived more than 3 days |
|
| 2016-09-23 09:55:32 |
Maksym Strukov |
description |
Steps:
0. Master node /var partition should be small, to run into 'not enough space' when collecting logs. On my env /var has ~50gb free space, and log snapshot need ~334gb
1. cd /var/dump
2. fuel snapshot
Actual result:
Fuel create empty log snapshot:
[root@fuel dump]# fuel snapshot
Generating dump...
Downloading: http://10.20.0.2:8000/api/dump/fuel-snapshot-2016-09-22_10-21-53.tar Bytes: 10240
[==============================================================================]()
[root@fuel dump]# ls -hal
total 20K
drwxr-xr-x. 2 root root 4.0K Sep 22 10:22 .
drwxr-xr-x. 25 root root 4.0K Sep 21 13:47 ..
-rw-r--r--. 1 root root 10K Sep 22 10:22 fuel-snapshot-2016-09-22_10-21-53.tar
I re-run timmy directly with same command as Fuel did:
[root@fuel dump]# timmy --logs --days 3 --dest-file /var/dump/fuel-snapshot-2016-09-22_10-21-53/config.tar.gz --log-file /var/log/timmy.log
Initializing node data: done
Calculating logs size: done
Total logs size to collect before compression: 334176MB.
Compressed logs will take less space.
Log collection period: 3 days.
Checking free space: done
And checking exit code:
[root@fuel dump]# echo $?
0
[root@fuel dump]# ls fuel-snapshot-2016-09-22_10-21-53/
...
2016-09-22 18:13:07,356 INFO: nodes: is_enough_space(): logsize: 334291MB * 1.05, free space: 57770MB
2016-09-22 18:13:07,356 ERROR: nodes: is_enough_space(): Not enough space in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", logsize: 334291MB * 1.05, available: 57770MB. Decrease logs_size_coefficient config parameter (--logs-coeff CLI parameter) or free up space.
2016-09-22 18:13:07,356 ERROR: cli: main(): Not enough space for logs in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", exiting.
Root problem is that Timmy return exit code 0 when out of free space and can't gather logs.
Fuel receive timmy exit code == 0 and creating empty tar file which return to User.
By default /var partition allocate 40% from master node HDD size
Workaround:
None
Environment:
[root@fuel dump]# timmy -V
1.20.3
Master node has HDD 500 gb with /var partition 185 GB
Cluster has 200 nodes, deployed and lived more than 3 days |
Steps:
0. Master node /var partition should be small, to run into 'not enough space' when collecting logs. On my env /var has ~50gb free space, and log snapshot need ~334gb
1. cd /var/dump
2. fuel snapshot
Actual result:
Fuel create empty log snapshot:
[root@fuel dump]# fuel snapshot
Generating dump...
Downloading: http://10.20.0.2:8000/api/dump/fuel-snapshot-2016-09-22_10-21-53.tar Bytes: 10240
[==============================================================================]()
[root@fuel dump]# ls -hal
total 20K
drwxr-xr-x. 2 root root 4.0K Sep 22 10:22 .
drwxr-xr-x. 25 root root 4.0K Sep 21 13:47 ..
-rw-r--r--. 1 root root 10K Sep 22 10:22 fuel-snapshot-2016-09-22_10-21-53.tar
I re-run timmy directly with same command as Fuel did:
[root@fuel dump]# timmy --logs --days 3 --dest-file /var/dump/fuel-snapshot-2016-09-22_10-21-53/config.tar.gz --log-file /var/log/timmy.log
Initializing node data: done
Calculating logs size: done
Total logs size to collect before compression: 334176MB.
Compressed logs will take less space.
Log collection period: 3 days.
Checking free space: done
And checking exit code:
[root@fuel dump]# echo $?
0
[root@fuel dump]# ls fuel-snapshot-2016-09-22_10-21-53/
...
2016-09-22 18:13:07,356 INFO: nodes: is_enough_space(): logsize: 334291MB * 1.05, free space: 57770MB
2016-09-22 18:13:07,356 ERROR: nodes: is_enough_space(): Not enough space in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", logsize: 334291MB * 1.05, available: 57770MB. Decrease logs_size_coefficient config parameter (--logs-coeff CLI parameter) or free up space.
2016-09-22 18:13:07,356 ERROR: cli: main(): Not enough space for logs in "/var/dump/fuel-snapshot-2016-09-22_10-21-53", exiting.
Root problem is that Timmy return exit code 0 when out of free space and can't gather logs.
Fuel receive timmy exit code == 0 and creating empty tar file which return to User.
By default /var partition allocate 40% from master node HDD size
Workaround:
None
Environment:
[root@fuel dump]# timmy -V
1.20.3
Master node has HDD 500 gb with /var partition 185 GB
Cluster has 200 nodes, deployed more than 3 days ago |
|
| 2016-09-23 10:15:47 |
Maksym Strukov |
fuel: status |
Incomplete |
In Progress |
|
| 2016-09-23 10:16:00 |
Maksym Strukov |
fuel: assignee |
Maksym Strukov (unbelll) |
Timmy Development Team (timmy-core) |
|
| 2016-09-26 10:17:47 |
Vitaly Sedelnik |
fuel: milestone |
9.1 |
9.2 |
|
| 2016-12-13 19:49:00 |
Dmitry Sutyagin |
fuel: status |
In Progress |
Fix Released |
|
