Error executing start command

[markitosgv]

I'm under Centos 7, I've supervisor installed and running.

When I try to execute:

php bin/console rabbitmq-supervisor:control start, nothing seems to happen.

If I try same command with --wait-for-supervisord flag:
It says: Misuse of shell builtins

What I'm doing wrong?

[Phobetor]

Hi @markitosgv

First of all: the "Misuse of shell builtins" message is a wrong interpretation of the exit code by symfony's process component. The message is plain wrong. It comes from a command call failing with exit code 2.

According to one of supervisor's contributors "the only condition that causes exit code 2 is when an unhandled exception occurs inside supervisorctl."

Do you have any messages in your supervisor.log?

[Phobetor]

Hi @markitosgv

Dumb question first (sorry): did you run rabbitmq-supervisor:build or rabbitmq-supervisor:rebuild before the start command? These commands are creating the configuration that is needed to start.

And finally some problems I stepped over that lead to errors like that:

• paths were not accessible where supervisor is configured to store its pid or sock files
• old pid or sock files that were laying around from previous runs that did not exit properly

[webdevilopers]

I had the same error message "Misuse of shell builtins" in #36 @markitosgv . It means that you could be using to many relative path infos e.g. "../". Could you show us your full path to the configuration?

[imper86]

I have the same error.
@webdevilopers my full path to configuration is "/home/ubuntu/code/kuriernat/var/supervisor/dev" if you meant that
@Phobetor how can I check if paths are not accessible? Should I change supervisor global config in some way? Or generally does supervisor must have specific configuration?

Edit:
To test if supervisor is running normally i copied config generated by bundle and sipmly created new file inside /etc/supervisor/conf.d. After reread and update supervisor is running just as expected, without errors.

One more edit:
Ok, I found something - i actually run vagrant ubuntu virtual machine and it seems that supervisor can't initialize .sock file in shared directory, where i keep my code. So changing sock_file location helped and now it's working great :)