Forum Discussion
Get HTTP Monitor
If that doesn't work, the best way to figure out what you need is to enable monitor logging and watch the log for the RECV string.
There's SOL12531 that talks about monitors a little bit, and then this article that adds a little extra information.
- Open the pool that is having the problem (let's call it MY_POOL)
- Make sure the monitor is active on the pool (let's call it MY_MONITOR)
- On the Members tab in the pool settings, click on one of the members (let's call it 10.0.0.1:443)
- Enable the checkbox for Monitor Logging
-
Open an SSH session (I use Putty to connect) to the device and log in to the shell.
- Run the command cd /var/log/monitors
- Run the command ls -l
- Look for the file referencing your pool and member (most likely in our example it'd be something like _Common_RDP_MONITOR__Common_10.0.0.1_443.log)
- Run the command tail -f FILENAME (where FILENAME is the log filename)
- It may be visible immediately, but you should see where the monitor sends the request to the server (and you'll see the send string), and you're looking for the recv string that comes back.
- Take that recv string and update the monitor and see if the pool member(s) show up green again.
-
Go back in and disable the monitor logging for that member so you don't have excessive logging filling up space.
This should help figure it out. If your log file ever looks like it's not updating, delete the file and remove the monitor from the pool and re-add it. I've found that will kick it back off again.
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com