Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Absent Member.
Absent Member.
1374 views

Upgraded to 1.2.4 one of five POAs will now not work

Hi.

I had 1.2.3 upgraded on wednesday night to 1.2.4 and I have 5 separate sites, the main site with it's GW 8.0.2 connector and the mobile server and 4 other sites, these 4 other sites are 3 x 8.0.2 on oes2 the other is on windows 2008 with 8.0.3.

This creates 5 POA's in total. One of our remote 8.0.2 POAs just stopped talking to mobility the minute we did the upgrade and that is it... It's not talked since. I am completely stumped I can remotely connect to the far POA i've restarted the server the poa the mobility server, i've shutdown groupwise completely on the local server on the same site as the mobility server and nothing has fixed it.

I can talk to port 7191 on the remote server via telnet and get the exact same message as I get from all our other remote sites. I can do this back to the main server as well.... everything looks fine it's still talking via LDAP as I can log onto the mobility server as one of the users on port 8120 but it will just not connect to that site at all. Telnet test shows that there was no miracle where a firewall got turned on somehwere in between at the exact second we did the upgrade, I'm utterly stumped.

Please can anyone suggest a starting point for my investigations...

So the main Site lets call it A can talk via telnet to port 7191 on sites B C D and E sites B C D and E can all do the same telnet test back to the main site. The mobile server can also do all of these tests. But when you look on the groupwise connector on the mobile server, in the list of POA's there is A B C D and no E!! There used to be!!
Labels (1)
Tags (2)
0 Likes
4 Replies
Absent Member.
Absent Member.

Ohhhh I noticed that on the effected POA for some reason LDAP was off!

So i've turned this back on... but rather amusingly I restarted the mobility services and it said the connector.xml had an error so wouldn't start. A colleague changed the key so I guess there might be a typo in the security key! It could be my macs fault it has this scary habit of autocorrecting far to many things when I'm in safari 🙂
0 Likes
Absent Member.
Absent Member.

Typo I meant IMAP not LDAP brain thinking about to many things!! So anyway connector fixed it's still not talking to the one site so now that site looks identical to all the others and yet it will not work.. Frustrated.
0 Likes
Absent Member.
Absent Member.

booktrunk sounds like they 'said':

>
> Typo I meant IMAP not LDAP brain thinking about to many things!! So
> anyway connector fixed it's still not talking to the one site so now
> that site looks identical to all the others and yet it will not work..
> Frustrated.


So my response to booktrunk's comment is...

Thanks for sharing what went on there. I was having a similar issue
for some users, all on the same post office. Happened to check, imap
not turned on......................D'OH!!!!

--
Stevo
0 Likes
Absent Member.
Absent Member.

Funnily enough... In the end it wasn't that, I thought that had to be it but no still wasn't working. But thankfully I solved it... The trust key was the issue we had.

turns out my colleague who updated it didn't realise but we appear to have different trust keys and he upgraded it and put on a different trust key. I spotted it because I manually at times make a backup of the connector.xml file and I ran diff comparing my last backup of the file to the current connector.xml and it showed the trusted key had changed.

swapped to the other trusted key and it worked perfectly straight away!!

It was actually using out blackberry trust key which seems to have never been set to trust this one site because no-one there uses a blackberry!!

so our own fault, just part of the learning experience but shows the value if backing up your config files 😉
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.