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

Upgraded to 18.1, did the upgrade from Groupwise Install. In Administration DOM,
  • 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.
  • 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
  • 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.
  • 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
  • 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.
  • gwpoa quits if it doesn't get the desired port while gwia silently ignores it.
  • 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
  • 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.
  • 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
  • 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.