search

uec / Issue.Tracker

Automatically exported from code.google.com/p/usc-epigenome-center
0 stars 0 forks source link

GENEUS entries not showing in ECDP #792

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
Data entered for flow cell C4Y90ACXX not showing up on ECDP, been several days

Original issue reported on code.google.com by cmnico...@gmail.com on 11 Aug 2014 at 3:52

GoogleCodeExporter commented 8 years ago 
I'll check it out.

Original comment by zack...@gmail.com on 11 Aug 2014 at 5:21

GoogleCodeExporter commented 8 years ago 
I see it there, but since there is no analysis for anything yet, its "no date 
entered"

Original comment by zack...@gmail.com on 11 Aug 2014 at 11:27

GoogleCodeExporter commented 8 years ago 
and no fastq exist under
runs/gastorage2/140806_SN550_0413_BC4Y90ACXX/Data/Intensities/BaseCalls

either.

Original comment by zack...@gmail.com on 11 Aug 2014 at 11:40

GoogleCodeExporter commented 8 years ago 
when a run has no files yet, we should use the geneus date.

Original comment by zack...@gmail.com on 12 Aug 2014 at 7:00

GoogleCodeExporter commented 8 years ago 
ECDP and GENEUS are not communicating correctly still.  The new run still shows 
as No Date Entered (even though the analyses are basically finished) and the 
run before has not updated from Reads Available even though analysis files have 
been ready for a couple of days

Original comment by cmnico...@gmail.com on 13 Aug 2014 at 4:04

GoogleCodeExporter commented 8 years ago 
ok, l was hoping it was a fluke that would disappear, but it looks like its 
something else is going on, I will take a deeper look.

Original comment by zack...@gmail.com on 13 Aug 2014 at 5:34

GoogleCodeExporter commented 8 years ago 
That's all I can ask.  Thank you!

On Wed, Aug 13, 2014 at 10:34 AM, <usc-epigenome-center@googlecode.com>
wrote:

Original comment by cmnico...@gmail.com on 13 Aug 2014 at 5:37

GoogleCodeExporter commented 8 years ago 
tracked down the bug

we migrated the role of storegw to our new VM. during the migration it looks 
like the updatedb is failing due to a group permission problem. this means the 
state of the filesystem is stuck in time at Aug 8th. this explains why things 
are stale on ecdp.

fix in progress

Original comment by zack...@gmail.com on 13 Aug 2014 at 9:08

GoogleCodeExporter commented 8 years ago 
I think its fixed now, take a look at the main site (beta hasnt been updated 
yet) and see if it looks correct.

Original comment by zack...@gmail.com on 14 Aug 2014 at 5:05

GoogleCodeExporter commented 8 years ago

Original comment by zack...@gmail.com on 14 Aug 2014 at 8:51