1. Subscriptions
  2. Services
  3. Hardware
  4. Support

ClearFoundation

Forums
Welcome, Guest
ClearFoundation
Server
Mail
Critical eMail issue after upgrade from 4.3 to 5.1
(1 viewing) 1 Guest
Go to bottomPage: 12
TOPIC: Critical eMail issue after upgrade from 4.3 to 5.1
#7507
Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
Wow! I am in a jam on this one! We had a really nice working 4.3 Enterprise system running. This weekend, I upgraded to 5.1SP1 in order to get the latest/greatest software features for SAMBA, etc.

Now however, the mail system has collapsed. During the upgrade, there was a cyrus-imapd importing error. I thought that I had resolved it by yum remove and reinstalling cyrus-umapd.

Mail seemed to be flowing INTO the system, but, was not delivered to the users. A bit of checking finds the queue filling up with errors. The message log is clogged with lines similar to:

Mar 14 19:12:05 gateway mailfilter[9803]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <001401cac3a0$70e48a90$52ad9fb0$@org>> [pid 9803 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:12:05 gateway mailfilter[9803]: [horde] Failed to connect socket: Connection refused, original code <ID: <001401cac3a0$70e48a90$52ad9fb0$@org>> [pid 9803 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]
Mar 14 19:12:05 gateway mailfilter[9800]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <001401cac3a0$70e48a90$52ad9fb0$@org>> [pid 9800 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:12:05 gateway mailfilter[9800]: [horde] Failed to connect socket: Connection refused, original code <ID: <001401cac3a0$70e48a90$52ad9fb0$@org>> [pid 9800 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]
Mar 14 19:12:05 gateway mailfilter[9804]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <001401cac3a0$70e48a90$52ad9fb0$@org>> [pid 9804 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:12:05 gateway mailfilter[9804]: [horde] Failed to connect socket: Connection refused, original code <ID: <001401cac3a0$70e48a90$52ad9fb0$@org>> [pid 9804 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]
Mar 14 19:12:53 gateway mailfilter[9818]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <20100313124821.druggxxecw@daxx.lowlightguiding.com>> [pid 9818 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:12:53 gateway mailfilter[9818]: [horde] Failed to connect socket: Connection refused, original code <ID: <20100313124821.druggxxecw@daxx.lowlightguiding.com>> [pid 9818 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]
Mar 14 19:13:50 gateway mailfilter[9834]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <20100314231350.32BC97B81BA@gateway.omegafsi.com>> [pid 9834 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:13:50 gateway mailfilter[9834]: [horde] Failed to connect socket: Connection refused, original code <ID: <20100314231350.32BC97B81BA@gateway.omegafsi.com>> [pid 9834 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]
Mar 14 19:14:52 gateway mailfilter[9852]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <20100314231449.E11B87B81C0@gateway.omegafsi.com>> [pid 9852 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:14:52 gateway mailfilter[9852]: [horde] Failed to connect socket: Connection refused, original code <ID: <20100314231449.E11B87B81C0@gateway.omegafsi.com>> [pid 9852 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]
Mar 14 19:14:53 gateway mailfilter[9853]: [horde] PHP Error: fsockopen(): unable to connect to 127.0.0.1:2003 (Connection refused) <ID: <2fb9d3111003141614l68270c3fiebb80dcf1afb5ed7@mail.gmail.com>> [pid 9853 on line 363 of "/usr/webconfig/pear/Kolab/Filter/Filter.php"]
Mar 14 19:14:53 gateway mailfilter[9853]: [horde] Failed to connect socket: Connection refused, original code <ID: <2fb9d3111003141614l68270c3fiebb80dcf1afb5ed7@mail.gmail.com>> [pid 9853 on line 64 of "/usr/webconfig/pear/Kolab/Filter/Transport.php"]


So, apparently, the email is getting delivered to postfix, but, cannot get delivered to the local users. The are tons of errors related to horde / kolab /filter. I yum-removed and reinstalled the 17 modules related to horde, postfix, etc.

So, what am I missing????

What else do you need to see to point me in the right direction?

thank you!
John
John_Satterfield
Fresh Boarder
Posts: 17
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#7508
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
Simple first test - is cyrus running and listening on port 2003 ?
Code:

[root@georgina ~]# service cyrus-imapd status
cyrus-master (pid 3628) is running...
[root@georgina ~]# netstat -nlp | grep -E 'Local|2003'
Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name   
tcp        0      0 127.0.0.1:2003              0.0.0.0:*                   LISTEN      3628/cyrus master   
[root@georgina ~]# 
Tony Ellis
Platinum Boarder
Posts: 486
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2010/03/14 19:57 By track.
The administrator has disabled public write access.
http://kirstie.poweredbyclear.com
  
#7509
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
Tony:

YES to is running...

NO to netstat as per your posting. It comes back blank.

It appears that cyrus-master is listening at 110, 143, and 2000.

So, how do I fix it, Boss-man?
John_Satterfield
Fresh Boarder
Posts: 17
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2010/03/14 20:14 By jsatt4.
The administrator has disabled public write access.
 
#7512
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
I'm not a "Boss-man" - and mail is not my forte

Next question is - what causes cyrus to open port 2003 - judging by your other error messages - I suspect Kolab, but not sure...

Since this is an upgrade - did all of kolab get installed/upgraded? Here's my list for what it is worth...

Code:

[root@georgina ~]# rpm -qa | grep kolab
php-kolab-2.2.0-3.2.v5
perl-kolab-2.2.0-2.2.v5
kolabconf-2.2.0-1.2.v5
app-kolab-5.1-20
kolab-filter-2.2.0-3.1.v5
kolabd-schema-2.2.0-5.5.v5
kolabd-2.2.0-5.5.v5
[root@georgina ~]# 
Tony Ellis
Platinum Boarder
Posts: 486
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
http://kirstie.poweredbyclear.com
  
#7514
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
Please forgive my flippance, Tony. I was just happy to hear from someone who could point me in the right direction. Your input is very much appreciated.

In answer to your questions:

1) I believe that kolab was installed on the 4.3 . I did manually use yum to remove and reinstall kolab, hoping that this would fix it. But, it did not.

2) I have the same kolab modules and versions as your references.

So, I should be looking for where kolab is configured for 2003 instead of 2000?

John
John_Satterfield
Fresh Boarder
Posts: 17
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#7515
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
OK - a little bit of research and found this in /etc/cyrus.conf

Code:

....
  lmtp          cmd="lmtpd -a" listen="127.0.0.1:2003"
....


Now to find out what lmtpd is...
Tony Ellis
Platinum Boarder
Posts: 486
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2010/03/14 20:43 By track.
The administrator has disabled public write access.
http://kirstie.poweredbyclear.com
  
#7516
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
I did check my /etc/services file and see two items:

1) LMTP mail delivery service at TCP and UDP 24

2) cfinger (GNU finger) service at TCP 2003
John_Satterfield
Fresh Boarder
Posts: 17
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#7518
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
I'm out of time at the moment and must go - are these open...

Code:

[root@georgina etc]# netstat -nlp | grep lmtp
unix  2      [ ACC ]     STREAM     LISTENING     10011  3628/cyrus-master   /var/lib/imap/socket/lmtp
unix  2      [ ACC ]     STREAM     LISTENING     10698  3848/master         private/lmtp
[root@georgina etc]# 


I'm sure somehow this gets back to Kolab...

Sorry about the wraps - Code Tags should not allow that...
Tony Ellis
Platinum Boarder
Posts: 486
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2010/03/14 21:06 By track.
The administrator has disabled public write access.
http://kirstie.poweredbyclear.com
  
#7519
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
Yes, these are open.

Tony, I appreciate your time and effort.

John
John_Satterfield
Fresh Boarder
Posts: 17
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#7521
Re:Critical eMail issue after upgrade from 4.3 to 5.1 4 Months, 2 Weeks ago  
Ok - managed to grap a few minutes...

this is a section of /usr/webconfig/pear/Kolab/Filter/Transport.php

Code:

...
    function Transport($host = '127.0.0.1', $port = 2003)
    {
        $this->host = $host;
        $this->port = $port;
        $this->transport = false;
    }

    function &createTransport() {
        return PEAR::raiseError(_("Abstract method Transport::createTransport() called!"));
    }

    function start($sender, $recips)
    {
        $transport = $this->createTransport();
        if ($transport instanceof PEAR_Error) {
            return $transport;
        }
        $this->transport = $transport;
        
        $myclass = get_class($this->transport);
        $this->got_newline = true;

        $result = $this->transport->connect();  
...

The last line is 64 where you get your error - so I think in this case Kolab is a victim - the problem is port 2003 not being opened...

Not sure, but you might be able to stop cyrus with

service cyrus-imapd stop

then run in debug mode - might show something - but check this out first... might require some syslog settings enabled...

/usr/lib/cyrus-imapd/cyrus-master -D
Tony Ellis
Platinum Boarder
Posts: 486
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
http://kirstie.poweredbyclear.com
  
Go to topPage: 12
Moderators: David Loper, Peter Baldwin, Piotr Smalira, Tim Burgess
  get the latest posts directly to your desktop

Google Translate