Highlighted
New Member.
1825 views

0CA0 Error Listen Port 143 is already in use. [856A

Upgraded to 18.1, did the upgrade from Groupwise Install. In Administration DOM, & PO shows to be GW18.1

After upgrade POA would not start.

Looked in log and had the following line "15:54:00 0CA0 Error Listen Port 143 is already in use. [856A]"

Went into POA-Agent settings unchecked IMAP
POA would still not restart. Rebooted Windows Server 2016
POA still would not start.
Stopped MTA & Internet Agent, Tried starting POA again and it started.
Went to restart MTa & IA, they both started and POA is still running.

We use IMAP for phones but afraid to recheck the box since have had so much trouble trying to get POA running

Anyone got any ideas?

Labels (1)
0 Likes
11 Replies
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

While an infrastructure service such as mail really shouldn't run on Windows...
What does
netstat -abno
(run from an administrative prompt) show as owning process for port 143 when this issue strikes? Is IMAP enabled at GWIA level?
Is the database level at 1810?
It might, of course, also be a plain defect due to some sort of timing issue.
0 Likes
Highlighted
New Member.

Re: 0CA0 Error Listen Port 143 is already in use. [856A

mathiasbraun;2490830 wrote:
While an infrastructure service such as mail really shouldn't run on Windows...
What does
netstat -abno
(run from an administrative prompt) show as owning process for port 143 when this issue strikes?
Running netstat -abno with IMAP unchecked in POA and POA now running does not show anything using 143

Is IMAP enabled at GWIA level?
Yes
Is the database level at 1810?
Yes
It might, of course, also be a plain defect due to some sort of timing issue.


Problem did not start until after upgrading to 18.1

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

If i understand this correctly you've previously had imap enabled on both POA and GWIA. On which ports? I'm asking because you mentioned "...not show anything using 143" which would, if GWIA's IMAP listener would be configured for 143, mean that we'd have an additional issue there.
0 Likes
Highlighted
New Member.

Re: 0CA0 Error Listen Port 143 is already in use. [856A

mathiasbraun;2490874 wrote:
If i understand this correctly you've previously had imap enabled on both POA and GWIA. On which ports? I'm asking because you mentioned "...not show anything using 143" which would, if GWIA's IMAP listener would be configured for 143, mean that we'd have an additional issue there.


Yes, IMAP was enabled on both GWIA & POA before upgrade to 18.1 I was only able to get POA to running after upgrading to 18.1 by turning IMAP off in POA, starting POA first and then GWIA & MTA

Yesterday I went and turned on POP in GWIA since I was hoping I could get email to our phones. As I was going to change my phone over to POP I started getting emails via IMAP. So in GWIA I have both pop & IMAP enabled and IMAP NOT enabled in the POA but getting emails to phones via IMAP.

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

So it's been merely a config issue, as when two daemons compete for the same port on the same box, likely one of them will fail. Obviously something has changed with applying 18.1.0, maybe
- gwpoa, instead of silently tolerating that it doesn't get a desired port, now quits entirely in this situation or
- timing has changed in regards to "how claims port 143 first"
i'll do a quickcheck in lab.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

gwpoa quits if it doesn't get the desired port while gwia silently ignores it.
0 Likes
Highlighted
New Member.

Re: 0CA0 Error Listen Port 143 is already in use. [856A

mathiasbraun;2491008 wrote:
gwpoa quits if it doesn't get the desired port while gwia silently ignores it.


It's working now so I am not going to mess with it, but I thought I had to have both GWIA & POA have IMAP enabled to have IMAP to work. But with me having both IMAP and POP enabled in GWIA I have IMAP working so I am going to leave alone. My firewall is blocking the POP port so I am OK with having POP enabled.

0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

Historically there hasn't been any IMAP or POP3 support on the POA at all. If enabled at GWIA level, GWIA will build C/S connections to the POs in question on behalf of the user. You can nowadays have enabled e.g. IMAP on both POA and GWIA, but you must configure different ports (or different ip addresses) if they're running on the same box.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

On 18.11.2018 03:34, mathiasbraun wrote:
>
> Historically there hasn't been any IMAP or POP3 support on the POA at
> all. If enabled at GWIA level, GWIA will build C/S connections to the
> POs in question on behalf of the user. You can nowadays have enabled
> e.g. IMAP on both POA and GWIA, but you must configure different ports
> (or different ip addresses) if they're running on the same box.
>
>

Well, that's very old History. IMAP support in the POA is there for many
many versions and years now. At *least* since Groupwise 6.5, but maybe
even before that.

I'm surprised this has worked before. Must be a windows thing. On Linux,
both GWIA and POA forever since don't start when they find a port they
are supposed to use is in use already. *Except* when there are multiple
IP addresses available, and the port is available on at least one IP,
then it starts.

CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

As mentioned. I've tested (and just retested) with an 18.1.0 system (running on linux, of course. No infrastructure services on client OS). GWIA silently goes ahead if the required port is already allocated while POA quits at loadtime. So either this behaviour is new with 18.1.0 or timing has changed in the OP's system in a way that GWIA wins the race for port 143 and the POA angrily quits.
0 Likes
Highlighted
Knowledge Partner
Knowledge Partner

Re: 0CA0 Error Listen Port 143 is already in use. [856A

On 19.11.2018 12:44, mathiasbraun wrote:
>
> As mentioned. I've tested (and just retested) with an 18.1.0 system
> (running on linux, of course. No infrastructure services on client OS).
> GWIA silently goes ahead if the required port is already allocated while
> POA quits at loadtime.


That's a change from the last time I ran into it (2012 or 2014, not 100%
sure). Back then (and in older versions too), GWIA would definitely quit
(very silently I might add, without writing a single line into the logs)
when the IMAP port was taken (by the POA, or some other service) at
start time.


CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
CU,
--
Massimo Rosen
Micro Focus Knowledge Partner
No emails please!
http://www.cfc-it.de
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.