Final Call ... XenServer Boot Media
-
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
XS rewrote the rsyslog.conf every time.
Ah, I never saw that mentioned and that means that you were addressing the wrong thing. You needed to stop it changing rsyslog.conf. What did you do to stop it from doing that?
Nothing. I followed the instructions in the above mentioned article.
If this article isn't for doing what you want, why expect it to do something different than it is intended to do?
I'm not.
I don't understand your question/comment.
Why were you following the instructions in that article? What was the end goal?
To prevent XS from logging locally when I have it set up to log externally.
But the files to do that were not yet modified, right? So we aren't up to step one yet. That's my point. There are config files that make this happen, but those were not changed. Only the ones that they change, were changed, but that won't do anything.
How was @BRRABill suppose to know that he's editing the wrong files? I guess it's called RTFM.
-
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
XS rewrote the rsyslog.conf every time.
Ah, I never saw that mentioned and that means that you were addressing the wrong thing. You needed to stop it changing rsyslog.conf. What did you do to stop it from doing that?
Nothing. I followed the instructions in the above mentioned article.
If this article isn't for doing what you want, why expect it to do something different than it is intended to do?
I'm not.
I don't understand your question/comment.
Why were you following the instructions in that article? What was the end goal?
To prevent XS from logging locally when I have it set up to log externally.
But the files to do that were not yet modified, right? So we aren't up to step one yet. That's my point. There are config files that make this happen, but those were not changed. Only the ones that they change, were changed, but that won't do anything.
Step one is to point XS loggin external. I did that.
Did you? Unless it was in the right file, you didn't. You tried to, but that's not the same as doing it.
Yes, I did.
This is accomplished by setting the external logging server in XenCenter.
Or are you saying THAT is incorrect?
Well, WAS it correct? DId it work through a reboot? Did you set it where you now know that you were supposed to or where you now know that it would not work?
To expand upon this - when you made the change to send to an external log server in the first file (the one that keeps getting overwritten) did those changes stay through a reboot? and after a reboot, were logs actually going to the external log server?
-
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
XS rewrote the rsyslog.conf every time.
Ah, I never saw that mentioned and that means that you were addressing the wrong thing. You needed to stop it changing rsyslog.conf. What did you do to stop it from doing that?
Nothing. I followed the instructions in the above mentioned article.
If this article isn't for doing what you want, why expect it to do something different than it is intended to do?
I'm not.
I don't understand your question/comment.
Why were you following the instructions in that article? What was the end goal?
To prevent XS from logging locally when I have it set up to log externally.
But the files to do that were not yet modified, right? So we aren't up to step one yet. That's my point. There are config files that make this happen, but those were not changed. Only the ones that they change, were changed, but that won't do anything.
How was @BRRABill suppose to know that he's editing the wrong files? I guess it's called RTFM.
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
What if he had just opened an editor and made his own file in /tmp/mychanges.txt and wrote in it "don't write logs locally?" That also would not work. But we might say "how was he supposed to know that he had to modify a specific file?"
It's clear that he tried and made a good guess. But it is also clear that the actual configuration was not done correctly and that the first step has to be identifying the right place to make the changes. Instead, changes were made and failure concluded before looking to see which file needed to be modified.
-
@Danp said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
Nothing. I followed the instructions in the above mentioned article.
That's a really old post from well before XS7 came out. According to this recent post by a Citrix employee, the proper file to be editing is /etc/rsyslog.d/xenserver.conf
Did you try editing this file?
-
@stacksofplates No, I haven't attempted it yet.
-
@scottalanmiller said in Final Call ... XenServer Boot Media:
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
But now I'm just complaining! back to the issue at hand.
-
@Danp said in Final Call ... XenServer Boot Media:
@stacksofplates No, I haven't attempted it yet.
Sorry I was referring to @BRRABill to see if it worked.
-
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
But now I'm just complaining! back to the issue at hand.
This isn't the OS. This is a file that was added to overwrite changes made. Without looking at an XS system, I'm assuming it's a boot script.
-
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
But now I'm just complaining! back to the issue at hand.
You see it ALL the time. That's what the entire GUI is! That's what every DevOps tools does, yes even on Windows.
-
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
But now I'm just complaining! back to the issue at hand.
Ever seen a GPO on Windows? That does this too. Try making a local change then having GP overwrite it. Exactly the same.
-
@Dashrender said in Final Call ... XenServer Boot Media:
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
I have most certainly seen it many times on Windows.
-
@scottalanmiller said in Final Call ... XenServer Boot Media:
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
XS rewrote the rsyslog.conf every time.
Ah, I never saw that mentioned and that means that you were addressing the wrong thing. You needed to stop it changing rsyslog.conf. What did you do to stop it from doing that?
Nothing. I followed the instructions in the above mentioned article.
If this article isn't for doing what you want, why expect it to do something different than it is intended to do?
I'm not.
I don't understand your question/comment.
Why were you following the instructions in that article? What was the end goal?
To prevent XS from logging locally when I have it set up to log externally.
But the files to do that were not yet modified, right? So we aren't up to step one yet. That's my point. There are config files that make this happen, but those were not changed. Only the ones that they change, were changed, but that won't do anything.
How was @BRRABill suppose to know that he's editing the wrong files? I guess it's called RTFM.
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
What if he had just opened an editor and made his own file in /tmp/mychanges.txt and wrote in it "don't write logs locally?" That also would not work. But we might say "how was he supposed to know that he had to modify a specific file?"
It's clear that he tried and made a good guess. But it is also clear that the actual configuration was not done correctly and that the first step has to be identifying the right place to make the changes. Instead, changes were made and failure concluded before looking to see which file needed to be modified.
He was following some instructions he found. I do recall the thread on here last or the week before where it was discovered that the file wasn't keeping the changes through a reboot, but then I wasn't able to keep following it.
-
@Dashrender said in Final Call ... XenServer Boot Media:
He was following some instructions he found. I do recall the thread on here last or the week before where it was discovered that the file wasn't keeping the changes through a reboot, but then I wasn't able to keep following it.
And it was proven that those were bad instructions.
-
@Dashrender said in Final Call ... XenServer Boot Media:
He was following some instructions he found. I do recall the thread on here last or the week before where it was discovered that the file wasn't keeping the changes through a reboot, but then I wasn't able to keep following it.
They were rather random ones, though, that they themselves talked about how it didn't work and were resorting to things like trying to stop file writes rather than looking for the right file. So it sounded like they said right in it that the directions were wrong, right?
-
@Dashrender said in Final Call ... XenServer Boot Media:
He was following some instructions he found. I do recall the thread on here last or the week before where it was discovered that the file wasn't keeping the changes through a reboot, but then I wasn't able to keep following it.
I've been through the instructions and there are a few issues. One is that they are very old and predate the XS7 system, I think that they predate XS6.5 as well. And they dont address what he was wanting to do, they don't (that I can find) even talk about not writing the logs locally.
-
@scottalanmiller said in Final Call ... XenServer Boot Media:
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
But now I'm just complaining! back to the issue at hand.
You see it ALL the time. That's what the entire GUI is! That's what every DevOps tools does, yes even on Windows.
OK I get the DevOps thing, but I don't agree with the GUI, the GUI doesn't load pre those files being ran and update the file. It's more like
@stacksofplates said -
This is a file that was added to overwrite changes made. Without looking at an XS system, I'm assuming it's a boot script.
So this is an XS thing, not a rsyslog thing?
-
@scottalanmiller said in Final Call ... XenServer Boot Media:
@Dashrender said in Final Call ... XenServer Boot Media:
@scottalanmiller said in Final Call ... XenServer Boot Media:
Well it was getting overwritten. That's a pretty big give away. Something else was changing his configuration. So that wasn't the final configuration. When you look at the documents, they do tell you that that isn't the file in this case and that there is a separate master file that controls that one.
To which I reply - fraking OS. While it's not impossible so see something like this on Windows, I don't personally recall seeing a file that edits a file like this.
But now I'm just complaining! back to the issue at hand.
Ever seen a GPO on Windows? That does this too. Try making a local change then having GP overwrite it. Exactly the same.
OK Fine I acquiesce, you're right.
-
@Dashrender said in Final Call ... XenServer Boot Media:
So this is an XS thing, not a rsyslog thing?
Yes. If you install CentOS 7, it will not do this.
-
@Dashrender said in Final Call ... XenServer Boot Media:
So this is an XS thing, not a rsyslog thing?
Yes, because he has to control things from the GUI. Some management component is making the changes here, not rsyslog.
As XenCenter can make the syslog changes, it is completely possible that the configuration issue is external with XC pushes the changes from there.
-
@JaredBusch said in Final Call ... XenServer Boot Media:
@Dashrender said in Final Call ... XenServer Boot Media:
He was following some instructions he found. I do recall the thread on here last or the week before where it was discovered that the file wasn't keeping the changes through a reboot, but then I wasn't able to keep following it.
And it was proven that those were bad instructions.
it was? oh? Well then I guess he forgot to mention that from the other thread (snark intended).
