Custom Track URL error

[Zhangsj]

Hi, dear UCSC members

I want to upload BAM file to UCSC, but got the following error:

Can't access My BAM's bigDataUrl ftp://162.105.138.90/adipose.sorted.bam and/or the associated index file ftp://162.105.138.90/adipose.sorted.bam.bai: TCP non-blocking connect() to 162.105.138.90 timed-out in select() after 10000 milliseconds - Cancelling! 

The track line is: track type=bam name="My BAM" bigDataUrl=ftp://162.105.138.90/adipose.sorted.bam

I had set up FTP server on 162.105.138.90 with vsFTP and config it as passive connection mode as UCSC requires. The anonymous FTP is on. The adipose.sorted.bam.bai has been in the same directory as adipose.sorted.bam.

Did I miss something else? Hope your reply.

------------------

With best wishes,

Shijian Sky Zhang

---------------------------------------
Institute of Molecular Medicine, Peking University
Yingjie Exchange Center
Beijing 100871, China
E-mail: zhang...@foxmail.com

           zhang...@pku.edu.cn

 

[Steve Heitner]

Hello, Shijian.

I just attempted to browse to your FTP site and it was unavailable.  If you are unable to view the contents of the directory in a web browser, you will likewise be unable to load your files as a custom track.  Make sure that when you browse to ftp://162.105.138.90, you can see your files in the directory.  Once you can do that, try loading your custom track again.

Please contact us again at gen...@soe.ucsc.edu if you have any further questions.

---
Steve Heitner
UCSC Genome Bioinformatics Group

--
 
 
 

[Zhangsj]

Sorry, I should had told that I had tried this and I really could view my data on browser and I don't set the listen_address for vsftp. So I guess it's not the IP permit for UCSC to access my FTP.

------------------ Original ------------------

From:  "Steve Heitner"<st...@soe.ucsc.edu>;

Date:  Tue, Apr 2, 2013 01:59 AM

To:  "'Zhangsj'"<zhang...@foxmail.com>; "'genome'"<gen...@soe.ucsc.edu>;

Subject:  RE: [genome] Custom Track URL error

[Steve Heitner]

Hello, Shijian.

If you are unable to solve the connection problem at your institution, you may consider one of the many public storage solutions available.  Also, we recommend using HTTP rather than FTP.  The URL will operate more efficiently, requiring only one connection and a single request rather than two connections and several setup requests.

--