Open JimStanford99 opened 8 years ago
sravanareddy
commented
8 years ago We're consuming 62% of 92GB now, so unless they're trying to upload 20GB jobs, there's enough space. Any chance you could test it out on some largish files? It's possible something went wrong on the last batch of code modification (#118).
It's also possible someone else was running a high memory job around the same time they tried uploading. I don't see anything amiss in the server logs, though.
JimStanford99
commented
8 years ago Okay, thanks. I'll check on it.
On Fri, Mar 4, 2016 at 8:14 AM, Sravana Reddy notifications@github.com wrote:
We're consuming 62% of 92GB now, so unless they're trying to upload 20GB jobs, there's enough space. Any chance you could test it out on some largish files? It's possible something went wrong on the last batch of code modification (#118 https://github.com/sravanareddy/darlaweb/pull/118).
It's also possible someone else was running a high memory job around the same time they tried uploading. I don't see anything amiss in the server logs, though.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192279841 .
JimStanford99
commented
8 years ago Can we run WAV files that are 890 MB? They are using an 890 MB WAV file with a TextGrid for boundaries. I'll try it myself.
On Fri, Mar 4, 2016 at 8:49 AM, James Stanford stanfo23@gmail.com wrote:
Okay, thanks. I'll check on it.
On Fri, Mar 4, 2016 at 8:14 AM, Sravana Reddy notifications@github.com wrote:
We're consuming 62% of 92GB now, so unless they're trying to upload 20GB jobs, there's enough space. Any chance you could test it out on some largish files? It's possible something went wrong on the last batch of code modification (#118 https://github.com/sravanareddy/darlaweb/pull/118).
It's also possible someone else was running a high memory job around the same time they tried uploading. I don't see anything amiss in the server logs, though.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192279841 .
sravanareddy
commented
8 years ago It should accept them. Unless the server timed out while running it, but in that case, they'd at least get the job-started confirmation message...
On Fri,Mar 4, at 4:12 PM, JimStanford99 notifications@github.com wrote:
Can we run WAV files that are 890 MB? They are using an 890 MB WAV file with a TextGrid for boundaries. I'll try it myself.
On Fri, Mar 4, 2016 at 8:49 AM, James Stanford stanfo23@gmail.com wrote:
Okay, thanks. I'll check on it.
On Fri, Mar 4, 2016 at 8:14 AM, Sravana Reddy notifications@github.com wrote:
We're consuming 62% of 92GB now, so unless they're trying to upload 20GB jobs, there's enough space. Any chance you could test it out on some largish files? It's possible something went wrong on the last batch of code modification (#118 https://github.com/sravanareddy/darlaweb/pull/118).
It's also possible someone else was running a high memory job around the same time they tried uploading. I don't see anything amiss in the server logs, though.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192279841 .
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192467898.
JimStanford99
commented
8 years ago Thanks. I just sent their file to your cs.dartmouth address. Their 900 MB failed for me, too -- no error message, just not able to upload. Probably too big?
On Fri, Mar 4, 2016 at 6:50 PM, Sravana Reddy notifications@github.com wrote:
It should accept them. Unless the server timed out while running it, but in that case, they'd at least get the job-started confirmation message...
On Fri,Mar 4, at 4:12 PM, JimStanford99 notifications@github.com wrote:
Can we run WAV files that are 890 MB? They are using an 890 MB WAV file with a TextGrid for boundaries. I'll try it myself.
On Fri, Mar 4, 2016 at 8:49 AM, James Stanford stanfo23@gmail.com wrote:
Okay, thanks. I'll check on it.
On Fri, Mar 4, 2016 at 8:14 AM, Sravana Reddy < notifications@github.com> wrote:
We're consuming 62% of 92GB now, so unless they're trying to upload 20GB jobs, there's enough space. Any chance you could test it out on some largish files? It's possible something went wrong on the last batch of code modification (#118 <https://github.com/sravanareddy/darlaweb/pull/118 ).
It's also possible someone else was running a high memory job around the same time they tried uploading. I don't see anything amiss in the server logs, though.
— Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192279841
.
— Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192467898 .
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192527042 .
sravanareddy
commented
8 years ago Seems like a time-out issue when uploading. I'm still looking into it.
sravanareddy
commented
8 years ago It seems that there's no problem on the Apache dev server, only the Lighttpd production one. I assume there's a setting we need to change on the max upload size.
@irenelfeng if you're not too busy with finals, can you poke around and see how to increase the maximum upload size in the lighttpd.conf file? I think the max waiting time is ok, because it's 72000 seconds (20 min), and the upload didn't take nearly that long.
JimStanford99
commented
8 years ago Thanks.
On Sat, Mar 5, 2016 at 8:46 PM, Sravana Reddy notifications@github.com wrote:
It seems that there's no problem on the Apache dev server, only the Lighttpd production one. I assume there's a setting we need to change on the max upload size.
@irenelfeng https://github.com/irenelfeng if you're not too busy with finals, can you poke around and see how to increase the maximum upload size in the lighttpd.conf file? I think the max waiting time is ok, because it's 72000 seconds (20 min), and the upload didn't take nearly that long.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192779609 .
irenelfeng
commented
8 years ago I could look into it a bit tomorrow and/or wednesday, but probably not in between those times as I have a big project due wednesday. I'll let you know how far I get tomorrow if so.
Irene On Mar 5, 2016 10:32 PM, "JimStanford99" notifications@github.com wrote:
Thanks.
On Sat, Mar 5, 2016 at 8:46 PM, Sravana Reddy notifications@github.com wrote:
It seems that there's no problem on the Apache dev server, only the Lighttpd production one. I assume there's a setting we need to change on the max upload size.
@irenelfeng https://github.com/irenelfeng if you're not too busy with finals, can you poke around and see how to increase the maximum upload size in the lighttpd.conf file? I think the max waiting time is ok, because it's 72000 seconds (20 min), and the upload didn't take nearly that long.
— Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192779609
.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-192795244 .
JimStanford99
commented
8 years ago Hi Irene, Will you be able to work on the timeout problem during the break next week? Thanks! Jim
irenelfeng
commented
8 years ago Yes sorry jim! I just realized I didn't look into this week even though I said I would. Finals always eats up more time than expected. I will let you know of any results I get by monday!
Irene On Mar 12, 2016 9:46 PM, "JimStanford99" notifications@github.com wrote:
Hi Irene, Will you be able to work on the timeout problem during the break next week? Thanks! Jim
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-195858815 .
JimStanford99
commented
8 years ago No problem. Thanks, Irene!
On Sat, Mar 12, 2016 at 10:13 PM, irenelfeng notifications@github.com wrote:
Yes sorry jim! I just realized I didn't look into this week even though I said I would. Finals always eats up more time than expected. I will let you know of any results I get by monday!
Irene On Mar 12, 2016 9:46 PM, "JimStanford99" notifications@github.com wrote:
Hi Irene, Will you be able to work on the timeout problem during the break next week? Thanks! Jim
— Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-195858815
.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-195861403 .
irenelfeng
commented
8 years ago can you send me the wav file to try uploading it?
sravanareddy
commented
8 years ago irenelfeng
commented
8 years ago at what point did you get an error?
I successfully uploaded the file, and filled out the speaker information when uploading the file with the textGrid but alignment extraction still failed (in an error email)
JimStanford99
commented
8 years ago Thanks, Irene. Hmm. Well, the problem was in the upload stage. There was no error message -- it just never uploaded, so we assumed it was some kind of timeout problem. The user in Australia first reported the problem with that file, and I had the same problem with the same file then. At that time, Sravana said that it worked on Dev but not on Prod. Which version did you use?
On Sun, Mar 13, 2016 at 8:07 PM, irenelfeng notifications@github.com wrote:
at what point did you get an error?
I successfully uploaded the file, and filled out the speaker information when uploading the file with the textGrid but alignment extraction still failed (in an error email)
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-196086281 .
irenelfeng
commented
8 years ago I looked into the folder where we store all our uploads, and it looked like the file uploaded actually! i was using the production server.
I think the reason I got the error was that I accidentally deleted a file that does the alignment extraction in the FAVE folder. once I get that back I think it should've worked. so once i get that back it should be ok!
On Sun, Mar 13, 2016 at 8:11 PM, JimStanford99 notifications@github.com wrote:
Thanks, Irene. Hmm. Well, the problem was in the upload stage. There was no error message -- it just never uploaded, so we assumed it was some kind of timeout problem. The user in Australia first reported the problem with that file, and I had the same problem with the same file then. At that time, Sravana said that it worked on Dev but not on Prod. Which version did you use?
On Sun, Mar 13, 2016 at 8:07 PM, irenelfeng notifications@github.com wrote:
at what point did you get an error?
I successfully uploaded the file, and filled out the speaker information when uploading the file with the textGrid but alignment extraction still failed (in an error email)
— Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-196086281
.
— Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-196086472 .
sravanareddy
commented
8 years ago Is it all set? Which file was it? If a file was deleted, every job will fail, so I want to make sure it's back up.
sravanareddy
commented
8 years ago @irenelfeng Any luck looking into this timeout error?
irenelfeng
commented
8 years ago Yeah the upload is working for me, after I resaved the lighttpd configuration file - it is taking an hour and a half though. Have you tried since 10am yesterday? That is when I made the change.
However, The fave extract is failing at a certain time too, which is strange. I can open that as a separate issue maybe? On Mar 19, 2016 9:08 PM, "Sravana Reddy" notifications@github.com wrote:
@irenelfeng https://github.com/irenelfeng Any luck looking into this timeout error?
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-198817109
JimStanford99
commented
8 years ago Hmm. Well, this morning I tried the upload again from home -- still stuck on the upload page after almost two hours. But my computer only needed 5-10 minutes to download the same audio file from Dropbox onto my computer, so it doesn't seem to be an Internet speed problem.
On Sun, Mar 20, 2016 at 7:22 AM, irenelfeng notifications@github.com wrote:
Yeah the upload is working for me, after I resaved the lighttpd configuration file - it is taking an hour and a half though. Have you tried since 10am yesterday? That is when I made the change.
However, The fave extract is failing at a certain time too, which is strange. I can open that as a separate issue maybe? On Mar 19, 2016 9:08 PM, "Sravana Reddy" notifications@github.com wrote:
@irenelfeng https://github.com/irenelfeng Any luck looking into this timeout error?
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-198817109
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-198906749
sravanareddy
commented
8 years ago Uploads are always slower than downloads, and it also depends on the speed of Darla's connection, so we can't compare against Dropbox. Still, it shouldn't get stuck. I'll look into later tonight.
On Mar 20, 2016, at 11:51 AM, JimStanford99 notifications@github.com wrote:
Hmm. Well, this morning I tried the upload again from home -- still stuck on the upload page after almost two hours. But my computer only needed 5-10 minutes to download the same audio file from Dropbox onto my computer, so it doesn't seem to be an Internet speed problem.
On Sun, Mar 20, 2016 at 7:22 AM, irenelfeng notifications@github.com wrote:
Yeah the upload is working for me, after I resaved the lighttpd configuration file - it is taking an hour and a half though. Have you tried since 10am yesterday? That is when I made the change.
However, The fave extract is failing at a certain time too, which is strange. I can open that as a separate issue maybe? On Mar 19, 2016 9:08 PM, "Sravana Reddy" notifications@github.com wrote:
@irenelfeng https://github.com/irenelfeng Any luck looking into this timeout error?
— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-198817109
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub < https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-198906749>
— You are receiving this because you commented. Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-198951771
irenelfeng
commented
8 years ago Did you test it again? My job went through in uploading, however something went wrong in FAVE-extract. Here are the errors recorded for the job:
https://www.dropbox.com/s/74egi14b5uep7al/2016_3_19_11_bNgbi.errors?dl=0
JimStanford99
commented
8 years ago Hmm, I was unable to upload it yesterday after two hours. I have never gotten past the upload stage on this file. Thanks for your help.
On Mon, Mar 21, 2016 at 3:47 PM, irenelfeng notifications@github.com wrote:
Did you test it again? My job went through in uploading, however something went wrong in FAVE-extract. Here are the errors recorded for the job:
https://www.dropbox.com/s/74egi14b5uep7al/2016_3_19_11_bNgbi.errors?dl=0
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/sravanareddy/darlaweb/issues/119#issuecomment-199446144
Would you please check to see if the server is full? Some larger jobs from Australia seem to be rejected during upload.