Hey Ido,
I actually copied & pasted those committed changes in dramaa.py manually
and it serves well as a temporary solution.
D
On Tue, Jan 22, 2013 at 10:51 PM, Ido Tamir wrote:
> Is it possible to backport this onto the latest distribution?
> Yes, I'm lazy, but there are also others that ar
Is it possible to backport this onto the latest distribution?
Yes, I'm lazy, but there are also others that are still updating
within the next weeks and will have problems without them being
aware of this fix.
best,
ido
On Jan 21, 2013, at 9:50 PM, Nate Coraor wrote:
> Hi all,
>
> The commit[1
Thanks Nate,
I tried that commit and seems it fixes the issue.
Thanks
Derrick
On Tue, Jan 22, 2013 at 7:50 AM, Nate Coraor wrote:
> Hi all,
>
> The commit[1] that fixes this is not in the January 11 distribution.
> It'll be part of the next distribution.
>
> --nate
>
> [1]
> https://bitbuck
Hi all,
The commit[1] that fixes this is not in the January 11 distribution. It'll be
part of the next distribution.
--nate
[1]
https://bitbucket.org/galaxy/galaxy-central/commits/c015b82b3944f967e2c859d5552c00e3e38a2da0
On Jan 21, 2013, at 3:10 PM, Anthonius deBoer wrote:
> I have seen thi
I have seen this same issue exactly. Python just dies without any errors in the
log. Using the latest galaxy-dist
Sent from my iPhone
On Jan 20, 2013, at 8:35 PM, Derrick Lin wrote:
> Update to the 11 Jan 2013 dist does not help with this issue. :(
>
> I checked the database and have the look
Update to the 11 Jan 2013 dist does not help with this issue. :(
I checked the database and have the look at the job entries that handler0
tried to stop then shutdown:
| 3088 | 2013-01-03 14:25:38 | 2013-01-03 14:27:05 |531 |
toolshed.g2.bx.psu.edu/repos/kevyin/homer/homer_findPeaks/0.1.2
I had a close look at the code in
galaxy-dist / lib / galaxy / jobs / handler.py
galaxy-dist / lib / galaxy / jobs / runners / drmaa.py
and found that stopping "deleted" and "deleted_new" seems to be normal
routine for the job handler. Could not find any exception that caused the
shutdown.
I do
Hi guys,
We have updated our galaxy to 20 Dec 2012 release. Recently we found that
some submitted jobs could not start (stay gray forever).
We found that it was caused by the job manager sent jobs to a handler
(handler0) whose python process crashed and died.
>From the handler log we found the l
