# Connecting to compiled Paraview 5.5.2 server from Mac client crashes

**URL:** https://discourse.paraview.org/t/connecting-to-compiled-paraview-5-5-2-server-from-mac-client-crashes/424
**Category:** ParaView Support
**Created:** [August 13, 2018, 7:14pm UTC](https://discourse.paraview.org/t/connecting-to-compiled-paraview-5-5-2-server-from-mac-client-crashes/424 "2018-08-13T19:14:13Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![zachdayz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/z/82dd89/32.png) [@zachdayz](https://discourse.paraview.org/u/zachdayz)
#### Post date: [August 13, 2018, 7:14pm UTC](https://discourse.paraview.org/t/connecting-to-compiled-paraview-5-5-2-server-from-mac-client-crashes/424/1 "2018-08-13T19:14:13Z")

</div>

Hello,

I have compiled Paraview 5.5.2 with MPI and OSMesa support on a RedHat cluster. Linux and Windows clients are able to connect to the server without issue, but connecting to it from a Mac client causes a crash with this error message.

```auto
[day@node994 bin]$ ./pvserver
Waiting for client...
Connection URL: cs://node994.cm.cluster:11111
Accepting connection(s): node994.cm.cluster:11111
Client connected.
ERROR: In /home/day/build/ParaView-v5.5.2/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 808
vtkSocketCommunicator (0x3ad9100): Could not receive tag. 1

ERROR: In /home/day/build/ParaView-v5.5.2/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 301
vtkTCPNetworkAccessManager (0x2763240): Some error in socket processing.

Exiting...

```

I went back and built 5.5.0 and 5.5.1 as well and have encountered this issue there as well, leading me to believe that this is not a Paraview issue but rather a system-specific configuration one. However, I have been unable to find anything that may be a culprit for such an issue.

---

<div class="post-metadata">

### Author: ![Dave\_DeMarle](https://discourse.paraview.org/user_avatar/discourse.paraview.org/dave_demarle/32/27_2.png) [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [August 13, 2018, 7:19pm UTC](https://discourse.paraview.org/t/connecting-to-compiled-paraview-5-5-2-server-from-mac-client-crashes/424/2 "2018-08-13T19:19:12Z")

</div>

There is a bug on mac in 5.5.2 such that there will be a crash in the Mac client when it connects to a server that does not have OSPRay enabled. Try connecting to it from the mac 5.5.1 no ospray binaries.

This is fixed in master and will be fixed in 5.6.0.

---

<div class="post-metadata">

### Author: ![zachdayz](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/z/82dd89/32.png) [@zachdayz](https://discourse.paraview.org/u/zachdayz)
#### Post date: [August 13, 2018, 7:58pm UTC](https://discourse.paraview.org/t/connecting-to-compiled-paraview-5-5-2-server-from-mac-client-crashes/424/3 "2018-08-13T19:58:01Z")

</div>

As I mentioned before, 5.5.1 still crashes. However, I’ll try compiling 5.5.2 with OSPray via the Superbuild.

---

<div class="post-metadata">

### Author: ![Dave\_DeMarle](https://discourse.paraview.org/user_avatar/discourse.paraview.org/dave_demarle/32/27_2.png) [@Dave\_DeMarle](https://discourse.paraview.org/u/Dave_DeMarle)
#### Post date: [August 13, 2018, 9:07pm UTC](https://discourse.paraview.org/t/connecting-to-compiled-paraview-5-5-2-server-from-mac-client-crashes/424/4 "2018-08-13T21:07:38Z")

</div>

Specifically try the 5.5.1-NOOSPRAY binary from the kitware download site. In 5.5.0 and 5.5.1 all three clients would fail if the server lacked ospray.