Hi Philipp,
Thanks for your hint – building beforehand did the job for me… I can now actually see and probably use a bunch of processor and sink pipeline elements (in pipeline editor and via install pipeline elements). However, if I try to use adapters (I would like to use messages from a MQTT broker as data source) I cannot seem to get any (when trying both cli (env set to full) and compose-based (docker-compose.full.yaml) installation). For this, I click on connect and neither Data Marketplace nor My Adapters lets me set up an MQTT (or any other) data source. What could be the problem here? Thank you and best Martin Von: Philipp Zehnder <[email protected]> Gesendet: Montag, 27. Dezember 2021 10:11 An: [email protected] Betreff: Re: No pipeline-elements available Hi Martin, thanks for writing us and sorry for the confusion about the development setup. Recently, we merged our repositories into one to ease the development [1] and did not update all the documentation yet. However, we plan to do this before the next release. I updated the description how to setup a development environment for new processing elements [2]. I hope this helps for the setup and that the error is gone when you use the CLI to start up StreamPipes. Please let me know when you have any problems or when something is not clear. You can also contact us if you find documentation that is no longer up to date so that we can update it. Philipp [1] https://github.com/apache/incubator-streampipes [2] https://cwiki.apache.org/confluence/display/STREAMPIPES/Extensions Von: Martin Trat < <mailto:[email protected]> [email protected]> Antworten an: < <mailto:[email protected]> [email protected]> Datum: Freitag, 24. Dezember 2021 um 14:39 An: "[email protected] <mailto:[email protected]> " <[email protected] <mailto:[email protected]> > Betreff: No pipeline-elements available Dear StreamPipes Community, Installing StreamPipes 0.68.0 via release download from GitHub worked for me. However, in order to develop custom processors, I would like to use a recent snapshot state. I cloned c6527b9 from the dev branch of incubating-streampipes repo, stopped all containers, pruned images, volumes and containers and attempted a compose-based installation (using docker-compose.full.yml). I followed the rather sparse documentation from the website (documentation version selected “master” under “Pre-release versions”) and the repository’s readme under installer/compose. Browsing my then running UI instance, I cannot download/install/see any pipeline elements (0 available). Do I need to execute any installer scripts, set environment variables or do anything the like? Do I need another repo for pipeline elements? Also, I consulted with a partnering company, contributing to StreamPipes. They also use a snapshot installation and can still draw pipeline elements (I also tried pulling the commit they are using, but to no avail). It therefore seems counter intuitive when proposing the following error to be relevant for missing pipeline elements. However, they confirm their pipeline-elements-all-flink container being continuously stuck in restarting state. The container shows the following log on repeat: ``` 12:00:05.079 SP [main] INFO o.a.s.s.consul.ConsulProvider - Checking if consul is available... 12:00:05.094 SP [main] INFO o.a.s.s.consul.ConsulProvider - Successfully connected to Consul Exception in thread "main" java.lang.NullPointerException: id at java.util.Objects.requireNonNull(Objects.java:228) at com.orbitz.consul.model.agent.ImmutableRegistration$Builder.id(ImmutableRegistration.java:847) at org.apache.streampipes.svcdiscovery.consul.SpConsulServiceDiscovery.createRegistrationBody(SpConsulServiceDiscovery.java:120) at org.apache.streampipes.svcdiscovery.consul.SpConsulServiceDiscovery.registerService(SpConsulServiceDiscovery.java:49) at org.apache.streampipes.container.base.StreamPipesServiceBase.registerService(StreamPipesServiceBase.java:66) at org.apache.streampipes.container.base.StreamPipesServiceBase.startStreamPipesService(StreamPipesServiceBase.java:42) at org.apache.streampipes.service.extensions.base.StreamPipesExtensionsServiceBase.startExtensionsService(StreamPipesExtensionsServiceBase.java:67) at org.apache.streampipes.container.standalone.init.StandaloneModelSubmitter.init(StandaloneModelSubmitter.java:57) at org.apache.streampipes.pe.flink.AllFlinkPipelineElementsInit.main(AllFlinkPipelineElementsInit.java:105) 12:01:07,931 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback-test.xml] 12:01:07,932 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Could NOT find resource [logback.groovy] 12:01:07,932 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [logback.xml] at [jar:file:/streampipes-processing-element-container.jar!/logback.xml] 12:01:07,969 |-INFO in ch.qos.logback.core.joran.spi.ConfigurationWatchList@f97bd761 <mailto:ch.qos.logback.core.joran.spi.ConfigurationWatchList@f97bd761> - URL [jar:file:/streampipes-processing-element-container.jar!/logback.xml] is not of type file 12:01:08,155 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set 12:01:08,161 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.core.ConsoleAppender] 12:01:08,170 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT] 12:01:08,279 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - This appender no longer admits a layout as a sub-component, set an encoder instead. 12:01:08,279 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - To ensure compatibility, wrapping your layout in LayoutWrappingEncoder. 12:01:08,279 |-WARN in ch.qos.logback.core.ConsoleAppender[STDOUT] - See also http://logback.qos.ch/codes.html#layoutInsteadOfEncoder for details 12:01:08,279 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.streampipes] to INFO 12:01:08,279 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.lightcouch] to ERROR 12:01:08,279 |-INFO in ch.qos.logback.classic.joran.action.LoggerAction - Setting level of logger [org.apache.kafka] to ERROR 12:01:08,281 |-INFO in ch.qos.logback.classic.joran.action.RootLoggerAction - Setting level of ROOT logger to INFO 12:01:08,282 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [STDOUT] to Logger[ROOT] 12:01:08,282 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration. 12:01:08,286 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@75dd924 <mailto:ch.qos.logback.classic.joran.JoranConfigurator@75dd924> - Registering current configuration as safe fallback point ``` Some possibly relevant information: * Ubuntu 20.04 * Software requirements from documentation fulfilled * Latest v1 docker-compose v 1.29.2 * docker v 20.10.10 * Reasonably powerfully sized VM meeting hardware requirements * Deviations from default * Running UI at host port 81 Thank you very much for helping me with this! Best Martin ......................................................... Martin Trat, M.Sc. Wissenschaftlicher Mitarbeiter | Research Associate Intelligent Systems and Production Engineering (ISPE) Process & Data Management in Engineering (PDE) FZI Forschungszentrum Informatik Haid-und-Neu-Str. 10–14 76131 Karlsruhe, Germany Tel.: +49 721 9654-509 [email protected] <mailto:[email protected]> | www.fzi.de/mitarbeiter/trat <http://www.fzi.de/mitarbeiter/trat> | https://linkedin.com/in/martin-trat <https://linkedin.com/in/martin-trat-372599139> www.fzi.de <http://www.fzi.de/> | www.twitter.com/FZI_official <http://www.twitter.com/FZI_official> | www.facebook.com/FZI.Official <http://www.facebook.com/FZI.Official> | www.youtube.com/FZIchannel <http://www.youtube.com/FZIchannel> ......................................................... FZI Forschungszentrum Informatik Stiftung des bürgerlichen Rechts Stiftung Az: 14-0563.1 Regierungspräsidium Karlsruhe Vorstand: Prof. Dr. Andreas Oberweis, Jan Wiesenberger, Prof. Dr.-Ing. J. Marius Zöllner Vorsitzender des Kuratoriums: Ministerialdirigent Günther Leßnerkraus .........................................................
smime.p7s
Description: S/MIME cryptographic signature
