Dears, I still have to verify this but it seems that there's a bug in custom track handling. It happened that some users had hundreds of tracks on a local mirror. Some of those tracks were bigWig pointing to another web server. Due to maintenance the secondary web server (hosting the bigDataUrl) has been switched off. The users received this message:
Error(s): Custom track error (Couldn't connect to host001.instruments.ifom-ieo-campus.it 80 ): removing custom tracks I was expecting only bigWig to disappear but all their tracks were deleted from user session and couldn't be restored. Next week I'm going to test this on an alternate web server hosting bigWig (or any other bigData), meanwhile I would like to know if there is any procedure to rollback users custom track to the last working configuration. I've tried to track users hguid and hgsid, to copy the "content" content in SQL but nothing changes. Thanks d /* Davide Cittaro Cogentech - Consortium for Genomic Technologies via adamello, 16 20139 Milano Italy tel.: +39(02)574303007 e-mail: [email protected] */ _______________________________________________ Genome maillist - [email protected] https://lists.soe.ucsc.edu/mailman/listinfo/genome
