View Issue Details [ Jump to Notes ] | [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0015316 | ParaView | (No Category) | public | 2015-02-11 17:56 | 2015-09-06 12:17 | ||||
Reporter | Alan Scott | ||||||||
Assigned To | Utkarsh Ayachit | ||||||||
Priority | high | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | unable to reproduce | ||||||
Platform | OS | OS Version | |||||||
Product Version | git-master | ||||||||
Target Version | 4.4 | Fixed in Version | 4.4 | ||||||
Summary | 0015316: Error in output prints when connecting remote server. | ||||||||
Description | Linux, master, remote server. We are now getting an error during connects. The connect is then successful. The error is as follows: ERROR: In ..../ParaView4/ParaViewCore/ClientServerCore/Core/vtkTCPNetworkAccessManager.cxx, line 424 vtkTCPNetworkAccessManager (0x18a5da0): ********************************************************************** Connection failed during handshake. This can happen for the following reasons: 1. Connection dropped during the handshake. 2. vtkSocketCommunicator::GetVersion() returns different values on the two connecting processes (Current value: 100). 3. ParaView handshake strings are different on the two connecting processes (Current value: paraview.4.3.connect_id.844800032). ********************************************************************** Let me know if you need my client and server side command that runs paraview and pvserver. (Note to self - paraview2redsky_4.4.0-junk) | ||||||||
Tags | No tags attached. | ||||||||
Project | Sandia | ||||||||
Topic Name | |||||||||
Type | incorrect functionality | ||||||||
Attached Files | |||||||||
Relationships | |
Relationships |
Notes | |
(0034359) Utkarsh Ayachit (administrator) 2015-04-13 11:46 edited on: 2015-04-13 11:47 |
I don't know where to begin with this one. You must be getting a similar message on the client side, are you? If so, what does that print out? Basically, I need the messages printed out on both the client and the server root node and we can see what can can diagnose. |
(0034552) Utkarsh Ayachit (administrator) 2015-06-12 23:19 |
requesting feedback. Please feel free to reopen if you're still seeing this. |
(0034561) Alan Scott (manager) 2015-06-15 19:03 |
This has magically gone away. I will write it up again if it appears again. |
Notes |
Issue History | |||
Date Modified | Username | Field | Change |
2015-02-11 17:56 | Alan Scott | New Issue | |
2015-02-11 17:57 | Alan Scott | Target Version | => 4.4 |
2015-04-13 11:46 | Utkarsh Ayachit | Note Added: 0034359 | |
2015-04-13 11:47 | Utkarsh Ayachit | Note Edited: 0034359 | |
2015-06-12 23:19 | Utkarsh Ayachit | Note Added: 0034552 | |
2015-06-12 23:19 | Utkarsh Ayachit | Status | backlog => customer review |
2015-06-12 23:19 | Utkarsh Ayachit | Resolution | open => fixed |
2015-06-12 23:19 | Utkarsh Ayachit | Assigned To | => Utkarsh Ayachit |
2015-06-12 23:19 | Utkarsh Ayachit | Resolution | fixed => unable to reproduce |
2015-06-15 19:03 | Alan Scott | Note Added: 0034561 | |
2015-06-15 19:03 | Alan Scott | Status | customer review => closed |
2015-06-15 19:03 | Alan Scott | Fixed in Version | => git-master |
2015-09-06 12:17 | Utkarsh Ayachit | Fixed in Version | git-master => 4.4 |
Issue History |
Copyright © 2000 - 2018 MantisBT Team |