Article ID: 4197, created on Mar 24, 2008, last review on May 1, 2014

  • Applies to:
  • Sphera

Symptoms

 

The following errors are written to /var/log/messages:
Aug 2 21:00:22 localhost : sphera#0#saproxy/saproxy_select.cc#185#1445#16387#2005/08/02,21:00:22 #1123003620l#15#localhost.localdomain#saproxy#1#4###Internal mismatch in the select thread. Attempting to reset...
Aug 2 21:25:09 localhost : sphera#0#saproxy/saproxy_select.cc#185#1445#16387#2005/08/02,21:25:09 #1123009222l#15#localhost.localdomain#saproxy#1#4###Internal mismatch in the select thread. Attempting to reset...


 

Resolution

 

It seems that the source of this issue is a known bug in saproxy module.
As this issue with SAproxy was fixed after UP3 was released, we are providing you with a new SAproxy binary that should fix this situation.
Please find it attached.
 
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.


* Note! this solution is relevant for servers running SD 3.7 UP2 and above.  The problem is fixed in SD 3.7 UP3.

Note #2 The new-saproxy is attached to this article

 

Attachments

5f478287f7e74fe9b07217d8131cd741 6311ae17c1ee52b36e68aaf4ad066387

Email subscription for changes to this article
Save as PDF