Final Call ... XenServer Boot Media
-
@BRRABill said in Final Call ... XenServer Boot Media:
XS still logs locally even if you send the logs elsewhere.
I was under the impression that constant writing to a USB would kill it pretty quickly.
Can you show the entire configuration file for that situation?
-
@stacksofplates said in Final Call ... XenServer Boot Media:
@BRRABill said in Final Call ... XenServer Boot Media:
XS still logs locally even if you send the logs elsewhere.
I was under the impression that constant writing to a USB would kill it pretty quickly.
It just uses rsyslog. If you remove all of the local log info from /etc/rsyslog.conf it will only send to the remote server. You have to restart the rsyslog server after you do your edits.
This is important, XS uses rsyslog, the questions are purely ones about rsyslog, not XS. Don't think of this as how "XS behaves", it's just a matter of configuring rsyslog. It's identical to any OS that uses rsyslog.
-
@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?
-
@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.
-
@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
-
@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
According to that post, XS7 has logging turned off be default?
Or am I reading that wrong?
-
@BRRABill By default, the messages file isn't being used for the system logs.
-
@Danp said in Final Call ... XenServer Boot Media:
@BRRABill By default, the messages file isn't being used for the system logs.
But the logs themselves are still writing, correct?
So you think if I comment out the xenserver.conf file, that might maintain the changes?
-
@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?
-
@BRRABill said in Final Call ... XenServer Boot Media:
@Danp said in Final Call ... XenServer Boot Media:
@BRRABill By default, the messages file isn't being used for the system logs.
But the logs themselves are still writing, correct?
So you think if I comment out the xenserver.conf file, that might maintain the changes?
If that is what Citrix says, then yes.
-
Just try editing that file, reboot and see.
-
I'd say A.
You can always make backups of the metadata for the VMs as well. I'd know where to go looking in XenCenter, and I'd be very surprised if you can't do the same thing through Xen Orchestra. I don't feel like trying to configure access from home here just to go look for you tho, sorry.
-
@travisdh1 said in Final Call ... XenServer Boot Media:
I'd know where to go looking in XenCenter, and I'd be very surprised if you can't do the same thing through Xen Orchestra.
Actually, XO doesn't yet offer that option. See https://github.com/vatesfr/xo-web/issues/808.
-
@Danp said in Final Call ... XenServer Boot Media:
@travisdh1 said in Final Call ... XenServer Boot Media:
I'd know where to go looking in XenCenter, and I'd be very surprised if you can't do the same thing through Xen Orchestra.
Actually, XO doesn't yet offer that option. See https://github.com/vatesfr/xo-web/issues/808.
:slight_frown:
-
@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.
-
@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?
-
@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.
In XS it was an issue because the smaller logging partition filled up. So that article touched on how to use log rotating, or just simply disable local logging.
Their tips did not work for everyone, as evidenced by me and it the comments. They they suggesyed just making the file read-only.
Let me check how XS7 does logs. Maybe it is totally different.
I know @DustinB3403 had a thread about the logging as well.
I'd love to get this figured out and make it into a XS best practice, because it seems like every week there is a thread about it.
-
@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.
-
@BRRABill said in Final Call ... XenServer Boot Media:
Their tips did not work for everyone, as evidenced by me and it the comments. They they suggesyed just making the file read-only.
Sounds like they were just clueless and not even looking into the problem.
-
@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.
Step two is two edit the config file (which is different in XS as we have seen) to remove the sections that still reference local logging. By doing this, XS should never log locally.
However, this file keeps getting overwritten with an original copy.
