Jump to content
Welcome to our new Citrix community!
  • 0

Session hangs during initialisation : XTE service [error] (OS 10038)


Julien SYBILLE

Question

Dear all, I have a very strang error that I try to troubleshoot regarding the XTE service. 
 
I have a client that have very strang problem with two XenApp silos stream using citrix PVS 6.1 U 21 and XA 6.5 RP3
 
the pbs is that when a user try to connect the client hangs at starting the details pane display connexion.... 
 
post-10452397-0-58343400-1424185606_thumb.jpg
looking at the netork with wiresharke I identified that the client received a bad information return from the XTE service on port 2598. 
 

post-10452397-0-51357100-1424185313_thumb.jpg

 

the good tram should be : 

 

 post-10452397-0-49103800-1424185245_thumb.jpg

 

looking at the event logs of the XTE service I found the follwoing 

*************************************
[sat Feb 07 11:32:04 2015] [notice] Server built: Nov 15 2013 17:53:13
[sat Feb 07 11:32:04 2015] [notice] Parent: Created child process 3104
[sat Feb 07 11:32:05 2015] [notice] Child 3104: Child process is running
[sat Feb 07 11:32:05 2015] [notice] async engine initialized successfully, 8 worker threads started
[sat Feb 07 11:32:05 2015] [notice] Child 3104: Acquired the start mutex.
[sat Feb 07 11:32:05 2015] [notice] Child 3104: Starting 150 worker threads.
[sat Feb 07 11:32:05 2015] [error] (OS 10038)Une opération a été tentée sur autre chose qu’un socket.  : winnt_accept: getsockname error on listening socket, is IPv6 available?
[sun Feb 08 00:00:25 2015] [notice] Parent: Running
[sun Feb 08 00:00:25 2015] [notice] Child 3104: Running
 
[Tue Feb 17 11:47:19 2015] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Tue Feb 17 11:47:19 2015] [notice] Child 3104: Exit event signaled. Child process is ending.

*************************************

the interesting thing is that when I restart the service on  the XenApp serevr the ICA client pop me the following  

 

post-10452397-0-16467800-1424185799_thumb.jpg

your application is not avaliable. 

 

the second thin is that If I restart teh service it start well with no error in the XTE logs and the XenApp start session correctly. So the error seem to be only at random boot time... 

 

I have try this old one http://support.citrix.com/article/CTX106531 with no luck and look around the google search with no luck

 

Of course the Quick resolution for the moment is to disable the Session reliability on the farm, therfore my client want to use it. 

 

 My next step will be to try update XenApp to RP5 therfore I'm wondering if anyone have an idea or meet this pbs before and found a solution ? 

 

Julien

Link to comment

12 answers to this question

Recommended Posts

  • 0

We have the same exact problem and get the same socket error in the XTE error.log. Seemingly random servers in our farm will exhibit this behavior. To get it functional again it's a matter of restarting the XTE Server service, but by the time I arrive to the office to find the problem server and restart the service, we've already had a lot of users attempt to log in. The issue then escalates to management and I have them breathing down my neck. I was hoping Hotfix Rollup 5 would address the issue, but sadly it does not. This has been an intermittent issue for us for years...

Link to comment
  • 0

Hi All,

 

Just in case someone else comes across this problem, which we've also experienced in our environment...

 

After confirming the problem only occurs on a reboot of the Citrix server, the workaround we've deployed is to create a Windows scheduled task on the server in question (using PsService) which restarts the 'Citrix XTE Server' service approximately 30 minutes after a server reboot.

 

So if the server boots and has the issue as described in the original post, an automated restart of this service fixes the issue without any business interruption or manual intervention (assuming your servers restart in the early hours of the morning). If the server boot and does not exhibit any issue, restarting the Citrix XTE service does not cause any problems. 

 

I hope this helps someone out there!

 

Best Regards,

 

Jermaine

Link to comment
  • 0

We have this exact same problem.  I'm about to implement a scheduled restart XTE service I guess unless no one else knows of a permanent fix.  I saw one article about resetting the IP stack in Windows.  Has anyone had any luck with that?  

 

We use PVS & all our imaged servers reboot nightly so chances are there are a few that are always like this when they come back up.

Link to comment
  • 0

Same Problem here. XTE Service stops responding. Server has no Connections. XTE Log:

 

[Fri Mar 23 00:21:27 2018] [notice] Server built: Jan 26 2016 11:54:23
[Fri Mar 23 00:21:27 2018] [notice] Parent: Created child process 5372
[Fri Mar 23 00:21:30 2018] [notice] Child 5372: Child process is running
[Fri Mar 23 00:21:30 2018] [notice] async engine initialized successfully, 16 worker threads started
[Fri Mar 23 00:21:30 2018] [warn] (OS 6)Das Handle ist ungültig.  : child: send_other_children_handles(), Unable to write number of other children to parent.
[Fri Mar 23 00:21:30 2018] [notice] Child 5372: Acquired the start mutex.
[Fri Mar 23 00:21:30 2018] [warn] (OS 109)Die Pipe wurde beendet.  : Parent: get_childs_other_children(), Unable to read pipe data from child.
[Fri Mar 23 00:21:30 2018] [notice] Child 5372: Starting 150 worker threads.
[Fri Mar 23 00:21:30 2018] [error] (OS 10038)Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.  : winnt_accept: getsockname error on listening socket, is IPv6 available?
[Fri Mar 23 00:21:30 2018] [error] (OS 10038)Ein Vorgang bezog sich auf ein Objekt, das kein Socket ist.  : winnt_accept: getsockname error on listening socket, is IPv6 available?
[Fri Mar 23 08:49:12 2018] [notice] Parent: Received shutdown signal -- Shutting down the server.
[Fri Mar 23 08:49:12 2018] [notice] Child 5372: Exit event signaled. Child process is ending.
[Fri Mar 23 08:49:13 2018] [notice] Child 5372: Released the start mutex
[Fri Mar 23 08:49:14 2018] [notice] Child 5372: Waiting for 150 worker threads to exit.
[Fri Mar 23 08:49:14 2018] [notice] Child 5372: All worker threads have exited.
[Fri Mar 23 08:49:14 2018] [notice] Child 5372: Child process is exiting
[Fri Mar 23 08:49:14 2018] [notice] Parent: Child process exited successfully.
[Fri Mar 23 08:49:17 2018] [notice] Server built: Jan 26 2016 11:54:23
[Fri Mar 23 08:49:17 2018] [notice] Parent: Created child process 1428
[Fri Mar 23 08:49:19 2018] [notice] Child 1428: Child process is running
[Fri Mar 23 08:49:19 2018] [notice] async engine initialized successfully, 16 worker threads started
[Fri Mar 23 08:49:19 2018] [warn] (OS 109)Die Pipe wurde beendet.  : Parent: get_childs_other_children(), Unable to read pipe data from child.
[Fri Mar 23 08:49:19 2018] [warn] (OS 6)Das Handle ist ungültig.  : child: send_other_children_handles(), Unable to write number of other children to parent.
[Fri Mar 23 08:49:19 2018] [notice] Child 1428: Acquired the start mutex.
[Fri Mar 23 08:49:19 2018] [notice] Child 1428: Starting 150 worker threads.

 

 

After restarting the XTE Service at 08:49 user can connect!

Does anybody have a solution for that Problem?

We have a call open at Citrix Support.

 

Regards, Holger

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...