🚀 Impact 2024: The industrial data and AI conference for and by users | Nominate speakers now for a...
The extractor seems to be doing okay under the right conditions. So as of now, this issue is resolved.
After some more testing, the observed issues with connection to CDF seem to be due to using two different network connections (one to OPC-UA server and another to the internet) on the system running the extractor. Looks like the extractor goes into error state only when the two connections are not unplugged and plugged back in at the same time during testing.Need to run a few more tests on my end to confirm this. But the extractor seems to be able to reconnect to CDF when we unplug and re-plug both connections at the same time.
@Einar Omang Thanks for the suggestions. I was able to get the OPC-UA server reconnect to work by setting source.restart-on-reconnect in the extractor config file.About the CDF issue, it does look like the extractor is able to push data to CDF for a few seconds initially after network reconnect as you said. But the extractor does go to failure mode after a few seconds and data upload to CDF stops at this point. I was able to reproduce this failure multiple times upon repeating the same test. So it seems to me that the failure may be connected to some condition brought about by the network interruption.If you have any more suggestions about Cognite settings in the extractor config file that might help automatically reset the CDF connection parameters on reconnect, or any other ideas, please do let me know.Also attaching debug logs from the most recent CDF re-connect test for your reference.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.