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

beanstalkd progress exit #565

Closed
pz9042 opened this issue Sep 12, 2019 · 6 comments
Closed

beanstalkd progress exit #565

pz9042 opened this issue Sep 12, 2019 · 6 comments
Labels
WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.

Comments

@pz9042
Copy link

pz9042 commented Sep 12, 2019

this morning I use command sudo /usr/local/beanstalkd/bin/beanstalkd -b /data/beanstalkd -l 0.0.0.0 -p 11300 -u beanstalkd & start service,but in afternoon,the progress exit. beanstalkd version is 1.11,os version is centos 7.6.1810. I not found any relate message in /var/log/message

@ysmolski
Copy link
Member

@pz9042 can you provide more details?

@ysmolski ysmolski added the WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided. label Sep 14, 2019
@ysmolski
Copy link
Member

By default beanstalkd writes into stderr and not to /var/log/messages. You might want to capture stderr.

@pz9042
Copy link
Author

pz9042 commented Sep 15, 2019

thanks,because i start service on backend,and not redirect stderr, I will provide the error info tomorrow

@pz9042
Copy link
Author

pz9042 commented Sep 16, 2019

start command : /usr/local/beanstalkd/bin/beanstalkd -b /data/beanstalkd -l 0.0.0.0 -p 11300 -u beanstalkd >/tmp/beanstalkd.txt 2>&1 &
[root@dev ~]# ps aux |grep -i bean root 20916 0.0 0.0 112724 1000 pts/0 S+ 15:15 0:00 grep --color=auto -i bean [root@dev ~]# ll /tmp/beanstalkd.txt -rw-r--r-- 1 root root 0 9月 16 10:21 /tmp/beanstalkd.txt [root@dev ~]#
there is no any message

@pz9042
Copy link
Author

pz9042 commented Sep 18, 2019

/usr/local/beanstalkd/bin/beanstalkd: prot.c:710 in check_err: read(): Connection reset by peer

@ysmolski
Copy link
Member

This is a normal message, it means that client's connection was lost during the read operation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
WaitingForInfo Issue is not actionable because of missing required information, which needs to be provided.
Projects
None yet
Development

No branches or pull requests

2 participants