similar to: Timer Daemon doesn't start

Hi, im trying to execute multiple cmds in a method that use the same view which has multiple calls to the same partial inside it. However i cant get it to work correctly, so any help here would be appreciated heres the controller code def index cmd_df = "df -Ph" exec_cmd(cmd_df) cmd_sys = "uname -a" exec_cmd(cmd_sys) end private def exec_cmd(cmd)

On Dec 4, 2013, at 3:35 PM, Roger Price wrote: > I would like nut to become more loquacious, and to log a much more complete report of its activity. At present nut reports that its components have started operation but does not automatically log their activity when UPS's switch between OB and OL. I believe that this under-reporting of important facts is too minimalist - it would be

Hi Eric, > NRPE: Error receiving data from daemon > Seems as this is not a SSL Problem. Do you have a nagios user account? Cat > /etc/passwd Yep! Both hosts have nagios user accounts. Demonstrating from the client: [root at ops:~] #id nagios uid=2002(nagios) gid=2002(nagios) groups=2002(nagios),2008(nagioscmd) And this is from the monitoring server: [root at monitor1:~] #id

> > Oh my mistake. I mean nrpe without parameters. It should say something > about SSL/TLS aktiv or so. > You could test nrpe without SSL. Use nrpe -n - H host This is what I see about ssl if I just run nrpe on the client without any flags: [root at ops:~] #nrpe| head -8 NRPE - Nagios Remote Plugin Executor Copyright (c) 1999-2008 Ethan Galstad (nagios at nagios.org) Version: 2.15

> > is it working on localhost or not???!!! it could be selinux problem also, > if context is not correct. It's working on localhost: [root at puppet:~] #telnet localhost 5666 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. I notice if I stop the firewall on the puppet host (for no more than 2 seconds) and hit NRPE from the monitoring host it works:

Eero, where did you installed this nrpe package? is selinux running enforcing > mode (getenforce command), try disabling with setenforce 0. why you are > running it under xinetd as usual way is to run it as nrped daemon. > For NRPE I usually do a source install with these flags: ./configure make all make install-plugin make install-daemon make install-daemon-config make install-xinetd

I would like nut to become more loquacious, and to log a much more complete report of its activity. At present nut reports that its components have started operation but does not automatically log their activity when UPS's switch between OB and OL. I believe that this under-reporting of important facts is too minimalist - it would be better for system administrators and for the nut

well. how about trying default setting and running nrped without xinetd. -- Eero 2015-05-01 14:14 GMT+03:00 Tim Dunphy <bluethundr at gmail.com>: > > This is strange... > > Do you have SSL aktive on both systems? Run nrpr localy without > parameters > > (this should return some nrpe stats) and check ldd for libssl. > > > I don't seem to have that command.

Hi NRPE: Error receiving data from daemon Seems as this is not a SSL Problem. Do you have a nagios user account? Cat /etc/passwd Am 01.05.2015 18:45 schrieb "Tim Dunphy" <bluethundr at gmail.com>: > > > > Oh my mistake. I mean nrpe without parameters. It should say something > > about SSL/TLS aktiv or so. > > You could test nrpe without SSL. Use nrpe -n -

Hello, not sure if it is a scripting problem or an owner/group problem but when I try to send an email following en event using upssched-cmd, the script exits on the line where I send the email with this message in syslog : Mar 19 20:49:51 chaudron-nautique upssched[1377]: exec_cmd(/path/upssched-cmd onbatt1) returned 78 The log messages prior to the email (logger -t upssched-cmd message)

Mongrel clusters lets yuo pick a path to your logs with the "-l " switch. I tried giving a pathc that contains the rotatelogs like -l |/usr/sbin/rotatelogs /var/log/mongrel.log 3600" And it just gave me error. So I rolledup my sleeves and dig into: 1) /usr/lib/ruby/gems/1.8/gems/mongrel_cluster-1.0.5/lib/mongrel_cluster/init.rb 2)

Hi, I am currently implementing SSH ver1 client for my school work and testing it with OpenSSH servers. Unfortunately I cannot execute commands after succesful login without allocate pty. My client send SSH_CMSG_EXEC_SHELL packet on server, but dont receive any answer. According RFC defined SSH1, server should send SSH_SMSG_SUCCESS or SSH_SMSG_FAILURE message. So I tried send

> This is strange... > Do you have SSL aktive on both systems? Run nrpr localy without parameters > (this should return some nrpe stats) and check ldd for libssl. I don't seem to have that command. [root at monitor1:~] #find / -name "*nrpr" 2> /dev/null [root at monitor1:~] # And that's on either system. And if I do an ldd on both, this is what I can tell:

is it working on localhost or not???!!! it could be selinux problem also, if context is not correct. -- Eero 2015-05-04 1:55 GMT+03:00 Tim Dunphy <bluethundr at gmail.com>: > > > > It's listening on both IPv6 and IPv4. Specifically, why is that a > problem? > > > The central problem seems to be that the monitoring host can't hit nrpe on > port 5666 UDP.

Oh my mistake. I mean nrpe without parameters. It should say something about SSL/TLS aktiv or so. You could test nrpe without SSL. Use nrpe -n - H host Am 01.05.2015 13:18 schrieb "Eero Volotinen" <eero.volotinen at iki.fi>: > well. how about trying default setting and running nrped without xinetd. > > -- > Eero > > 2015-05-01 14:14 GMT+03:00 Tim Dunphy

This is strange... Do you have SSL aktive on both systems? Run nrpr localy without parameters (this should return some nrpe stats) and check ldd for libssl. Am 01.05.2015 07:32 schrieb "Tim Dunphy" <bluethundr at gmail.com>: > Hi Eric, > > Thanks for your reply. I do have nrpe running under xinetd on the host I'm > trying to monitor. > > And running the

> > It's listening on both IPv6 and IPv4. Specifically, why is that a problem? The central problem seems to be that the monitoring host can't hit nrpe on port 5666 UDP. [root at monitor1:~] #/usr/local/nagios/libexec/check_nrpe -H puppet.mydomain.com CHECK_NRPE: Socket timeout after 10 seconds. It is listening on the puppet host on port 5666 [root at puppet:~] #lsof -i :5666

Hey folks, Ok so I'm having another issue with SELinux. However I think I'm pretty close to a solution and just need a nudge in the right directtion. I wrote a puppet module that gets systems into bacula backups. Part of the formula is to distribute key/cert pairs with permissions that allow bacula to read them so that bacula can talk to the host over TLS. It's pretty slick, I must

Hi, am 7 Dez schrieb Charles Lepple: >> MONITOR dummyups at localhost 1 monmaster masterpass master >> MONITOR testups at localhost 0 monmaster masterpass master >> MINSUPPLIES 1 > To simplify, you could eliminate "dummyups" and use "MINSUPPLIES 0". Maybe there's a bug. To monitor an UPS wich doesn't supply power to a raspi I used: MONITOR

Hi Eric, Thanks for your reply. I do have nrpe running under xinetd on the host I'm trying to monitor. And running the nrpe checl locally: [root at ops:~] #/usr/local/nagios/libexec/check_nrpe -H localhost NRPE v2.15 [root at ops:~] #grep only_from /etc/xinetd.d/nrpe only_from = 127.0.0.1 216.120.248.126 And I do have port 5666 open on the security group for this host.