Service stuck and consuming disk space












0














What is the best practice to avoid this case
Example,



filebeat   5098  5128       root    3r      REG              253,1 31035908096     657022 /var/log/aaa/aaa.access.log.1 (deleted)


There is a logrotate to mv aaa.access.log file while processed by filebeat. nano and tail can be stucking a file but i am focusing on filebeat app.
What is the best practice to solve this permanently ?
Especially, filebeat app.










share|improve this question


















  • 1




    Since filebeat is long-running, you will likely need the copytruncate option offered by logrotate.
    – Haxiel
    2 days ago












  • @Haxiel i have 166 ansible scripts. Adding copytruncate to each file is not good idea. I know it works. But do you have other way to avoid that pls ?
    – Nicky Puff
    2 days ago






  • 2




    I'm not quite sure what you mean. The QA you've linked shows how to solve this manually by truncating the file. Since you're already using logrotate, copytruncate will do this automatically. What's missing here?
    – Haxiel
    2 days ago










  • @Haxiel nvm, got it mate
    – Nicky Puff
    2 days ago
















0














What is the best practice to avoid this case
Example,



filebeat   5098  5128       root    3r      REG              253,1 31035908096     657022 /var/log/aaa/aaa.access.log.1 (deleted)


There is a logrotate to mv aaa.access.log file while processed by filebeat. nano and tail can be stucking a file but i am focusing on filebeat app.
What is the best practice to solve this permanently ?
Especially, filebeat app.










share|improve this question


















  • 1




    Since filebeat is long-running, you will likely need the copytruncate option offered by logrotate.
    – Haxiel
    2 days ago












  • @Haxiel i have 166 ansible scripts. Adding copytruncate to each file is not good idea. I know it works. But do you have other way to avoid that pls ?
    – Nicky Puff
    2 days ago






  • 2




    I'm not quite sure what you mean. The QA you've linked shows how to solve this manually by truncating the file. Since you're already using logrotate, copytruncate will do this automatically. What's missing here?
    – Haxiel
    2 days ago










  • @Haxiel nvm, got it mate
    – Nicky Puff
    2 days ago














0












0








0







What is the best practice to avoid this case
Example,



filebeat   5098  5128       root    3r      REG              253,1 31035908096     657022 /var/log/aaa/aaa.access.log.1 (deleted)


There is a logrotate to mv aaa.access.log file while processed by filebeat. nano and tail can be stucking a file but i am focusing on filebeat app.
What is the best practice to solve this permanently ?
Especially, filebeat app.










share|improve this question













What is the best practice to avoid this case
Example,



filebeat   5098  5128       root    3r      REG              253,1 31035908096     657022 /var/log/aaa/aaa.access.log.1 (deleted)


There is a logrotate to mv aaa.access.log file while processed by filebeat. nano and tail can be stucking a file but i am focusing on filebeat app.
What is the best practice to solve this permanently ?
Especially, filebeat app.







logrotate lsof






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 days ago









Nicky PuffNicky Puff

154




154








  • 1




    Since filebeat is long-running, you will likely need the copytruncate option offered by logrotate.
    – Haxiel
    2 days ago












  • @Haxiel i have 166 ansible scripts. Adding copytruncate to each file is not good idea. I know it works. But do you have other way to avoid that pls ?
    – Nicky Puff
    2 days ago






  • 2




    I'm not quite sure what you mean. The QA you've linked shows how to solve this manually by truncating the file. Since you're already using logrotate, copytruncate will do this automatically. What's missing here?
    – Haxiel
    2 days ago










  • @Haxiel nvm, got it mate
    – Nicky Puff
    2 days ago














  • 1




    Since filebeat is long-running, you will likely need the copytruncate option offered by logrotate.
    – Haxiel
    2 days ago












  • @Haxiel i have 166 ansible scripts. Adding copytruncate to each file is not good idea. I know it works. But do you have other way to avoid that pls ?
    – Nicky Puff
    2 days ago






  • 2




    I'm not quite sure what you mean. The QA you've linked shows how to solve this manually by truncating the file. Since you're already using logrotate, copytruncate will do this automatically. What's missing here?
    – Haxiel
    2 days ago










  • @Haxiel nvm, got it mate
    – Nicky Puff
    2 days ago








1




1




Since filebeat is long-running, you will likely need the copytruncate option offered by logrotate.
– Haxiel
2 days ago






Since filebeat is long-running, you will likely need the copytruncate option offered by logrotate.
– Haxiel
2 days ago














@Haxiel i have 166 ansible scripts. Adding copytruncate to each file is not good idea. I know it works. But do you have other way to avoid that pls ?
– Nicky Puff
2 days ago




@Haxiel i have 166 ansible scripts. Adding copytruncate to each file is not good idea. I know it works. But do you have other way to avoid that pls ?
– Nicky Puff
2 days ago




2




2




I'm not quite sure what you mean. The QA you've linked shows how to solve this manually by truncating the file. Since you're already using logrotate, copytruncate will do this automatically. What's missing here?
– Haxiel
2 days ago




I'm not quite sure what you mean. The QA you've linked shows how to solve this manually by truncating the file. Since you're already using logrotate, copytruncate will do this automatically. What's missing here?
– Haxiel
2 days ago












@Haxiel nvm, got it mate
– Nicky Puff
2 days ago




@Haxiel nvm, got it mate
– Nicky Puff
2 days ago










0






active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492940%2fservice-stuck-and-consuming-disk-space%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes
















draft saved

draft discarded




















































Thanks for contributing an answer to Unix & Linux Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.





Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


Please pay close attention to the following guidance:


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f492940%2fservice-stuck-and-consuming-disk-space%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

How to make a Squid Proxy server?

第一次世界大戦

Touch on Surface Book