On Fri, May 8, 2015 at 1:27 AM, Gene Cooperman <[email protected]> wrote:
> Anyway, we've now released DMTCP 2.4.0-rc4. As far as we know,
> rc4 should work fine for both 64- and 32-bit Linuxes, and it should
> also work for multi-arch:
> a) are there still any bugs specific to the 32-bit Linux only?
There seems to be a new bug, looks like a minor
oversight regarding some configurations specific
to my setup (perhaps in config, not the code itself?)
This is for python, R, ocaml or anything, I guess:
/installs/dmtcp-dmtcp-ee5cdb6/
bin:cbo: ./dmtcp_restart_script.sh
dmtcp_coordinator starting...
Host: localhost.localdomain (127.0.0.1)
Port: 7779
Checkpoint Interval: disabled (checkpoint manually instead)
Exit on last client: 1
Backgrounding...
[29978] ERROR at dmtcp_restart.cpp:362 in runMtcpRestart;
REASON='JASSERT(false) failed'
newArgs[0] = mtcp_restart-32
newArgs[1] = --fd
(strerror((*__errno_location ()))) = No such file or directory
Message: exec() failed
dmtcp_restart (29978): Terminating...
------------------------------------------------------------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
_______________________________________________
Dmtcp-forum mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
