OTRS cannot send Notifications after server IP change

Hello, after a change of IP, our OTRS installation is not able to send notifications anymore. At error_log we see: [Thu Oct 11 09:06:02 2012] [error] [client 194.79.86.4] Invalid method in request \x03 [Thu Oct 11 09:06:06 2012] [error] [client 194.79.86.4] Invalid method in request \x03 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Oct 11 10:58:33 2012, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Message: Can't connect to LXWMTS02: Invalid argument!, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Traceback (11551): , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Email::SMTP::Send (v1.21.2.2) Line: 91, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Email::Send (v1.45) Line: 553, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Ticket::Article::SendAgentNotification (v1.185.2.2) Line: 2073, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Ticket::Article::ArticleCreate (v1.185.2.2) Line: 370, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::Modules::AgentTicketClose::Run (v1.46) Line: 494, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Web::InterfaceAgent::Run (v1.35) Line: 824, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: /opt/otrs/bin/cgi-bin/index.pl (v1.87) Line: 47, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 [Thu Oct 11 11:00:07 2012] [error] [client 172.26.129.198] ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Oct 11 11:00:07 2012, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489 The old IP used to be 172.26129.21 and now is 172.26.130.5. Since the SMTP server LXWMTS02 is reachable and the login/password used for authentication did not change, I don´t know what could be happening? Some info stored in database or any config file maybe? Does anyone have some idea? Thanks for any input and feedback you can provide.

Can the OTRS server ping and telnet LXWMTS02 port 25? On Fri, Oct 12, 2012 at 5:10 PM, Maurício Ramos < Mauricio.Ramos@wedotechnologies.com> wrote:
Hello, after a change of IP, our OTRS installation is not able to send notifications anymore. At error_log we see:****
** **
[Thu Oct 11 09:06:02 2012] [error] [client 194.79.86.4] Invalid method in request \x03****
[Thu Oct 11 09:06:06 2012] [error] [client 194.79.86.4] Invalid method in request \x03****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Oct 11 10:58:33 2012, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Message: Can't connect to LXWMTS02: Invalid argument!, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Traceback (11551): , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Email::SMTP::Send (v1.21.2.2) Line: 91, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Email::Send (v1.45) Line: 553, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Ticket::Article::SendAgentNotification (v1.185.2.2) Line: 2073, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Ticket::Article::ArticleCreate (v1.185.2.2) Line: 370, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::Modules::AgentTicketClose::Run (v1.46) Line: 494, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Web::InterfaceAgent::Run (v1.35) Line: 824, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: /opt/otrs/bin/cgi-bin/index.pl (v1.87) Line: 47, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
[Thu Oct 11 11:00:07 2012] [error] [client 172.26.129.198] ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Oct 11 11:00:07 2012, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489****
** **
The old IP used to be 172.26129.21 and now is 172.26.130.5. Since the SMTP server LXWMTS02 is reachable and the login/password used for authentication did not change, I don´t know what could be happening? Some info stored in database or any config file maybe?****
** **
Does anyone have some idea? ****
** **
Thanks for any input and feedback you can provide.****
** **
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Hello,
It could be that LXWMTS02 has relay configured for the old IP address and
now that it has changed, it no longer accept SMTP request from your OTRS
machine. Have you seen the logs at LXWMTS02 and it's mail relay
configuration?
Leonardo Certuche
www.itconsultores.com.co
Medellín, Colombia
On 12 October 2012 17:45, Gerald Young
Can the OTRS server ping and telnet LXWMTS02 port 25?
On Fri, Oct 12, 2012 at 5:10 PM, Maurício Ramos < Mauricio.Ramos@wedotechnologies.com> wrote:
Hello, after a change of IP, our OTRS installation is not able to send notifications anymore. At error_log we see:****
** **
[Thu Oct 11 09:06:02 2012] [error] [client 194.79.86.4] Invalid method in request \x03****
[Thu Oct 11 09:06:06 2012] [error] [client 194.79.86.4] Invalid method in request \x03****
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Oct 11 10:58:33 2012, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Message: Can't connect to LXWMTS02: Invalid argument!, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Traceback (11551): , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Email::SMTP::Send (v1.21.2.2) Line: 91, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Email::Send (v1.45) Line: 553, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Ticket::Article::SendAgentNotification (v1.185.2.2) Line: 2073, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Ticket::Article::ArticleCreate (v1.185.2.2) Line: 370, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::Modules::AgentTicketClose::Run (v1.46) Line: 494, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: Kernel::System::Web::InterfaceAgent::Run (v1.35) Line: 824, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] Module: /opt/otrs/bin/cgi-bin/index.pl (v1.87) Line: 47, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 10:58:33 2012] [error] [client 172.26.129.198] , referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
[Thu Oct 11 11:00:07 2012] [error] [client 172.26.129.198] ERROR: OTRS-CGI-10 Perl: 5.8.8 OS: linux Time: Thu Oct 11 11:00:07 2012, referer: http://172.26.130.5/otrs/index.pl?Action=AgentTicketClose&TicketID=489*** *
** **
The old IP used to be 172.26129.21 and now is 172.26.130.5. Since the SMTP server LXWMTS02 is reachable and the login/password used for authentication did not change, I don´t know what could be happening? Some info stored in database or any config file maybe?****
** **
Does anyone have some idea? ****
** **
Thanks for any input and feedback you can provide.****
** **
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs
--------------------------------------------------------------------- OTRS mailing list: otrs - Webpage: http://otrs.org/ Archive: http://lists.otrs.org/pipermail/otrs To unsubscribe: http://lists.otrs.org/cgi-bin/listinfo/otrs

Hello and thanks you all for helping us out with this issue.
We found hard coded at ./Kernel/Config/Files/ZZZAuto.pm.ori a reference to the old IP at the line that says ...
$Self->{'SendmailModule::Host'} = '172.26.129.21';
We found this by issuing a find command like ...
[otrs@fpwdev01 ~]$ pwd
/opt/otrs
[otrs@fpwdev01 ~]$ find ./ -type f -exec grep "172.26" {} \; -print
$Self->{'SendmailModule::Host'} = '172.26.129.21';
./Kernel/Config/Files/ZZZAuto.pm.ori
.
.
.
After correcting this to the new IP everything went back to normal operation!
Just registering, our OTRS installation is 2.3.4.
Thanks you all again!!
From: otrs-bounces@otrs.org [mailto:otrs-bounces@otrs.org] On Behalf Of Leonardo Certuche
Sent: sábado, 13 de outubro de 2012 12:31
To: User questions and discussions about OTRS.
Subject: Re: [otrs] OTRS cannot send Notifications after server IP change
Hello,
It could be that LXWMTS02 has relay configured for the old IP address and now that it has changed, it no longer accept SMTP request from your OTRS machine. Have you seen the logs at LXWMTS02 and it's mail relay configuration?
Leonardo Certuche
www.itconsultores.com.cohttp://www.itconsultores.com.co
Medellín, Colombia
On 12 October 2012 17:45, Gerald Young
participants (3)
-
Gerald Young
-
Leonardo Certuche
-
Maurício Ramos