Hello Paraview community,
recently I upgraded to v 6.0.1 and I noticed that calling `pvserver` by `mpiexec` prompts `n` times `connection waiting` messages.
```auto
$ mpiexec -n 3 pvserver
WRN - The configuration file has not been found, using default parameters.
WRN - The configuration file has not been found, using default parameters.
WRN - The configuration file has not been found, using default parameters.
Waiting for client...
Connection URL: cs://DEVICE-NAME:11111
Accepting connection(s): DEVICE-NAME:11111
Waiting for client...
Connection URL: cs://DEVICE-NAME:11111
Waiting for client...
Connection URL: cs://DEVICE-NAME:11111
Accepting connection(s): DEVICE-NAME:11111
Accepting connection(s): DEVICE-NAME:11111
```
I’m testing this on my local machine (windows 11). Also after making the connection using paraview GUI, under `memory inspector` tab, only one processor is connected.
I would appreciate your insights on this issue.
Best regards, hamed
---
I’m not sure if I get the question correctly.
I downloaded `ParaView-6.0.1-MPI-Windows-Python3.12-msvc2017-AMD64.msi` from [www.paraview.org/download/](http://www.paraview.org/download/) and followed the installation procedure using the default settings.
Is there any specific setting that I must check?
---
> [@hamed](#):
>
> `MPI Enabled: On`
Ok, thats good.
So what if you navigate to
```auto
C:\Program Files\ParaView 6.0.1\bin
```
And run
`.\mpiexec.exe -np 4 .\pverser.exe`
---
on the cmd side:
```auto
[Hamed C: ... bin]$ mpiexec.exe -np 4 ./pvserver.exe
WRN - The configuration file has not been found, using default parameters.
WRN - The configuration file has not been found, using default parameters.
WRN - The configuration file has not been found, using default parameters.
WRN - The configuration file has not been found, using default parameters.
Waiting for client...
Connection URL: cs://DESKTOP-VCRFBLH:11111
Waiting for client...
Connection URL: cs://DESKTOP-VCRFBLH:11111
Accepting connection(s): DESKTOP-VCRFBLH:11111
Accepting connection(s): DESKTOP-VCRFBLH:11111
Waiting for client...
Connection URL: cs://DESKTOP-VCRFBLH:11111
Accepting connection(s): DESKTOP-VCRFBLH:11111
Waiting for client...
Connection URL: cs://DESKTOP-VCRFBLH:11111
Accepting connection(s): DESKTOP-VCRFBLH:11111
Client connected.
```
On the Paraview memory inspector:
---
```auto
[Hamed C: ... bin]$ .\mpiexec.exe -np 4 .\pvserver.exe
.\mpiexec.exe : The term '.\mpiexec.exe' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ .\mpiexec.exe -np 4 .\pvserver.exe
+ ~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (.\mpiexec.exe:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
```
BTW, I’m on windows 11
---
> [@hamed](#):
>
> BTW, I’m on windows 11
Please use cmd, not powershell.
ha wait, Im wrong about the command, sorry.
Ill check on my side, one sec.
---
```auto
C:\Users\Hamed>mpiexec
Usage: ./mpiexec [global opts] [local opts for exec1] [exec1] [exec1 args] : [local opts for exec2] [exec2] [exec2 args] : ...
Global options (passed to all executables):
Global environment options:
-genv {name} {value} environment variable name and value
-genvlist {env1,env2,...} environment variable list to pass
-genvnone do not pass any environment variables
-genvall pass all environment variables not managed
by the launcher (default)
Other global options:
-f {name} file containing the host names
-hosts {host list} comma separated host list
Local options (passed to individual executables):
Other local options:
-n/-np {value} number of processes
{exec_name} {args} executable name and arguments
Hydra specific options (treated as global):
Launch options:
-launcher launcher to use (service lsf blaunch)
-launcher-exec executable to use to launch processes
-enable-x/-disable-x enable or disable X forwarding
Resource management kernel options:
-rmk resource management kernel to use (hpc lsf)
Processor topology options:
-bind-to process binding
-map-by process mapping
-membind memory binding policy
Other Hydra options:
-verbose verbose mode
-info build information
-print-all-exitcodes print exit codes of all processes
-ppn processes per node
-prepend-rank prepend rank to output
-prepend-pattern prepend pattern to output
-outfile-pattern direct stdout to file
-errfile-pattern direct stderr to file
-nameserver name server information (host:port format)
-disable-auto-cleanup don't cleanup processes on error
-disable-hostname-propagation let MPICH auto-detect the hostname
-localhost local hostname for the launching node
-usize universe size (SYSTEM, INFINITE, )
Intel(R) MPI Library specific options: