Despliegue y supervisión

In case anybody has the same problem, that the installation of SUPERVISOR is not allowed on production-server, I solved this with a workaround by using a cronjob (starting every 5 minutes) with this bash-script:

#!/bin/sh

# check with '$ which php' and add to variable
PHP_FOLDER="/usr/bin/php"

# give your root folder of your symfony-project
SYMFONY_FOLDER="$HOME/your/symfony/project"

# define the transporters that shall be treated
TRANSPORTERS="async_1 async_2"

# define timezone to avoid mismatch between php for console and php for web (or server). Different
# timezones, would delay the treatment of the messages in the queues. E.g. check timezone with
#      SERVER time: $ echo $TZ
# PHP-Console time: $ php -r 'echo date_default_timezone_get();'
TIMEZONE="Europe/Berlin"

# Show folder (main intention is to exit if folder not exists)
echo "Change folder to:"
cd "$SYMFONY_FOLDER" || exit
pwd

echo ""
echo "Stop any running Workers"
env -i "$PHP_FOLDER" -q "$SYMFONY_FOLDER"/bin/console messenger:stop-workers

echo ""
echo "Starting Worker (messenger:consume)"
env -i "$PHP_FOLDER" -d date.timezone=$TIMEZONE -q "$SYMFONY_FOLDER"/bin/console messenger:consume -vv $TRANSPORTERS  --memory-limit=100M

Happy coding!

Hey Tim,

Thank you for sharing your workaround with others! Good idea to start the command via CRON ;)

Cheers!

Hello again !
A tiny precision, wich I faced : on ubuntu server I had to precise the directory where the supervisor should find the app so my worker looks like :
[program:messenger-consume]
command=php bin/console messenger:consume async --time-limit=3600
directory=/var/www/html/my-app

One other thing about supervisor, it seems he prefer now working with .conf files and not .ini (easy to fix, but you have to think about this --> http://supervisord.org/runn...

Are aware of a trouble for the FlySystem to delete files in a handler? I can't do it on production while I'm ok on local dev (still searching btw)

Just in case, the correct link is: http://supervisord.org/runn...

Hey Remi,

Yeah, it makes sense. In our example we use the absolute path so it works. If you use a relative path like only "bin/console" - you have to specify the directory of your project. Thank you for some tips! Might be useful for other users.

About problem with deleting files in a handler. Hm, most probably you have different permissions, so it sounds like permission problem. Is it for all the folders? Or some of them are removed successfully but some are not?

Cheers!

Hm, most probably you have different permissions, so it sounds like permission problem. Is it for all the folders? Or some of them are removed successfully but some are not?

Mmm... Not sure because my filesystem works perfectly in the controller in production... I'll explore further and keep you update (i didn't try it syncronously yet to make a differential diagnosis)

Hey @Rémi Dck

I also believe that the file deletion problem is due to permissions. I think you just have to tell supervisor to run your worker as your web user (usually named as "www"). Here is an example of how to do it but I didn't give it a try: https://stackoverflow.com/a...

Cheers!

OMG you're the best Diego. Thanks a lot !!!
I dug in and the tail is a little bit tricky (to me, i'm not a unix user...)
The first step is finding the web user, like you said and the best command for this is less /etc/passwd. For Ubuntu 18.04 seems to be www-data
Next in messenger-worker.conf change user name and add environnement targeting the home directory of www-data
Aaaand done ! Love it.

Awesome! Excellent job man because I wrote the name wrong, it usually is www-data not just www :p

Hello guys,
I'm using Docker for deployment and my image have supervisor installed within. Now in order to execute these three command :

supervisorctl reread
supervisorctl update
supervisorctl start messenger-consume:*

Where should I put them? In Dockerfile or a entrypoint command? They should be run after the container is up if I'm not wrong ?

Yo @Dang!

Hmm. I am FAR from an expert on Docker, especially in a production environment. However, I believe that you would have a specific (PHP) container set up for running supervisor and that supervisor would be your main CMD on that container (and you'd run supervisor with nodaemon=true). Again, this is NOT my area of expertise, so I could be misguided, but that's my impression :).

Cheers!

Hi. What is/are the possible strategy/strategies to use if the Consumer throws an exception for any reason ? Assuming that the environment is Production. Thanks.

Hey Marko,

The best strategy is to do a few more retries after some time, and if still no success - move that message into a failed messages queue where you can retry the message manually when the problem will be fixed. That's the strategy we use on SymfonyCasts, and IIRC we covered it in this course :)

Cheers!

Hello Victor! Thanks a lot for your quick answer. Does Supervisor have any role in this issue (in production) ?

Hey Marko,

Supervisor is about a different problem, it helps to restart the worker on the server, so it's a bit different. If for some reasons you mean that your worker crashes, i.e. stops on the production that you have to restart it manually again - then yes, you need that supervisor that will restart the worker for you. But the problems you described relates to different things if I understand you correctly.

Cheers!

I really hate asking this question.
Is there an easy windows solution?

Rainer S.

Yeah that's a good question, I'm hot sure but probably this link https://github.com/alexsilv... will help you, but I think you already saw this link. Unfortunately I can't advise you some real production example for windows, also there is not so many windows servers, that's why there is not so many solutions for it!

Cheers! Hope it will help!

Has anyone by any chance run supervisor on an AWS EB setup? (Elastic Beanstalk, using .ebextension files)

Hey Chad,

Unfortunately, I have not run it personally. Though it looks like there's some solutions around the internet, e.g.: https://gist.github.com/vra...

I hope this helps!

Cheers!

Thanks, this is one of the articles I used to get things going.

Hey Chad,

Ah, great! Sorry, can't say something more about it, have never done it before. Probably someone who use it could suggest you a good tip about it.

Cheers!

the following .ebextension config file is working to install supervisor and start messenger:consume, but the .env file is required to be populated with all the database credentials and such

files:
  "/tmp/messenger-consume.conf":
    mode: "000644"
    owner: root
    group: root
    content: |
      [program:messenger-consume]
      command=php /var/www/html/bin/console messenger:consume async --time-limit=1800 --memory-limit=340M --sleep=30
      user=webapp
      numprocs=1
      autostart=true
      autorestart=true
      process_name=%(program_name)s_%(process_num)02d

  "/tmp/supervisord.conf":
    mode: "000644"
    owner: root
    group: root
    content: |
      ; supervisor config file

      [unix_http_server]
      file=/var/run/supervisor.sock   ; (the path to the socket file)
      chmod=0700                       ; sockef file mode (default 0700)

      [supervisord]
      user=root
      logfile=/var/log/supervisor/supervisord.log ; (main log file;default $CWD/supervisord.log)
      pidfile=/var/run/supervisord.pid ; (supervisord pidfile;default supervisord.pid)
      childlogdir=/var/log/supervisor            ; ('AUTO' child log dir, default $TEMP)

      ; the below section must remain in the config file for RPC
      ; (supervisorctl/web interface) to work, additional interfaces may be
      ; added by defining them in separate rpcinterface: sections
      [rpcinterface:supervisor]
      supervisor.rpcinterface_factory = supervisor.rpcinterface:make_main_rpcinterface

      [supervisorctl]
      serverurl=unix:///var/run/supervisor.sock ; use a unix:// URL  for a unix socket

      ; The [include] section can just contain the "files" setting.  This
      ; setting can list multiple files (separated by whitespace or
      ; newlines).  It can also contain wildcards.  The filenames are
      ; interpreted as relative to this file.  Included files *cannot*
      ; include files themselves.

      [include]
      files = /etc/supervisor/conf.d/*.conf
      ; Change according to your configurations

commands:
  01_01_install_supervisord:
    command: |
      sudo easy_install supervisor
      sudo mkdir -p /etc/supervisor/conf.d/
      sudo mkdir -p /var/log/supervisor
      sudo touch /var/log/supervisor/supervisord.log
    ignoreErrors: true

container_commands:
  01_01_copy_supervisor_configuration_files:
    command: |
      sudo mv /tmp/supervisord.conf /etc/supervisord.conf
      sudo mv /tmp/messenger-consume.conf /etc/supervisor/conf.d/messenger-consume.conf
    ignoreErrors: true
  02_01_start_supervisord:
    command: |
      sudo /usr/local/bin/supervisord -c /etc/supervisord.conf
      sudo /usr/local/bin/supervisorctl reread
      sudo /usr/local/bin/supervisorctl update
      sudo /usr/local/bin/supervisorctl restart all
      sudo /usr/local/bin/supervisorctl start messenger-consume:*
    ignoreErrors: true```

Hey Chad,

Thank you for sharing this solution with others! I'm glad you were able to get it working.

Cheers!

Hello,

When running supervisorctl -c /usr/local/etc/supervisord.ini start messenger-consume:*, I get zsh: no matches found: messenger-consume:*. But it seems the workers are actually working, because I tried to upload an image and it worked. In the video, there's no message after you start the supervisor with messenger-consume:*. So I'm just wondering if I'm doing something wrong...

Thanks!

Hey Ajie62!

Hmm. Try this command to see what's going on:

supervisorctl -c /usr/local/etc/supervisord.ini start

I definitely don't like that "no matches found". Also try using the stop command to see if it stops anything. Here's a screenshot of what starting and stopping looks on my machine - you can see how "start" sometimes doesn't have any output (if it's already started) but sometimes does.

https://imgur.com/Pz601gU

Also, the zsh: no matches found: messenger-consume:* is odd... the error should come from supervisorctl... not from "zsh". Try surrounding messenger-consume:* with quotes. I don't know zsh well... but I'm wondering if it's somehow interpreting something differently...

Cheers!

Hey, thanks for you answer! The problem was oh-my-zsh. I removed it an now everything works fine. I assume I could have solved the problem and keep oh-my-zsh, but I wanted to save time and keep learning :) Thank you again, weaverryan