Discussions
Categories
- 17.9K All Categories
- 3.4K Industry Applications
- 3.3K Intelligent Advisor
- 63 Insurance
- 536.4K On-Premises Infrastructure
- 138.3K Analytics Software
- 38.6K Application Development Software
- 5.8K Cloud Platform
- 109.5K Database Software
- 17.5K Enterprise Manager
- 8.8K Hardware
- 71.1K Infrastructure Software
- 105.3K Integration
- 41.6K Security Software
OGG Microservices: Adding PATH fails with OGG-08518 'The network connection could not be established

I have created extract process EXT01. Now I am adding PATH (similar to DataPump in GG Classic Architecture) with the following parameters:
I can telnet to the mentioned <Receiver ip> : <Receiver port> and <Distributor ip> : <Distributor port>
If I just click Create Path without running it , and then try to start the path I receive the following picture:
This is an error message that I receive when starting path;
Do you have an idea?
Answers
-
I used self signed certificates during setup. I think I have correct certificates in my wallet.
I've even tried to start the browser from the same node where Distribution server is running. But I get the following error when trying to startup path
2019-04-10T23:01:04.074+0000 INFO | Negotiated cipher: 0x0035 - 'TLS_RSA_WITH_AES_256_CBC_SHA'. (Thread 7)2019-04-10T23:01:04.074+0000 INFO | Request received from 127.0.0.1 'anonymous' https PATCH /services/v2/sources/prim2stby HTTP/1.1 'Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0' - - - '-' - https://localhost:9003/ (Thread 7)2019-04-10T23:01:04.074+0000 INFO | 'oggadmin' IS authorized for 'operator' role by Cookie. (Thread 7)2019-04-10T23:01:04.074+0000 INFO | Negotiated cipher: 0x0035 - 'TLS_RSA_WITH_AES_256_CBC_SHA'. (prim2stby)2019-04-10T23:01:04.139+0000 ERROR| Secure Comm Error : SSL Connection not close gracefully (28864). (prim2stby)2019-04-10T23:01:04.139+0000 ERROR| Secure Comm Error : SSL Connection not close gracefully (28864). (prim2stby)2019-04-10T23:01:04.142+0000 ERROR| Error initializing the network channel (prim2stby)2019-04-10T23:01:04.142+0000 ERROR| Exception Code: OGG-08525 (prim2stby)2019-04-10T23:01:04.142+0000 ERROR| Exception Message: The network connection could not be established. (prim2stby)2019-04-10T23:01:04.142+0000 ERROR| Exception, killing the path maritest (prim2stby)2019-04-10T23:01:04.143+0000 WARN | Path killed. (prim2stby)2019-04-10T23:01:04.145+0000 INFO | Response returned with HTTP/1.1 500 Internal Error 561 (Thread 7)
-
Are you meaning to go from an MA deployment to an OGG Classic architecture installation? That is what you are doing when you select 'ogg' as the target from the dropdown box. If that is what you are trying to do, then you cannot use a secure deployment and must use an unsecured deployment installation to go to a Classic OGG installation target.
If you want to get from one secure MA deployment to another secure MA deployment, then choose 'wss' as the target.
-
I have modified parameters by the following way:
But getting the following error in distsrvr.log
2019-05-16T06:34:01.217+0000 INFO | Request received from <my computer public ip> 'anonymous' https PATCH /services/v2/sources/prim2stby HTTP/1.1 'Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/74.0.3729.131 Safari/537.36' - - - '-' https://<node's public ip>:9003 https://<node's public ip>:9003/ (Thread 6)2019-05-16T06:34:01.217+0000 INFO | 'oggadmin' IS authorized for 'operator' role by Cookie. (Thread 6)2019-05-16T06:34:01.217+0000 INFO | Negotiated cipher: 0x0035 - 'TLS_RSA_WITH_AES_256_CBC_SHA'. (prim2stby)2019-05-16T06:34:01.217+0000 ERROR| Secure Comm Error : SSL Connection not close gracefully (28864). (prim2stby)2019-05-16T06:34:01.217+0000 ERROR| Secure Comm Error : SSL Connection not close gracefully (28864). (prim2stby)2019-05-16T06:34:01.217+0000 ERROR| Error initializing the network channel (prim2stby)2019-05-16T06:34:01.217+0000 ERROR| Exception Code: OGG-08525 (prim2stby)2019-05-16T06:34:01.217+0000 ERROR| Exception Message: The network connection could not be established. (prim2stby)2019-05-16T06:34:01.217+0000 ERROR| Exception, killing the path prim2stby (prim2stby)2019-05-16T06:34:01.217+0000 WARN | Path killed. (prim2stby)2019-05-16T06:34:01.217+0000 INFO | Response returned with HTTP/1.1 500 Internal Error 570 (Thread 6)
-
Hi, are both your source and target installations in secure mode, meaning you created certificates? Or are both in unsecure mode? You can't have mixed mode.
If you have done the installation of both in unsecure mode, then use 'ws' as the protocol.
-
Both are in secured mode
-
Hi ,
Please check the below,
For a non-secure deployment, the RESTful API calls occur over plain-text HTTP and conveyance between Distribution Server and Receiver Server is performed using the UDT, ogg://, and ws:// protocols
This is documented in the below link,
https://docs.oracle.com/goldengate/c1230/gg-winux/GGSAU/GGSAU.pdf
2 Setting Up Secure or Non-Secure Deployments
Regards,
Veera
-
I have the same issue, Have anyone can fix it?
-
Both are in secured mode. Which protocol should be used on target?
-
Please Help Me!!
-
Can you from source server: telnet targetgg.ttnet.com 9004