Unsolved
This post is more than 5 years old
114 Posts
0
795
SourceOne Search Services to loadbalancer
I'm at a customer who was implemented SourceOne and is currently on S6.8 SP2 with a hotfix applied.
They want to upgrade to S1 7.1 SP2 (latest version).
But while upgrading, the Search we're facing the following:
The 'xxxxxxxLOADBALANCER URLxxxxx' was reached but encountered an error. This will prevent Retrieval from SourceOne Web Services and impact production.
To view and resolve the error, use the link http://LOADBALANCERURL/ExDominoShortcut/Notes.aspx?getver=1
This page isn't found (404).
The previous installation entered the loadbalancerurl to connect to the Web Services.
But when installing, you just need to put the local hostname to this field I suppose?
Because entering a load balancer URL will create a loopback to this worker?
Gary_Reardon
272 Posts
0
December 18th, 2014 06:00
Hi Ben,
How many servers are involved?
Do you have specific Search only and or Mobile only servers?
Are you trying to load balance the Web services and have Search & Mobile point to the load balancing.address instead of directly to the server there are installed on?
What I typically do is have each service point to the server they are installed on and then load balance across the multiple servers for the search & mobile services.
The likelihood that web services would be down and search and/or mobile services still running is probably pretty rare and not worth the aggravation of maintaining that configuration.
BenCs
114 Posts
0
December 23rd, 2014 02:00
Hi Gary,
The previous implementor has set the Loadbalancer URL for the Web Services name inside the Search setup.
Because this uses SSL and the local (self-signed) certificates were expired, this caused this error.
Although they implemented the Mobile Services installation, but they're on a Notes environment.
Gary_Reardon
272 Posts
0
December 23rd, 2014 05:00
Depending on the Loadbalancer, you may be able to offload the SSL there and use non-SSL to connection to the servers.
You'll have the same issue if the loadbalancer SSL Cert is expired, of course.
BenCs
114 Posts
0
December 23rd, 2014 05:00
Thanks for your advice Gary.
SourceOne continued working while the certificate was expired since april this year. We faced this issue as soon as we've tried to upgrade the Search Service to the latest version.
Gary_Reardon
272 Posts
0
December 23rd, 2014 10:00
Exactly.
It won't get by the expired cert in the test connection during the installation.
The other way around it is to stop IIS and let the connection failed and chose to ignore it during the install.
I've had a similar problem when the customer has applied more restrictive permissions on the SourceOne install drive and the install test fails.