Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

I finally managed to identify the problem. The server could not reach (due to dns resolve issues) the resources listed in the sdc.log in the section:

2019-06-28 16:16:55,883 [user:] [pipeline:] [runner:] [thread:main] [stage:] INFO  ClassLoaderStageLibraryTask - Reading from Repository Manifest URL: http://archives.streamsets.com/datacollector/3.9.1/tarball/repository.manifest.json
2019-06-28 16:17:23,200 [user:] [pipeline:] [runner:] [thread:main] [stage:] INFO  ClassLoaderStageLibraryTask - Reading from Repository Manifest URL: http://archives.streamsets.com/datacollector/3.9.1/tarball/enterprise/repository.manifest.json
2019-06-28 16:17:23,726 [user:] [pipeline:] [runner:] [thread:main] [stage:] INFO  ClassLoaderStageLibraryTask - Reading from Repository Manifest URL: http://archives.streamsets.com/datacollector/3.9.1/legacy/repository.manifest.json

So the startup procedure was waiting an indefinitely amount of time... The suggestion was taken from this post: https://www.codetd.com/en/article/6412721

I apologize for the time wasted trying to solve a problem that was clearly not attributable to SDC...