5.14 It is the latest monit in yum repository On Fri, 27 May 2016, 08:03 Martin Pala, <[email protected]> wrote:
> Which monit version it is? > > In the past, monit cleared the environment variables and reset PATH when > executing the start program in a sandbox. When the program depends on some > env. variable or used for example relative paths internally, it then > failed. Old monit versions also didn't log the program output. > > I recommend to upgrade monit (latest release 5.18 is recommended). > > Best regards, > Martin > > > On 26 May 2016, at 22:13, Volkan Celebi <[email protected]> wrote: > > Thanks again, > > It is really newbie questions but unfortunately I should ask again. I > wrote this into config file > > check process mumudvb11096 matching "mumudvb -d -c /root/42/11096" > start program = "/usr/bin/mumudvb -d -c /root/42/11096" > > I didn't write any stop program parameter because I haven't got anyone. > After that I checked via Webgui and It was working. I have killed the > working pid of "mumudvb -d -c /root/42/11096" and tested it but I got > "Execution failed error" I can start mumudvb from every location with this > command = "mumudvb -d -c /root/42/11096" but now I didn't understand why it > didn't work. Also monit procmatch gives no error for "/usr/bin/mumudvb -d > -c /root/42/11096" > > any help would be appreciated > > Have a nice day > > On 26 May 2016 at 15:37, Martin Pala <[email protected]> wrote: > >> Hello, >> >> you can use the pattern based process check: >> >> check process mumdvb11557 matching "mumudvb -d -c /root/42/11557" >> start program = ... #set your start program here >> stop program = ... #set your stop program here >> >> You can use monit CLI interface to test patterns: >> >> monit procmatch "mumudvb -d -c /root/42/11557" >> >> Note: upgrade to monit 5.18 is recommended if you have a process similar >> to apache fork mode (where a master process spawns children and all match >> the same pattern). >> >> >> Regards, >> Martin >> >> >> >> > On 26 May 2016, at 14:05, Volkan Celebi <[email protected]> wrote: >> > >> > Hello, >> > >> > Thanks your answer Martin. I decided intall Monit which mumudvb working >> Server, too. I think It would be far away easier to make a working config. >> I will ask further help. For example this process from system killed: >> > >> >> mumudvb -d -c /root/42/11557 >> > How can I realise this process working not anymore and it should be >> start again. Because of this, as far as I now there is no any possibility >> to give any process to custom pid. Every pids assigning from system >> automatically. Any small tips/config would be very nice. >> > >> > Thanks in advance >> > Volkan Çelebi >> > >> > >> > >> > On 23 May 2016 at 14:30, Martin Pala <[email protected]> wrote: >> > Hello, >> > >> > you can restart the process on remote machine only if you install monit >> on that remote machine too - it provides an HTTP GUI, which can be used to >> restart services. Each mumudvb instance will then have its own service >> entry in monit configuration file. >> > >> > Regards, >> > Martin >> > >> > >> >> On 23 May 2016, at 13:12, Volkan Celebi <[email protected]> wrote: >> >> >> >> Dear all, >> >> >> >> for a while I am looking a solution for this. I installed monit on my >> server and I can get alerts but I need monitor processes on different >> machines and I have to start them from monit installed machine. I need >> monitor these process but problem is if any "mumudvb" process fail I have >> to start it with custom configuration file. Every single mumudvb process >> works with different config files. Is there any way to realize it monit? >> >> >> >> Here is the quickview to processes: >> >> >> >> root@localhost ~]# ps aux | grep mumudvb >> >> root 5034 4.8 0.6 103040 21116 ? SLl Apr29 175:13 >> mumudvb -d -c /root/42/12729 >> >> root 5691 6.1 0.6 37504 21108 ? SLl Apr29 221:56 >> mumudvb -d -c /root/42/12422 >> >> root 6160 3.1 0.6 37608 21080 ? SLl Apr29 114:26 >> mumudvb -d -c /root/42/12265 >> >> root 6796 7.6 0.6 103060 21136 ? SLl Apr29 275:19 >> mumudvb -d -c /root/42/10962 >> >> root 7209 7.2 0.6 37524 21128 ? SLl Apr29 263:44 >> mumudvb -d -c /root/42/11855 >> >> root 7774 6.6 0.6 37516 21120 ? SLl Apr29 241:36 >> mumudvb -d -c /root/42/11557 >> >> root 8154 8.4 0.6 37516 21120 ? SLl Apr29 304:43 >> mumudvb -d -c /root/42/11957 >> >> root 10964 5.6 0.6 37484 21088 ? SLl 11:50 31:36 >> mumudvb -d -c /root/19/12544.75 >> >> root 13578 6.9 0.7 40092 23680 ? SLl 10:10 45:38 >> mumudvb -d -c /root/13/12520 >> >> root 19671 0.0 0.0 112644 932 pts/12 R+ 21:11 0:00 grep >> --color=auto mumudvb >> >> root 24324 3.2 0.6 103040 21116 ? SLl Apr29 116:15 >> mumudvb -d -c /root/42/12525 >> >> root 27398 7.7 0.6 37508 21112 ? SLl 10:25 50:11 >> mumudvb -d -c /root/19/12187.50 >> >> root 32246 3.3 0.6 103124 21200 ? SLl Apr29 110:28 >> mumudvb -d -c /root/42/11096 -v --card7 >> >> >> >> -- >> >> Volkan Çelebi >> >> IT System Spezialist >> >> Heimstr. 10 >> >> 8953 Dietikon >> >> Tel: +41 788 488 319 >> >> -- >> >> To unsubscribe: >> >> https://lists.nongnu.org/mailman/listinfo/monit-general >> > >> > >> > -- >> > To unsubscribe: >> > https://lists.nongnu.org/mailman/listinfo/monit-general >> > >> > >> > >> > -- >> > Volkan Çelebi >> > IT System Spezialist >> > Heimstr. 10 >> > 8953 Dietikon >> > Tel: +41 788 488 319 >> > -- >> > To unsubscribe: >> > https://lists.nongnu.org/mailman/listinfo/monit-general >> >> >> -- >> To unsubscribe: >> https://lists.nongnu.org/mailman/listinfo/monit-general > > > > > -- > Volkan Çelebi > IT System Spezialist > Heimstr. 10 > 8953 Dietikon > Tel: +41 788 488 319 > -- > 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
