Jun 27 12:13:05 localhost : sphera#0#saproxy/saproxy_select.cc#185#1445#16387#2009/06/27,12:13:05 #1123003620l#15#localhost.localdomain#saproxy#1#4###Internal mismatch in the select thread. Attempting to reset…
Jun 27 12:17:03 localhost : sphera#0#saproxy/saproxy_select.cc#185#1445#16387#2009/06/27,12:17:05 #1123009222l#15#localhost.localdomain#saproxy#1#4###Internal mismatch in the select thread. Attempting to reset…
The issue is a known bug in saproxy module.
As this issue with SAproxy was fixed after UP3 was released, The new SAproxy binary that should fix this situation.
http://kb.parallels.com/Attachments/3835/Attachments/saproxy-new.zip
Please follow the procedure below for installation (replacement of the existing SAproxy):
1. cd SPHERA_BASE/bin directory
2. mv saproxy saproxy-old
3. mv saproxy-new saproxy
4. killall -9 saproxy
This procedure would cause no SD or server downtime.
As you kill saproxy process, watchdog would restart the new saproxy and everything will be in place.
No comments:
Post a Comment