Eh, this should have been sent to the mailing list.
I would also like to note that I should modify "/etc/supervisord.conf" and
not "/etc/supervisor.conf".
/Jens
---------- Forwarded message ----------
From: Jens Rantil <jens.ran...@gmail.com>
Date: Thu, Dec 1, 2011 at 3:17 PM
Subject: Re: [Supervisor-users] supervisorctl without configuration
To: Ales Zoulek <ales.zou...@gmail.com>
Hi Ales,
I am sorry if my initial question was not clear enough but you answered it
very well in your second answer :) I was indeed trying to connect remotely
without having a configuration file.
I will now create an /etc/supervisor.conf file containing "[supervisord]".
This should solve my issue! However, I do consider this a bug and file will
file an issue on Github!
Thanks!
Jens
On Thu, Dec 1, 2011 at 3:04 PM, Ales Zoulek <ales.zou...@gmail.com> wrote:
> Hi,
>
> I'm not sure I understand the question correctly, but I'll try :)
>
> supervisord needs configuration file just to start as a server, so you
> already have the config file on both servers, if the supervisord is
> running. (Supposing the supervisor is installed there from distribution
> package, the default config is already there -
> /etc/supervisor/supervisord.conf on ubuntu).
>
> By default, the supervisorctl command looks for the config file on the
> same paths as supervisord. So it should find it.Or you can tell it where to
> look for it by supervisorctl -c PATH_TO_CONFIG_FILE
>
> Next thing is that (again by default) the conf file includes both
> [supervisord] and [supervisorctl] sections, so it serves as both client and
> server config.
>
> So usualy you don't need to do anything extra to run supervisorctl
> (client), in case the machine is already set up to be able to run
> supervisord (server)
>
>
>
> A bit different use case (and maybe that's whats your question is?) is how
> to connect remotely to the supervisords running on several servers from one
> box (let's say your laptop). Fortunately that's not an isue neither. You
> are right, it needs to be able to read *any* config file with
> [supervisorctl] section, but that section can be completely empty and you
> can just:create an empty config and use it:
>
> {~ } echo '[supervisorctl]' >| supervisorctl.conf
> {~ } supervisorctl -s http://myserver:9000 -c supervisorctl.conf
>
> So you don't need each server's config files. You just need *any* config
> file to run the client and override all defaults in command line arguments.
>
> And yes, I agree that it should be able to run without any config as well.
> :)
>
>
> Regards,
>
>
> Ales
>
>
>
> ------------------------------------------------------
> Ales Zoulek
> +420 604 332 515
> Jabber: ales.zou...@gmail.com
> ------------------------------------------------------
>
>
> On Thu, Dec 1, 2011 at 2:10 PM, Jens Rantil <jens.ran...@gmail.com> wrote:
>
>> Hi,
>>
>> I have a couple of servers that are running supervisor to keep
>> applications running. Something that annoys me is the fact that I will need
>> each server's configuration file to be able to connect to it using
>> supervisoctl. Is this right?
>>
>> My question is twofold; How come the configuration is needed? Second
>> question, is has it been discussed whether it should be possible to also
>> connect to supervisor using supervisorctl without having the configuration
>> file at hand?
>>
>> Keep on rockin',
>> Jens
>>
>> --
>> Want to know how full my inbox is? Or how to get in touch with me faster?
>> Or tell me your e-mail is not that important? Then check this out:
>> http://courteous.ly/4WtfZY
>>
>> _______________________________________________
>> Supervisor-users mailing list
>> Supervisor-users@lists.supervisord.org
>> http://lists.supervisord.org/mailman/listinfo/supervisor-users
>>
>>
>
--
Want to know how full my inbox is? Or how to get in touch with me faster?
Or tell me your e-mail is not that important? Then check this out:
http://courteous.ly/4WtfZY
--
Want to know how full my inbox is? Or how to get in touch with me faster?
Or tell me your e-mail is not that important? Then check this out:
http://courteous.ly/4WtfZY
_______________________________________________
Supervisor-users mailing list
Supervisor-users@lists.supervisord.org
http://lists.supervisord.org/mailman/listinfo/supervisor-users
