CPRS connectivity problem:WSAETIMEDOUT

[pratik bandal]

Hi All,

I am getting Error WSAETIMEDOUT while connecting CPRS to VistA.
Below is the Error:
Error Encountered
Function was:recv
Error was:WSAETIMEDOUT

I am able to telnet to the port to which are connecting the application.
When i do 'telnet localhost 9230' it hangs for some time and close the connection(approximate hang period is 20 seconds)

I also checked TASKMAN in VistA which is showing as running.

I am suspecting that problem is associated with linux server(Red Hat Enterprise Linux Server release 5.10 (Tikanga)) .

I observed same problem with different versions of GT.M i.e.5.4002A ,V6.0003 and V6.2-002A.

Is there any server parameter which can cause this problem?

Below is the output of selinux status,
$ /usr/sbin/sestatus
SELinux status:                 disabled

Below is the result of ZPRINT BREAD+6^XWBRW:BREAD+12,

 U XWBTDEV
 F  D  Q:DONE
 . S S=L-$L(R),R=R_$E(XWBRBUF,1,S),

XWBRBUF=$E(XWBRBUF,S+1,999999)
 . I ($L(R)=L)!(R[$C(4))!(C>TO) S DONE=1 Q
 . R XWBRBUF#S:2 S:'$L(XWBRBUF) C=C+1 S:$L(XWBRBUF) C=0 I +$DEVICE S DONE=1
 . I $G(XWBDEBUG)>2,$L(XWBRBUF) D LOG^XWBDLOG("rd: "_$E(XWBRBUF,1,252))
 . Q


I also checked for XTERs,but didn't found any.

[Nancy Anthracite]

What is your setup? Are you running a virtual machine on an instance of Windows or what exactly? And what vdrsion of VistA are you using?
-- Nancy Anthracite

Sent from my Android device with K-9 Mail. Please excuse my brevity.

>--
>--
>http://groups.google.com/group/Hardhats
>To unsubscribe, send email to Hardhats+u...@googlegroups.com
>
>---
>You received this message because you are subscribed to the Google
>Groups "Hardhats" group.
>To unsubscribe from this group and stop receiving emails from it, send
>an email to hardhats+u...@googlegroups.com.
>For more options, visit https://groups.google.com/d/optout.

[pratik bandal]

Hi Nancy,

It is a physical server having (Red Hat Enterprise Linux Server release 5.10 (Tikanga) installed on it.
We are using WorldVistA1.

[Nancy Anthracite]

You should probably be using WorldVistA 2.0 or the Alpha of the 2.5 release, depending on what you are doing. However, whatever the case, if you are using a physical server and localhost is working from inside with telnet, you almost certainly have an issue with the route to the machine. Try testing telnet from the outside.

 

--

Nancy Anthracite

> > <javascript:>

> >

> > >---

> > >You received this message because you are subscribed to the Google

> > >Groups "Hardhats" group.

> > >To unsubscribe from this group and stop receiving emails from it, send

> > >an email to hardhats+u...@googlegroups.com <javascript:>.

[pratik bandal]

Hi Nancy,

I have checked telnet from outside as well,it is working fine.
The request is also reaching the application programs on the server.
First XWB is assigned value [XWB] and code reaches New style broker NEW^XWBTCPM,
after a while XWB is assigned value {XWB} and then reaches the old style broker OLD^XWBTCPM1.
I am have also taken ZJOB of the CPRS process ,PFA.

[Sunil Arora]

May I suggest that you may check the firewall settings or maybe for time being for testing sake, just disable your firewall and see if it works..

Regards

-

Sunil

--

--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

*


P*lease consider the environment before printing this document and/or any
attachments it may contain.

[Nancy Anthracite]

That is a problem that it is going to the old style broker. Look at the log in EHR, presuming that you were using the directions for installing WorldVistA EHR. Also, I think you already said you looked at D ^XTER, correct,

 

--

Nancy Anthracite

 

On Friday, December 04, 2015 04:50:12 AM pratik bandal wrote:

> Hi Nancy,

>

> I have checked telnet from outside as well,it is working fine.

> The request is also reaching the application programs on the server.

> First XWB is assigned value [XWB] and code reaches New style broker

> NEW^XWBTCPM,

> after a while XWB is assigned value {XWB} and then reaches the old style

> broker OLD^XWBTCPM1.

> I am have also taken ZJOB of the CPRS process ,PFA.

>

> On Friday, December 4, 2015 at 6:00:32 PM UTC+5:30, Nancy Anthracite wrote:

> > You should probably be using WorldVistA 2.0 or the Alpha of the 2.5

> > release, depending on what you are doing. However, whatever the case, if

> > you are using a physical server and localhost is working from inside with

> > telnet, you almost certainly have an issue with the route to the machine.

> > Try testing telnet from the outside.

> >

> >

> >

> >

> > Nancy Anthracite

[pratik bandal]

Hi Nancy,

Yes,I also believe that it is going to the old style broker which is causing the problem.
We have been using this EHR instance ,which used to work fine,we also used to connect CPRS.
But suddenly some parameter got changed and we started getting this error.
Can there be some server level parameter which can cause this or any file permission issue?

[pratik bandal]

Hi nancy,
Also,We didn't found any XTERs.

[Nancy Anthracite]

I am not aware of what on the server might be causing the problem. This is the same machine, same network, etc. that you were using previously? Did you start patching WorldVistA EHR and run into trouble?

 

Also, are you logging the connections with an error setup as suggested. If not, try running your script that gets called by XINETD from the command line and see what you get for an output. It should not work, of course, but there may be a hint in the log regarding permissions, etc.

 

Can you figure out from the log what RPCs were was called after which it switched over to the old broker?

 

--

Nancy Anthracite

[pratik bandal]

Hi Nancy,

We were trying GT.M newer version testing,

For performing database backup we had attached new external disc to the server,before that CPRS and other application connectivity was fine with latest(V6.2-002A) as well as older GT.M(5.4002A) version.

I am also checking permissions.

[Nancy Anthracite]

Did you do your backup with Mupip backup? If you didn't and you are using he backup to test, then that may be your problem. Also, I don't know how to handle using mupip backup to then stand up a new test instance when journaling is running although I expect it it possible.

 

--

Nancy Anthracite

[pratik bandal]

Yes nancy,

Backup was taken using mupip backup.

Same backup works fine on other servers.

[Bhaskar, K.S]

Here's what I see as the salient points:

• This is a system that used to work, but no longer works.
• The observable symptom is that when CPRS tries connecting, the client reports a WSATIMEDOUT error. A telnet to the port both from the local machine and an external machine connects, hangs for about 20 seconds, and then disconnects. This means that the connection is being accepted by the server, goes through [x]inetd, and starts the RPC broker process. So, there are no network or OS issues.

This means that having established a TCP connection, the client and RPC broker fail to communicate. This is what needs troubleshooting, and if Pratik is right that the old style broker is running, that explains the problem (though not the solution). Some questions for Pratik:

• When you "I also believe that it is going to the old style broker" how do you know that this is what is happening?
• Exactly what changes were made between the system that worked and the system that doesn't? It's hard to believe that just adding disk drives made VistA stop working. Was there some other change (e.g., a change to the machine name - if you do that, you have to reconfigure VistA)?

Regards
-- Bhaskar

--

--
http://groups.google.com/group/Hardhats
To unsubscribe, send email to Hardhats+u...@googlegroups.com

---
You received this message because you are subscribed to the Google Groups "Hardhats" group.

To unsubscribe from this group and stop receiving emails from it, send an email to hardhats+u...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
GT.M - Rock solid. Lightning fast. Secure. Pick any three.

_____________
The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you.

[pratik bandal]

Hi Nancy,

This issue has been resolved.

We changed the port which we were using for connecting the application and now it is working fine.

[Nancy Anthracite]

Great! I have been running all of the things I wanted to look at through my head and that was ot one of them so I am vlad you found it. Be sure to mention it on Hardhat so others will benefit.

-- Nancy Anthracite

Sent from my Android device with K-9 Mail. Please excuse my brevity.

[pratik bandal]

Yes,nancy.
This is updated on hardhats.
Also thanks for your support on this issue.

[pratik bandal]

Hi Bhaskar,

This issue has been resolved.
We changed the port which we were using for connecting the application and now it is working fine.

Also thanks for your valuable suggestions and time
Regard,
Pratik Bandal