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

ELM crashing


Akinola Oke

Question

My ELM installation often crashes and the only option I have is to reboot the server.

 

Though I have two installations, Test and Production, and this phonomena only occur on the production.

The difference between both is that the production has its "Storage Location" on a Netapp filer.

 

What I get on the browser is " An unexpected exception occured. If this problem continues, contact Technical support and provide them with the details of this exception"

On the "Appliance" itself, there are entries "block nbd....: Receive control failed (result -32) and "CIFS VFS: Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers", "cifs_mount failed w/return code = -95.

 

Is there a know issue wiht Netapp fileer and What would be the resolving it.

 

Thanks

Link to comment

8 answers to this question

Recommended Posts

  • 0

We do not have any known issues using NetApp, if we did it would be listed in the below url.

 

https://docs.citrix.com/en-us/citrix-app-layering/4/known-issues.html

 

 

There are many messages posted to the ELM console, which we consider to be benign. The below article lists those, with the error, "..failed w/return code = -95', being one of the messages.

 

https://support.citrix.com/article/CTX231811



As for the ELM crashing. Are you at our one of our latest releases? Are there any logs in the Netapp which correlate to when the failure happens? I recommend opening a case for someone to review the ELM logs, to see if there is anything that can be done to prevent the failures.

Link to comment
  • 0
3 minutes ago, Raymond Colon said:

We do not have any known issues using NetApp, if we did it would be listed in the below url.

 

https://docs.citrix.com/en-us/citrix-app-layering/4/known-issues.html

 

 

There are many messages posted to the ELM console, which we consider to be benign. The below article lists those, with the error, "..failed w/return code = -95', being one of the messages.

 

https://support.citrix.com/article/CTX231811



As for the ELM crashing. Are you at our one of our latest releases? Are there any logs in the Netapp which correlate to when the failure happens? I recommend opening a case for someone to review the ELM logs, to see if there is anything that can be done to prevent the failures.

The production is not yet on the latest release, but on 19.3.0.63.

 

The problem is not new and should not be related to any releases. I have been having it for quite a while and been ignoring it since I have a workaround. Just wish to resolve it.

I will have to open a case as suggested.

Link to comment
  • 0
3 hours ago, Akinola Oke said:

"CIFS VFS: Dialect not supported by server. Consider specifying vers=1.0 or vers=2.0 on mount for accessing older servers", "cifs_mount failed w/return code = -95.

 

Are you seeing this from the hypervisor console of the ELM? Or are you seeing this in an error message or from a log while connected to the ELM with ssh?

 

This message would only occur when the ELM establishes a connection to the SMB share. It seems that the share is reporting it supports a specific SMB version but then cannot talk the CIFS dialect of that protocol version. As the message states you can set the SMB version to something lower to ensure compatibility. To do this please see this solution which should be done from an ssh session to the ELM:

 

https://support.citrix.com/article/CTX225742

 

As noted in the article we did see a brief time when NetApp shares would not work with SMB version 3.02 and using only SMB 2.0 or 1.0 would work. I have not seen this issue reported for some time now and it is possible this was related to an older NetApp firmware version or a setting on the share itself.

 

 

Crashing:

As for your ELM crashing. I would be surprised if the SMB share is causing this but please let us know if it helps. The worst that should happen would be the inability to access the file share for layer imports / exports and elastic layer updates. The ELM logs would show if we are getting hung up reconnecting to the share or something like that but we should be failing gracefully if it cannot connect. For us to analyze the logs you would need a support case.

 

Is the error message you are seeing a Silverlight exception? This means the Silverlight app running in your browser lost connection to the web server on the ELM. Does refreshing your web browser session allow it to reconnect? Do you have a proxy or network filter that touches the network traffic between the production ELM and the computer you are using to log into the App Layering web console? We have seen some network filters allow communication for a period of time and then cut us off with an ECONNREST message.

Link to comment
  • 0

Thanks richardbuf for the more details given.

 

The "CIFS VFS......" message are shown directly on the Appliance console on the hypervisor.

I would have to ignore these or make changes as necessary.

 

As to the crashing, it just occurred today again. The error message is on the browser is on the browser and here is more to it.

 

1)

System.TimeoutException: [HttpRequestTimedOutWithoutDetail]
Arguments: http://elmURL/Unidesk.Web/API.asmx
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.50918.00&File=System.ServiceModel.dll&Key=HttpRequestTimedOutWithoutDetail ---> System.Net.WebException ---> System.Net.WebException
   at System.Net.Browser.BrowserHttpWebRequest.InternalEndGetResponse(IAsyncResult asyncResult)
   at System.Net.Browser.BrowserHttpWebRequest.<>c__DisplayClassa.<EndGetResponse>b__9(Object sendState)
   at System.Net.Browser.AsyncHelper.<>c__DisplayClass4.<BeginOnUI>b__0(Object sendState)
   --- End of inner exception stack trace ---
   at System.Net.Browser.AsyncHelper.BeginOnUI(SendOrPostCallback beginMethod, Object state)
   at System.Net.Browser.BrowserHttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelAsyncRequest.CompleteGetResponse(IAsyncResult result)
   --- End of inner exception stack trace ---
   at System.ServiceModel.Channels.Remoting.RealProxy.Invoke(Object[] args)
   at proxy_2.EndQueryImageDetail(IAsyncResult )
   at UdmcSilverlight.Proxy.UnideskApiClient.HandleResult[T](IAsyncResult asyncResult, Func`2 endFunction, Boolean doNotRaiseCommExceptionEvent)
   at UdmcSilverlight.Proxy.UnideskApiClient.<>c__DisplayClass89_0`1.<CreateTask>b__0(IAsyncResult r)
   at System.Threading.Tasks.TaskFactory`1.FromAsyncCoreLogic(IAsyncResult iar, Func`2 endFunction, Action`1 endAction, Task`1 promise)

  ServiceConfiguration:  BaseAddress: http://elmURL/, Binding: System.ServiceModel.BasicHttpBinding, Address: http://elmURL/Unidesk.Web/API.asmx

 

2)

An unexpected exception occurred.  If this problem continues, contact Technical Support and provide them with the details of this exception.

[HttpRequestTimedOutWithoutDetail]
Arguments: http://elmURL/Unidesk.Web/API.asmx
Debugging resource strings are unavailable. Often the key and arguments provide sufficient information to diagnose the problem. See http://go.microsoft.com/fwlink/?linkid=106663&Version=5.1.50918.00&File=System.ServiceModel.dll&Key=HttpRequestTimedOutWithoutDetail

 

I cannot say if it has always be same message all the time, but this is what I got today.

Refreshing the browser has never helped. I just have to reboot "ELM Appliance.

Link to comment
  • 0

That looks like the Silverlight error I was thinking of. We would need more logs from the ELM to get a better idea of what is going on there. As I mentioned before check for network filters or firewalls that might be breaking the connection. Could something be limiting or conflicting with the ELM's IP address? Possibly test powering down the ELM for a while and then ping the IP address. If something responds then you have an IP conflict.

 

If you are not doing so already, please try connecting to a VM that is on the same subnet as the ELM and be sure the data path does not get rerouted anywhere else first. See if you have the same problem from that VM as it shouldn't have the same policies applied. If that works then there is something between your management PC and the ELM appliance.


 

Quote


The "CIFS VFS......" message are shown directly on the Appliance console on the hypervisor.

I would have to ignore these or make changes as necessary.


 

 

As for making the SMB version changes. From the hypervisor console just press enter a few times until you see a login prompt. Those messages will clear as you login. Alternatively connect over SSH and the messages won't be in your way.

Link to comment
  • 0

Hi Richard

 

Possible checks relating to network have already been done and I would not limit the issue to problem between a particular managementPC and the ELM appliance, as once occured we experience it on all PCs. Though the ELM and the PCs are on different subnets. 

In order to try managementPC from same subnet, I would have to wait till the issue occurs again.

 

Since there are different logs, which one should I look into or provide, in order to trace out what the cause could be?

 

Thanks

Link to comment
  • 0
On 9/13/2019 at 10:03 PM, Richard Buffone said:

Just an ELM logs export would be enough. Please do this shortly after you reboot the ELM when you encounter the problem.

 

The logs can be exported from: System -> Manage Appliance -> Export Logs

 

 

Thank you

Hello Richard,

 

I just encountered the problem again and I have exported the logs.

Should I make it available here?

 

Thanks

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...