'inode table usage' spiking every morning at 8amInode tables sharply decrease without reasonDetermine...
What can I do if someone tampers with my SSH public key?
Unfamiliar notation in Diabelli's "Duet in D" for piano
Draw this image in the TIKZ package
Sort array by month and year
What the error in writing this equation by latex?
A vote on the Brexit backstop
Does an unused member variable take up memory?
What is the purpose of a disclaimer like "this is not legal advice"?
Too soon for a plot twist?
Why is there an extra space when I type "ls" on the Desktop?
Is "cogitate" used appropriately in "I cogitate that success relies on hard work"?
Can I negotiate a patent idea for a raise, under French law?
Should we avoid writing fiction about historical events without extensive research?
Unidentified signals on FT8 frequencies
Insult for someone who "doesn't know anything"
What does "rhumatis" mean?
Why does a car's steering wheel get lighter with increasing speed
I am the light that shines in the dark
What is the best index strategy or query SELECT when performing a search/lookup BETWEEN IP address (IPv4 and IPv6) ranges?
Precision notation for voltmeters
After Brexit, will the EU recognize British passports that are valid for more than ten years?
How strong is the axiom of well-ordered choice?
Help! My Character is too much for her story!
School performs periodic password audits. Is my password compromised?
'inode table usage' spiking every morning at 8am
Inode tables sharply decrease without reasonDetermine Location of Inode Usagedirtied inodeLinux: Why change inode size?What does it mean if inode usage is high?How to debug inode usageCan someone explain the “use-cases” for the default munin graphs?Inode tables sharply decrease without reasonWhat is INODE usage and can I reduce it?Remove orphaned Inode (LVM) without unmount or restartUnderstanding XFS inode limits
I installed munin on my ubuntu server. It's showing my 'inode table usage' spiking every morning at 8am. It then rapidly curves down and settles over the course of several hours. What might cause this?
I thought it might be something running in /etc/cron.daily but this was set to run at 6a.m. and I've changed it to 4am. The spike remains at 8am. I also enabled cron logging, but can't see anything getting launched at 8a.m.
It's a virtual server hosted by memset. Could it be caused by something happening on the virtual host?
munin inode
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
add a comment |
I installed munin on my ubuntu server. It's showing my 'inode table usage' spiking every morning at 8am. It then rapidly curves down and settles over the course of several hours. What might cause this?
I thought it might be something running in /etc/cron.daily but this was set to run at 6a.m. and I've changed it to 4am. The spike remains at 8am. I also enabled cron logging, but can't see anything getting launched at 8a.m.
It's a virtual server hosted by memset. Could it be caused by something happening on the virtual host?
munin inode
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
add a comment |
I installed munin on my ubuntu server. It's showing my 'inode table usage' spiking every morning at 8am. It then rapidly curves down and settles over the course of several hours. What might cause this?
I thought it might be something running in /etc/cron.daily but this was set to run at 6a.m. and I've changed it to 4am. The spike remains at 8am. I also enabled cron logging, but can't see anything getting launched at 8a.m.
It's a virtual server hosted by memset. Could it be caused by something happening on the virtual host?
munin inode
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
I installed munin on my ubuntu server. It's showing my 'inode table usage' spiking every morning at 8am. It then rapidly curves down and settles over the course of several hours. What might cause this?
I thought it might be something running in /etc/cron.daily but this was set to run at 6a.m. and I've changed it to 4am. The spike remains at 8am. I also enabled cron logging, but can't see anything getting launched at 8a.m.
It's a virtual server hosted by memset. Could it be caused by something happening on the virtual host?
munin inode
munin inode
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
edited Nov 16 '11 at 17:17
Harry Wood
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
asked Nov 14 '11 at 12:09
Harry WoodHarry Wood
22129
22129
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
On a default ubuntu/debian set-up, some things will run via 'anacron'. The timing of this can depend on a number of factors, particularly when the machine started up, but on a server machine it will trigger at 7:30 a.m. every morning by default.
This is configured in the file /etc/cron.d/anacron , so a simple solution is to edit that file and and set the configured time to something more convenient (e.g. middle of the night if you are concerned about the tasks impacting day time performance) There is no need to restart anything.
The cron log which I enabled, was in fact showing the initiation of anacron at 7:30. Anacron delays for a little while before doing anything and also presumably queued up several jobs, the result being that one job was starting up at about 8a.m. each day and causing a lot of inode table usage (people have suggested the mlocate db re-index) I don't know that it was causing any performance problems, but it seems healthier now to see it doing this in the middle of the night.
There is some brief documentation specific to ubuntu here: https://help.ubuntu.com/community/CronHowto#How_Anacron_is_Set_Up
...and much more detailed explanation of the interplay between cron and anacron here:
https://linuxformat.com//tuxradarchive/content/automate-linux-cron-and-anacron
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
add a comment |
Look for cronjobs running at about that time. In Ubuntu check the files in /etc/cron.daily first, as well as root's crontab ("sudo crontab -l"). Most likely it is something like log rotation, or log analysis that is creating many temporary file.
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
1
Or trying logging in at 8am, and runningtop:-)
– nickgrim
Nov 15 '11 at 11:21
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "2"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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%2fserverfault.com%2fquestions%2f330728%2finode-table-usage-spiking-every-morning-at-8am%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
On a default ubuntu/debian set-up, some things will run via 'anacron'. The timing of this can depend on a number of factors, particularly when the machine started up, but on a server machine it will trigger at 7:30 a.m. every morning by default.
This is configured in the file /etc/cron.d/anacron , so a simple solution is to edit that file and and set the configured time to something more convenient (e.g. middle of the night if you are concerned about the tasks impacting day time performance) There is no need to restart anything.
The cron log which I enabled, was in fact showing the initiation of anacron at 7:30. Anacron delays for a little while before doing anything and also presumably queued up several jobs, the result being that one job was starting up at about 8a.m. each day and causing a lot of inode table usage (people have suggested the mlocate db re-index) I don't know that it was causing any performance problems, but it seems healthier now to see it doing this in the middle of the night.
There is some brief documentation specific to ubuntu here: https://help.ubuntu.com/community/CronHowto#How_Anacron_is_Set_Up
...and much more detailed explanation of the interplay between cron and anacron here:
https://linuxformat.com//tuxradarchive/content/automate-linux-cron-and-anacron
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
add a comment |
On a default ubuntu/debian set-up, some things will run via 'anacron'. The timing of this can depend on a number of factors, particularly when the machine started up, but on a server machine it will trigger at 7:30 a.m. every morning by default.
This is configured in the file /etc/cron.d/anacron , so a simple solution is to edit that file and and set the configured time to something more convenient (e.g. middle of the night if you are concerned about the tasks impacting day time performance) There is no need to restart anything.
The cron log which I enabled, was in fact showing the initiation of anacron at 7:30. Anacron delays for a little while before doing anything and also presumably queued up several jobs, the result being that one job was starting up at about 8a.m. each day and causing a lot of inode table usage (people have suggested the mlocate db re-index) I don't know that it was causing any performance problems, but it seems healthier now to see it doing this in the middle of the night.
There is some brief documentation specific to ubuntu here: https://help.ubuntu.com/community/CronHowto#How_Anacron_is_Set_Up
...and much more detailed explanation of the interplay between cron and anacron here:
https://linuxformat.com//tuxradarchive/content/automate-linux-cron-and-anacron
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
add a comment |
On a default ubuntu/debian set-up, some things will run via 'anacron'. The timing of this can depend on a number of factors, particularly when the machine started up, but on a server machine it will trigger at 7:30 a.m. every morning by default.
This is configured in the file /etc/cron.d/anacron , so a simple solution is to edit that file and and set the configured time to something more convenient (e.g. middle of the night if you are concerned about the tasks impacting day time performance) There is no need to restart anything.
The cron log which I enabled, was in fact showing the initiation of anacron at 7:30. Anacron delays for a little while before doing anything and also presumably queued up several jobs, the result being that one job was starting up at about 8a.m. each day and causing a lot of inode table usage (people have suggested the mlocate db re-index) I don't know that it was causing any performance problems, but it seems healthier now to see it doing this in the middle of the night.
There is some brief documentation specific to ubuntu here: https://help.ubuntu.com/community/CronHowto#How_Anacron_is_Set_Up
...and much more detailed explanation of the interplay between cron and anacron here:
https://linuxformat.com//tuxradarchive/content/automate-linux-cron-and-anacron
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
On a default ubuntu/debian set-up, some things will run via 'anacron'. The timing of this can depend on a number of factors, particularly when the machine started up, but on a server machine it will trigger at 7:30 a.m. every morning by default.
This is configured in the file /etc/cron.d/anacron , so a simple solution is to edit that file and and set the configured time to something more convenient (e.g. middle of the night if you are concerned about the tasks impacting day time performance) There is no need to restart anything.
The cron log which I enabled, was in fact showing the initiation of anacron at 7:30. Anacron delays for a little while before doing anything and also presumably queued up several jobs, the result being that one job was starting up at about 8a.m. each day and causing a lot of inode table usage (people have suggested the mlocate db re-index) I don't know that it was causing any performance problems, but it seems healthier now to see it doing this in the middle of the night.
There is some brief documentation specific to ubuntu here: https://help.ubuntu.com/community/CronHowto#How_Anacron_is_Set_Up
...and much more detailed explanation of the interplay between cron and anacron here:
https://linuxformat.com//tuxradarchive/content/automate-linux-cron-and-anacron
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
edited 3 mins ago
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
answered Nov 23 '11 at 9:45
Harry WoodHarry Wood
22129
22129
add a comment |
add a comment |
Look for cronjobs running at about that time. In Ubuntu check the files in /etc/cron.daily first, as well as root's crontab ("sudo crontab -l"). Most likely it is something like log rotation, or log analysis that is creating many temporary file.
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
1
Or trying logging in at 8am, and runningtop:-)
– nickgrim
Nov 15 '11 at 11:21
add a comment |
Look for cronjobs running at about that time. In Ubuntu check the files in /etc/cron.daily first, as well as root's crontab ("sudo crontab -l"). Most likely it is something like log rotation, or log analysis that is creating many temporary file.
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
1
Or trying logging in at 8am, and runningtop:-)
– nickgrim
Nov 15 '11 at 11:21
add a comment |
Look for cronjobs running at about that time. In Ubuntu check the files in /etc/cron.daily first, as well as root's crontab ("sudo crontab -l"). Most likely it is something like log rotation, or log analysis that is creating many temporary file.
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
Look for cronjobs running at about that time. In Ubuntu check the files in /etc/cron.daily first, as well as root's crontab ("sudo crontab -l"). Most likely it is something like log rotation, or log analysis that is creating many temporary file.
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
answered Nov 14 '11 at 12:29
mfarvermfarver
2,4761016
2,4761016
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
1
Or trying logging in at 8am, and runningtop:-)
– nickgrim
Nov 15 '11 at 11:21
add a comment |
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
1
Or trying logging in at 8am, and runningtop:-)
– nickgrim
Nov 15 '11 at 11:21
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
It certainly looks like something scheduled, but I can't see anything in the root or my user crontab. I even tried this bash script: stackoverflow.com/questions/134906/… to check if there was some cron stuff I was missing. Any other schedule mechanisms I could check (beyond cron) ? I wondered about postgres autovacuum, but I think that's more regular than daily
– Harry Wood
Nov 14 '11 at 13:21
1
1
Or trying logging in at 8am, and running
top :-)– nickgrim
Nov 15 '11 at 11:21
Or trying logging in at 8am, and running
top :-)– nickgrim
Nov 15 '11 at 11:21
add a comment |
Thanks for contributing an answer to Server Fault!
- 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%2fserverfault.com%2fquestions%2f330728%2finode-table-usage-spiking-every-morning-at-8am%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
