[Anand Raghavan]

We experienced a similar problem to yours with a couple of our interfaces using VPN. As Chris suggested, you have to adjust the tcp_keepidle parameter.

We run CL 5.6 on IBM AIX 5.3.   We contacted our System Admin to change the tcp_keepidle command to 1800 half seconds (you need root access to change that)

Here is our setting:

---

$ uname -a

AIX ieprod 3 5

$ no -a | grep tcp_keepidle

            tcp_keepidle = 1800

---

Hope that helps.

[Anand Raghavan]

David Burks from Healthvision got back to me immediately.  We use the client on the Windows Platform so I had to change the brand.txt on the PC, although we run the Cloverleaf Engine on AIX 5.3.  

Thanks David for setting me straight.

Johnny, please email me and I can help you with the problem.

[Anand Raghavan]

I did exactly as listed on this forum.

I made my edits to brand.txt and did not see the change in the GUI

So, I stopped all the processes, stopped the Lock Mgr & Monitor Daemon and restarted everything.   The GUI still shows the 972 xxx xxxx number.

We are running Cloverleaf 5.6 on AIX 5.3.

I am sending a ticket to Support.

Thanks,

[Anand Raghavan]

Rob,

Do we have to bounce the hostserver ? I made the edits to brand.txt and still see the old 972 number in the GUI (Help –> Support)

Thanks,

[Anand Raghavan]

BTW,  we ran into a problem with interfaces via VPN.  If there is little or no traffic for extended periods of time, the VPN used to time out and disconnect.

We run Cloverleaf 5.6 under AIX 5.3

There is a limits file called /etc/security/limits owned by “root”.  

We had get our UNIX admin to adjust the tcp_keepidle parameter

For example:

the default value in the file was

tcp_keepidle=14400

This parameter is measured in half seconds.

We reduced it to 600 (5 minutes).   So, every five minutes the OS would send a keep alive packet to maintain a persistent connection

Hope this helps out someone.

-Anand

[Anand Raghavan]

Jim,

That is a good point.  There is another way to do it if you are running Cloverleaf under UNIX.

For example, I make my edits to a version of NetConfig called NetConfig.axr143.

If you look at the “notes” directory underneath the site:

---

$ pwd

/hci/qdx5.6/integrator/adt_in_prd/notes

$ ls

NetConfig         NetConfig.axr143

---

I perform a recursive copy of the contents of the “NetConfig.axr143” directory to “NetConfig” underneath the notes directory, as it is safer than working on the actual NetConfig file.

[Anand Raghavan]

For the person who is experiencing X-windows issues.   I had to deal with this a week ago and to avoid any more headaches for people, here are some tips.  

We run Cloverleaf on IBM AIX (Unix 5.3) and we use the Cloverleaf Client on Windows to communicate.  Some utilities like hciupgradeutility, hciserveradmin on the UNIX servers require GUI windows.  

I installed Cygwin/X on my PC. Cygwin/X is free and an is an X-Window emulator that is for Windows.  Once installed, please start the X-Win server and type

xhost +

Here is a sample session on my PC:

---

axr143@WMDCINT02 ~

$ xhost +

access control disabled, clients can connect from any host

---

Some security folks may balk at the result above but make sure you dont enable this for a long time. Just close X-Win server as soon as your done.

Now, on the UNIX machine, you need to type this

---

> export DISPLAY=172.22.35.22:0

---

Obviously, your PC’s IP address needs to be input there

Now, , you can type

hciserveradmin or hciupgradeutility at the command prompt on your UNIX machine and you will see the GUI windows.  

Hope this helps out people.  

It took me a day to get all this since Cloverleaf does not publish all this information, as these are site specific instructions.

These are just tips and tidbits I picked up from my colleagues and posted it here.

[/b]

[Anand Raghavan]

Keith is right.  I would talk to the foreign system that is sending you the message and ask them if they changed something (if this problem just cropped up).

Also, you could perform an octal dump of the offending message and see what characters are being sent.

[Anand Raghavan]

Thanks Max!

Their techsupport has always been amazing.  I have called them at odd hours in the night and they have gotten back to me in less than 30 minutes.

It is nice to talk to a real person in this day and age of IVR (interactive voice response) systems.

[Anand Raghavan]

We ran into this issue as well.  It is most probably caused by files/directories not being owned by the user “hci”.  Someone may have installed the Cloverleaf application as “root”.

The best possible solution would be to shut down all the processes, shutdown the monitor daemon and lock manager and run the

hciverify -F command.

You need to have root access to run the hciverify -F command.

Hope that helps.

[Anand Raghavan]

I would also try

append obxlist2 “$fields+” in place of

append obxlist2 “$field “

as it makes for more readable code.  To someone else (apart from the coder) reading it, it is easy to miss the whitespace.

Just a suggestion

[Anand Raghavan]

Also check your TCL scripts.  If you have two CONTINUE statements in your TCL script, it may cause the above error.   You should only use it once per message.  Hope that helps.

[Anand Raghavan]

Please check into the

tcp_keepidle parameter that is set by the Unix Administrator.  We had to reboot the box as this parameter affects new TCP connections (does not affect exisiting TCP connections)

We had a similar problem.  After we adjusted our tcp_keepidle parameter, it resolved our issue(s).

This parameter is usually set in half-seconds.   We set it to 14400.

BTW, our CloverLeaf runs on IBM-AIX.

Thanks,

Anand

[Author]

Replies