
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Im getting the following while trying to enable the intergration bridge.
Oops.
Accepted Solutions

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thank you for pointing me in the right direction.
I was missing Hazelcast port. I didn't think it was required as i don't have a clustered environment.
Thanks
Dave

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi,
The info below is not enough to tell the real cause of the issue, but it is probably related to the configurations used during the instalaltion of Sync and IBS.
Do you have Sync, IBS and Octane installed on the same domain and using the same protocol (either http or https)?
Can you access successfully the IBS machine from Octane and Sync, the Sync from IBS and Octane etc? You could try this by running the following WGET commands from your Octane server: wget sync_url/admin/server/version
wget opb/admin/server/version.
Thanks!

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thank you for your reply.
I get a 503 error from Octane to IBS server
[root@<Octane Server> conf]# wget -v http://<IBS Server>.<Company>.com:8080/opb/
--2018-02-21 03:38:15-- http://<IBS Server>.<Company>.com:8080/opb/
Resolving <IBS Server>.<Company>.com (<IBS Server>.<Company>.com)... 172.**.**.**
Connecting to <IBS Server>.<Company>.com (<IBS Server>.<Company>.com)|172.**.**.**|:8080... connected.
HTTP request sent, awaiting response... 503 Service Unavailable
2018-02-21 03:38:15 ERROR 503: Service Unavailable.
Same results from Octane to Sync
IBS to Octane
HTTP request sent, awaiting response... 200 OK
Length: 2175 (2.1K) [text/html]
Saving to: ‘index.html?site’
100%[===================================================================================================================================================================================================>] 2,175
Same results from Sync to Octane
Thanks
Dave

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Okay David, so it looks like you have access to IBS and Sync from your Octane machine, which is good, but it seems that IBS was not deployed properly (hence the 503 response).
I guess the issue is in the ibs.yml file you have set for installing IBS, but I cannot tell what the issue is if I don't see the values. You should review all the users, passwords and URLs you have set in there. Maybe it will be easy for you to compare ibs.yml with the sync.yml (they have quite a similar format) and you could notice what is wrong there.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Thank you for pointing me in the right direction.
I was missing Hazelcast port. I didn't think it was required as i don't have a clustered environment.
Thanks
Dave


- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
HI,
We have the same issue, what did you put for the Hazelcast port? We tried with both empty and 5701, but no luck!
Thanks.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
Hi Toan,
Port 5701 should be fine.
I found it useful to set the hazelcast "clusterNodes" parameter to "- localhost" as indicated in the Syncronizer install guide.
Were you able to overcome the issue?
BR,
Deyan