# Error: "Some error in socket processing"
**URL:** https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549
**Category:** ParaView Support
**Created:** [March 28, 2019, 2:34am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549 "2019-03-28T02:34:47Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@gridley](https://discourse.paraview.org/u/gridley)
#### Post date: [March 28, 2019, 2:34am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/1 "2019-03-28T02:34:47Z")
Hi all,
I’m trying to render some openfoam data on AWS, and to simplify things, just using mesa CPU rendering. I’m trying to check if I can save an image of my data set going parallel across ten nodes with 16 threads a piece. So, I start my pvserver as follows:
```
#!/bin/bash
#SBATCH -N 8
#SBATCH -n 192
mpi=/shared/opt/ParaView-5.6.0-osmesa-MPI-Linux-64bit/bin/mpiexec
$mpi -n 192 /shared/opt/ParaView-5.6.0-osmesa-MPI-Linux-64bit/bin/pvserver --force-offscreen-rendering --mpi
```
Then try to run this simple script using pvpython from the same binary download:
```
from paraview.simple import *
from paraview import servermanager
# connect to server
connection = servermanager.Connect('ip-172-31-0-19', 11111)
sphere = Sphere()
view = servermanager.CreateRenderView()
# make a sphere source
WriteImage('test.png')
```
Unfortunately, I get this error on the server:
```
Waiting for client...
Connection URL: cs://ip-172-31-0-19:11111
Accepting connection(s): ip-172-31-0-19:11111
Client connected.
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_osmesa_superbuild/build/superbuild/paraview/src/VTK/Parallel/Core/vtkSocketCommunicator.cxx, line 808
vtkSocketCommunicator (0x1f72a10): Could not receive tag. 1
ERROR: In /home/buildslave/dashboards/buildbot/paraview-pvbinsdash-linux-shared-release_osmesa_superbuild/build/superbuild/paraview/src/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 297
vtkTCPNetworkAccessManager (0x110f110): Some error in socket processing.
```
What’s up here?
---
### Author:  [@kevin-bruhwiler](https://discourse.paraview.org/u/kevin-bruhwiler)
#### Post date: [March 10, 2021, 11:04pm UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/2 "2021-03-10T23:04:44Z")
I am getting the exact same error trying to get the Nvidia Index plugin to work. Any dataset I add will cause the following errors on the server-side:
`( 231.995s) [pvserver]vtkSocketCommunicator.c:808 ERR| vtkSocketCommunicator (0x55a388dedf10): Could not receive tag. 1 `
`( 231.996s) [pvserver]vtkTCPNetworkAccessMana:297 ERR| vtkTCPNetworkAccessManager (0x55a388b76f50): Some error in socket processing. Exiting...`
and then crash both the server and the ParaView client. Any insight into what’s actually going on here would be enormously appreciated.
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [March 11, 2021, 9:03am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/3 "2021-03-11T09:03:08Z")
This error is highly non specific and could be caused by many things.
Please provide precise steps to reproduce.
---
### Author:  [@kevin-bruhwiler](https://discourse.paraview.org/u/kevin-bruhwiler)
#### Post date: [March 11, 2021, 5:44pm UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/4 "2021-03-11T17:44:48Z")
Thanks for the fast response!
I’m working from the instructions here, specifically the ParaView Server/Running with Docker section:
[https://ngc.nvidia.com/catalog/containers/nvidia-hpcvis:paraview-index](https://ngc.nvidia.com/catalog/containers/nvidia-hpcvis:paraview-index)
I can connect to the Docker container from ParaView, and browse files inside of it, but attempting to visualize any dataset causes the crashes. I’ve tried adding Wavelets, as the instructions suggest, and tried loading custom datasets. Both produce the same two error messages.
My guess is that the issue is with the IndeX plugin and not with ParaView, but I was hoping to get more information about what that error actually means so I can troubleshoot it myself.
---
### Author:  [@lukasWiel](https://discourse.paraview.org/u/lukasWiel)
#### Post date: [March 31, 2021, 4:04pm UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/5 "2021-03-31T16:04:47Z")
I have the same issue, in 5.9.0 (both server and client), and have exact steps to reproduce them:
1: on a cluster, start a pvserver. I just use a single thread server which is already difficult enough for now.
2: on my home computer, I set up an ssh tunnel to the compute node to which the pvserver was assigned.
3: I connect my client to the server. I get about 20 errors (that I somehow think I should actually solve first), but the connection is made, so confirms the server log.
4: I open a very simple example vtu file from John Burkardt: [https://people.math.sc.edu/Burkardt/data/vtu/ugridex.vtu](https://people.math.sc.edu/Burkardt/data/vtu/ugridex.vtu)
5: [apply]
6: I actually see a rendering of the model (and a lot more errors).
7: there are two quantities in the vtu file: csum and nmax. When the selector ‘solid color’ is changed into any of those two, then even before apply these two errors are given on the server side, and both server and client crash.
I hope this helps. best wishes
Lukas
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 1, 2021, 10:10am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/6 "2021-04-01T10:10:12Z")
No issues here.
> Errors
Please share these
> SSH
Please share your ssh tunnel command
What is your rendering setup ? Remote or local ? OpenGL ? EGL ? OSMesa ?
---
### Author:  [@lukasWiel](https://discourse.paraview.org/u/lukasWiel)
#### Post date: [April 6, 2021, 11:00am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/7 "2021-04-06T11:00:54Z")
Dear Mathieu,
thank you for your reaction.
I have to do a walk of shame here…
the reason of these errors was partly discovered:
For the client I used the 5.9.0 prebuilt binaries.
For the server I compiled the 5.9.0. manually, because I was dumb enough to actually try and run the prebuilt pvserver with our system mpirun (openmpi 4.0.4), and not with the mpiexec so helpfully provided with the binaries. This caused the error that is typically associated with the build not being properly parallel:
The first thread is fine, and all all other threads show:
> Socket error in call to bind. Address already in use.
To prevent this, I compiled Paraview myself with our system MPI, which eventually enabled me to run a server in parallel with it, but then there are subtle differences that make the two (the prebuilt and my system-MPI built) incompatible.
Because our various users will eventually run Paraview clients on their home machines, I wished to allow them to use the prebuilt binaries, and to prevent them all from having to do a manual compile, but that would only work when the server runs from that same set of binaries as well, which it now does.
Now all I have to do is to give the GPU nodes of the cluster a sufficient X environment so that PVserver can open the render window, which it currently cannot.
The SSH tunnel command was:
> ssh -f -L 11111:gpu001:11111 eejit.geo.uu.nl
with the name of the login node being eejit.geo.uu.nl, and the GPU node being gpu001.
That now works, and it is possible to load data and view models, although ‘remote rendering disabled’ until I fixed the X environment stuff.
We are running this with OpenGL
We wish to eventually use remote rendering, because the models of some of the users can run into the several tens of gigabytes, and while that is easy enough for the cluster, it is too much for their little laptops. 😉
I will get let you know when I have the X stuff set up properly and managed to enable remote rendering.
For completenes’ sake, although no longer really relevant for me: the runtime errors (on the client side) from the version conflict were:
> **click to show**
>
> > ( 10.639s) [paraview]vtkOSPRayMaterialLibrar:280 ERR| vtkOSPRayMaterialLibrary (0x141469e0): JSON parsing error: \* Line 1, Column 1
> > Syntax error: value, object or array expected.
> >
> > ( 11.603s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.603s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.603s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.603s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.603s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.603s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.607s) [paraview] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x15192ca0): Object type: vtkTextProperty, could not find requested method: “SetCellOffset”
> > or the method was called with incorrect arguments.
> >
> > while processing
> > Message 0 = Invoke
> > Argument 0 = vtk\_object\_pointer {vtkTextProperty (0x2175a50)}
> > Argument 1 = string\_value {SetCellOffset}
> > Argument 2 = int32\_value {0}
> >
> > ( 11.608s) [paraview] vtkPVSessionCore.cxx:373 ERR| vtkPVSessionCore (0x15192ca0): Aborting execution for debugging purposes.
> > ############ ABORT #############
> > ( 11.608s) [paraview] vtkSIProxy.cxx:621 ERR| vtkSIProxy (0x2175950): Could not parse property: CellOffset
> > ( 11.608s) [paraview] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x15192ca0): Object type: vtkTextProperty, could not find requested method: “SetCellOffset”
> > or the method was called with incorrect arguments.
> >
> > while processing
> > Message 0 = Invoke
> > Argument 0 = vtk\_object\_pointer {vtkTextProperty (0x2175a50)}
> > Argument 1 = string\_value {SetCellOffset}
> > Argument 2 = int32\_value {0}
> >
> > ( 11.608s) [paraview] vtkPVSessionCore.cxx:373 ERR| vtkPVSessionCore (0x15192ca0): Aborting execution for debugging purposes.
> > ############ ABORT #############
> > ( 11.609s) [paraview] vtkSIProxy.cxx:621 ERR| vtkSIProxy (0x1517dfa0): Could not parse property: CellOffset
> > ( 11.609s) [paraview] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x15192ca0): Object type: vtkTextProperty, could not find requested method: “SetCellOffset”
> > or the method was called with incorrect arguments.
> >
> > while processing
> > Message 0 = Invoke
> > Argument 0 = vtk\_object\_pointer {vtkTextProperty (0x2175a50)}
> > Argument 1 = string\_value {SetCellOffset}
> > Argument 2 = int32\_value {0}
> >
> > ( 11.609s) [paraview] vtkPVSessionCore.cxx:373 ERR| vtkPVSessionCore (0x15192ca0): Aborting execution for debugging purposes.
> > ############ ABORT #############
> > ( 11.609s) [paraview] vtkSIProxy.cxx:621 ERR| vtkSIProxy (0x2177d50): Could not parse property: CellOffset
> > ( 11.610s) [paraview] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x15192ca0): Object type: vtkTextProperty, could not find requested method: “SetCellOffset”
> > or the method was called with incorrect arguments.
> >
> > while processing
> > Message 0 = Invoke
> > Argument 0 = vtk\_object\_pointer {vtkTextProperty (0x2175a50)}
> > Argument 1 = string\_value {SetCellOffset}
> > Argument 2 = int32\_value {0}
> >
> > ( 11.610s) [paraview] vtkPVSessionCore.cxx:373 ERR| vtkPVSessionCore (0x15192ca0): Aborting execution for debugging purposes.
> > ############ ABORT #############
> > ( 11.610s) [paraview] vtkSIProxy.cxx:621 ERR| vtkSIProxy (0x23ab7a0): Could not parse property: CellOffset
> > ( 11.610s) [paraview] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x15192ca0): Object type: vtkTextProperty, could not find requested method: “SetCellOffset”
> > or the method was called with incorrect arguments.
> >
> > while processing
> > Message 0 = Invoke
> > Argument 0 = vtk\_object\_pointer {vtkTextProperty (0x2175a50)}
> > Argument 1 = string\_value {SetCellOffset}
> > Argument 2 = int32\_value {0}
> >
> > ( 11.611s) [paraview] vtkPVSessionCore.cxx:373 ERR| vtkPVSessionCore (0x15192ca0): Aborting execution for debugging purposes.
> > ############ ABORT #############
> > ( 11.611s) [paraview] vtkSIProxy.cxx:621 ERR| vtkSIProxy (0x2179060): Could not parse property: CellOffset
> > ( 11.611s) [paraview] vtkPVSessionCore.cxx:372 ERR| vtkPVSessionCore (0x15192ca0): Object type: vtkTextProperty, could not find requested method: “SetCellOffset”
> > or the method was called with incorrect arguments.
> >
> > while processing
> > Message 0 = Invoke
> > Argument 0 = vtk\_object\_pointer {vtkTextProperty (0x2175a50)}
> > Argument 1 = string\_value {SetCellOffset}
> > Argument 2 = int32\_value {0}
> >
> > ( 11.611s) [paraview] vtkPVSessionCore.cxx:373 ERR| vtkPVSessionCore (0x15192ca0): Aborting execution for debugging purposes.
> > ############ ABORT #############
> > ( 11.611s) [paraview] vtkSIProxy.cxx:621 ERR| vtkSIProxy (0xda7610): Could not parse property: CellOffset
> > ( 11.614s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x2175950): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9098
> > location: 17
> > [paraview\_protobuf.ProxyState.property] {
> > name: “FontSize”
> > value {
> > type: INT
> > integer: 12
> > }
> > }
> >
> > ( 11.614s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x1517dfa0): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9099
> > location: 17
> > [paraview\_protobuf.ProxyState.property] {
> > name: “FontSize”
> > value {
> > type: INT
> > integer: 12
> > }
> > }
> >
> > ( 11.615s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x2177d50): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9100
> > location: 17
> > [paraview\_protobuf.ProxyState.property] {
> > name: “FontSize”
> > value {
> > type: INT
> > integer: 12
> > }
> > }
> >
> > ( 11.615s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x23ab7a0): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9101
> > location: 17
> > [paraview\_protobuf.ProxyState.property] {
> > name: “FontSize”
> > value {
> > type: INT
> > integer: 12
> > }
> > }
> >
> > ( 11.615s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x2179060): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9102
> > location: 17
> > [paraview\_protobuf.ProxyState.property] {
> > name: “FontSize”
> > value {
> > type: INT
> > integer: 12
> > }
> > }
> >
> > ( 11.615s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0xda7610): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9103
> > location: 17
> > [paraview\_protobuf.ProxyState.property] {
> > name: “FontSize”
> > value {
> > type: INT
> > integer: 12
> > }
> > }
> >
> > ( 11.616s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.616s) [paraview] VisRTXBackend.cxx:42 WARN| VisRTX Error: Unsupported device
> > ( 11.701s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x2175950): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9098
> > location: 17
> > [paraview\_protobuf.ProxyState.log\_name]: “RenderView1/AxesGrid/GridAxes3DActor/XLabelProperties”
> >
> > ( 11.701s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x1517dfa0): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9099
> > location: 17
> > [paraview\_protobuf.ProxyState.log\_name]: “RenderView1/AxesGrid/GridAxes3DActor/XTitleProperties”
> >
> > ( 11.702s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x2177d50): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9100
> > location: 17
> > [paraview\_protobuf.ProxyState.log\_name]: “RenderView1/AxesGrid/GridAxes3DActor/YLabelProperties”
> >
> > ( 11.702s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x23ab7a0): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9101
> > location: 17
> > [paraview\_protobuf.ProxyState.log\_name]: “RenderView1/AxesGrid/GridAxes3DActor/YTitleProperties”
> >
> > ( 11.702s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0x2179060): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9102
> > location: 17
> > [paraview\_protobuf.ProxyState.log\_name]: “RenderView1/AxesGrid/GridAxes3DActor/ZLabelProperties”
> >
> > ( 11.703s) [paraview] vtkSIProxy.cxx:302 ERR| vtkSIProxy (0xda7610): Incorrect message received. Missing xml\_group and xml\_name information.
> > global\_id: 9103
> > location: 17
> > [paraview\_protobuf.ProxyState.log\_name]: “RenderView1/AxesGrid/GridAxes3DActor/ZTitleProperties”
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 6, 2021, 11:08am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/8 "2021-04-06T11:08:33Z")
> To prevent this, I compiled Paraview myself with our system MPI, which eventually enabled me to run a server in parallel with it, but then there are subtle differences that make the two (the prebuilt and my system-MPI built) incompatible.
You can also use `--system-mpi` option with our binaries.
> but then there are subtle differences that make the two (the prebuilt and my system-MPI built) incompatible.
> Because our various users will eventually run Paraview clients on their home machines, I wished to allow them to use the prebuilt binaries, and to prevent them all from having to do a manual compile, but that would only work when the server runs from that same set of binaries as well, which it now does.
If that is so, this is a bug. The only requirement is that the paraview version is strictly the same.
> although ‘remote rendering disabled’ until I fixed the X environment stuff.
>
> We are running this with OpenGL
>
> We wish to eventually use remote rendering, because the models of some of the users can run into the several tens of gigabytes, and while that is easy enough for the cluster, it is too much for their little laptops.
Yes, you need to use remote rendering in that case.
---
### Author:  [@lukasWiel](https://discourse.paraview.org/u/lukasWiel)
#### Post date: [April 14, 2021, 10:11am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/9 "2021-04-14T10:11:44Z")
That helped indeed! Thank you.
I now have enough working to get my users out of troubled water, and I can figure out more details at leisure. If you wish I can contribute more findings later on. What would be the proper place to do so?
To make life easier for myself I experimented with the headless prebuilt binaries.
Using them I can now connect to a parallel pvserver on a compute node.
Surprisingly to see that when a client connects, the server threads all pull a full core load for about 12 seconds. During this time, the client is frozen. After this timethe server threads go to idle, the interface ‘blinks’ briefly to white and back again, and I can load and render data.
These compute nodes have 48 cores (two 24 core CPUs).
Funny enough the connecting and rendering works well up to a 42-thread pvserver, for 43 and higher, both the server and the client crash the following error (It appears to be a Qt related issue, so maybe I messed something up there as well):
> $ ./paraview
> VisRTX 0.1.6, using devices:
> 0: GeForce GTX 1660 Ti (Total: 6.2 GB, Available: 5.4 GB)
> ( 29.630s) [paraview]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x15e5fa50): Could not receive tag. 55629
> ( 29.630s) [paraview]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x15e5fa50): Could not receive tag. 55629
> ( 29.630s) [paraview]vtkOSPRayMaterialLibrar:280 ERR| vtkOSPRayMaterialLibrary (0x15138170): JSON parsing error: \* Line 1, Column 1
> Syntax error: value, object or array expected.
>
> ( 29.642s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.643s) [paraview]vtkSocketCommunicator.c:710 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send length.
> ( 29.646s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.646s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.646s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.646s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.647s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.647s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.647s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.648s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.648s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.648s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.648s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.648s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.650s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.651s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.651s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.651s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.651s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.651s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.652s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.652s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.652s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.652s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.652s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.652s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.652s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.652s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.652s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.652s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.652s) [paraview] vtkSocket.cxx:532 ERR| vtkClientSocket (0x16751820): Socket error in call to send. Broken pipe.
> ( 29.652s) [paraview]vtkSocketCommunicator.c:704 ERR| vtkSocketCommunicator (0x15e5fa50): Could not send tag.
> ( 29.653s) [paraview]vtkSocketCommunicator.c:781 ERR| vtkSocketCommunicator (0x15e5fa50): Could not receive tag. 55628
> free(): double free detected in tcache 2
>
> Loguru caught a signal: SIGABRT
> Stack trace:
> 58 0x407b2a /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/paraview-real() [0x407b2a]
> 57 0x7fbc71ffb0b3 \_\_libc\_start\_main + 243
> 56 0x40778a /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/paraview-real() [0x40778a]
> 55 0x7fbc6f47d120 QCoreApplication::exec() + 128
> 54 0x7fbc6f47462a QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) + 298
> 53 0x7fbc3c3aa003 /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/plugins/platforms/…/…/lib/libQt5XcbQpa.so.5(+0x5e003) [0x7fbc3c3aa003]
> 52 0x7fbc6fb070db QWindowSystemInterface::sendWindowSystemEvents(QFlagsQEventLoop::ProcessEventsFlag) + 187
> 51 0x7fbc6fb2bb35 QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent\*) + 261
> 50 0x7fbc6fb2a8ad QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent\*) + 1837
> 49 0x7fbc6f475dd8 QCoreApplication::notifyInternal2(QObject\*, QEvent\*) + 280
> 48 0x7fbc7144a260 QApplication::notify(QObject\*, QEvent\*) + 704
> 47 0x7fbc7144318c QApplicationPrivate::notify\_helper(QObject\*, QEvent\*) + 156
> 46 0x7fbc7149d8fb /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libQt5Widgets.so.5(+0x1b68fb) [0x7fbc7149d8fb]
> 45 0x7fbc7149b467 /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libQt5Widgets.so.5(+0x1b4467) [0x7fbc7149b467]
> 44 0x7fbc714497cc QApplicationPrivate::sendMouseEvent(QWidget\*, QMouseEvent\*, QWidget\*, QWidget\*, QWidget\*\*, QPointer&, bool, bool) + 460
> 43 0x7fbc6f475dd8 QCoreApplication::notifyInternal2(QObject\*, QEvent\*) + 280
> 42 0x7fbc7144adc8 QApplication::notify(QObject\*, QEvent\*) + 3624
> 41 0x7fbc7144318c QApplicationPrivate::notify\_helper(QObject\*, QEvent\*) + 156
> 40 0x7fbc715b269b QMenu::event(QEvent\*) + 171
> 39 0x7fbc71480c28 QWidget::event(QEvent\*) + 424
> 38 0x7fbc715b0413 QMenu::mouseReleaseEvent(QMouseEvent\*) + 403
> 37 0x7fbc715af57f /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libQt5Widgets.so.5(+0x2c857f) [0x7fbc715af57f]
> 36 0x7fbc715a83fc /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libQt5Widgets.so.5(+0x2c13fc) [0x7fbc715a83fc]
> 35 0x7fbc7143f3bc QAction::activate(QAction::ActionEvent) + 204
> 34 0x7fbc7143cfb2 QAction::triggered(bool) + 50
> 33 0x7fbc6f4a41ea QMetaObject::activate(QObject\*, int, int, void\*\*) + 1850
> 32 0x7fbc71cc78e7 pqServerConnectReaction::connectToServerWithWarning() + 87
> 31 0x7fbc71cc7860 pqServerConnectReaction::connectToServer() + 240
> 30 0x7fbc71cc7648 pqServerConnectReaction::connectToServerUsingConfiguration(pqServerConfiguration const&) + 24
> 29 0x7fbc70d7df99 pqServerLauncher::connectToServer() + 633
> 28 0x7fbc70d7c688 pqServerLauncher::connectToPrelaunchedServer() + 552
> 27 0x7fbc705ed856 pqObjectBuilder::createServer(pqServerResource const&, int) + 854
> 26 0x7fbc6e84e510 vtkSMSession::ConnectToRemoteInternal(char const\*, int, bool, int) + 1040
> 25 0x7fbc6da6b388 vtkProcessModule::RegisterSession(vtkSession\*) + 376
> 24 0x7fbc68d98102 /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libvtkCommonCore-pv5.9.so.1(+0x3f3102) [0x7fbc68d98102]
> 23 0x7fbc68c1f209 vtkCallbackCommand::Execute(vtkObject\*, unsigned long, void\*) + 25
> 22 0x7fbc6ed57f10 /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libvtkGUISupportQt-pv5.9.so.1(+0x39f10) [0x7fbc6ed57f10]
> 21 0x7fbc6ed442ab /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libvtkGUISupportQt-pv5.9.so.1(+0x262ab) [0x7fbc6ed442ab]
> 20 0x7fbc6f4a41ea QMetaObject::activate(QObject\*, int, int, void\*\*) + 1850
> 19 0x7fbc705837b9 /home/lukas/paraview/ParaView-5.9.0-MPI-Linux-Python3.8-64bit/bin/…/lib/libpqCore-pv5.9.so.1(+0x7a7b9) [0x7fbc705837b9]
> 18 0x7fbc705804f2 pqServerManagerObserver::connectionCreated(long long) + 50
> 17 0x7fbc6f4a41ea QMetaObject::activate(QObject\*, int, int, void\*\*) + 1850
> 16 0x7fbc7063a418 pqServerManagerModel::onConnectionCreated(long long) + 648
> 15 0x7fbc7057f0e2 pqServerManagerModel::serverReady(pqServer\*) + 50
> 14 0x7fbc6f4a41ea QMetaObject::activate(QObject\*, int, int, void\*\*) + 1850
> 13 0x7fbc70605869 pqPluginManager::loadPluginsFromSettings(pqServer\*) + 489
> 12 0x7fbc6e8015ad vtkSMPluginManager::LoadPluginConfigurationXMLFromString(char const\*, vtkSMSession\*, bool) + 157
> 11 0x7fbc6e800be5 vtkSMPluginLoaderProxy::LoadPluginConfigurationXMLFromString(char const\*) + 133
> 10 0x7fbc6e817364 vtkSMProxy::UpdatePropertyInformation() + 20
> 9 0x7fbc6e81f79c vtkSMProxy::UpdatePropertyInformationInternal(vtkSMProperty\*) + 396
> 8 0x7fbc6e84b1c5 vtkSMRemoteObject::PullState(paraview\_protobuf::Message\*) + 117
> 7 0x7fbc6e85529d vtkSMSessionClient::PullState(paraview\_protobuf::Message\*) + 301
> 6 0x7fbc6cf1dea1 vtkMultiProcessStream::operator\>\>(std::string&) + 321
> 5 0x7fbc7206e0ed /lib/x86\_64-linux-gnu/libc.so.6(+0x9a0ed) [0x7fbc7206e0ed]
> 4 0x7fbc7206c47c /lib/x86\_64-linux-gnu/libc.so.6(+0x9847c) [0x7fbc7206c47c]
> 3 0x7fbc720643ee /lib/x86\_64-linux-gnu/libc.so.6(+0x903ee) [0x7fbc720643ee]
> 2 0x7fbc71ff9859 abort + 299
> 1 0x7fbc7201a18b gsignal + 203
> 0 0x7fbc7201a210 /lib/x86\_64-linux-gnu/libc.so.6(+0x46210) [0x7fbc7201a210]
> ( 29.653s) [paraview] :0 FATL| Signal: SIGABRT
> error: exception occurred: Child aborted
---
### Author:  [@mwestphal](https://discourse.paraview.org/u/mwestphal)
#### Post date: [April 27, 2021, 7:54am UTC](https://discourse.paraview.org/t/error-some-error-in-socket-processing/1549/10 "2021-04-27T07:54:12Z")
Can you open an issue : [https://gitlab.kitware.com/paraview/paraview/-/issues](https://gitlab.kitware.com/paraview/paraview/-/issues) ?