Error messaging

  • beetle
  • 12/10/07
  • Offline
Posted: Fri, 2011-06-17 19:57

Can someone tell me whose idea it was to use "Bad file descriptor" as an error message? What the heck does it mean? It doesn't tell me why my upload failed. Please make error messages helpful. Don't mean to bad mouth anyone, but dang it I'm frustrated with this thing.


Howdy, Sorry, I know it can

  • andreychek
  • 01/04/09
  • Online Now
  • Fri, 2011-06-17 20:11

Howdy,

Sorry, I know it can be frustrating sometimes :-)

Can you describe exactly what you're doing, and how you're going about doing it? And when in that process do you get that error?

-Eric


I was uploading a zip file

  • beetle
  • 12/10/07
  • Offline
  • Fri, 2011-06-17 20:14

I was uploading a zip file and it got to the end of the upload and said that it failed: Bad file descriptor I just don't know what a file descriptor is, let alone a bad one.


I figured it out. It was the

  • beetle
  • 12/10/07
  • Offline
  • Fri, 2011-06-17 20:26

I figured it out. It was the permissions on the directory I was uploading to. It would seem more useful to me if the error message said something "Failed to upload file: Check file permissions." Maybe it's just me. Anyway, thanks for replying, Eric. I do appreciate the effort.


It generally means that

  • andreychek
  • 01/04/09
  • Online Now
  • Fri, 2011-06-17 20:27

It generally means that something pretty odd went wrong... so we'll need some more details about what's going on there :-)

For example, how are you uploading the file... via FTP? SCP? The Webmin File manager?

Are you overwriting a zip file that already exists on the server, or is this the first time you've uploaded it?

Also, is it possible that account is over quota? If it were, that could produce some unusual messages :-)

-Eric


The account is definitely not

  • beetle
  • 12/10/07
  • Offline
  • Fri, 2011-06-17 20:39

The account is definitely not over quota. I was not overwriting, and I was uploading via the upload/download module in Webmin. As I say though, it turned out to be a permissions issue.