Discussion:
AW: [otrs] [Error][Kernel::System::Email::SMTP::Send][127]Can'tconnect to host: Bad file descriptor!
Buechling, Thomas
2007-10-11 09:35:32 UTC
Permalink
Hallo,

thanks for your fast reply!

exchange.rudolph.log is our mail server, yes...

there are no other errors as far as i can see...

[Wed Oct 10 15:36:47 2007][Notice][Kernel::System::Web::InterfaceAgent::Run] Response::Agent: 1s taken (URL:Action=AgentTicketQueue&QueueID=2:***@localhost)
[Wed Oct 10 15:36:58 2007][Notice][Kernel::System::Web::InterfaceAgent::Run] Response::Agent: 1s taken (URL:Action=AgentTicketCompose&ResponseID=1&TicketID=2&ArticleID=2:***@localhost)
[Wed Oct 10 15:37:02 2007][Error][Kernel::System::Email::SMTP::Send][127] Can't connect to exchange.rudolph.log: Bad file descriptor!
[Wed Oct 10 15:37:02 2007][Notice][Kernel::System::Web::InterfaceAgent::Run] Response::Agent: 0s taken (URL:Action=AgentTicketCompose:***@localhost)
[Wed Oct 10 15:37:27 2007][Notice][Kernel::System::Web::InterfaceAgent::Run] Response::Agent: 2s taken (URL:Action=AdminSysConfig:***@localhost)

-----Ursprüngliche Nachricht-----
Von: otrs-***@otrs.org [mailto:otrs-***@otrs.org]Im Auftrag von
Henning Oschwald
Gesendet: Donnerstag, 11. Oktober 2007 11:30
An: User questions and discussions about OTRS.org
Betreff: Re: [otrs]
[Error][Kernel::System::Email::SMTP::Send][127]Can'tconnect to host: Bad
file descriptor!
I updated from OTRS 2.2.2 to 2.2.3 ( Windows, ITSM 1.0.3 ) and moved
to another host and everything works fine, but i can not send any more
emails! Fetching emails works good, but i can not send any
notifications, mails etc..
Can't connect to exchange.rudolph.log: Bad file descriptor!
Exchange.rudolf.log is your mail relay host, right?

Is there any error message above this one in the logs?

Henning
--
Henning Oschwald
((otrs)) :: OTRS GmbH :: Europaring 4 :: D - 94315 Straubing
Fon: +49 (0) 9421 56818-0 :: Fax: +49 (0) 9421 56818-18
http://www.otrs.com/ :: Communication with success!
Bernd Walter Warter
2007-10-11 10:40:11 UTC
Permalink
Could it be that the server adress is exchange.rudolph-log.de ?
Similar to the domain used for the WWW-Adress ?

Best Regards
Bernd Warter
Post by Buechling, Thomas
Hallo,
thanks for your fast reply!
exchange.rudolph.log is our mail server, yes...
there are no other errors as far as i can see...
[Wed Oct 10 15:37:02 2007][Error][Kernel::System::Email::SMTP::Send][127] Can't connect to exchange.rudolph.log: Bad file descriptor!
-----Ursprüngliche Nachricht-----
Henning Oschwald
Gesendet: Donnerstag, 11. Oktober 2007 11:30
An: User questions and discussions about OTRS.org
Betreff: Re: [otrs]
[Error][Kernel::System::Email::SMTP::Send][127]Can'tconnect to host: Bad
file descriptor!
I updated from OTRS 2.2.2 to 2.2.3 ( Windows, ITSM 1.0.3 ) and moved
to another host and everything works fine, but i can not send any more
emails! Fetching emails works good, but i can not send any
notifications, mails etc..
Can't connect to exchange.rudolph.log: Bad file descriptor!
Exchange.rudolf.log is your mail relay host, right?
Is there any error message above this one in the logs?
Henning
Buechling, Thomas
2007-10-15 10:28:12 UTC
Permalink
After a lot of search a localized the Error...
It seems to be a bug in OTRS:

It only appears when i set ( at Config.pm for example ) the Path of the OTRS-Installation
$Self->{'FQDN'} = 'helpdesk.rudolph.log:4080';
but not when using port 80
$Self->{'FQDN'} = 'helpdesk.rudolph.log';

The Mail script so seems to use this Value at OTRS 2.2.3 ( not at 2.2.2 ), but it can not handle Port Numbers!!!

unfortunately we can not use port 80.. so all the Links in Notification-Mails would be wrong with this setting..
But at least mails can be sent!


Freundliche Grüße

i. A. Thomas Büchling
Praktikant / IT-Services

Tel +49 (0)561/ 4991 -125
Fax +49 (0)561/ 4991 -93125
***@rudolph-log.de
http://www.rudolph-log.de
http://www.logeon.net
--------------------------------------
Rudolph Logistik Gruppe
--------------------------------------
Rudolph Holding GmbH
Harzweg 10
D 34225 Baunatal

Amtsgericht Kassel HRB 6548
Geschäftsführer: Jürgen Rudolph, Werner Rudolph, Torsten Rudolph, Peter Malkomeß
-------------------------------------
Abonnieren Sie unseren Newsletter RudolphREPORT unter http://www.rudolph-log.de/aktuelles/aktuelles.cfm




-----Ursprüngliche Nachricht-----
Von: otrs-***@otrs.org [mailto:otrs-***@otrs.org]Im Auftrag von
Henning Oschwald
Gesendet: Donnerstag, 11. Oktober 2007 11:30
An: User questions and discussions about OTRS.org
Betreff: Re: [otrs]
[Error][Kernel::System::Email::SMTP::Send][127]Can'tconnect to host: Bad
file descriptor!
I updated from OTRS 2.2.2 to 2.2.3 ( Windows, ITSM 1.0.3 ) and moved
to another host and everything works fine, but i can not send any more
emails! Fetching emails works good, but i can not send any
notifications, mails etc..
Can't connect to exchange.rudolph.log: Bad file descriptor!
Exchange.rudolf.log is your mail relay host, right?

Is there any error message above this one in the logs?

Henning
--
Henning Oschwald
((otrs)) :: OTRS GmbH :: Europaring 4 :: D - 94315 Straubing
Fon: +49 (0) 9421 56818-0 :: Fax: +49 (0) 9421 56818-18
http://www.otrs.com/ :: Communication with success!
Nils Breunese (Lemonbit)
2007-10-15 11:29:20 UTC
Permalink
Post by Buechling, Thomas
After a lot of search a localized the Error...
It only appears when i set ( at Config.pm for example ) the Path of the OTRS-Installation
$Self->{'FQDN'} = 'helpdesk.rudolph.log:4080';
but not when using port 80
$Self->{'FQDN'} = 'helpdesk.rudolph.log';
The Mail script so seems to use this Value at OTRS 2.2.3 ( not at
2.2.2 ), but it can not handle Port Numbers!!!
unfortunately we can not use port 80.. so all the Links in
Notification-Mails would be wrong with this setting..
But at least mails can be sent!
A port number is by definition not a part of a fully qualified domain
name, so it would indeed be incorrect to add :4080 to $Self->
{'FQDN'}. I don't know if (or how well) OTRS handles being run on
another port, but this doesn't seem to be the way to configure this.
Maybe someone else on this list can shed some light on running OTRS
on a different port.

Maybe you could just 'hardcode' the :4080 into the notification
template?

Nils Breunese.

Loading...