Project

General

Profile

Actions

Bug #2536

closed

Failed to upload file

Added by mariannaf over 10 years ago. Updated about 10 years ago.

Status:
Invalid
Priority:
Normal
Category:
-
Target version:
-
ASK QUESTIONS IN Forums:

Description

Hello

I'm working with lighttpd version 1.4.32.
OS - Linux 2.6.30 on ARM; gcc - 4.2.1.
Browsers - IE9, Chrome, FireFox
The task is to upload file with size about 30M.
Post message written in javascript, and then call to php to move file to specified folder.
Most of the time, file uploaded successfully. But suddenly something is happen and file is failed to be uploaded.
It doesn't matter file's size (tried to upload 1M,3M,4M without success). I observes chunk files (1M per each), and when it arrives to 29-30 chunks, no aggregation to one file and all these chunks are disappearing. I found several links describing my problem, f.e
http://stackoverflow.com/questions/18243322/uploading-file-through-php-with-lighttpd-not-working-properly
http://redmine.lighttpd.net/issues/1542
But no one of the suggestions didn't worked for me.
HTTP analyzer (Fiddler2) returns error 404 - no such page ??
I'm inside this bug several days and I don't see any light in front :(.
Really need your help.
Thank you in advance, Marianna


Files

lighty_epeg.conf (2.48 KB) lighty_epeg.conf mariannaf, 2013-12-01 12:22
php.ini (48.9 KB) php.ini mariannaf, 2013-12-01 12:22
Actions #1

Updated by giuse_pes over 10 years ago

Hi, thanks for signaling this bug. However, can you upload the configuration used for lighhttpd and for php.ini?
I've tried to reproduce this bug in my local environment several times, but I've never got the problem. I used file between 1MB up to 1GB, and verify them with md5, but they were always uploaded correctly.

Thanks for you help.

Updated by mariannaf over 10 years ago

Thanks for quick response.
Attached find, please, required configuration files.

Actions #3

Updated by mariannaf over 10 years ago

Hello,

Is there some update regarding this bug?
Do you need more information: source code, printouts...

Thanks in advance, Marianna

Actions #4

Updated by stbuehler over 10 years ago

  • Priority changed from Urgent to Normal
  • "But suddenly something is happen and file is failed to be uploaded." - that is not a useful error description. http response code, does php get called at all, lighttpd error log, php error log, does php get the file, ... - perhaps just the php backend is down? perhaps your disk/quota is full (ARM sounds like a rather limited environment)?
  • "and when it arrives to 29-30 chunks, no aggregation to one file and all these chunks are disappearing" - lighttpd doesn't aggregate the files on disk at all, it only sends them via the socket to php, so no bug in lighttpd here.

And: please don't ever set the priority again, as you have no idea what it is for.

Actions #5

Updated by mariannaf over 10 years ago

Hello,

1. HTTP response code: 404 - Not Found
2. On HTTP analyzer Fiddler2 - php source get called
3. No error in lighttpd log
4. No error in php log
5. I verified that Php didn't get a file
6. No problem with disk quota
7. Regarding chunk files - I didn't blame the lighty, just describing the situation.

I search the internet regarding this problem and found several links (send you before) describing my problem, but no solution was found. As I wrote "... suddenly something ...": most of the time uploading of the file pass successfully (different files on different devices), and "suddenly" one file failed to be uploaded and since that time, no file can be uploaded. No reset of device, no reset of browsers help. I provided required config files (lighttpd and php).

Thanks, Marianna

Actions #6

Updated by darix over 10 years ago

add debug.log-request-handling = true to your config
and you will see why it doesnt find your php file. this is a config bug but not a lighty bug. it could also be php returned that 404 to you.

Actions #7

Updated by mariannaf over 10 years ago

Hello,

Thank you for pointing me to the debug flags.
While enabling several debug variables, I could find my bug.

Thanks for the support.

Actions #8

Updated by stbuehler over 10 years ago

  • Status changed from New to Invalid
Actions #9

Updated by stbuehler about 10 years ago

  • Target version deleted (1.4.x)
Actions

Also available in: Atom