Hi Ashutosh,
Regarding your first email, did you try the configuration option
--enable-m32, which compiles in 32 bit mode? It should solve your problem.
In your last email, what kind of application are you trying to run under
DMTCP? From the info you provided, there's only one process. However, the
socket connection indicates that it's communicating to certain remote
process via socket. DMTCP won't handle the socket correctly in this case.
There're two possible workarounds:
1. Running the remote process under DMTCP as well;
2. Identifying the socket connection and let DMTCP ignore the socket so
that it won't try to drain the socket at ckpt time.
If it's a client-server program, the second way is more suitable, check out
the isBlacklistedTcp() method below:
https://github.com/dmtcp/dmtcp/blob/2.5/src/plugin/ipc/socket/socketconnection.cpp#L220
If the remote peer of the socket is also controlled by you (the user), then
the first solution is better: you can run the processes as a whole
computation under DMTCP.
Let me know if you have any further questions,
Jiajun
On Fri, Apr 29, 2016 at 5:13 PM, Ashutosh Varma <ashutosh.va...@synopsys.com
> wrote:
> Can I get some guidance from this forum if the errors highlighted in my
> original email below can be a problem? I seem to be able to proceed and
> initiate checkpoint both from within the application and dmtcp_coordinator.
>
>
>
> However, the application is not continuing after checkpoint due to:
>
>
>
> client->identity() = 542501268d386022-41000-5723c850
>
> [22905] NOTE at dmtcp_coordinator.cpp:1030 in startCheckpoint;
> REASON='starting checkpoint, suspending all nodes'
>
> s.numPeers = 1
>
> [22905] NOTE at dmtcp_coordinator.cpp:1032 in startCheckpoint;
> REASON='Incremented computationGeneration'
>
> compId.computationGeneration() = 1
>
> [22905] NOTE at dmtcp_coordinator.cpp:392 in updateMinimumState;
> REASON='locking all nodes'
>
> [22905] NOTE at dmtcp_coordinator.cpp:398 in updateMinimumState;
> REASON='draining all nodes'
>
>
>
> which doesn’t complete and I can keep seeing:
>
>
>
> Message: Still draining socket... perhaps remote host is not running under
> DMTCP?
>
> [41000] WARNING at kernelbufferdrainer.cpp:125 in onTimeoutInterval;
> REASON='JWARNING(false) failed'
>
> _dataSockets[i]->socket().sockfd() = 11
>
> buffer.size() = 0
>
> WARN_INTERVAL_SEC = 10
>
>
>
> Which may be a different issue and I would like advise on how to trace
> open sockets.
>
>
>
> -Ash
>
>
>
> *From:* Ashutosh Varma [mailto:ashutosh.va...@synopsys.com]
> *Sent:* Thursday, April 28, 2016 4:23 PM
> *To:* dmtcp-forum@lists.sourceforge.net
> *Subject:* [Dmtcp-forum] 32-bit executable and LD_PRELOAD errors
>
>
>
> I have two issues:
>
>
>
> [100528] WARNING at dmtcp_launch.cpp:762 in setLDPreloadLibs;
> REASON='JWARNING(libdmtcp != "libdmtcp.so") failed'
>
> libdmtcp = libdmtcp.so
>
> Message: You appear to be checkpointing a 32-bit target under 64-bit Linux.
>
> DMTCP was unable to find the 32-bit installation.
>
> See DMTCP FAQ or try:
>
> ./configure --enable-m32 && make clean && make -j && make install
>
> ./configure && make clean && make -j && make install
>
>
>
> ERROR: ld.so: object 'libdmtcp_alloc.so' from LD_PRELOAD cannot be
> preloaded: ignored.
>
> ERROR: ld.so: object 'libdmtcp_dl.so' from LD_PRELOAD cannot be preloaded:
> ignored.
>
> ERROR: ld.so: object 'libdmtcp_ipc.so' from LD_PRELOAD cannot be
> preloaded: ignored.
>
> ERROR: ld.so: object 'libdmtcp_svipc.so' from LD_PRELOAD cannot be
> preloaded: ignored.
>
> ERROR: ld.so: object 'libdmtcp_timer.so' from LD_PRELOAD cannot be
> preloaded: ignored.
>
> ERROR: ld.so: object 'libdmtcp.so' from LD_PRELOAD cannot be preloaded:
> ignored.
>
> ERROR: ld.so: object 'libdmtcp_pid.so' from LD_PRELOAD cannot be
> preloaded: ignored.
>
> [40000] WARNING at dlwrappers.cpp:75 in dlopen; REASON='JWARNING(ret)
> failed'
>
> filename = libnspr4.so
>
> flag = 5
>
> Message: dlopen failed. You may also see a message 'ERROR: ld.so:'
>
> from libdl.so. If this happens only under DMTCP, then consider setting
>
> the environment variable DMTCP_DL_PLUGIN to "0" before 'dmtcp_launch'.
>
> If the problem persists, please write to the DMTCP developers.
>
>
>
> Are both related to the fact that DMTCP is compiled for 64 bit while the
> binary app is 32 bit? It does go ahead even after this error though I could
> not try checkpointing for some other reasons.
>
>
>
> -Ash
>
>
>
>
> ------------------------------------------------------------------------------
> Find and fix application performance issues faster with Applications
> Manager
> Applications Manager provides deep performance insights into multiple
> tiers of
> your business applications. It resolves application problems quickly and
> reduces your MTTR. Get your free trial!
> https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
> _______________________________________________
> Dmtcp-forum mailing list
> Dmtcp-forum@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dmtcp-forum
>
>
------------------------------------------------------------------------------
Find and fix application performance issues faster with Applications Manager
Applications Manager provides deep performance insights into multiple tiers of
your business applications. It resolves application problems quickly and
reduces your MTTR. Get your free trial!
https://ad.doubleclick.net/ddm/clk/302982198;130105516;z
_______________________________________________
Dmtcp-forum mailing list
Dmtcp-forum@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dmtcp-forum