I forgot another simple but also not perfect option:
- Just monitor the availability of the remote port (21) using the TCP Socket plugin
Given the fact that you seemed to be willing to actually monitor a file transfer and not only the server response, I suppose that will not be a sufficient solution, just as some of the other suggestions I made.
On 30.11.2012, at 18:08, Peter Eckel <lists@eckel-edv.de> wrote:
On 29.11.2012, at 23:01, rwmastel <hq-users@hyperic.org> wrote:
>> Unrecognized SSL message, plaintext connection
Could it be that the remote server is not a standard FTP server but 'speaks' only FTP over TLS (http://tools.ietf.org/html/rfc4217)? The plugin doesn't support this, I'm afraid.
In this case you have several options, e.g.:
- Check whether the remote server also supports plain text FTP on a different port
- Set up an SSL tunnel to the remote server (e.g. using Stunnel)
- Write a script (as outlined before) that runs the test connection and use it in the Script-Plugin or in a custom XML plugin (depending on your requirements)
- Write an enhancement request to VMware to support FTPS and wait for it to be implemented