[OMPI users] Error when trying to kill a spawned process

Hi. I am having a problem when I try to kill a spawned process. I am using ompi 1.4.3. I use the command ompi-clean to kill all the processes I have running, but those ones which were dynamically spawned are not killed. Any idea? Thanks in advance.

[OMPI users] Scheduling dynamically spawned processes

Hi there. I'm developing a distributed system with a communication layer based on Open MPI. As part of my project, I have to create a process scheduler. So I decided to use the MPI_Spawn function to dynamically create (it is an requirement of the system) the process across the cluster's nodes. Is

Re: [OMPI users] Error when trying to kill a spawned process

The point is: I have a system composed by a set of mpi processes. These processes run as daemons in each cluster machine. I need a way to kill those ones when I decide to shutdown the system. Thanks On Fri, May 6, 2011 at 2:51 PM, Rodrigo Oliveira wrote: > Hi. > > I am having a probl

[OMPI users] Problems with Mpi Accept - ORTE_ERROR_LOG

Hi there. I am developing a server/client application using Open MPI 1.5.3. In a point of the server code I open a port to receive connections from a client. After that, I call the function MPI_Comm_accept and on the client side I call MPI_Comm_connect. Sometimes I get an ORTE_ERROR_LOG, as showed

Re: [OMPI users] Problems with Mpi Accept - ORTE_ERROR_LOG

ered by race conditions in the app as well, but ultimately > is something we need to clean up. > > > On Jun 27, 2011, at 9:29 AM, Rodrigo Oliveira wrote: > > Hi there. > > I am developing a server/client application using Open MPI 1.5.3. In a point > of the server code I op

Re: [OMPI users] Problems with Mpi Accept - ORTE_ERROR_LOG

Hi Ralph. The version you have suggested works properly. Thank you so much for the attention. On Mon, Jul 4, 2011 at 3:42 PM, Ralph Castain wrote: > If you download a 1.5 tarball tagged at r24853 or above, the problem should > be fixed. > > > On Jul 4, 2011, at 12:34 PM, R

[OMPI users] Problems with MPI_Iprobe

Hi there. I have an application in which I need to terminate a process anytime due an external command. In order to maintain the consistence of the processes, I need to receive the messages that were already sent to the terminating process. I used the MPI_Iprobe to check whether there is messages

[OMPI users] Flow control in OMPI

Hi there, I am facing some problems in an Open MPI application. Part of the application is composed by a sender and a receiver. The problem is that the sender is so much faster than the receiver, what causes the receiver's memory to be completely used, aborting the application. I would like to kn

Re: [OMPI users] Flow control in OMPI

Hi I am still having this problem in my application. Does someone have a solution or a clue? Thanks On Thu, Aug 25, 2011 at 11:58 PM, Rodrigo Oliveira < rsilva.olive...@gmail.com> wrote: > Hi there, > > I am facing some problems in an Open MPI application. Part of the > appli

[OMPI users] Checkpoint an MPI process

Hi, I'd like to know if there is a way to checkpoint a specific process running under an mpirun call. In other words, is there a function CHECKPOINT(rank) in which I can pass the rank of the process I want to checkpoint? I do not want to checkpoint the entire application, but just one of its proce

Re: [OMPI users] Checkpoint an MPI process

MPI only supports the checkpointing of the whole > > application. There has been some work on uncoordinated checkpointing > > with message logging, though I do not know the state of that work with > > regards to availability. That work has been undertaken by the

Re: [OMPI users] MPI_Comm_split and intercommunicator - Problem

, am I wrong? According to open mpi documentation, this function can be used to do that, but it is not working. Anyone have any idea about what can be? Best regards Rodrigo Oliveira On Mon, Jan 23, 2012 at 4:53 PM, Thatyene Louise Alves de Souza Ramos < thaty...@dcc.ufmg.br> wrote: >

Re: [OMPI users] MPI_Comm_split and intercommunicator - Problem

e process with a color that does not exist in the other group or > with the color = MPI_UNDEFINED. > > On Wed, Jan 25, 2012 at 4:28 PM, Rodrigo Oliveira < > rsilva.olive...@gmail.com> wrote: > >> Hi Thatyene, >> >> I took a look in your code and it seems to be lo

[OMPI users] Problem with MPI_Barrier (Inter-communicator)

am I doing something wrong? Thanks in advance Rodrigo Oliveira

Re: [OMPI users] Problem with MPI_Barrier (Inter-communicator)

al or a small reproducer? It might be > much easier to hunt the problem down... > > Thanks > Edgar > > On 3/19/2012 8:12 PM, Rodrigo Oliveira wrote: > > Hi there. > > > > I am facing a very strange problem when using MPI_Barrier over an > > inter-communicator after

Re: [OMPI users] Problem with MPI_Barrier (Inter-communicator)

The command I use to compile and run is: mpic++ server.cc -o server && mpic++ client.cc -o client && mpirun -np 1 ./server Rodrigo On Tue, Mar 20, 2012 at 3:40 PM, Rodrigo Oliveira wrote: > Hi Edgar. > > Thanks for the response. The simplified code is attached:

Re: [OMPI users] Problem with MPI_Barrier (Inter-communicator)

Hi Edgar, Did you take a look at my code? Any idea about what is happening? I did a lot of tests and it does not work. Thanks On Tue, Mar 20, 2012 at 3:43 PM, Rodrigo Oliveira wrote: > The command I use to compile and run is: > > mpic++ server.cc -o server && mpic++ cl

Re: [OMPI users] Problem with MPI_Barrier (Inter-communicator)

Hi Edgar. Thanks for the response. I just did not understand why the Barrier works before I remove one of the client processes. I tryed it with 1 server and 3 clients and it worked properly. After I removed 1 of the clients, it stops working. So, the removal is affecting the functionality of Barr

Re: [OMPI users] Problem with MPI_Barrier (Inter-communicator)

a lot for your attention and for the solution. Best regards, Rodrigo Oliveira On Tue, Mar 27, 2012 at 1:10 PM, Rodrigo Oliveira wrote: > > Hi Edgar. > > Thanks for the response. I just did not understand why the Barrier works > before I remove one of the client processes. > &