[gentoo-user] Re: nagios remote host

2012-11-26 Thread Moritz Schlarb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

You have to configure nrpe on the remote host you want to monitor.

E.g. you want to execute check_load on the remote host - to get this
working, you have to tell the nrpe server that check_load means.
In a normal environment, the check name is the only parameter you can
pass to a remote nrpe plugin for security reasons.

Am 23.11.2012 20:59, schrieb Joseph:
 Is there any easy documentation how to configure nagios on Gentoo
 to monitor remote host? The documntation below is out of date: 
 http://www.gentoo.org/doc/en/nagios-guide.xml
 
 I have emerged nrpe and started on both server and client, is it
 correct? On the server I have created directory: 
 /etc/nagios/objects does this directory have to have ownership
 nagios:nagios ?
 
 Inside this directory I have have created files: nrpe-command.cfg 
 define command { command_name check_nrpe command_line
 $USER1$/check_nrpe -H $HOSTADDRESS$ -c $ARG1$ }
 
 nrpe-hosts.cfg define host { use linux-server host_name
 clinic-atom alias Gentoo Linux Web Server address 192.168.141.1 }
 
 nrpe-services.cfg define service { use generic-service host_name
 clinic-atom service_description Current Load check_command
 check_nrpe!check_load }
 
 define service { use generic-service host_name clinic-atom 
 service_description Root Partition check_command
 check_nrpe!check_disk }
 
 On the client I just emerge nrpe and started it. Why isn't it
 working?

- -- 
Moritz Schlarb
-BEGIN PGP SIGNATURE-
Version: GnuPG v2.0.19 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQEcBAEBAgAGBQJQs1GcAAoJEEXT29373YiIcckIAIa3WjuzuJNFKOmDn19s3cgo
vhtRixm41hqrOgTIkMDHGmDLREAhFim07+dYlYvZLUqxRykoGZt+0XBMBscvF7h/
afXXMtO21M+MT0QG6nl+eHvv6/avmuCoJ0d5FBJyxDzTw/AxyR2nDLstIeGYlr+h
P2SItcR3PElB3VraMIr8HnthYIwgPw0ApAX8NtU+/b8pKSAYZjIUX0bZ7NLqR+ZS
GjEI+B3BLNb8yW7egyfGXUpBhG5aEwP1dBfAQT4QazGDidnWlIGdY9YWSZoO3T+t
OdIicRuDghF0kXx6EzB5RNMppLZavhszWppbzgArImCGji41FzLRVbFYG1F9Ow8=
=0P9g
-END PGP SIGNATURE-



[gentoo-user] Re: Failed to emerge dev-lang/python-2.5.4-r4

2011-09-14 Thread Moritz Schlarb
Hey Wonko,
thanks for your answer...

I played around and found that there's a place in the Makefile, where
various PATHs are set, but not LD_LIBRARY_PATH, so I set it myself, and
continues by hand and it worked
I already wanted to file a bug, so I ran emerge again to get the build
logs again, but then emerge ran fine...

So... Nevermind! ;)

Am 14.09.2011 02:52, schrieb Alex Schuster:
 Moritz Schlarb writes:
 
 
 /usr/bin/install -c -m 644 pyconfig.h
 /var/tmp/portage/dev-lang/python-2.5.4-r4/image//usr/include/python2.5/pyconfig.h
 emake failed
  * ERROR: dev-lang/python-2.5.4-r4 failed (install phase):
  *   emake altinstall maninstall failed
 [...]
 Doesn't make much sense to me, failing at installing to
 python2.5-specific directories... I would investigate further, but I
 don't know how to make portage tell me more about the error that
 occured! But I'm eager to learn, would be great if someone could tell
 me where to look for debugging infos.
 
 Look at yout build.log, line 942, a libpython2.5.so.1.0 cannot be found.
 I don't know why, and I have no time to look further right now. I'd try
 again with MAKEOPTS=-j1 in case something was executed out of order and in
 parallel, but that's just a tip, no idea if this might help. Look
 in /var/tmp/portage/dev-lang/python-2.5.4-r4/image/ and check if this
 library exists, and maybe try to do by hand what failed in the build log.
 
 Sorry, my time is up,
 
   Wonko
 
 

-- 
Moritz Schlarb




[gentoo-user] Failed to emerge dev-lang/python-2.5.4-r4

2011-09-13 Thread Moritz Schlarb
Hi at all!

For using Google App Engine, I wanted to emerge Python 2.5, so I did
emerge -av =dev-lang/python-2.5.4-r4
and everything went fine, until:
/usr/bin/install -c -m 644 pyconfig.h
/var/tmp/portage/dev-lang/python-2.5.4-r4/image//usr/include/python2.5/pyconfig.h
emake failed
 * ERROR: dev-lang/python-2.5.4-r4 failed (install phase):
 *   emake altinstall maninstall failed
 *
 * Call stack:
 * ebuild.sh, line  56:  Called src_install
 *   environment, line 5753:  Called die
 * The specific snippet of code:
 *   emake DESTDIR=${D} altinstall maninstall || die emake
altinstall maninstall failed;

Doesn't make much sense to me, failing at installing to
python2.5-specific directories... I would investigate further, but I
don't know how to make portage tell me more about the error that occured!
But I'm eager to learn, would be great if someone could tell me where to
look for debugging infos.

I've uploaded:
complete build log: https://www.dropbox.com/s/t47wn56vtynlh3y/build.log
ebuild environment file:
https://www.dropbox.com/s/p1zdtxzewuc0745/environment
emerge --info =dev-lang/python-2.5.4-r4:
https://www.dropbox.com/s/8ran13tlk32p8f0/info
emerge -pqv =dev-lang/python-2.5.4-r4:
https://www.dropbox.com/s/rscag1azv3j5dwn/pqv

Looking forward to some instructions...
Regards,
Moritz



[gentoo-user] Re: Wireless Configuration...

2011-09-09 Thread Moritz Schlarb
Am 07.09.2011 16:06, schrieb Michael Mol:
 I believe NetworkManager provides WPA supplicant functionlaity, so I
 don't think you need wpa_supplicant if you have NetworkManager. It's
 been a *long* time (about five years) since I messed with wireless
 configuration daemons, though. Lots of things can change in that time,
 including memory...
 

I don't think so! NetworkManager generates a configuration file on the
fly for wpa_supplicant, so you still need it, you just don't need to
configure it anywhere else than NetworkManager!

Regards
-- 
Moritz Schlarb