Hi, that is a good point and we should discuss how we can improve this process for none technical users.
Currently I run StreamPipes always as a deamon with the -d flag. Then when an error occurs I print the docker logs. When running the compose version with ‘docker-compose logs #SERVICE_NAME” and when running the CLI with ‘./streampipes logs #SERVICE_NAME”. However, this only works for developers, as they know which services are running and which service might have triggered the problem. Does anyone have an idea how we can improve this? We already had first prototypes to collect the logs from all services, but this is a quite complex feature with many things to consider. Therefore the question if someone has an idea how we can make it easier for users to send us the logs? Philipp > On 19. Jan 2021, at 18:00, Lukas Ott <[email protected]> wrote: > > Hi StreamPipes-Team, > > I ran into a serious issue and could not find the information how to access > the relevant log files: > > I had StreamPipes Running -> No error messages occurred in the UI > -> Did the tutorial -> Not data in the dashboard -> Wanted to stop as > stated here: > https://streampipes.apache.org/docs/docs/faq-common-problems/#no-data-is-shown-in-the-live-dashboard > > > So one thing what would probably help a lot is an overview of log files and > where to find them. > > So me as a user can get them and attach them to a Jira Issue to support / > help improve StreamPipes. > > So please give me some hints where to find and access the relevant files > and i will add them to a Jira Ticket to solve the issue. > > Thank you! :-) > > Here is what I did in the terminal (running Ubuntu 20.04 based Pop_OS!): > > Gracefully stopping... (press Ctrl+C again to force) > Stopping streampipes_ui_1 ... done > Stopping streampipes_connect-worker-main_1 ... done > Stopping streampipes_backend_1 ... done > Stopping streampipes_pipeline-elements-all-flink_1 ... done > Stopping streampipes_sources-watertank-simulator_1 ... done > Stopping streampipes_sources-vehicle-simulator_1 ... done > Stopping streampipes_pipeline-elements-all-jvm_1 ... done > Stopping streampipes_connect-master_1 ... done > Stopping streampipes_kafka_1 ... done > Stopping streampipes_taskmanager_1 ... done > Stopping streampipes_jobmanager_1 ... done > Stopping streampipes_activemq_1 ... done > Stopping streampipes_consul_1 ... done > Stopping streampipes_influxdb_1 ... done > Stopping streampipes_zookeeper_1 ... done > Stopping streampipes_couchdb_1 ... done > lukas@pop-os:~/Downloads/streampipes/apache-streampipes-installer-0.67.0-incubating-source-release/incubator-streampipes-installer/cli$ > sudo ./streampipes clean > [WARN] This will remove: > - StreamPipes docker network > - all dangling StreamPipes imagesAre you sure you want to continue? [y/N]: > y > [INFO] No dangling StreamPipes images found > [INFO] Removing StreamPipes docker network > lukas@pop-os:~/Downloads/streampipes/apache-streampipes-installer-0.67.0-incubating-source-release/incubator-streampipes-installer/cli$ > sudo ./streampipes start > StreamPipes CLI - Manage your StreamPipes environment with easeUsage: > streampipes COMMAND [OPTIONS]Options: > --help, -h show help > --version, -v show versionCommands: > clean Remove StreamPipes data volumes, dangling images and network > down Stop and remove StreamPipes containers > env Inspect and select StreamPipes environments > info Get information > logs Get container logs for specific container > ps List all StreamPipes container for running environment > pull Download latest images from Dockerhub > restart Restart StreamPipes environment > up Create and start StreamPipes container environmentRun > 'streampipes COMMAND --help' for more info on a command. > lukas@pop-os:~/Downloads/streampipes/apache-streampipes-installer-0.67.0-incubating-source-release/incubator-streampipes-installer/cli$ > sudo ./streampipes restart > [INFO] No StreamPipes environment running > lukas@pop-os:~/Downloads/streampipes/apache-streampipes-installer-0.67.0-incubating-source-release/incubator-streampipes-installer/cli$ > sudo ./streampipes up > _______ __ ______ __ > | __| |_.----.-----.---.-.--------.| __ \__|.-----.-----.-----. > |__ | _| _| -__| _ | || __/ || _ | -__|__ --| > |_______|____|__| |_____|___._|__|__|__||___| |__|| __|_____|_____| > |__|Welcome to > Apache StreamPipes - wait for installation to be finished...[INFO] > Version: 0.67.0 > [INFO] Environment: 'full' > [INFO] Mode: Development mode, all ports mapped > [INFO] Creating docker network 'spnet' > [INFO] Creating docker volumes and starting docker containers > Starting streampipes_consul_1 ... error > Starting streampipes_activemq_1 ... > Starting streampipes_couchdb_1 ... > Starting streampipes_activemq_1 ... error > Starting streampipes_jobmanager_1 ... > Starting streampipes_influxdb_1 ... Starting streampipes_zookeeper_1 > ... errorERROR: for streampipes_activemq_1 Cannot start service > activemq: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > found > Starting streampipes_couchdb_1 ... error > Starting streampipes_influxdb_1 ... errorERROR: for > streampipes_influxdb_1 Cannot start service influxdb: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > found > Starting streampipes_jobmanager_1 ... error > ERROR: for streampipes_couchdb_1 Cannot start service couchdb: > network e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e > not foundERROR: for streampipes_jobmanager_1 Cannot start service > jobmanager: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > foundERROR: for consul Cannot start service consul: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > foundERROR: for activemq Cannot start service activemq: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > foundERROR: for zookeeper Cannot start service zookeeper: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > foundERROR: for influxdb Cannot start service influxdb: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > foundERROR: for couchdb Cannot start service couchdb: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > foundERROR: for jobmanager Cannot start service jobmanager: network > e21db18d83588e4000331e454a86534b3ca00e099bbcf98e37af7cbc317bdb5e not > found > ERROR: Encountered errors while bringing up the project.
