Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Register
  • Sign in
  • ParaView ParaView
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 2k
    • Issues 2k
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 84
    • Merge requests 84
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Artifacts
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ParaViewParaView
  • ParaViewParaView
  • Issues
  • #2206
Closed
Open
Issue created Sep 01, 2005 by Kitware Robot@kwrobotOwner

server crashes while loading data when number of procs>2

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.


the server crashes with the following error messages when number of pvserver > 2, but after client connects to the server:

Error message:Listen on port: 11111 Waiting for client... connected to port 11111 Client connected. Process id: 0 >> ERROR: In /home/johnny/app/paraview/paraview-2.2.1/VTK/IO/vtkDataReader.cxx, line 432 vtkDataSetReader (0x200d5e0): Unrecognized file type: ##* for file: (Null FileName)

Process id: 0 >> ERROR: In /home/johnny/app/paraview/paraview-2.2.1/VTK/Filtering/vtkExecutive.cxx, line 680 vtkStreamingDemandDrivenPipeline (0x200d450): Algorithm vtkDataSetReader(0x200d5e0) returned failure for request: vtkInformation (0x200d8e0) Debug: Off Modified Time: 29862 Reference Count: 1 Registered Events: (none) ALGORITHM_AFTER_FORWARD: 1 FORWARD_DIRECTION: 0 REQUEST_DATA_OBJECT: 1

[node01:3] Fatal Error: Unexpected disconnect received from [node01:0] at line 1698 in file vapiutil.c [node01:2] Fatal Error: [node01:1] Fatal Error: Unexpected disconnect received from [node01:0] at line 1698 in file vapiutil.c Unexpected disconnect received from [node01:0] at line 1698 in file vapiutil.c

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking