Run ssh forwarding command before nagios command [closed] - linux

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I have a number of machines which I would like to check using my Nagios box. They sit behind a machine which is reachable from my Nagios box; all are running Linux. These machines have no routing to outside networks. If I need to reach the machines manually I either ssh to the intermediate box and then ssh to the other machines, or I'll use ssh to forward a port.
I usually use SNMP for most of my checks. So my thought is that prior to my Nagios box running a check I could have it run a command to forward the needed port, then get rid of the forward when done. Can anyone guide me on the best way to do this?
Thanks!

You probably want to look into Nagios passive checks. As described in the documentation:
Passive checks are useful for monitoring services that are:
Asynchronous in nature and cannot be monitored effectively by polling
their status on a regularly scheduled basis
Located behind a firewall and cannot be checked actively from the monitoring host
Your use case is pretty clearly the second one.

Related

How can I SSH remotely into my linux VirtualBox? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I am trying to remotely access a virtual box remotely. Because this is a virtualbox hosted on a windows machine, it does not have it's own IP address to use for SSH login. I have tried changing the network settings to Bridge Adapter to get an IP, but nothing has worked. Are there some steps I am missing, or what else can I do to SSH into the box? Thanks.
If you were using the NAT mode before and you have no reason to change it other then the SSH, you can do it in that mode. Just expand the advanced settings in the network configuration and create a port forwarding rule for the port 22. Then you will be able to SSH to the VM by using the host's ip address.

Run SSH without ANY Authentication [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 6 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I know it flies in the face of the very notion of a "secure shell," but I would like a way to run SSH that requires absolutely no authentication whatsoever. I have a collection of machines that run on a totally air gaped network. It's used for a hardware prototyping project, and for reasons beyond my understanding some of these machines occasionally start asking for a password regardless of the fact that they have all been cloned with the same SSH keys that work some times.
I'd really like to side step all the security issues that can prevent SSH from connecting to a machine. I've seen in other posts people strongly recommending against what I am trying to do; but I've wasted enough time trying to fight SSH's security features. Is there a flag I can use? A change to a config file? Another version of SSH I can install?
Any help would be appreciated.
It seems that you want a 'remote shell', so try rsh.

Explanation of ssh command with option -D [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
I am studying ssh and I haven't understood the following command with option D
ssh -D 9999 username#remotehost.net
can someone explain what this command does exactly with an example and when it is useful?
This will forward all packets to remotehost.net from localhost:9999 (in your example). In a nutshell this is socks proxy.
From ssh man page:
Specifies a local “dynamic” application-level port forwarding. This works by allocating a socket to listen to port on
the local
side, optionally bound to the specified bind_address. Whenever a connection is made to this port, the connection is
forwarded over
the secure channel, and the application protocol is then used to determine where to connect to from the remote machine. Currently
the SOCKS4 and SOCKS5 protocols are supported, and ssh will act as a SOCKS server. Only root can forward privileged ports.
Dynamic port forwardings can also be specified in the configuration file.

How is the VM and the local machine connect with each other? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 7 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
VM
I have a web service that need to run on CentOS VM.
Mac OS X
On the other hand, I have a Laravel project running my Mac OS X in local machine through MAMP.
The project working great with MAMP. Now, I need to make a API call to the web service that're currently running in the VM.
I'm curious how is the VM and the local machine connect with each other.
How do I solve that ?
I'm not a linux/VM expert.
Any hints / suggestion on that will be much appreciated !
After a couple days of researching and experimenting, I be able to do it.
grabbing the IP
run ifconfig and look for inet addr:172.16.67.137 of eth0
Disabled firewall on the VM
Result
On a Mac just go to that URL

Alternatives to "reboot" after changing crucial files in a working server? [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
Closed 9 years ago.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Improve this question
Assume I have a server already functioning and providing an app to users. At one moment, I have to modify some crucial /etc/ configuration files. For example, /etc/security/limits.conf.
After I do the changes, documentation usually suggests rebooting the machine.
reboot
But this would imply that all processes in the server die, am I right? So, basically what will happen to the guys checking my app hosted on the server that I just "rebooted"? I think the service will stop for a while. Is there any other command or alternative less painful to do after changing crucial files?
I'm on CentOS & Nginx.
PD: If somebody could provide also a link to the difference between "shutdown" and "reboot" (because I found only some vague things), that would be great.
Easy part first - if you run shutdown your computer ends up being off. As in no power. As in, very difficult to fix remotely :). Reboot restarts everything.
It is fairly rare to require a reboot under linux - the only reason to reboot that I can think of is if you upgraded the kernel, if your machine is crashing really badly, or if you want to install some types of new hardware (RAM, plug-in cards etc).
Mostly, when you edit "important files in /etc", you can restart just a part of the system. For example, you might need to restart just your webserver.
There is no complete rule. Try googling "reload ". For example, googling "reload /etc/security/limits" suggests logging out, then logging back in.

Resources