-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
rhel/centos salt-minion yum output in terminal #3855
Comments
I do have |
Thanks for the report! |
it's not just yum output apparently... If i use a returner from the salt-master, the returner output ALSO shows in my minion terminal on RHEL/Centos. Still doesn't happen on Ubuntu. On master: salt '*' test.ping -s -t 1 --return local In minion terminal, I suddenly see: [root@salt-test ~]# {'fun': 'test.ping', 'jid': '20130227212345183550', 'return': True, 'id': 'oscontrol1', 'success': True} |
@ydavid365 log_level is for the console, log_level_logfile is for the log file. |
K. Wasn't aware that there are teo different options. But this isn't expected behavior right? I'd expect that console output should only show if I'm running salt-minion in non-daemon mode. Regardless, it doesn't exhibit the same behavior across Ubuntu and rhel, and clearly seems to be a bug. On Mar 3, 2013, at 6:39 PM, Erik Johnson notifications@github.com wrote:
|
I believe this happened before in RHEL/CentOS, but I don't remember what was done to fix it. @thatch45, do you remember? |
The problem here is what we do to bypass a bug in daemonizing + multiprocessing in python, basically the shell output is not redirected after daemonizing because if it is then the minion crashes when test is displayed in a job execution. So what we need to do is figure out how to redirect stdout + stderr is such a way that does not crash the minion. |
I just discovered this in my office as well. 0.13.1 on CentOS 6.4. |
We might be able to fix this with some of the recent changes to how minion procs get started |
no, the minion still crashes if the output is redirected... |
Quiet down Yum's logging. Fixes #3855.
w00t! On Fri, Nov 15, 2013 at 3:16 AM, Pedro Algarvio notifications@github.comwrote:
|
Salt does not need any of `sys.stdout`, `sys.stderr` and `syslog` logging handlers which are configured by Yum, specially because we're using Yum as an API, not as another CLI tool. Any logging will go through salt's logging handlers.
I'm using salt 0.13.1 on centos 6.3 .
my salt-minion is started using
service salt-minion start
Whenever I log into the instance, I notice that salt-related yum output shows up in my terminal.
here's a recent example:
The text was updated successfully, but these errors were encountered: