ca-erp-sessionlinker Throwing 00515-ERR: Error occurred while evaluating link

[venkata Kishore Babu Bellam]

Can some one please explain What These errors means in Session linker logs, On Daily basis we are seeing these errors in session linker access logs.

 

Thu Oct 19 01:07:40 2017-12320946:26215-ERR: No data available... timeout

Fri Nov 10 10:32:52 2017-11468976:00772-ERR: Error determining whether response is available.
Fri Nov 10 10:32:52 2017-11468976:00772-ERR: Error occurred while evaluating link
Fri Nov 10 10:32:52 2017-11468976:00515-ERR: Failed to write all data!
Fri Nov 10 10:32:52 2017-11468976:00515-ERR: Error occurred while evaluating link
Fri Nov 10 10:32:58 2017-11468976:00515-ERR: Failed to connect
Fri Nov 10 10:32:58 2017-11468976:00515-ERR: Error occurred while evaluating link

 

And we are seeing below Error messages in linkerdaemon.log

 

Wed Nov 15 04:02:10 EST 2017 startsessionlinker.sh called. Checking to see if Daemon is running....
Wed Nov 15 04:02:10 EST 2017 Named Pipe File not found. Proceed with startup.
Wed Nov 15 04:02:10 EST 2017 Starting Session Linker Daemon.
Wed Nov 15 04:02:11 2017-18415680:01029-ERR: Accept failed with code -2
Wed Nov 15 04:02:11 2017-18415680:01029-ERR: Error code from accept() is 'No such file or directory' (2)
Wed Nov 15 04:02:11 EST 2017 Session Linker Started.

 

As you know session linker has two types of logs

1. linkerdaemon.log(Startup/stop log)

2. SessLinkInit Log (session linker access log) 

 

We need some help on how to use below session linker tools , if any specific docuement which explains how to use it and test.

 

The SessionLinker Daemon (sessionlinkd), which runs on UNIX web servers, can be tested independently of the Apache module by using the following test tools:
■ testclient
■ swarmconnect

[Patrick Dussault]

Hi Bellamkishore,

You reported this :

 "And we are seeing below Error messages in linkerdaemon.log

  Wed Nov 15 04:02:10 EST 2017 startsessionlinker.sh called. Checking
  to see if Daemon is running.... 
 
  Wed Nov 15 04:02:10 EST 2017 Named
  Pipe File not found. Proceed with startup."

Are both Web Agent, startsessionlinker.sh and Web Server running with
the same user ? If not, could you insure that all 3 runs with the same
user ?

Best Regards,
Patrick

[venkata Kishore Babu Bellam]

I.H.S Webserver & SIteminder Webagent running as same user

 

sessionlinkd process running as root user. 

 

From last 10 years those processes running as above only ( Webserver, webagent process running with Same User, sessionlinkd process running as root user)

[Stephen McQuiggan]

Interesting root for ten years - The webserver and sesisonlink inter-processing communication is recommended to run as the same user.  Suggest setting this is lower environment to see if errors no longer occur 

[venkata Kishore Babu Bellam]

Hi Stephen,

 

Is there any restriction for IBM HTTP Server to run sessionlinkd process as root user only. 

[Vijay Masurkar]

Venkata,  Greetings. You said you ran the sessionlinker test tools and you have uploaded the outputs.

 

Testing the Daemon 

- testclient Testing Tool

- swarmconnect Testing Tool .

 

Please follow up with the support engineer on the case. We can try to get some answer internally as to what those outputs mean. Secondly, please verify thoroughly the component compatibilities (in the PSM) for PS and the AIX webserver, since both host sessionlinker components. It's not affecting the functionality (if I'm reading correctly your case). One possibility is that it is detecting orphaned sessions, and these off-peak errors (you mentioned) may not be clearly stating what they indicate.  We need to improve those.

 

Thanks & Regards.

- Vijay

[venkata Kishore Babu Bellam]

I have ran testclient tool for session linker when we seen too many open files. I don't no how to read/understand the output of testclent tool.

 

Is there any documentation/knowlwdge case how to use testclient & swarmconnect tools and understand is my session linker working as required.

 

Wed Oct 18 03:29:19 2017-36700170:01029-ERR: Accept failed with code -1
Wed Oct 18 03:29:19 2017-36700170:01029-ERR: Error code from accept() is 'Too many open files' (24)
Wed Oct 18 03:29:24 2017-36700170:00258-ERR: Accept failed with code -1
Wed Oct 18 03:29:24 2017-36700170:00258-ERR: Error code from accept() is 'Too many open files' (24)

 

[Patrick Dussault]

Hi bellamkishore,

 

Just to precise aside.

 

The error :

"No data available... timeout"

 

 

is related to the fact that the tool makes a connection to the
SessionLinker, it sends to it data, but waiting 15 seconds for the
reply, it times out.

 

Insure that all components run with the same user. Check permissions
on the following files and directory, and make sure they are
accessible for the user that runs all components.

 

 

/tmp/sessionlinker
/var/tmp/

 

 

I hope that helps, and follow up in a case to get this trouble shoot
further.

 

 

Best Regards,
Patrick