rsyslog doesnt seem to write to log file, without restart after touch'ing the filersyslog not loggingRestart...
Why are Stein manifolds/spaces the analog of affine varieties/schemes in algebraic geometry?
Why didn't Thanos use the Time Stone to stop the Avengers' plan?
Are runways booked by airlines to land their planes?
Do photons bend spacetime or not?
Expected maximum number of unpaired socks
Gravitational Force Between Numbers
WordPress 5.2.1 deactivated my jQuery
Does French have the English "short i" vowel?
Why did the person in charge of a principality not just declare themself king?
Is it truly impossible to tell what a CPU is doing?
Is this statement about cut time correct?
Why haven't we yet tried accelerating a space station with people inside to a near light speed?
便利な工具 what does な means
How do I superimpose two math symbols?
Can I tell a prospective employee that everyone in the team is leaving?
Why isn't 'chemically-strengthened glass' made with potassium carbonate to begin with?
What Armor Optimization applies to a Mithral full plate?
Beginner looking to learn/master musical theory and instrumental ability. Where should I begin?
USPS Back Room - Trespassing?
Why did other houses not demand this?
Drums and punctuation
What is the use case for non-breathable waterproof pants?
Is superuser the same as root?
What are the conditions for RAA?
rsyslog doesnt seem to write to log file, without restart after touch'ing the file
rsyslog not loggingRestart rsyslog after NTP time syncHow to redirect logs to syslog for an application which doesn't support syslog yet?Rsyslog is losing messagesCron stopped logging to /var/log/cron.logrsyslog not forwarding messages to remote rsyslog serverrsyslog is still sending messages to omusrmsg even after using `stop` commandrsyslog filling up /var/log puts the system downSyslog forwarding to RsyslogWhat is causing my rsyslog timezone offset and / or time to be incorrect?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
I have a separate file for logging local7 facility, and this file is touched and
permissions set, from my installer. But sometimes I see that the logs are not being written to it (after I do a re-install) until I do rsyslog restart!
Is it mandatory to restart rsyslog if the log file is touched by another program/application ?
(since the installer is run as root, the
log file's time-stamp will be changed due to touch - will this cause rsyslog to not write to the log file ?)
rsyslog
asked Oct 8 '14 at 11:11
vyomvyom
143114
bumped to the homepage by Community♦ 25 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a separate file for logging local7 facility, and this file is touched and
permissions set, from my installer. But sometimes I see that the logs are not being written to it (after I do a re-install) until I do rsyslog restart!
Is it mandatory to restart rsyslog if the log file is touched by another program/application ?
(since the installer is run as root, the
log file's time-stamp will be changed due to touch - will this cause rsyslog to not write to the log file ?)
rsyslog
asked Oct 8 '14 at 11:11
vyomvyom
143114
bumped to the homepage by Community♦ 25 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have a separate file for logging local7 facility, and this file is touched and
permissions set, from my installer. But sometimes I see that the logs are not being written to it (after I do a re-install) until I do rsyslog restart!
Is it mandatory to restart rsyslog if the log file is touched by another program/application ?
(since the installer is run as root, the
log file's time-stamp will be changed due to touch - will this cause rsyslog to not write to the log file ?)
rsyslog
asked Oct 8 '14 at 11:11
vyomvyom
143114
I have a separate file for logging local7 facility, and this file is touched and
permissions set, from my installer. But sometimes I see that the logs are not being written to it (after I do a re-install) until I do rsyslog restart!
Is it mandatory to restart rsyslog if the log file is touched by another program/application ?
(since the installer is run as root, the
log file's time-stamp will be changed due to touch - will this cause rsyslog to not write to the log file ?)
rsyslog
rsyslog
asked Oct 8 '14 at 11:11
vyomvyom
143114
asked Oct 8 '14 at 11:11
vyomvyom
143114
edited Oct 8 '14 at 16:59
vyom
asked Oct 8 '14 at 11:11
vyomvyom
143114
asked Oct 8 '14 at 11:11
vyomvyom
143114
asked Oct 8 '14 at 11:11
vyomvyom
143114
143114
bumped to the homepage by Community♦ 25 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 25 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
rsyslogd has each log file open continuously for writing and it doesn't know that you've yanked the file out from under it. The file your installer removed is still on disk in an unlinked state and is still being written to. You can tell rsyslogd to reopen all log files by killall -HUP rsyslogd instead of doing a full restart.
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
my installer is not removing the file, its just doing atouch+chmod- for this too, do I need akill -HUP?
– vyom
Oct 8 '14 at 12:59
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
ok, I meanttouch, I have edited the question, to keep it simple, the installer always does atouch <file>and thenchmodon it. So, from your explanation I dont need aHUP, but somehow I see this issue that after an installation the logging not happening until I restartrsyslog!
– vyom
Oct 8 '14 at 17:00
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%2f160016%2frsyslog-doesnt-seem-to-write-to-log-file-without-restart-after-touching-the-fi%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
rsyslogd has each log file open continuously for writing and it doesn't know that you've yanked the file out from under it. The file your installer removed is still on disk in an unlinked state and is still being written to. You can tell rsyslogd to reopen all log files by killall -HUP rsyslogd instead of doing a full restart.
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
my installer is not removing the file, its just doing atouch+chmod- for this too, do I need akill -HUP?
– vyom
Oct 8 '14 at 12:59
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
ok, I meanttouch, I have edited the question, to keep it simple, the installer always does atouch <file>and thenchmodon it. So, from your explanation I dont need aHUP, but somehow I see this issue that after an installation the logging not happening until I restartrsyslog!
– vyom
Oct 8 '14 at 17:00
add a comment |
rsyslogd has each log file open continuously for writing and it doesn't know that you've yanked the file out from under it. The file your installer removed is still on disk in an unlinked state and is still being written to. You can tell rsyslogd to reopen all log files by killall -HUP rsyslogd instead of doing a full restart.
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
my installer is not removing the file, its just doing atouch+chmod- for this too, do I need akill -HUP?
– vyom
Oct 8 '14 at 12:59
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
ok, I meanttouch, I have edited the question, to keep it simple, the installer always does atouch <file>and thenchmodon it. So, from your explanation I dont need aHUP, but somehow I see this issue that after an installation the logging not happening until I restartrsyslog!
– vyom
Oct 8 '14 at 17:00
add a comment |
rsyslogd has each log file open continuously for writing and it doesn't know that you've yanked the file out from under it. The file your installer removed is still on disk in an unlinked state and is still being written to. You can tell rsyslogd to reopen all log files by killall -HUP rsyslogd instead of doing a full restart.
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
rsyslogd has each log file open continuously for writing and it doesn't know that you've yanked the file out from under it. The file your installer removed is still on disk in an unlinked state and is still being written to. You can tell rsyslogd to reopen all log files by killall -HUP rsyslogd instead of doing a full restart.
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
answered Oct 8 '14 at 12:32
doneal24doneal24
3,0441920
3,0441920
my installer is not removing the file, its just doing atouch+chmod- for this too, do I need akill -HUP?
– vyom
Oct 8 '14 at 12:59
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
ok, I meanttouch, I have edited the question, to keep it simple, the installer always does atouch <file>and thenchmodon it. So, from your explanation I dont need aHUP, but somehow I see this issue that after an installation the logging not happening until I restartrsyslog!
– vyom
Oct 8 '14 at 17:00
add a comment |
my installer is not removing the file, its just doing atouch+chmod- for this too, do I need akill -HUP?
– vyom
Oct 8 '14 at 12:59
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
ok, I meanttouch, I have edited the question, to keep it simple, the installer always does atouch <file>and thenchmodon it. So, from your explanation I dont need aHUP, but somehow I see this issue that after an installation the logging not happening until I restartrsyslog!
– vyom
Oct 8 '14 at 17:00
my installer is not removing the file, its just doing a
touch + chmod - for this too, do I need a kill -HUP ?– vyom
Oct 8 '14 at 12:59
my installer is not removing the file, its just doing a
touch + chmod - for this too, do I need a kill -HUP ?– vyom
Oct 8 '14 at 12:59
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
@vyom Your installer is creating a new file via touch according to your post. If you create a new file you will need to send a HUP to rsyslogd or restart it. If you are just changing a timestamp or permissions then you do not need to do anything.
– doneal24
Oct 8 '14 at 16:34
ok, I meant
touch, I have edited the question, to keep it simple, the installer always does a touch <file> and then chmod on it. So, from your explanation I dont need a HUP, but somehow I see this issue that after an installation the logging not happening until I restart rsyslog !– vyom
Oct 8 '14 at 17:00
ok, I meant
touch, I have edited the question, to keep it simple, the installer always does a touch <file> and then chmod on it. So, from your explanation I dont need a HUP, but somehow I see this issue that after an installation the logging not happening until I restart rsyslog !– vyom
Oct 8 '14 at 17:00
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.
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%2f160016%2frsyslog-doesnt-seem-to-write-to-log-file-without-restart-after-touching-the-fi%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
