This seems like a common enough issue, but I couldn’t find what I wanted to do in my search. I can copy and paste this command form the result page and run it from the icinga2 server and it finds the check_ping just fine.Ĭan someone help point in the right direction. Dynamic Port Forwarding: Use Your SSH Server as a Proxy. the command will prompt me type password: Proxy password for usernamehttpproxy: but nothing happened after my type. Then made this: object CheckCommand "proxy-hostalive" /check_ping) failed: No such file or directory i want to ssh the server via a security http proxy whth command like this: ssh -o Prox圜ommand'nc -X connect -x httpproxy:port -P username h p' usernameserver. I made a host with check_command = "proxy-hostalive" Keep in mind that in order to bind to low ports (like 80 or 443 ), youll need to SSH as root. To avoid having to log on twice, first to another login node in the VSC network and then from there on to Muk, one can set up a so-called ssh proxy. I am having trouble replicating this in icinga2. This will bind :80 to your localhost:8080. We made a custom hostalive in nagios previously to go through this. For a simple proxy, ssh with port forwarding can be used. For example: ssh -D 12345 myuserremotesshserver. I can’t install agents, and there is no VPN between them, the networks are isolated except for this single point of entry through SSH. If the proxy environment variables are set for the user only they will get lost when running commands with sudo. SOCKS is built in to OpenSSH, so its a trivial matter to set up a local SOCKS proxy with the -D flag. Many are other networks that I have to ssh through to a single machine and then run checks from there.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |