Getting annoyed with broken pipe errors

[webaus]

We have been finding that almost daily our plesk 8.2.0.4 installs under windows 2008 are having broken pipe errors:

get_config_string failed: PRODUCT_DATA_D: The system cannot find the file specified. (Error code 2) at Unable to connect to pipe \\.\pipe\psapipe

is there a way to prevent these from occuring as they are getting a bit annoying and without any apparent way of remotely monitoring plesk services we end up finding out from clients half the time that the service is down

 

[Amin Taheri]

Try upgrading to Plesk 8.6 and see if it keeps occuring. i would also invest in a third party monitor or at least one that doesnt reside on the same server its supposed to monitor.

 

[webaus]

sorry that was a typo we are running 8.6.04 and it happens on all our Plesk servers from time to time but seems to mainly affect the windows 2008 servers

Im not aware of any monitoring services designed to monitor plesk services itself remotely?

what are they?

 

[Amin Taheri]

Im not sure about things specifically designed for plesk but you can find monitoring for specific services - for example you can do a basic http GET against port 80/443/8443 and make sure you get back a result, and in some cases you can even check against page content to make sure that the page loads and not a 500/404 error for example.

The ones that I am aware of are all really expensive becuase we have hundreds of servers, so I dont look at the cheap stuff. But I do know that there are several out there.

I'm sorry I cant be more helpful though.

 

[webaus]

yeah we use a redundant and clustered Nagios setup for all port monitoring and thats fine.

The problem with trying to monitor plesk is that the broken pipe error occurs after you try and authenticate on port 8443 so any port monitoring of it will show it as up

I have seen plenty of Plesk Linux monitors but not one for Windows

 

[JTRipper]

same exact problem here after upgrading from 8.2 to 8.6 :-(
any ideas ?
anyone ?