[SOLVED] gpgme error: Bad file descriptor

I tried to install a new system today. I chrooted into it and wanted to install some packages, but all I got was this error instead:
error: GPGME Error: bad file descriptor
error: <package>: missing required signature
And that for each and every single package...
I ran pacman-key --init and --populate, set SigLevel to Optional in pacman.conf, did pacman -Syu and all you want, still got the same error.
Last edited by DeatzoSeol (2012-06-17 22:55:10)

... which I have. Still the same.
OMG! I re-checked and found out there's no procfs in my chroot. Damn me it works now... what did I learn today? double-check your chroot.
Thanks
Last edited by DeatzoSeol (2012-06-17 22:55:46)

Similar Messages

Error : Bad file descriptor

Hi All,
I am getting Bad file descriptor error message while trying to run the below code :
try {
HSSFWorkbook wb = new HSSFWorkbook();
HSSFSheet sheet = wb.createSheet("Excel Sheet");
HSSFRow rowhead = sheet.createRow((short) 0);
rowhead.createCell((short) 0).setCellValue("Roll No");
rowhead.createCell((short) 1).setCellValue("Name");
rowhead.createCell((short) 2).setCellValue("Class");
rowhead.createCell((short) 3).setCellValue("Marks");
rowhead.createCell((short) 4).setCellValue("Grade");
int index = 1;
while (index<=110){
        HSSFRow row = sheet.createRow((short) index);
        row.createCell((short) 0).setCellValue(index);
        row.createCell((short) 1).setCellValue("Java");
        row.createCell((short) 2).setCellValue("Write to Excel");
        row.createCell((short) 3).setCellValue(index+15);
        row.createCell((short) 4).setCellValue("NA");
          index++;
       FileOutputStream fileOut = new FileOutputStream("\\\\remotepc1111\\C$\\test\\TestExcel.xls");
     wb.write(fileOut);
     fileOut.close();
catch (Exception e) {
System.out.println(e.getMessage());
}I read some where on the internet that this could be because of fileOut.close(). I tried after commenting that, but result was same.
Could some one point me what mistake I am making.
Thanks a lot.
AR

RAMJANE wrote:
As I am running this code through JSP file so printStackTrace() is not working for me. From Java standalone program it is working fine.The general strategy when doing old school JSP development is to use a servlet to do the business logic stuff and a JSP only to render the view. The strategy is basically to:
- enter in the Servlet which will do stuff and prepare data
- any data prudent to the view is put in the request scope using setAttribute()
- make the servlet forward to the JSP that renders the view (which does not always have to be the same one!)
- render the view using JSTL only - no Java code and/or scriptlets
that creates clean, easy to debug and maintain code. Of course that does mean that each 'page' has at least two resources, but that is true for most of any framework you can use too.
As for printStackTrace() "not working" - the output ends up in the server's log files. Check there.

Upload-Szenario - WDRuntimeException Bad file descriptor

Hi All,
i'm using the Adobe Document Services on a NW04, ADS SP 19, NWDS 2.0.19 with IE 6.0.2900 SP2.
If i use the Upload-UI-Element to show a PDF i got the error: Bad file descriptor !!
The PDF to upload is not corrupt, an i can open it with Acrobat Reader or the Tutorial (Download-Upload-Szenario) - Example.
I had a binary Value-Attribute mapped as Data-Element of the UploadUI-Element. Read the Context-Value-Attribute to the controller context element and the Interactive Form Element had the reference to the attribute as pdfsource. The same code as the tutorial.
What's wrong ?
I didn't find anything about the error !
Thanks for help.
Regards Jürgen
Exception(com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Bad file descriptor) during processing a Web Dynpro Application, Session with IDs: (J2EE7802600)ID1177271450DB10984010199363513659End,78651230d78a11db9c34000d608e44df,Id78651230d78a11db9c34000d608e44df6
[EXCEPTION]
com.sap.tc.webdynpro.services.exceptions.WDRuntimeException: Bad file descriptor
     at com.sap.tc.webdynpro.clientimpl.http.client.AbstractHttpClient.updateUpLoad(AbstractHttpClient.java:478)
     at com.sap.tc.webdynpro.progmodel.context.ModifiableBinaryType.parse(ModifiableBinaryType.java:95)
     at com.sap.tc.webdynpro.clientserver.data.DataContainer.doParse(DataContainer.java:1418)
     at com.sap.tc.webdynpro.clientserver.data.DataContainer.validatePendingUserInput(DataContainer.java:1328)
     at com.sap.tc.webdynpro.clientserver.data.DataContainer.validatePendingUserInput(DataContainer.java:672)
     at com.sap.tc.webdynpro.clientserver.cal.ClientComponent.validate(ClientComponent.java:624)
     at com.sap.tc.webdynpro.clientserver.cal.ClientApplication.validate(ClientApplication.java:741)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.transportData(WebDynproMainTask.java:712)
     at com.sap.tc.webdynpro.clientserver.task.WebDynproMainTask.execute(WebDynproMainTask.java:649)
     at com.sap.tc.webdynpro.clientserver.cal.AbstractClient.executeTasks(AbstractClient.java:59)
     at com.sap.tc.webdynpro.clientserver.cal.ClientManager.doProcessing(ClientManager.java:251)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doWebDynproProcessing(DispatcherServlet.java:154)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doContent(DispatcherServlet.java:116)
     at com.sap.tc.webdynpro.serverimpl.defaultimpl.DispatcherServlet.doPost(DispatcherServlet.java:55)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
     at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:401)
     at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:266)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:387)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:365)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.invokeWebContainer(RequestAnalizer.java:944)
     at com.sap.engine.services.httpserver.server.RequestAnalizer.handle(RequestAnalizer.java:266)
     at com.sap.engine.services.httpserver.server.Client.handle(Client.java:95)
     at com.sap.engine.services.httpserver.server.Processor.request(Processor.java:160)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
     at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:100)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:170)
Caused by: java.io.IOException: Bad file descriptor
     at java.io.FileInputStream.readBytes(Native Method)
     at java.io.FileInputStream.read(FileInputStream.java:177)
     at com.sap.tc.webdynpro.clientimpl.http.client.AbstractHttpClient.writeIn2Out(AbstractHttpClient.java:493)
     at com.sap.tc.webdynpro.clientimpl.http.client.AbstractHttpClient.updateUpLoad(AbstractHttpClient.java:435)
     ... 29 more

Two things I think helped to solve this
PROPAGATE_EXCEPTIONS = True
in config.py and I removed threading from my vassal ini file the ending uwsgi files looked like this:
/etc/uwsgi/emperor.ini:
[uwsgi]
emperor = /etc/uwsgi/vassals
master = true
plugins = python2
uid = http
gid = http
[/etc/uwsgi/vassals/test.ini:
[uwsgi]
chdir = /srv/http/test_dir/src
wsgi-file = run.py
callable = app
processes = 4
stats = 127.0.0.1:9191
max-requests = 5000
enable-threads = true
vacuum = true
thunder-lock = true
socket = /run/uwsgi/test-sock.sock
chmod-socket = 664
harakiri = 60
logto = /var/log/uwsgi/test.log
Not sure on the
PROPAGATE_EXCEPTIONS = True
but removing the threads option in test.ini and making sure there was a master option in emperor.ini seemed to have solved the issue of sql being tossed around to different treads, or at least it complaining about it and crashing the site out, either or.
Also don't use the uwsgi from this distribution, get it from pip, the distros are broken.

[SOLVED] Cups refuses to work: "bad file descriptor"

I am not getting CUPS to work on a new installation.
I need to use cups as a client printing to a printer attached to a separate server. What I did:
1. I installed the cups package and started/enabled the service in systemd.
2. The remote server has a working CUPS installation (accessible and working from other computers)
3. I can see the remote printer listed among the printers in CUPS's local web interface
However, every job sent to the printer (from the GUI: KDE based apps such as Okular, etcetera) silently fails.
No job is ever listed on the CUPS web interface.
If I try to check on CUPS status with lstat I get the following error:
$> lpstat
lpstat: bad file descriptor
Any suggestion on how to fix the problem?
Edit: more info
It seems that cups is running fine according to systemd:
[stefano@gorgias ~]$ systemctl status cups
● cups.service - CUPS Printing Service
Loaded: loaded (/usr/lib/systemd/system/cups.service; enabled)
Active: active (running) since Mon 2014-08-04 17:56:32 CDT; 16h ago
Main PID: 2832 (cupsd)
Status: "Scheduler is running..."
CGroup: /system.slice/cups.service
└─2832 /usr/bin/cupsd -f
Aug 04 17:56:32 gorgias systemd[1]: Started CUPS Printing Service.
but not so according to CUPS itself:
[stefano@gorgias ~]$ lpstat -t
scheduler is not running
no system default destination
lpstat: Bad file descriptor
lpstat: Bad file descriptor
lpstat: Bad file descriptor
lpstat: Bad file descriptor
lpstat: Bad file descriptor
So systemd tells me the scheduler is running, while CUPS claims it is not
Last edited by stefano (2014-08-06 22:15:53)

Stefano,
I can't thank you enough for posting your solution! I have spent the last several days trying to get libreoffice and evince to even see my printer. I've been up and down so many cups web interface sessions, I lost count long ago. Finally, I came across some commands I'd never seen before, in particular 'lpstat' which also gave me the 'bad file descriptor' message. Googling provided next to nothing in help, but it did produce a link to your post, which is like finding a needle in a haystack! Anyway, I updated /etc/cups/client.conf as you suggested, and now my applications can finally see my Brother HL-2280DW.
For what it's worth, I'm running a fresh archlinux install (as of a week or two ago), and just installed cups a few days ago:
root<t1>@benito:/etc/cups# uname -a
Linux benito 3.16.1-1-ARCH #1 SMP PREEMPT Thu Aug 14 07:40:19 CEST 2014 x86_64 GNU/Linux
root<t1>@benito:/etc/cups# pacman -Qs cups
local/brother-hl2280dw 2.0.4_2-3
Brother HL-2280DW CUPS Driver
local/cups 1.7.5-1
The CUPS Printing System - daemon package
local/cups-filters 1.0.57-1
OpenPrinting CUPS Filters
local/cups-pdf 2.6.1-2
PDF printer for cups
local/libcups 1.7.5-1
The CUPS Printing System - client libraries and headers
local/python2-pycups 1.9.66-2
Python CUPS Bindings
local/system-config-printer 1.4.4-1
A CUPS printer configuration tool and status applet
Again, my sincere thanks!!
(BTW, I'd also like to know why /etc/cups/client.conf doesn't work as advertised...)
Last edited by archzen (2014-08-24 06:44:58)

System error 9 bad file descriptor

Hello. I am running system 10.3.9 and when I try to sync I get this error message, "system error 9 bad file descriptor." Needless to say I am unable to sync. Has anyone run into this problem? Are there any suggestions to fix it?

We have authorization problem, restric by OHD technical name.

Installation:CSynEvent::~CSynEvent: an error occured;: Bad file descriptor

Hi,
CSynEvent::~CSynEvent: an error occured;: Bad file descriptor
I am getting the above error when I try installing SAP Netweaver 2004s SR1 on RedHat Linux 5.00
1. started ./sapinst in putty
2. started ./startInsGui.sh in HummingBird
Please help.
thanks,
Arun.

Dear Arun,
if you get the message
login timeout: unable to establish a valid connection
the sapinst GUI cannot connect to the sapinst server.
1) if you are using remote sapinst GUI
-> check if firewall is off via:
iptables -L
if your output is not like
# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination
then the firewall is active. Please shut it down or open the port for sapinst GUI
2) if you are using local sapinst GUI
-> check if X forwarding works (e.g.) via calling xterm or xeyes
Thanks,
Hannes

Bad File Descriptor ERROR

Hi Friends,
Here is my scenario:
while (INFINITE_LOOP) {
     1. Create eraser.db DB with enabling environment & no transaction in dir: /DB_DIR
     2. Create expire.db DB without enabling environment & no transaction in same dir: /DB_DIR
     3. Perform add - remove record operations on both dbs.
     3. Close both dbs & environment
     4. Remove entire directory : /DB_DIR (using posix rmdir & unlink apis)
     5. sleep for 2 mins. (This is for stress testing... actual sleep value is 24 hrs)
This while loop works for few iterations. But after few iterations I start getting below errors:
seek: 0: (0 * 4096) + 0: Bad file descriptor
eraser.db: write failed for page 0
eraser.db: unable to flush page: 0
seek: 4096: (1 * 4096) + 0: Bad file descriptor
eraser.db: write failed for page 1
eraser.db: unable to flush page: 1
seek: 8192: (2 * 4096) + 0: Bad file descriptor
eraser.db: write failed for page 2
eraser.db: unable to flush page: 2
Once these errors start occuring. All the db operations start failing for all the following iterations.
Now I have to stop my program & restart, then only db starts working as expected.
Kindly suggest the root cause of the problem.
Regards,
~ Ashish K.

Hi Friends,
The above mentioned issues was not related to BDB. Finally I found "opened once, but closed twice" file descriptor issue in my multi threaded code.In our code a socket descriptor was getting closed twice. After few iterations of running, this problem was unintentionally leading to closing of one of the internal file descriptor of BDB. Once I fixed that problem. BDB started working as expected.
For those who are unfamiliar to closing twice issue in multi threaded code read below:
foo ()
    fd = open();
    // some processing.
    close (fd);
    // some processing.
    close (fd);
The above code will work smoothly for a single threaded application. But in our case of multithreading, if a thread "X" call open(), when thread "Y" is in between the two close() calls, then in that case, thread "X" will get the same fd for open which thread "Y" was using (since open always return the smallest unused descriptor). File descriptors are shared by all the threads. So when thread "Y" carries out its second close(), it actually closes the file descriptor of thread "X", which was valid & in use.
This is what precisely happening with my code.
TIP: Whenever your multi threaded code, starts giving BDB errors like "Bad file descriptor" first check if there is a place in code where you are "opening once but closing twice" any file descriptor.
Regards,
~ Ashish K.

Ssh -W causes "getsockname failed: Bad file descriptor" errors

Using openssh 6.5p1-2, this error(?) message occurs frequently
getsockname failed: Bad file descriptor
This has been reported to debian and mindrot:
https://bugzilla.mindrot.org/show_bug.cgi?id=2200
https://bugs.debian.org/cgi-bin/bugrepo … bug=738693
and has been fixed:
https://bugzilla.mindrot.org/attachment.cgi?id=2407
Can this patch be applied to the official arch openssh package?

Have a look on the Arch bugtracker and see if it has been logged. If it hasn't, and hasn't been accepted upstream, you could open a report there: it's more likely a developer will see it there...

Oracle Portal item cannot be deleted using dav (Bad File Descriptor)

I cannot delete an Oracle Portal item with webdav. I get an error 500 and the item is not deleted.
When this same user logs in as portal user with a browser, the item kan be deleted.
So the user permissions are probably not the problem.
What can be the problem?
How do I have to solve this?
<h1>Info found in log files</h1>
<h2>C:\OraHome_2\webcache\logs</h2>
Here I find an access.log file, but this one does not seem to contain anything useful.
<h2>C:\OraHome_2\Apache\Apache\logs\</h2>
Here I find two recent log files:
<h3>access_log.1340236800</h3>
HTTP/1.1" 207 3215
192.168.6.57 - - [21/Jun/2012:09:28:53 +0200] "DELETE /dav_portal/portal/Bibnet/Open_Vlacc_regelgeving/Werkgroepen/vlacc_wgCAT/fgtest.txt HTTP/1.1" 500 431
<h3>error_log.1340236800</h3>
[Thu Jun 21 09:28:53 2012] [error] [client 192.168.6.57] [ecid: 3781906711623,1] Could not DELETE /dav_portal/portal/Bibnet/Open_Vlacc_regelgeving/Werkgroepen/vlacc_wgCAT/fgtest.txt. [500, #0] [mod_dav.c line 2008]
[Thu Jun 21 09:28:53 2012] [error] [client 192.168.6.57] [ecid: 3781906711623,1] (9)Bad file descriptor: Delete unsuccessful. [500, #0] [dav_ora_repos.c line 8913]
In the error log, you also often find back message :
[Thu Jun 21 10:33:02 2012] [notice] [client 192.168.6.57] [ecid: 3421133404379,1] ORA-20504: User not authorized to perform the requested operation
This has probably nothing to do with it, you also have this message when the delete is successful.
<h1>Versions I have used</h1>
Dav client: I have tried with clients "Oracle Drive 10.2.0.0.27 Patch" and Cyberduck 4.2.1
Oracle Portal 10.1.4
In the errorX.log file, I find back these lines too:
[Thu Jun 21 09:53:17 2012] [notice] [client 192.168.6.57] [ecid: 4348843884218,1] OraDAV: Initializing OraDAV Portal Driver (1.0.3.2.3-0030) using API version 2.00
[Thu Jun 21 09:53:17 2012] [notice] [client 192.168.6.57] [ecid: 4348843884218,1] OraDAV: oradav_driver_info Name=interMedia Version=2.3

You may want to try a rebuild of the DAV tables in Oracle Portal. Before you do so, take a backup of the Portal repository database to ensure that you can revert back in case of disaster.
Rebuilding the DAV tables is done with the following instructions :
<li> Start SQL*PLUS and connect to the Portal metadata repository database as PORTAL user
<li> Execute wwdav_loader.create_dav_content :
SQL> exec wwdav_loader.create_dav_content();{code}
Thanks,
EJ

Suddenly can't create dirs or files!? "Bad file descriptor"

Tearing my hair out...
Suddenly, neither root nor users can create files or directories in directories under /home. Attempting to do so gets: Error -51 in Finder, "Bad file descriptor" from command line, and "Invalid file handle" via SMB.
However, files and dirs can be: read, edited, moved, and occasionally copied. Rebooting made no difference.
Anyone have a clue on where to start on this?
Mac OS X 10.3.9. Dual G4 XServe with 2 x 7 x 250 G XRAID.
Many Mac OS X (10.3.9) Many
Many Mac OS X (10.3.9) Many

Indeed. This whole episode has exposed rather woeful lack of robustness on the part of the X Server and XRAID... various things failing and server hanging completely as a result of a few bad files on disk.. with lack of useful feedback as to what was happening.
Best I can tell, we had reached the stage where the next available disk location for directory or file was bad... blocking any further additions.
I've embarked on the process of copying everything off, remove crash-provoking files, replace one bad drive (hot swap didn't work), erase all, perform surface conditioning (bad-block finding) procedure, and maybe later this century will be copying all files back.
Looks to me like the bad block finding procedure is finding a few bad blocks on the supposedly good drives... presumably will isolate those, but maybe we need to get more new drives.
Many Mac OS X (10.3.9) Many

Bad File Descriptor in /dev/fd/3, and 94Gb of disk space missing

I noticed a few days ago, possibly as the result of a recent kernel panic, that I have a large chunk of hard drive space missing. The Finder reports that I have approximately 89Gb of free space, but using "df" reports that there is approximately 178Gb free. Using "du" doesn't report any unexpected huge files, so I tried running GrandPerspective. In addition to the usual file usage and free space, this shows a single 94Gb block of "miscellaneous used space".
I then booted into Single User mode to run fsck on the startup drive. This reported several errors, and took 3 passes to repair the directory structure, but didn't recover the missing space. I have subsequently run TechTool Pro and DiskWarrior on the startup drive (both of which found various minor errors), but the 94Gb still refuses to show itself.
I then tried using "find" to look for single large files, using "sudo find / -size +94371840" (anything larger than 90Gb), and I get the following errors:
find: /dev/fd/3: Bad file descriptor
find: /dev/fd/4: Not a directory
find: /dev/fd/5: Not a directory
After searching Google, a "Bad file descriptor" error points to an inode issue, that fsck cannot fix, but I don't know enough (read: anything) about inodes to risk running the clri command to zero the problem inode.
Short of blanking the startup disk and installing from scratch (not an attractive option), is there anything I can do to fix the broken inode and recover the missing space?
Any help appreciated.

Drawing Business wrote:
I then tried using "find" to look for single large files, using "sudo find / -size +94371840" (anything larger than 90Gb), and I get the following errors:
find: /dev/fd/3: Bad file descriptor
find: /dev/fd/4: Not a directory
find: /dev/fd/5: Not a directory
This is not an error and always happens with find unless you exclude the /dev hierarchy from the search. (Interestingly this seems to have gone away with 10.5??)
To locate your missing space, try WhatSize. Another alternative which I have not used personally is Disk Inventory X.
As an additional point, with 10.4 it is actually better to use Disk Utility, since it does more than fsck: Resolve startup issues and perform disk maintenance with Disk Utility and fsck, quote:
Note: If you're using Mac OS X 10.4 or later, you should use Disk Utility instead of fsck, whenever possible.

"The document 'Backup of Backup of Oral Report' could not be saved as 'Oral Report'. Bad file descriptor"

Hello,
Whenever I try to save my Keynote file, I receive an error message saying: "The document 'Backup of Backup of Oral Report' could not be saved as 'Oral Report'. Bad file descriptor".
I've tried using other name to save my file, saving the file as a backup, saving it within my documents, and on a USB, but the file won't save. I'm using Keynote '09, Version 5.1.1 (1034) on my Mac Desktop running Mac OS X Version 10.6.8
How can I fix this problem and save my file?

change icloud backup to local backup on this compuet. this worked for me.

Bad File Descriptor

Hello !
The following program is giving the above mentioned error. Can anyone help.
God bless you.
NADEEM
/** Using FileOutputStream(File object, boolean append) */
import java.io.* ;
// import java.lang.Thread ;                                     No need !
public class CopyingText {
public static void main(String args[]) {
int s ;                                // No need ! Do it directly.
Thread t = new Thread();
try {
   System.out.println("Enter java CopyingText Source.txt Target.txt\n");
   FileInputStream a = new FileInputStream(args[0]);
   FileOutputStream b = new FileOutputStream(args[1],true);
   s = a.available();
   System.out.println("Source Size : main() : " + a.available());
   System.out.println(a.getFD() + "\n");
    CopyingTxt rw = new CopyingTxt(a,b);
    rw.fileCopying(s);
    rw.bytesAvailable(s);             //IOException: Bad file descriptor : Reason ?
} catch(IOException e) {
    System.out.println("Main() :" + e );
    t.dumpStack();
class CopyingTxt extends CopyingText {
private int i , j ;
FileInputStream fa ;
FileOutputStream fb ;
CopyingTxt(FileInputStream a, FileOutputStream b) {
   fa = a ;
   fb = b ;
public int bytesAvailable(int s) throws IOException {
   System.out.println(fa.getFD() );
   System.out.println("Source Size : BytesAvailable() : " + s + " | " + fa.available());           // Giving problem ?
   return fa.available() ;
public void fileCopying(int s) throws IOException {
   bytesAvailable(s);                     // Placing after line 63 moves the
   do {                                   // marker to the end of file giving 0.
    i = fa.read();
    j++ ;
    if(i != -1) fb.write(i) ;
   } while(i!= -1);                       //EOF condition -1 .
   System.out.print("Bytes read : FileCopying()    :" + (j-1) + " | " + fa.available());
//   System.out.println(" File marker reaches the EOF(-1) , therefore giving 0.");
   fa.close();
   fb.close();

bob has no sister.Ah. Thanks for clarifying.
Indeed he has known no other woman since he found the true love of the jav.Not even a little action on the side? I'm impressed.

Bad File Descriptor when I try to create an Tale

I am getting the following error when I execute the ./dbca on Red Hat Linux
java.io.IOException: Bad file descriptor
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(FileInputStream.java:194)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(StreamDecoder.java:408)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(StreamDecoder.java:450)
at sun.nio.cs.StreamDecoder.read(StreamDecoder.java:182)
at java.io.InputStreamReader.read(InputStreamReader.java:167)
at java.io.BufferedReader.fill(BufferedReader.java:136)
at java.io.BufferedReader.readLine(BufferedReader.java:299)
at java.io.BufferedReader.readLine(BufferedReader.java:362)
at oracle.sysman.assistants.util.sqlEngine.SQLEngine$ErrorStreamReader.run(SQLEngine.java:1985)
at java.lang.Thread.run(Thread.java:534)

Hello Naveen,
I am experiencing exactly the same error message when trying to create a database through dbca(RH LInux). The assistant guides me through the process of locating the directories and naming the database but when I validate all choices and try to finish up the process I get the following error and dbca seem to enter some kind of loop. However nothing of the database is created. Did you manage to pass that stage if yes could you let me know how you went throught it. I am stuck to that point and no script was generated to manually create the DB.
If anyone else has a clue your advices are much awaited thanks in advance.
Nzavi
java.io.IOException: Bad file descriptor
at java.io.FileInputStream.readBytes(Native Method)
at java.io.FileInputStream.read(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.readBytes(Unknown Source)
at sun.nio.cs.StreamDecoder$CharsetSD.implRead(Unknown Source)
at sun.nio.cs.StreamDecoder.read(Unknown Source)
at java.io.InputStreamReader.read(Unknown Source)
at java.io.BufferedReader.fill(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at java.io.BufferedReader.readLine(Unknown Source)
at oracle.sysman.assistants.util.sqlEngine.SQLEngine$ErrorStreamReader.run(SQLEngine.java:1985)
at java.lang.Thread.run(Unknown Source)

Java.io.IOException: Bad file descriptor Jetty 9.2.10.v20150310

I started jetty in nonstop server on port 18095 and it was running fine, few days later suddenly noticed it consumes more CPU, when I check the log noticed the following log writing continiously
2015-07-08 13:25:48.606:WARN:oejs.ServerConnector:qtp26807578-18-acceptor-0@182e42f-ServerConnector@1f02fde {HTTP/1.1}{0.0.0.0:18095}:
java.io.IOException: Bad file descriptor (errno:4009)
at sun.nio.ch.ServerSocketChannelImpl.accept0(Native Method)
at sun.nio.ch.ServerSocketChannelImpl.accept(ServerSocketChannelImpl.java:241)
at org.eclipse.jetty.server.ServerConnector.accept(ServerConnector.java:377)
at org.eclipse.jetty.server.AbstractConnector$Acceptor.run(AbstractConnector.java:500)
at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:635)
at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:555)
at java.lang.Thread.run(Thread.java:724)
Can any one guess the root cause. Thanks.

I am using jdbc to connect the database. I want to update the blob fields that is picture into the database. Now i am using preparedstatement to update the fields. When it causes error, it will closed automatically. At that time, it causes bad file descriptor.

[SOLVED] gpgme error: Bad file descriptor

Similar Messages

Maybe you are looking for