Thanks for the bug report, Michael.  I have now fixed the bug upstream and
it will be part of the next DMTCP release.

Best,
Kapil

On Fri, Oct 17, 2014 at 1:57 PM, Michael Hanke <m...@debian.org> wrote:

> Package: dmtcp
> Version: 2.3.1-5
> Severity: normal
> Tags: upstream
>
> According to the docs the --join option of dmtcp_checkpoint offers a way
> to join an existing coordinator session and properly fail if that is not
> possible. However that option seems broken:
>
> m@meiner /tmp % dmtcp_coordinator --port 0 --daemon
> dmtcp_coordinator (DMTCP) 2.3.1
> License LGPLv3+: GNU LGPL version 3 or later
>     <http://gnu.org/licenses/lgpl.html>.
> This program comes with ABSOLUTELY NO WARRANTY.
> This is free software, and you are welcome to redistribute it
> under certain conditions; see COPYING file for details.
> (Use flag "-q" to hide this message.)
>
> dmtcp_coordinator starting...
>     Host: meiner (127.0.1.1)
>     Port: 45497
>     Checkpoint Interval: disabled (checkpoint manually instead)
>     Exit on last client: 0
> Backgrounding...
> m@meiner /tmp % dmtcp_checkpoint --port 45497 --join sleep 120
> [9065] ERROR at coordinatorapi.cpp:76 in getHostAndPort;
> REASON='JASSERT(mode & CoordinatorAPI::COORD_NEW || mode &
> CoordinatorAPI::COORD_ANY) failed'
> dmtcp_launch (9065): Terminating...
> 99 m@meiner /tmp % dmtcp_checkpoint --port 45497 sleep 120
> m@meiner /tmp %
>                           95%
>
>
> As you can see, dmtcp_checkpoint crashes with --join, but works as
> intended when used without. This bugs leaves, for example, the Condor
> DMTCP shim script without a way to reliably verify that a particular
> coordinator is used.
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (650, 'testing'), (600, 'unstable')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
>
> Kernel: Linux 3.16-2-amd64 (SMP w/4 CPU cores)
> Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages dmtcp depends on:
> ii  libc6       2.19-11
> ii  libgcc1     1:4.9.1-16
> ii  libstdc++6  4.9.1-16
>
> dmtcp recommends no packages.
>
> dmtcp suggests no packages.
>
> -- no debconf information
>

Reply via email to