Project

General

Profile

Bug #12032

activate beanstalkd logs

Added by Loic Dachary over 5 years ago. Updated 12 months ago.

Status:
New
Priority:
Urgent
Assignee:
Category:
-
Target version:
-
% Done:

0%

Source:
other
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Crash signature:

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

Related to sepia - Bug #12031: unable to schedule jobs on sepia (beanstalkd unresponsive) Resolved 06/16/2015

History

#1 Updated by Zack Cerza almost 5 years ago

  • Assignee set to Zack Cerza

#2 Updated by Zack Cerza almost 5 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 about 4 years ago

https://github.com/kr/beanstalkd/issues/229
Hrm - Zack - please see above for their unsatisfying answer

#4 Updated by Patrick Donnelly 12 months ago

  • Status changed from 12 to New

Also available in: Atom PDF