Skip to main content

Laravel Job queue Supervisord and beanstalkd

   Active: inactive (dead)
ubuntu@ip-172-31-29-15:/var/www/risk_advisor_dev/risk_advisor/API$ sudo service supervisor status
● supervisor.service - Supervisor process control system for UNIX
   Loaded: loaded (/lib/systemd/system/supervisor.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2018-09-05 02:44:50 UTC; 49min ago
     Docs: http://supervisord.org
  Process: 19220 ExecStop=/usr/bin/supervisorctl $OPTIONS shutdown (code=exited, status=0/SUCCESS)
 Main PID: 19223 (supervisord)
    Tasks: 4
   Memory: 111.6M
      CPU: 1min 47.037s
   CGroup: /system.slice/supervisor.service
           ├─19223 /usr/bin/python /usr/bin/supervisord -n -c /etc/supervisor/supervisord.conf
           ├─19229 php /var/www/risk_advisor_dev/risk_advisor/API/artisan queue:listen --timeout=3000
           ├─31175 sh -c '/usr/bin/php7.0' 'artisan' queue:work '' --once --queue='default' --delay=0 --memory=128 --sleep=3 --tries=0
           └─31176 /usr/bin/php7.0 artisan queue:work  --once --queue=default --delay=0 --memory=128 --sleep=3 --tries=0

Sep 05 02:44:50 ip-172-31-29-15 systemd[1]: Started Supervisor process control system for UNIX.
Sep 05 02:44:50 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:50,507 CRIT Supervisor running as root (no user in config file)
Sep 05 02:44:50 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:50,507 WARN Included extra file "/etc/supervisor/conf.d/riskadvisor.conf" during parsing
Sep 05 02:44:50 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:50,515 INFO RPC interface 'supervisor' initialized
Sep 05 02:44:50 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:50,515 CRIT Server 'unix_http_server' running without any HTTP authentication checking
Sep 05 02:44:50 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:50,515 INFO supervisord started with pid 19223
Sep 05 02:44:51 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:51,518 INFO spawned: 'laravel-queue' with pid 19229
Sep 05 02:44:52 ip-172-31-29-15 supervisord[19223]: 2018-09-05 02:44:52,520 INFO success: laravel-queue entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
ubuntu@ip-172-31-29-15:/var/www/risk_advisor_dev/risk_advisor/API$ sudo service beanstalkd status
● beanstalkd.service - Simple, fast work queue
   Loaded: loaded (/lib/systemd/system/beanstalkd.service; enabled; vendor preset: enabled)
   Active: active (running) since Fri 2018-07-20 23:15:34 UTC; 1 months 15 days ago
     Docs: man:beanstalkd(1)
 Main PID: 1168 (beanstalkd)
    Tasks: 1
   Memory: 264.0K
      CPU: 4min 25.902s
   CGroup: /system.slice/beanstalkd.service
           └─1168 /usr/bin/beanstalkd -l 127.0.0.1 -p 11300

Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.
ubuntu@ip-172-31-29-15:/var/www/risk_advisor_dev/risk_advisor/API$


Comments

Popular posts from this blog

Rand mm 10

https://stackoverflow.com/questions/2447791/define-vs-const Oh const vs define, many time I got unexpected interview question. As this one, I do not know much or try to study this. My work flow, and I believe of many programmer is that search topic only when we have task or job to tackle. We ignore many 'basic', 'fundamental' documents, RTFM is boring. So I think it is a trade off between the two way of study language. And I think there are a bridge or balanced way to extract both advantage of two method. There are some huge issue with programmer like me that prevent we master some technique that take only little time if doing properly. For example, some Red Hat certificate program, lesson, course that I have learned during Collage gave our exceptional useful when it cover almost all topic while working with Linux. I remember it called something like RHEL (RedHat Enterprise Linux) Certificate... I think there are many tons of documents, guide n books about Linux bu

Martin Fowler - Software Architecture - Making Architecture matter

  https://martinfowler.com/architecture/ One can appreciate the point of this presentation when one's sense of code smell is trained, functional and utilized. Those controlling the budget as well as developer leads should understand the design stamina hypothesis, so that the appropriate focus and priority is given to internal quality - otherwise pay a high price soon. Andrew Farrell 8 months ago I love that he was able to give an important lesson on the “How?” of software architecture at the very end: delegate decisions to those with the time to focus on them. Very nice and straight-forward talk about the value of software architecture For me, architecture is the distribution of complexity in a system. And also, how subsystems communicate with each other. A battle between craftmanship and the economics and economics always win... https://hackernoon.com/applying-clean-architecture-on-web-application-with-modular-pattern-7b11f1b89011 1. Independent of Frameworks 2. Testable 3. Indepe