Skip to content
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

mysql.processlist infinite loop #6297

Closed
drzero42 opened this issue Jul 24, 2013 · 2 comments
Closed

mysql.processlist infinite loop #6297

drzero42 opened this issue Jul 24, 2013 · 2 comments
Labels
Bug broken, incorrect, or confusing behavior help-wanted Community help is needed to resolve this Regression The issue is a bug that breaks functionality known to work in previous releases.
Milestone

Comments

@drzero42
Copy link
Contributor

Environment: Salt-master and salt-minion on two seperate Ubuntu 12.04.2 servers both running salt 0.16.0. The minion has a mysql-server running and has salt-minion configured with:
mysql.default_file: '/etc/mysql/debian.cnf'

I can run "salt '' mysql.version" and "salt '' mysql.db_list" just fine, but when I try mysql.processlist, this traceback happens:

Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/salt/minion.py", line 626, in _thread_return
    ret['return'] = func(*args, **kwargs)
  File "/usr/lib/pymodules/python2.7/salt/modules/mysql.py", line 841, in processlist
    log.debug('MySQL Process List:\n{0}'.format(processlist()))
  File "/usr/lib/pymodules/python2.7/salt/modules/mysql.py", line 841, in processlist
    log.debug('MySQL Process List:\n{0}'.format(processlist()))
  File "/usr/lib/pymodules/python2.7/salt/modules/mysql.py", line 841, in processlist
    log.debug('MySQL Process List:\n{0}'.format(processlist()))
... (repeated a lot!)
  File "/usr/lib/pymodules/python2.7/salt/modules/mysql.py", line 841, in processlist
    log.debug('MySQL Process List:\n{0}'.format(processlist()))
RuntimeError: maximum recursion depth exceeded
@basepi
Copy link
Contributor

basepi commented Jul 24, 2013

Thanks for the report, this should be fairly easy to fix. I think that is just a less-often-used function, which is why this hasn't popped up.

@techhat
Copy link
Contributor

techhat commented Jul 27, 2013

Fixed by #6350.

@techhat techhat closed this as completed Jul 27, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior help-wanted Community help is needed to resolve this Regression The issue is a bug that breaks functionality known to work in previous releases.
Projects
None yet
Development

No branches or pull requests

3 participants