2008/5/30 Jeff Squyres :
> I'd also like to re-emphasize something Andreas said earlier: SIGTERM
> *usually* means that some external entity is killing your
> application. It *could* be coming from within the application itself,
> but that's not too common.
>
> You might want to look into that to
I'd also like to re-emphasize something Andreas said earlier: SIGTERM
*usually* means that some external entity is killing your
application. It *could* be coming from within the application itself,
but that's not too common.
You might want to look into that to find out where the SIGTERM is
On 12:28 Fri 30 May , Lee Amy wrote:
> 2008/5/29 Andreas Schäfer :
> Thank you very much. If I do a shorter job it seems run well. And the job
> dosen't repeatedly fail at the same time, but it will fail at this error
> messages. Anyway, I'm not using a scheduling system. So any suggestions?
A
2008/5/29 Andreas Schäfer :
> Hi Amy,
>
> On 16:10 Thu 29 May , Lee Amy wrote:
> > MicroTar parallel version was terminated after 463 minutes with following
> > error messages:
> >
> > [gnode5:31982] [ 0] /lib64/tls/libpthread.so.0 [0x345460c430
Hi Amy,
On 16:10 Thu 29 May , Lee Amy wrote:
> MicroTar parallel version was terminated after 463 minutes with following
> error messages:
>
> [gnode5:31982] [ 0] /lib64/tls/libpthread.so.0 [0x345460c430]
> [gnode5:31982] [ 1] microtar(LocateNuc
Hello,
I use a bioinformatics software called MicroTar to do some work. But it
seems that it dosen't finish well.
MicroTar parallel version was terminated after 463 minutes with following
error messages:
[gnode5:31982] [ 0] /lib64/tls/libpthread.so
