Bad file descriptor что это

7

Why am I getting a bad file descriptor error?

I am trying to write a short program that acts like a client, like telnet. I receive from the user input like so: www.google.com 80 (the port number) and /index.html However, I get some errors. When I write some debug information, it says that I have a bad file descriptor and Read Failed on file descriptor 100 messagesize = 0.

4 Answers 4

You have a buffer overrun in your code. You’re attempting to allocate a bunch of character arrays together into a buffer than is only 5 bytes long:

This is likely overwriting your local variable hSocket , resulting in the «bad file descriptor error».

Since you’re using C++ (you have a vector in your code), just use a std::string instead of C arrays of characters so that you don’t have to worry about memory management.

Another cause of ‘Bad file descriptor’ can be encountered when trying to write into a location onto which you do not have write permission. For example, when trying to download content with wget in Windows environment:
Cannot write to ‘ftp.org.com/parent/child/index.html’ (Bad file descriptor).

Another case may be the target out file name includes characters the filesystem won’t allow. For instance, suppose you are running wget command on a Linux computer and the target path is an external hard drive formatted with NTFS. The Linux Ext4 filesystem will allow for characters such as ‘?’, but the NTFS filesystem will not. The default behavior for wget is to name the target folder as the specified url. If the url contains a special character like ‘:’, NTFS will not accept that character, resulting in the error "Bad file descriptor". You can disable this default behavior in wget with the —no-host-directories parameter.

Another cause of ‘bad file descriptor’ can be accidentally trying to write() to a read-only descriptor. I was stuck on that for a while because I was spending all my time looking for a second close() or buffer overrun.

Bad file descriptor что это

The error code macros are defined in the header file errno.h . All of them expand into integer constant values. Some of these error codes can’t occur on GNU systems, but they can occur using the GNU C Library on other systems.

Macro: int EPERM ¶

“Operation not permitted.” Only the owner of the file (or other resource) or processes with special privileges can perform the operation.

Macro: int ENOENT ¶

“No such file or directory.” This is a “file doesn’t exist” error for ordinary files that are referenced in contexts where they are expected to already exist.

Macro: int ESRCH ¶

“No such process.” No process matches the specified process ID.

Macro: int EINTR ¶

“Interrupted system call.” An asynchronous signal occurred and prevented completion of the call. When this happens, you should try the call again.

You can choose to have functions resume after a signal that is handled, rather than failing with EINTR ; see Primitives Interrupted by Signals.

Macro: int EIO ¶

“Input/output error.” Usually used for physical read or write errors.

Macro: int ENXIO ¶

“No such device or address.” The system tried to use the device represented by a file you specified, and it couldn’t find the device. This can mean that the device file was installed incorrectly, or that the physical device is missing or not correctly attached to the computer.

Macro: int E2BIG ¶

“Argument list too long.” Used when the arguments passed to a new program being executed with one of the exec functions (see Executing a File) occupy too much memory space. This condition never arises on GNU/Hurd systems.

Macro: int ENOEXEC ¶

“Exec format error.” Invalid executable file format. This condition is detected by the exec functions; see Executing a File.

Macro: int EBADF ¶

“Bad file descriptor.” For example, I/O on a descriptor that has been closed or reading from a descriptor open only for writing (or vice versa).

Macro: int ECHILD ¶

“No child processes.” This error happens on operations that are supposed to manipulate child processes, when there aren’t any processes to manipulate.

Macro: int EDEADLK ¶

“Resource deadlock avoided.” Allocating a system resource would have resulted in a deadlock situation. The system does not guarantee that it will notice all such situations. This error means you got lucky and the system noticed; it might just hang. See File Locks, for an example.

Macro: int ENOMEM ¶

“Cannot allocate memory.” The system cannot allocate more virtual memory because its capacity is full.

Macro: int EACCES ¶

“Permission denied.” The file permissions do not allow the attempted operation.

Macro: int EFAULT ¶

“Bad address.” An invalid pointer was detected. On GNU/Hurd systems, this error never happens; you get a signal instead.

Macro: int ENOTBLK ¶

“Block device required.” A file that isn’t a block special file was given in a situation that requires one. For example, trying to mount an ordinary file as a file system in Unix gives this error.

Macro: int EBUSY ¶

“Device or resource busy.” A system resource that can’t be shared is already in use. For example, if you try to delete a file that is the root of a currently mounted filesystem, you get this error.

Macro: int EEXIST ¶

“File exists.” An existing file was specified in a context where it only makes sense to specify a new file.

Macro: int EXDEV ¶

“Invalid cross-device link.” An attempt to make an improper link across file systems was detected. This happens not only when you use link (see Hard Links) but also when you rename a file with rename (see Renaming Files).

Macro: int ENODEV ¶

“No such device.” The wrong type of device was given to a function that expects a particular sort of device.

Macro: int ENOTDIR ¶

“Not a directory.” A file that isn’t a directory was specified when a directory is required.

Macro: int EISDIR ¶

“Is a directory.” You cannot open a directory for writing, or create or remove hard links to it.

Macro: int EINVAL ¶

“Invalid argument.” This is used to indicate various kinds of problems with passing the wrong argument to a library function.

Macro: int EMFILE ¶

“Too many open files.” The current process has too many files open and can’t open any more. Duplicate descriptors do count toward this limit.

In BSD and GNU, the number of open files is controlled by a resource limit that can usually be increased. If you get this error, you might want to increase the RLIMIT_NOFILE limit or make it unlimited; see Limiting Resource Usage.

Macro: int ENFILE ¶

“Too many open files in system.” There are too many distinct file openings in the entire system. Note that any number of linked channels count as just one file opening; see Linked Channels. This error never occurs on GNU/Hurd systems.

Macro: int ENOTTY ¶

“Inappropriate ioctl for device.” Inappropriate I/O control operation, such as trying to set terminal modes on an ordinary file.

Macro: int ETXTBSY ¶

“Text file busy.” An attempt to execute a file that is currently open for writing, or write to a file that is currently being executed. Often using a debugger to run a program is considered having it open for writing and will cause this error. (The name stands for “text file busy”.) This is not an error on GNU/Hurd systems; the text is copied as necessary.

Macro: int EFBIG ¶

“File too large.” The size of a file would be larger than allowed by the system.

Macro: int ENOSPC ¶

“No space left on device.” Write operation on a file failed because the disk is full.

Macro: int ESPIPE ¶

“Illegal seek.” Invalid seek operation (such as on a pipe).

Macro: int EROFS ¶

“Read-only file system.” An attempt was made to modify something on a read-only file system.

Macro: int EMLINK ¶

“Too many links.” The link count of a single file would become too large. rename can cause this error if the file being renamed already has as many links as it can take (see Renaming Files).

Macro: int EPIPE ¶

“Broken pipe.” There is no process reading from the other end of a pipe. Every library function that returns this error code also generates a SIGPIPE signal; this signal terminates the program if not handled or blocked. Thus, your program will never actually see EPIPE unless it has handled or blocked SIGPIPE .

Macro: int EDOM ¶

“Numerical argument out of domain.” Used by mathematical functions when an argument value does not fall into the domain over which the function is defined.

Macro: int ERANGE ¶

“Numerical result out of range.” Used by mathematical functions when the result value is not representable because of overflow or underflow.

Macro: int EAGAIN ¶

“Resource temporarily unavailable.” The call might work if you try again later. The macro EWOULDBLOCK is another name for EAGAIN ; they are always the same in the GNU C Library.

This error can happen in a few different situations:

An operation that would block was attempted on an object that has non-blocking mode selected. Trying the same operation again will block until some external condition makes it possible to read, write, or connect (whatever the operation). You can use select to find out when the operation will be possible; see Waiting for Input or Output.

Portability Note: In many older Unix systems, this condition was indicated by EWOULDBLOCK , which was a distinct error code different from EAGAIN . To make your program portable, you should check for both codes and treat them the same.

“Operation would block.” In the GNU C Library, this is another name for EAGAIN (above). The values are always the same, on every operating system.

C libraries in many older Unix systems have EWOULDBLOCK as a separate error code.

Macro: int EINPROGRESS ¶

“Operation now in progress.” An operation that cannot complete immediately was initiated on an object that has non-blocking mode selected. Some functions that must always block (such as connect ; see Making a Connection) never return EAGAIN . Instead, they return EINPROGRESS to indicate that the operation has begun and will take some time. Attempts to manipulate the object before the call completes return EALREADY . You can use the select function to find out when the pending operation has completed; see Waiting for Input or Output.

Macro: int EALREADY ¶

“Operation already in progress.” An operation is already in progress on an object that has non-blocking mode selected.

Macro: int ENOTSOCK ¶

“Socket operation on non-socket.” A file that isn’t a socket was specified when a socket is required.

Macro: int EMSGSIZE ¶

“Message too long.” The size of a message sent on a socket was larger than the supported maximum size.

Macro: int EPROTOTYPE ¶

“Protocol wrong type for socket.” The socket type does not support the requested communications protocol.

Macro: int ENOPROTOOPT ¶

“Protocol not available.” You specified a socket option that doesn’t make sense for the particular protocol being used by the socket. See Socket Options.

Macro: int EPROTONOSUPPORT ¶

“Protocol not supported.” The socket domain does not support the requested communications protocol (perhaps because the requested protocol is completely invalid). See Creating a Socket.

Macro: int ESOCKTNOSUPPORT ¶

“Socket type not supported.” The socket type is not supported.

Macro: int EOPNOTSUPP ¶

“Operation not supported.” The operation you requested is not supported. Some socket functions don’t make sense for all types of sockets, and others may not be implemented for all communications protocols. On GNU/Hurd systems, this error can happen for many calls when the object does not support the particular operation; it is a generic indication that the server knows nothing to do for that call.

Macro: int EPFNOSUPPORT ¶

“Protocol family not supported.” The socket communications protocol family you requested is not supported.

Macro: int EAFNOSUPPORT ¶

“Address family not supported by protocol.” The address family specified for a socket is not supported; it is inconsistent with the protocol being used on the socket. See Sockets.

Macro: int EADDRINUSE ¶

“Address already in use.” The requested socket address is already in use. See Socket Addresses.

Macro: int EADDRNOTAVAIL ¶

“Cannot assign requested address.” The requested socket address is not available; for example, you tried to give a socket a name that doesn’t match the local host name. See Socket Addresses.

Macro: int ENETDOWN ¶

“Network is down.” A socket operation failed because the network was down.

Macro: int ENETUNREACH ¶

“Network is unreachable.” A socket operation failed because the subnet containing the remote host was unreachable.

Macro: int ENETRESET ¶

“Network dropped connection on reset.” A network connection was reset because the remote host crashed.

Macro: int ECONNABORTED ¶

“Software caused connection abort.” A network connection was aborted locally.

Macro: int ECONNRESET ¶

“Connection reset by peer.” A network connection was closed for reasons outside the control of the local host, such as by the remote machine rebooting or an unrecoverable protocol violation.

Macro: int ENOBUFS ¶

“No buffer space available.” The kernel’s buffers for I/O operations are all in use. In GNU, this error is always synonymous with ENOMEM ; you may get one or the other from network operations.

Macro: int EISCONN ¶

“Transport endpoint is already connected.” You tried to connect a socket that is already connected. See Making a Connection.

Macro: int ENOTCONN ¶

“Transport endpoint is not connected.” The socket is not connected to anything. You get this error when you try to transmit data over a socket, without first specifying a destination for the data. For a connectionless socket (for datagram protocols, such as UDP), you get EDESTADDRREQ instead.

Macro: int EDESTADDRREQ ¶

“Destination address required.” No default destination address was set for the socket. You get this error when you try to transmit data over a connectionless socket, without first specifying a destination for the data with connect .

Macro: int ESHUTDOWN ¶

“Cannot send after transport endpoint shutdown.” The socket has already been shut down.

Macro: int ETOOMANYREFS ¶

“Too many references: cannot splice.”

Macro: int ETIMEDOUT ¶

“Connection timed out.” A socket operation with a specified timeout received no response during the timeout period.

Macro: int ECONNREFUSED ¶

“Connection refused.” A remote host refused to allow the network connection (typically because it is not running the requested service).

Macro: int ELOOP ¶

“Too many levels of symbolic links.” Too many levels of symbolic links were encountered in looking up a file name. This often indicates a cycle of symbolic links.

Macro: int ENAMETOOLONG ¶

“File name too long.” Filename too long (longer than PATH_MAX ; see Limits on File System Capacity) or host name too long (in gethostname or sethostname ; see Host Identification).

Macro: int EHOSTDOWN ¶

“Host is down.” The remote host for a requested network connection is down.

Macro: int EHOSTUNREACH ¶

“No route to host.” The remote host for a requested network connection is not reachable.

Macro: int ENOTEMPTY ¶

“Directory not empty.” Directory not empty, where an empty directory was expected. Typically, this error occurs when you are trying to delete a directory.

Macro: int EPROCLIM ¶

“Too many processes.” This means that the per-user limit on new process would be exceeded by an attempted fork . See Limiting Resource Usage, for details on the RLIMIT_NPROC limit.

Macro: int EUSERS ¶

“Too many users.” The file quota system is confused because there are too many users.

Macro: int EDQUOT ¶

“Disk quota exceeded.” The user’s disk quota was exceeded.

Macro: int ESTALE ¶

“Stale file handle.” This indicates an internal confusion in the file system which is due to file system rearrangements on the server host for NFS file systems or corruption in other file systems. Repairing this condition usually requires unmounting, possibly repairing and remounting the file system.

Macro: int EREMOTE ¶

“Object is remote.” An attempt was made to NFS-mount a remote file system with a file name that already specifies an NFS-mounted file. (This is an error on some operating systems, but we expect it to work properly on GNU/Hurd systems, making this error code impossible.)

Macro: int EBADRPC ¶

Macro: int ERPCMISMATCH ¶

Macro: int EPROGUNAVAIL ¶

“RPC program not available.”

Macro: int EPROGMISMATCH ¶

“RPC program version wrong.”

Macro: int EPROCUNAVAIL ¶

“RPC bad procedure for program.”

Macro: int ENOLCK ¶

“No locks available.” This is used by the file locking facilities; see File Locks. This error is never generated by GNU/Hurd systems, but it can result from an operation to an NFS server running another operating system.

Macro: int EFTYPE ¶

“Inappropriate file type or format.” The file was the wrong type for the operation, or a data file had the wrong format.

On some systems chmod returns this error if you try to set the sticky bit on a non-directory file; see Assigning File Permissions.

Macro: int EAUTH ¶

Macro: int ENEEDAUTH ¶

Macro: int ENOSYS ¶

“Function not implemented.” This indicates that the function called is not implemented at all, either in the C library itself or in the operating system. When you get this error, you can be sure that this particular function will always fail with ENOSYS unless you install a new version of the C library or the operating system.

Macro: int ELIBEXEC ¶

“Cannot exec a shared library directly.”

Macro: int ENOTSUP ¶

“Not supported.” A function returns this error when certain parameter values are valid, but the functionality they request is not available. This can mean that the function does not implement a particular command or option value or flag bit at all. For functions that operate on some object given in a parameter, such as a file descriptor or a port, it might instead mean that only that specific object (file descriptor, port, etc.) is unable to support the other parameters given; different file descriptors might support different ranges of parameter values.

If the entire function is not available at all in the implementation, it returns ENOSYS instead.

Macro: int EILSEQ ¶

“Invalid or incomplete multibyte or wide character.” While decoding a multibyte character the function came along an invalid or an incomplete sequence of bytes or the given wide character is invalid.

Macro: int EBACKGROUND ¶

“Inappropriate operation for background process.” On GNU/Hurd systems, servers supporting the term protocol return this error for certain operations when the caller is not in the foreground process group of the terminal. Users do not usually see this error because functions such as read and write translate it into a SIGTTIN or SIGTTOU signal. See Job Control, for information on process groups and these signals.

Macro: int EDIED ¶

“Translator died.” On GNU/Hurd systems, opening a file returns this error when the file is translated by a program and the translator program dies while starting up, before it has connected to the file.

Macro: int ED ¶

“?.” The experienced user will know what is wrong.

Macro: int EGREGIOUS ¶

“You really blew it this time.” You did what?

Macro: int EIEIO ¶

“Computer bought the farm.” Go home and have a glass of warm, dairy-fresh milk.

Macro: int EGRATUITOUS ¶

“Gratuitous error.” This error code has no purpose.

Macro: int EBADMSG ¶

Macro: int EIDRM ¶

Macro: int EMULTIHOP ¶

Macro: int ENODATA ¶

Macro: int ENOLINK ¶

“Link has been severed.”

Macro: int ENOMSG ¶

“No message of desired type.”

Macro: int ENOSR ¶

“Out of streams resources.”

Macro: int ENOSTR ¶

“Device not a stream.”

Macro: int EOVERFLOW ¶

“Value too large for defined data type.”

Macro: int EPROTO ¶

Macro: int ETIME ¶

Macro: int ECANCELED ¶

“Operation canceled.” An asynchronous operation was canceled before it completed. See Perform I/O Operations in Parallel. When you call aio_cancel , the normal result is for the operations affected to complete with this error; see Cancellation of AIO Operations.

Macro: int EOWNERDEAD ¶

Macro: int ENOTRECOVERABLE ¶

“State not recoverable.”

The following error codes are defined by the Linux/i386 kernel. They are not yet documented.

[Errno 9] Bad File Descriptor Python Solved

Before jumping right into the content directly, it’s essential to analyze the topics by asking some What and How questions. What is a Bad file descriptor error in Python? How do they occur? What are the ways that can help in solving this kind of errors? When we answer these questions, we can eventually understand the essence of this content by the end of this article.

When you don’t allow the code to perform the functions related to the file descriptors and the methods used, a Bad File Descriptor Error arises in Python, indicating the wrong way of implementing the code.

Kicking start with the basics always helps in understanding the core of the subject and hence assists in finding solutions to the most complex problems ever.

Cause of Errors Python

It’s salient to know that only by encountering many errors in code will you be highly proficient in the specific programming language. When you come across a new error, you try to detect where that error appeared from. Eventually, you start researching how to rectify the mistake.

There are even high chances of you exploring more and achieving various easier ways to apply the code better. At last, you will end up observing that your skills in the concept and knowledge about the same had grown vast.

Errors ought to occur in any possible programming language. In Python, errors generally occur when a particular code segment is not in compliance with the advised usage. Various errors are commonly faced by programmers, which include indentation, syntax, etc.

Rectifying these errors is no big deal when you review your code thoroughly. Have a complete understanding of the concepts and know enough about the right syntax to be used in the code.

What are File Descriptors in Python?

In Python, file descriptors are integers(positive) that identify the kernel’s open files kept in a table of files. They are generally non-negative values.

If found to be negative, that indicates error or a “no value” condition. They assist in performing various functions related to files. Descriptors, in general, are a unique way that Python follows to manage attributes.

They mainly help in accessing files, other input/output devices like network sockets or pipes.

File descriptors do perform various operations. They include:

• close(fd) – closes a file descriptor
• dup(fd1) – duplicates file descriptor
• fstat(fd) – returns the status of a file descriptor

The procedures mentioned above are elementary, and it’s important to know that file descriptors perform many more significant operations following the concept.

Understanding [Errno 9] Bad File Descriptor Error in Python

Have you encountered the following error message when you run your Python code when defining file directories or similar ones?

When you don’t allow the code to perform the functions related to the file descriptors and the methods used, these kinds of issues arise, indicating the wrong way of implementing the code.

Let’s understand this with an example:

The below image shows a code with a bad file descriptor error in the Python shell.

In the above code, the del file will delete the reference of the file object specified. Now, as per the code written, the close function was not called. This forces the destructor to close the file. As this resulted in closing a file that wasn’t open in the first place, OS throws an error – Bad file descriptor.

Best Ways to Solve from [Errno 9] Bad File Descriptor in Python

• Make sure you are using a valid file descriptor number. You will get a UNIX or Python Shell- Bad file descriptor error message when you fail using the right file descriptor number. This can cause issues when you open, close or use a file.
• Use the right modes while handling file descriptors. For example to read from the file you need to use the read mode. When you choose the wrong mode, that triggers an error.
• Analyse the concept and then implement the right functions at the right segments of your code.
• Make certain whether the function to be executed through your code was executed already or not.

[Errno 9] Bad File Descriptor in Python Socket Module

Another main area in which this error is seen is in the Python socket – Socket error Bad file descriptor. When dealing with this kind of program, you can notice that you will find a Bad file descriptor error message is seen along with some issues in opening/closing or accessing the socket.

You can tackle this error by finding the right method of executing the function through the prescribed way of performing the function in accordance with the file descriptor.

One common thing that you can notice while handling errors in Python in relevance to files and file descriptors is that many of us fail to follow and implement the proper functions of the file descriptors defined in the code to perform the operations.

In addition to the above-discussed problems, this issue occurs while executing simple print statements too. You should focus on knowing if your specific file descriptors are available in the console that you are running.

This might seem simple when phrased but can cause a huge trauma to the programmer who has invested hours in writing the code. First, make sure that the specifies file descriptors are available in the console in which you run your program.

How to solve Bad File Descriptor in Python Socket module?

One way of handling this error is to calmly ignore the print statements and use alternative segments of code that serve a similar purpose.

Consider the following code –

This error is caused when you specify a function to get executed when it has already completed doing the job. For instance, you order your code to close a file through your long lines of code. It shows an error like:

It means that the file defined in the program is already closed automatically while running the code. There lies no use in defining a separate method to perform the same task again.

FAQs Related to Bad File Descriptor Python Solved

When we try to perform an operation/activity on closed (non-opened) files, a bad file descriptor error is generated. During such an error, you should look for possibilities where your file may get closed in your code.

In python file descriptors are integers(positive) that do the job of identifying the open files kept in a table of files by the kernel. They are generally non-negative values (0, 1, or 2).

fcntl is a library in Python that controls the file and I/O on file descriptors.

Conclusion

Bad file descriptor mainly arises due to many factors that were discussed in brief above. The main fact is that they occur when the right functions do not perform in association with the file descriptors.

With clear analysis and better knowledge of the concept, one can easily detect these errors and transform the code into a successful one.

Как победить bad file descriptor?

Пытаюсь сделать загрузочную флешку
3-мя программами пробовал ultraiso, rufus,RosaImageWriter
вылетает ошибка при записи bad file descriptor
контрольную сумму образа проверил, все ок
флешка в обычном режиме работает, в чем проблема не пойму

делаю загрузочную debian, linux mint — все ок, стартуют
только пытаюсь записать образ более 2gb (rosa linux, nitrux) — одна программа кидает ошибки
rufus вроде как пишет, но по окончанию с флешки стартануть никак лезут ошибки
флешка 16gb