Fail2ban Debian 9, freeswitch
My server goes crazy with the CPU when I reload fail2ban
and sometimes mid day as well the CPU goes very high.
I remember a while ago I was told to switch to systemd
, any idea on how to do it?
fail2ban
add a comment |
My server goes crazy with the CPU when I reload fail2ban
and sometimes mid day as well the CPU goes very high.
I remember a while ago I was told to switch to systemd
, any idea on how to do it?
fail2ban
add a comment |
My server goes crazy with the CPU when I reload fail2ban
and sometimes mid day as well the CPU goes very high.
I remember a while ago I was told to switch to systemd
, any idea on how to do it?
fail2ban
My server goes crazy with the CPU when I reload fail2ban
and sometimes mid day as well the CPU goes very high.
I remember a while ago I was told to switch to systemd
, any idea on how to do it?
fail2ban
fail2ban
edited Dec 17 at 9:13
SouravGhosh
455311
455311
asked Dec 17 at 6:31
Moshe Rosen
1
1
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Most likely it is because of amount of data written to Freeswitch log. If you have lot of voip traffic, there will be lot of data written to log at high rate. Fail2ban has to scan all of that. Adjusting Freeswitch logging level to write less might help to reduce CPU usage. It will also improve IO performance.
When you restart fail2ban it rescans its database to load and block previously saved IP addresses. Most likely it is huge in your case. You can stop fail2ban and remove that database to speedup fail2ban startup. Use
fail2ban-client get dbfile
to find fail2ban database location.
add a comment |
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
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489411%2ffail2ban-debian-9-freeswitch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Most likely it is because of amount of data written to Freeswitch log. If you have lot of voip traffic, there will be lot of data written to log at high rate. Fail2ban has to scan all of that. Adjusting Freeswitch logging level to write less might help to reduce CPU usage. It will also improve IO performance.
When you restart fail2ban it rescans its database to load and block previously saved IP addresses. Most likely it is huge in your case. You can stop fail2ban and remove that database to speedup fail2ban startup. Use
fail2ban-client get dbfile
to find fail2ban database location.
add a comment |
Most likely it is because of amount of data written to Freeswitch log. If you have lot of voip traffic, there will be lot of data written to log at high rate. Fail2ban has to scan all of that. Adjusting Freeswitch logging level to write less might help to reduce CPU usage. It will also improve IO performance.
When you restart fail2ban it rescans its database to load and block previously saved IP addresses. Most likely it is huge in your case. You can stop fail2ban and remove that database to speedup fail2ban startup. Use
fail2ban-client get dbfile
to find fail2ban database location.
add a comment |
Most likely it is because of amount of data written to Freeswitch log. If you have lot of voip traffic, there will be lot of data written to log at high rate. Fail2ban has to scan all of that. Adjusting Freeswitch logging level to write less might help to reduce CPU usage. It will also improve IO performance.
When you restart fail2ban it rescans its database to load and block previously saved IP addresses. Most likely it is huge in your case. You can stop fail2ban and remove that database to speedup fail2ban startup. Use
fail2ban-client get dbfile
to find fail2ban database location.
Most likely it is because of amount of data written to Freeswitch log. If you have lot of voip traffic, there will be lot of data written to log at high rate. Fail2ban has to scan all of that. Adjusting Freeswitch logging level to write less might help to reduce CPU usage. It will also improve IO performance.
When you restart fail2ban it rescans its database to load and block previously saved IP addresses. Most likely it is huge in your case. You can stop fail2ban and remove that database to speedup fail2ban startup. Use
fail2ban-client get dbfile
to find fail2ban database location.
edited Dec 17 at 8:14
answered Dec 17 at 8:03
Nerijus Spl
212
212
add a comment |
add a comment |
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.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f489411%2ffail2ban-debian-9-freeswitch%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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