# ParaView Illegal instruction (core dumped)

**URL:** https://discourse.paraview.org/t/paraview-illegal-instruction-core-dumped/2636
**Category:** ParaView Support
**Created:** [September 27, 2019, 10:21am UTC](https://discourse.paraview.org/t/paraview-illegal-instruction-core-dumped/2636 "2019-09-27T10:21:51Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![GWAVE](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/g/4af34b/32.png) [@GWAVE](https://discourse.paraview.org/u/GWAVE)
#### Post date: [September 27, 2019, 10:21am UTC](https://discourse.paraview.org/t/paraview-illegal-instruction-core-dumped/2636/1 "2019-09-27T10:21:51Z")

</div>

I have to connect to a HPC center running pvserver, in which the ParaView install is version 5.6.1. When I make the remote connection from my office PC, the connection complains about version mismatch

```
ERROR: In /tmp/ParaView/5.6.1/intel-2018.5.274-mpi/ParaView-v5.6.1/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 502
vtkSocketCommunicator (0x1ad0a80): Client/server version hash mismatch.

ERROR: In /tmp/ParaView/5.6.1/intel-2018.5.274-mpi/ParaView-v5.6.1/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 333
vtkTCPNetworkAccessManager (0xe81c60): 
**********************************************************************
Connection failed during handshake. vtkSocketCommunicator::GetVersion()
 returns different values on the two connecting processes
 (Current value: 100).
**********************************************************************

```

I’m running Ubuntu 18LTS, where I originally tried to use the package build (version 5.4.1). This resulted in the error above. I did some research and it seems the solution is to get the exact same version. I went over to [ParaView download](https://www.paraview.org/download/) and grabbed the binary version 5.6.1. When I try to run the executable, I get the following error

```
Illegal instruction (core dumped)

```

That is all that is spit out and I have no clue what I can do to fix it. I tried to download binary version 5.7.0-RC1 and 5.7.0-RC4 where both executables seems to work fine, but again I can not connect to the server because of version mismatch.

Assuming I can not touch the server, how do I fix the “Illegal instruction” error to get the version 5.6.1 binary working?

---

<div class="post-metadata">

### Author: ![mwestphal](https://discourse.paraview.org/user_avatar/discourse.paraview.org/mwestphal/32/17_2.png) [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [September 30, 2019, 3:11am UTC](https://discourse.paraview.org/t/paraview-illegal-instruction-core-dumped/2636/2 "2019-09-30T03:11:18Z")

</div>

You indeed need to use the exact same version.

Regarding your issue with 5.6.1 :  
Which CPU do you have ?

A solution may be to build ParaView yourself.

---

<div class="post-metadata">

### Author: ![cory.quammen](https://discourse.paraview.org/user_avatar/discourse.paraview.org/cory.quammen/32/11193_2.png) [@cory.quammen](https://discourse.paraview.org/u/cory.quammen)
#### Post date: [October 28, 2019, 7:55pm UTC](https://discourse.paraview.org/t/paraview-illegal-instruction-core-dumped/2636/3 "2019-10-28T19:55:13Z")

</div>

GWAVE, you are likely running into an issue described here: [https://gitlab.kitware.com/paraview/paraview-superbuild/issues/126](https://gitlab.kitware.com/paraview/paraview-superbuild/issues/126)

The fix is in ParaView 5.7.0. Unless you can build the ParaView 5.6.1 client yourself without the AVX instruction set support, your only option is to try ParaView 5.6.0 with the 5.6.1 server (might work) or wait until the server is updated to 5.7.0 and use the ParaView 5.7.0 client.

---

<div class="post-metadata">

### Author: ![GWAVE](https://discourse.paraview.org/letter_avatar_proxy/v4/letter/g/4af34b/32.png) [@GWAVE](https://discourse.paraview.org/u/GWAVE)
#### Post date: [October 28, 2019, 9:02pm UTC](https://discourse.paraview.org/t/paraview-illegal-instruction-core-dumped/2636/4 "2019-10-28T21:02:54Z")

</div>

@mwestphal and @cory.quammen Thanks for your support. I ended up building version 5.6.1 on my own (without “super build”), which proved to be a bit of a challenge, but it did work connecting to the remote server.
