Error Deleting Ssl Certificate Bad File Descriptor
Contents |
Developer Within my Apache2 error.log file, i see several error messages like: [error] (9)Bad file descriptor: apr_socket_accept: (client socket) [error] (9)Bad file descriptor: apr_socket_accept: (client socket) [warn] long lost child came home! (pid 12345)
[error] (9)bad File Descriptor: Apr_socket_accept: (client Socket)
[notice] Graceful restart requested, doing restart [error] (9)Bad file descriptor: apr_socket_accept: (client socket) (9)Bad file openssl bad file descriptor descriptor: apr_socket_accept: (client socket) The Bad file descriptor error message seems to appear everytime Apache restarts. Does anyone what this error message means? I had this problem in the past too and understand that it seams to be a bug in Apache2, but now i am not sure... Debian Etch/Apache 2.2.3. Can anyone tell me more about such an error end if possible how to ovoid it. Thanks in advance! Last edited: Sep 4, 2008 Hans, Sep 4, 2008 #1 falko Super Moderator ISPConfig Developer Have you tried to upgrade Debian's Apache package? falko, Sep 5, 2008 #2 Hans Moderator ISPConfig Developer falko said: ↑ Have you tried to upgrade Debian's Apache package?Click to expand... (I know it is not the latest Apache2 version available) but the latest Apache2 version wich comes with Etch is 2.2.3. And as you can see, all the packages are installed already: # apt-get install apache2 apache2-doc apache2-mpm-prefork apache2-utils libexpat1 ssl-cert Reading package lists... Done Building dependency tree... Done apache2 is already the newest version. apache2-doc is already the newest version. apache2-mpm-prefork is already the newest version. apache2-utils is already the newest version. libexpat1 is already the newest version. ssl-cert is already the newest version. 0 upgraded, 0 newly installed, 0 to remove and 2 not upgraded. My system is up to date as i do an apt-get update/upgrade every single day. httpd -V also gives me:Apache 2.2.3 Last edited: Sep 6, 2008 Hans, Sep 5, 2008 #3 falko Super Moderator ISPConfig Developer Seems to be a problem with graceful restarts: http://www.linuxquestions.org/questions/linux-server-73/apache-bad-file-descriptor-593925/ https://issues.apache.org/bugzilla/show_bug.cgi?id=42829 Do you get the same error when you run a normal restart or a stop and then start? falko, Sep 6, 2008 #4 Hans Moderator ISPConfig Developer Thanks Falko, That are the articles i found too. For this reason i think indeed it's a bug in Apache 2.2.3. falko said: ↑ Do you get the same error when you run a normal restart or a stop and then start?Click to expand... When i do a normal start/stop or restart i don't have any er
this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ ssl connection hi,] I am very new user of openssl.In openssl s_client is working fine when i am used without proxy. For Ex: s_client -prexit connect secure.icicicdirect,com:443 -state is working fine but when i am used s_client through proxy ,it is not working and handsaking failed. for Ex: s_client -prexit connect 192.9.202.5.secure.icicidirect.com:443 -state it is https://www.howtoforge.com/community/threads/apache-error-bad-file-descriptor-apr_socket_accept.26571/ not working and handsaking is failed. Is any one can help me. Either gives the better solution for these case. Thanks ravi Kumar seetharaman Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ RE: ssl connection Please use the ipaddress with port number http://openssl.6102.n7.nabble.com/ssl-connection-td3169.html alone and try connecting -----Original Message----- From: [hidden email] [mailto:[hidden email]] On Behalf Of kumarravi_verma (sent by Nabble.com) Sent: Wednesday, January 11, 2006 3:47 PM To: [hidden email] Subject: ssl connection hi,] I am very new user of openssl.In openssl s_client is working fine when i am used without proxy. For Ex: s_client -prexit connect secure.icicicdirect,com:443 -state is working fine but when i am used s_client through proxy ,it is not working and handsaking failed. for Ex: s_client -prexit connect 192.9.202.5.secure.icicidirect.com:443 -state it is not working and handsaking is failed. Is any one can help me. Either gives the better solution for these case. Thanks ravi Kumar View this message in context: ssl connection Sent from the OpenSSL - User forum at Nabble.com. kumarravi_verma Reply | Threaded Open this post in threaded view ♦ ♦ | Report Content as Inappropriate ♦ ♦ RE: ssl connection OpenSSL> s_client -prexit -connect 202.56.245.223:443 -state Load
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers http://stackoverflow.com/questions/24708716/connection-error-using-netimapclient-in-perl or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up Connection error using Net::IMAPClient in Perl up vote 0 down vote favorite I am trying to connect to an Outlook email server via IMAP and the error I am getting is curious. Here is bad file a sample of my code: use Mail::IMAPClient; my $imap = Mail::IMAPClient->new; $host='outlook.office365.com'; $username='.....'; $password='.....'; $folder='INBOX'; $imap=Mail::IMAPClient->new( Server => $host, User => $username, Password => $password, Port => 993, Ssl => 1, Clear=> 5, Folder => $folder, Uid => 0, ) or die "Cannot connect to $host as $username: $@"; When I run this, the output line looks like this: Cannot connect to outlook.office365.com as [...]: Socket closed while reading data from server. More specifically, Socket closed while reading data from server bad file descriptor is what is confusing me. I specify port 993, so is the only remaining possible issue that there's a firewall in place that is preventing this? I have emailed my school's (this is a school email account) tech department (quite some time ago) and they have yet to get back, but hopefully I will hear from them soon. I get an even stranger error when I remove the line specifying the port, I am including it only in the hopes it is somehow relevant or helpful: Cannot connect to outlook.office365.com as [...]: Error sending '1 Login "baldassaren@wit.edu" {15} [password is shown here, along with a newline character I can't seem to force here] ' to IMAP: Bad file descriptor at ./test.pl line 10. perl imap imapclient share|improve this question asked Jul 12 '14 at 1:24 doomsday 588 What's with the assignment on the first line? You are creating a new client and immediately discarding it. I don't think it's the source of your problem but it's a distraction and should be corrected. –tripleee Jul 12 '14 at 6:04 You should turn on the debugging output from IMAPClient and post the resulting transcript (edit your question to include the updated information). –tripleee Jul 12 '14 at 6:07 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Please check directly with openssl: openssl s_client -connect outlook.office365.com:993 This should give you a connec