Daemon.log/Syslog files getting spamed with DHCP Information
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a linux VPS that's been running fine for 5 months now, up until about a few days ago. I get weekly reports on my server, and on the 03/01/2016, I had used 4gb of space, with 16gb free (20gb total). Yesterday I got a report saying I had used 20gb, with 0gb free.
I have not even made a change on my VPS since 24/12/2015, I've been too busy with work.
My syslog file is getting spammed with:
Jan 13 08:41:08 web01 ifup[354]: /sbin/dhclient-script: 28: .: Can't open /usr/share/sendmail/dynamic
Jan 13 08:41:08 web01 dhclient: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 ifup[354]: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 dhclient: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: RTNETLINK answers: File exists
Last night I cleared it, checked it this morning and it has: 1,084,162,664 lines of this repeated, about 4 times every second.
My daemon.log file is getting spammed with the exact same code, the same amount of times, so both files are 1 billion lines long, which is using 9gb so far, and its slowly climbing.
I have no issues SSHing onto the server, my website still works fine, webmin works, so it's not dropping the internet.
I have talked to my VPS customer support and they claim:
"Thanks for your inquiry. It looks like it's your VPS which is sending the DHCPDECLINE, not our DHCP server."
I have not made any changes in 3 weeks, and the only changes that have made within the last 2 weeks are when the VPS host restarted my VPS due to errors on my node.
I'd run some commands to get some stats for you guys, or configs, but I have no clue what to run :( I'm a total noob.
Any idea what could be causing this? Googling didn't help at all :(
networking server dhcp debian
add a comment |
I have a linux VPS that's been running fine for 5 months now, up until about a few days ago. I get weekly reports on my server, and on the 03/01/2016, I had used 4gb of space, with 16gb free (20gb total). Yesterday I got a report saying I had used 20gb, with 0gb free.
I have not even made a change on my VPS since 24/12/2015, I've been too busy with work.
My syslog file is getting spammed with:
Jan 13 08:41:08 web01 ifup[354]: /sbin/dhclient-script: 28: .: Can't open /usr/share/sendmail/dynamic
Jan 13 08:41:08 web01 dhclient: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 ifup[354]: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 dhclient: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: RTNETLINK answers: File exists
Last night I cleared it, checked it this morning and it has: 1,084,162,664 lines of this repeated, about 4 times every second.
My daemon.log file is getting spammed with the exact same code, the same amount of times, so both files are 1 billion lines long, which is using 9gb so far, and its slowly climbing.
I have no issues SSHing onto the server, my website still works fine, webmin works, so it's not dropping the internet.
I have talked to my VPS customer support and they claim:
"Thanks for your inquiry. It looks like it's your VPS which is sending the DHCPDECLINE, not our DHCP server."
I have not made any changes in 3 weeks, and the only changes that have made within the last 2 weeks are when the VPS host restarted my VPS due to errors on my node.
I'd run some commands to get some stats for you guys, or configs, but I have no clue what to run :( I'm a total noob.
Any idea what could be causing this? Googling didn't help at all :(
networking server dhcp debian
add a comment |
I have a linux VPS that's been running fine for 5 months now, up until about a few days ago. I get weekly reports on my server, and on the 03/01/2016, I had used 4gb of space, with 16gb free (20gb total). Yesterday I got a report saying I had used 20gb, with 0gb free.
I have not even made a change on my VPS since 24/12/2015, I've been too busy with work.
My syslog file is getting spammed with:
Jan 13 08:41:08 web01 ifup[354]: /sbin/dhclient-script: 28: .: Can't open /usr/share/sendmail/dynamic
Jan 13 08:41:08 web01 dhclient: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 ifup[354]: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 dhclient: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: RTNETLINK answers: File exists
Last night I cleared it, checked it this morning and it has: 1,084,162,664 lines of this repeated, about 4 times every second.
My daemon.log file is getting spammed with the exact same code, the same amount of times, so both files are 1 billion lines long, which is using 9gb so far, and its slowly climbing.
I have no issues SSHing onto the server, my website still works fine, webmin works, so it's not dropping the internet.
I have talked to my VPS customer support and they claim:
"Thanks for your inquiry. It looks like it's your VPS which is sending the DHCPDECLINE, not our DHCP server."
I have not made any changes in 3 weeks, and the only changes that have made within the last 2 weeks are when the VPS host restarted my VPS due to errors on my node.
I'd run some commands to get some stats for you guys, or configs, but I have no clue what to run :( I'm a total noob.
Any idea what could be causing this? Googling didn't help at all :(
networking server dhcp debian
I have a linux VPS that's been running fine for 5 months now, up until about a few days ago. I get weekly reports on my server, and on the 03/01/2016, I had used 4gb of space, with 16gb free (20gb total). Yesterday I got a report saying I had used 20gb, with 0gb free.
I have not even made a change on my VPS since 24/12/2015, I've been too busy with work.
My syslog file is getting spammed with:
Jan 13 08:41:08 web01 ifup[354]: /sbin/dhclient-script: 28: .: Can't open /usr/share/sendmail/dynamic
Jan 13 08:41:08 web01 dhclient: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 ifup[354]: DHCPDECLINE on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Jan 13 08:41:08 web01 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 dhclient: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Jan 13 08:41:08 web01 ifup[354]: DHCPOFFER from 169.254.169.254
Jan 13 08:41:08 web01 dhclient: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: DHCPACK from 169.254.169.254
Jan 13 08:41:08 web01 ifup[354]: RTNETLINK answers: File exists
Last night I cleared it, checked it this morning and it has: 1,084,162,664 lines of this repeated, about 4 times every second.
My daemon.log file is getting spammed with the exact same code, the same amount of times, so both files are 1 billion lines long, which is using 9gb so far, and its slowly climbing.
I have no issues SSHing onto the server, my website still works fine, webmin works, so it's not dropping the internet.
I have talked to my VPS customer support and they claim:
"Thanks for your inquiry. It looks like it's your VPS which is sending the DHCPDECLINE, not our DHCP server."
I have not made any changes in 3 weeks, and the only changes that have made within the last 2 weeks are when the VPS host restarted my VPS due to errors on my node.
I'd run some commands to get some stats for you guys, or configs, but I have no clue what to run :( I'm a total noob.
Any idea what could be causing this? Googling didn't help at all :(
networking server dhcp debian
networking server dhcp debian
asked Jan 12 '16 at 23:41
Joel MaleJoel Male
113
113
add a comment |
add a comment |
3 Answers
3
active
oldest
votes
For any future readers that have come here by google search:
I had the same problem. It seems to be caused by the script /etc/dhcp/dhclient-exit-hooks.d/sendmail
, that tries to access a file /usr/share/sendmail/dynamic
that may not exist, causing an error and apparently an endless restart-loop of dhclient.
In my case, upon removal of the sendmail package apt seems to have neglected to cleanup the /etc/dhcp/dhclient-exit-hooks.d/sendmail
script.
So either rm /etc/dhcp/dhclient-exit-hooks.d/sendmail
or mkdir -p /usr/share/sendmail && touch /usr/share/sendmail/dynamic
, may fix it for you (depending on if you want to keep sendmail or not).
edit: credits go to luchonacho for finding the cause, just wanted to add some clarification
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This not a best practis, usesudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
add a comment |
Had the same problem on a RaspberryPi. Been messing with it for hours. Found a few tidbits in my logs, suggesting that sendmail was somehow mixed up in the problem, and then finally found this post.
I ended up doing a "sudo apt-get purge sendmail*" and that finally fixed it.
add a comment |
If the solution is to cleanly purge sendmail, you might need to remove other sendmail packages as so:
$ sudo apt-get purge sendmail sendmail-base sendmail-bin
or
$ sudo apt-get purge sendmail*
Then you can try to switch on your interface again:
$ sudo ifup interface-name
sendmail related error messages should have disappeared.
If you still need sendmail
you can reinstall by:
$ sudo apt-get install sendmail sendmail-base sendmail-bin
$ sudo sendmailconfig
$ # you can say yes to all the questions and restart your http server
$ sudo service apache2 restart
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
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%2faskubuntu.com%2fquestions%2f720412%2fdaemon-log-syslog-files-getting-spamed-with-dhcp-information%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
For any future readers that have come here by google search:
I had the same problem. It seems to be caused by the script /etc/dhcp/dhclient-exit-hooks.d/sendmail
, that tries to access a file /usr/share/sendmail/dynamic
that may not exist, causing an error and apparently an endless restart-loop of dhclient.
In my case, upon removal of the sendmail package apt seems to have neglected to cleanup the /etc/dhcp/dhclient-exit-hooks.d/sendmail
script.
So either rm /etc/dhcp/dhclient-exit-hooks.d/sendmail
or mkdir -p /usr/share/sendmail && touch /usr/share/sendmail/dynamic
, may fix it for you (depending on if you want to keep sendmail or not).
edit: credits go to luchonacho for finding the cause, just wanted to add some clarification
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This not a best practis, usesudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
add a comment |
For any future readers that have come here by google search:
I had the same problem. It seems to be caused by the script /etc/dhcp/dhclient-exit-hooks.d/sendmail
, that tries to access a file /usr/share/sendmail/dynamic
that may not exist, causing an error and apparently an endless restart-loop of dhclient.
In my case, upon removal of the sendmail package apt seems to have neglected to cleanup the /etc/dhcp/dhclient-exit-hooks.d/sendmail
script.
So either rm /etc/dhcp/dhclient-exit-hooks.d/sendmail
or mkdir -p /usr/share/sendmail && touch /usr/share/sendmail/dynamic
, may fix it for you (depending on if you want to keep sendmail or not).
edit: credits go to luchonacho for finding the cause, just wanted to add some clarification
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This not a best practis, usesudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
add a comment |
For any future readers that have come here by google search:
I had the same problem. It seems to be caused by the script /etc/dhcp/dhclient-exit-hooks.d/sendmail
, that tries to access a file /usr/share/sendmail/dynamic
that may not exist, causing an error and apparently an endless restart-loop of dhclient.
In my case, upon removal of the sendmail package apt seems to have neglected to cleanup the /etc/dhcp/dhclient-exit-hooks.d/sendmail
script.
So either rm /etc/dhcp/dhclient-exit-hooks.d/sendmail
or mkdir -p /usr/share/sendmail && touch /usr/share/sendmail/dynamic
, may fix it for you (depending on if you want to keep sendmail or not).
edit: credits go to luchonacho for finding the cause, just wanted to add some clarification
For any future readers that have come here by google search:
I had the same problem. It seems to be caused by the script /etc/dhcp/dhclient-exit-hooks.d/sendmail
, that tries to access a file /usr/share/sendmail/dynamic
that may not exist, causing an error and apparently an endless restart-loop of dhclient.
In my case, upon removal of the sendmail package apt seems to have neglected to cleanup the /etc/dhcp/dhclient-exit-hooks.d/sendmail
script.
So either rm /etc/dhcp/dhclient-exit-hooks.d/sendmail
or mkdir -p /usr/share/sendmail && touch /usr/share/sendmail/dynamic
, may fix it for you (depending on if you want to keep sendmail or not).
edit: credits go to luchonacho for finding the cause, just wanted to add some clarification
edited Aug 16 '16 at 13:30
answered Aug 16 '16 at 13:19
Victor ClaessenVictor Claessen
7913
7913
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This not a best practis, usesudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
add a comment |
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This not a best practis, usesudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
Thank you so much, this is exactly an issue I had with one of our google virtual machines
– unc0nnected
Nov 14 '17 at 0:42
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This really saved us a lot of headache!!! Thank you so much!!!
– cbloss793
Jan 18 '18 at 22:00
This not a best practis, use
sudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
This not a best practis, use
sudo apt purge sendmail*
– zatamine
Oct 29 '18 at 20:19
add a comment |
Had the same problem on a RaspberryPi. Been messing with it for hours. Found a few tidbits in my logs, suggesting that sendmail was somehow mixed up in the problem, and then finally found this post.
I ended up doing a "sudo apt-get purge sendmail*" and that finally fixed it.
add a comment |
Had the same problem on a RaspberryPi. Been messing with it for hours. Found a few tidbits in my logs, suggesting that sendmail was somehow mixed up in the problem, and then finally found this post.
I ended up doing a "sudo apt-get purge sendmail*" and that finally fixed it.
add a comment |
Had the same problem on a RaspberryPi. Been messing with it for hours. Found a few tidbits in my logs, suggesting that sendmail was somehow mixed up in the problem, and then finally found this post.
I ended up doing a "sudo apt-get purge sendmail*" and that finally fixed it.
Had the same problem on a RaspberryPi. Been messing with it for hours. Found a few tidbits in my logs, suggesting that sendmail was somehow mixed up in the problem, and then finally found this post.
I ended up doing a "sudo apt-get purge sendmail*" and that finally fixed it.
answered Apr 4 '18 at 4:34
DeadTOmDeadTOm
211
211
add a comment |
add a comment |
If the solution is to cleanly purge sendmail, you might need to remove other sendmail packages as so:
$ sudo apt-get purge sendmail sendmail-base sendmail-bin
or
$ sudo apt-get purge sendmail*
Then you can try to switch on your interface again:
$ sudo ifup interface-name
sendmail related error messages should have disappeared.
If you still need sendmail
you can reinstall by:
$ sudo apt-get install sendmail sendmail-base sendmail-bin
$ sudo sendmailconfig
$ # you can say yes to all the questions and restart your http server
$ sudo service apache2 restart
add a comment |
If the solution is to cleanly purge sendmail, you might need to remove other sendmail packages as so:
$ sudo apt-get purge sendmail sendmail-base sendmail-bin
or
$ sudo apt-get purge sendmail*
Then you can try to switch on your interface again:
$ sudo ifup interface-name
sendmail related error messages should have disappeared.
If you still need sendmail
you can reinstall by:
$ sudo apt-get install sendmail sendmail-base sendmail-bin
$ sudo sendmailconfig
$ # you can say yes to all the questions and restart your http server
$ sudo service apache2 restart
add a comment |
If the solution is to cleanly purge sendmail, you might need to remove other sendmail packages as so:
$ sudo apt-get purge sendmail sendmail-base sendmail-bin
or
$ sudo apt-get purge sendmail*
Then you can try to switch on your interface again:
$ sudo ifup interface-name
sendmail related error messages should have disappeared.
If you still need sendmail
you can reinstall by:
$ sudo apt-get install sendmail sendmail-base sendmail-bin
$ sudo sendmailconfig
$ # you can say yes to all the questions and restart your http server
$ sudo service apache2 restart
If the solution is to cleanly purge sendmail, you might need to remove other sendmail packages as so:
$ sudo apt-get purge sendmail sendmail-base sendmail-bin
or
$ sudo apt-get purge sendmail*
Then you can try to switch on your interface again:
$ sudo ifup interface-name
sendmail related error messages should have disappeared.
If you still need sendmail
you can reinstall by:
$ sudo apt-get install sendmail sendmail-base sendmail-bin
$ sudo sendmailconfig
$ # you can say yes to all the questions and restart your http server
$ sudo service apache2 restart
answered Feb 9 at 2:59
rellampecrellampec
33
33
add a comment |
add a comment |
Thanks for contributing an answer to Ask Ubuntu!
- 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%2faskubuntu.com%2fquestions%2f720412%2fdaemon-log-syslog-files-getting-spamed-with-dhcp-information%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