Hi Martin,
Thank you I just did service monit restart and now it works.
My next question what is different between starting using say monit start
service1 or using the other method ./startDaemon.sh. I notice in both
methods when the missing pid monit do restart my app ?
Another thing just to confirm with you by enabling it am I allowing port
2812 access from outside or will this post any security concern even though
I am not using the web version?
set httpd port 2812 and
use address localhost # only accept connection from localhost
allow localhost # allow localhost to connect to the server and
allow admin:monit # require user 'admin' with password 'monit'
On Tue, Nov 10, 2015 at 1:03 AM, Martin Pala <[email protected]> wrote:
> Please make sure you did "monit reload" after configuration changes.
>
> Regards,
> Martin
>
>
>
> On 09 Nov 2015, at 16:49, frwa onto <[email protected]> wrote:
>
> Hi Martin,
> In my version I did this
>
> ## Monit has an embedded web server which can be used to view status of
> ## services monitored and manage services from a web interface. See the
> ## Monit Wiki if you want to enable SSL for the web server.
> #
> set httpd port 2812 and
> use address localhost # only accept connection from localhost
> allow localhost # allow localhost to connect to the server and
> allow admin:monit # require user 'admin' with password 'monit'
> # allow @monit # allow users of group 'monit' to connect (rw)
> # allow @users readonly # allow users of group 'users' to connect
> readonly
> #
> must I do any other configuration for port 2812 ? Cause I get this error
> Cannot create socket to [localhost]:2812 -- Connection refused
> In my case my centos is bare minimal with got gnome nothing ?
>
>
>
> On Mon, Nov 9, 2015 at 11:39 PM, Martin Pala <[email protected]>
> wrote:
>
>> You need to add it to the monit configuration file ... it is part of
>> default configuration file, snip:
>>
>> --8<--
>> ## Monit has an embedded HTTP interface which can be used to view status
>> of
>> ## services monitored and manage services from a web interface. The HTTP
>> ## interface is also required if you want to issue Monit commands from the
>> ## command line, such as 'monit status' or 'monit restart service' The
>> reason
>> ## for this is that the Monit client uses the HTTP interface to send these
>> ## commands to a running Monit daemon. See the Monit Wiki if you want to
>> ## enable SSL for the HTTP interface.
>> #
>> set httpd port 2812 and
>> use address localhost # only accept connection from localhost
>> allow localhost # allow localhost to connect to the server and
>> allow admin:monit # require user 'admin' with password 'monit'
>> --8<--
>>
>> See monit manual for details.
>>
>>
>> > On 09 Nov 2015, at 16:30, frwa onto <[email protected]> wrote:
>> >
>> > Hi Martin
>> > I got this error now when I did this monit start service1
>> ? Where to add the 'set httpd statement"?
>> >
>> > Action start not possible - monit http interface is not enabled, please
>> add the 'set httpd' statement ? Should I start using monit start command or
>> can I use the existing method to start it? Which the correct one?
>> >
>> > On Mon, Nov 9, 2015 at 11:27 PM, Martin Pala <[email protected]>
>> wrote:
>> > Hi,
>> >
>> > correct syntax is:
>> >
>> > monit start service1
>> >
>> > Regards,
>> > Martin
>> >
>> >
>> > > On 09 Nov 2015, at 16:23, frwa onto <[email protected]> wrote:
>> > >
>> > > Hi,
>> > > I have set below in my monit.conf.
>> > >
>> > > check process service1 with pidfile /var/run/wrapper.service1.pid
>> > > start program = "/etc/rc.d/init.d/service1 start" with
>> timeout 60 seconds
>> > > stop program = "/etc/rc.d/init.d/service1 stop"
>> > >
>> > > I tried to start the service in this manner
>> > > monit service1 start
>> > > Invalid argument -- service1 (-h will show valid arguments)
>> > >
>> > > So should I start using my existing method where I get into my
>> wrapper folder /usr/local/wra1/bin/ then key in ./startDaemon.sh? I would
>> like to know if I am doing the right thing?
>> > >
>> > > Thank you.
>> > >
>> > > --
>> > > To unsubscribe:
>> > > https://lists.nongnu.org/mailman/listinfo/monit-general
>> >
>> >
>> > --
>> > To unsubscribe:
>> > https://lists.nongnu.org/mailman/listinfo/monit-general
>> >
>> > --
>> > To unsubscribe:
>> > https://lists.nongnu.org/mailman/listinfo/monit-general
>>
>>
>> --
>> To unsubscribe:
>> https://lists.nongnu.org/mailman/listinfo/monit-general
>>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
>
>
> --
> To unsubscribe:
> https://lists.nongnu.org/mailman/listinfo/monit-general
>
--
To unsubscribe:
https://lists.nongnu.org/mailman/listinfo/monit-general
