Bug #12032
activate beanstalkd logs
% Done:
0%
Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature (v1):
Crash signature (v2):
Description
When beanstalk is unresponsive (see http://tracker.ceph.com/issues/12031), it would be nice to see logs that may explain the source of the problem.
Edit /etc/init.d/beanstalkd on teuthology, uncomment
#LOGDIR=/var/log/beanstalkd # Log directory to use
Related issues
History
#1 Updated by Zack Cerza about 8 years ago
- Assignee set to Zack Cerza
#2 Updated by Zack Cerza about 8 years ago
I set the following:
$ grep LOG /etc/init.d/beanstalkd LOGDIR=/var/log/beanstalkd # Log directory to use LOGFILE=$LOGDIR/$NAME.log # Server logfile
Then created /var/log/beanstalkd/
and restarted; days later and no logs :-/
#3 Updated by Ian Colle over 7 years ago
https://github.com/kr/beanstalkd/issues/229
Hrm - Zack - please see above for their unsatisfying answer
#4 Updated by Patrick Donnelly over 4 years ago
- Status changed from 12 to New
#5 Updated by Laura Flores 11 months ago
- Status changed from New to Resolved