Kafka: INFO exited: sample-data (exit status 0; expected)

By -

I have run the following command while making the kafka cluster up

sudo docker compose up kafka-cluster

i have successfully access the Landoop UI portal a day ago but when i shutdown the system and perform the same steps again. I am now unable to access the landoop ui from this local URL

http://127.0.0.1:3030

I am using Ubuntu 20.04 and the following logs has been generated in the terminal.

[sudo] password for pc-11: 
[+] Running 1/0
 ⠿ Container code-kafka-cluster-1  Created                                                                                                                                      0.0s
Attaching to code-kafka-cluster-1
code-kafka-cluster-1  | Setting advertised host to 127.0.0.1.
code-kafka-cluster-1  | Starting services.
code-kafka-cluster-1  | This is landoop’s fast-data-dev. Kafka 0.11.0.0, Confluent OSS 3.3.0.
code-kafka-cluster-1  | You may visit http://127.0.0.1:3030 in about a minute.
code-kafka-cluster-1  | 2022-07-14 08:48:34,716 CRIT Supervisor running as root (no user in config file)
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/01-zookeeper.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/02-broker.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/03-schema-registry.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/04-rest-proxy.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/05-connect-distributed.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/06-caddy.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/07-smoke-tests.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/08-logs-to-kafka.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,729 WARN Included extra file "/etc/supervisord.d/99-supervisord-sample-data.conf" during parsing
code-kafka-cluster-1  | 2022-07-14 08:48:34,731 INFO supervisord started with pid 7
code-kafka-cluster-1  | 2022-07-14 08:48:35,735 INFO spawned: 'sample-data' with pid 91
code-kafka-cluster-1  | 2022-07-14 08:48:35,753 INFO spawned: 'zookeeper' with pid 93
code-kafka-cluster-1  | 2022-07-14 08:48:35,766 INFO spawned: 'caddy' with pid 94
code-kafka-cluster-1  | 2022-07-14 08:48:35,770 INFO spawned: 'broker' with pid 95
code-kafka-cluster-1  | 2022-07-14 08:48:35,773 INFO spawned: 'smoke-tests' with pid 97
code-kafka-cluster-1  | 2022-07-14 08:48:35,776 INFO spawned: 'connect-distributed' with pid 98
code-kafka-cluster-1  | 2022-07-14 08:48:35,779 INFO spawned: 'logs-to-kafka' with pid 99
code-kafka-cluster-1  | 2022-07-14 08:48:35,782 INFO spawned: 'schema-registry' with pid 100
code-kafka-cluster-1  | 2022-07-14 08:48:35,785 INFO spawned: 'rest-proxy' with pid 101
code-kafka-cluster-1  | 2022-07-14 08:48:36,262 INFO exited: caddy (exit status 2; not expected)
code-kafka-cluster-1  | 2022-07-14 08:48:37,264 INFO success: sample-data entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,264 INFO success: zookeeper entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,266 INFO spawned: 'caddy' with pid 381
code-kafka-cluster-1  | 2022-07-14 08:48:37,267 INFO success: broker entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,267 INFO success: smoke-tests entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,267 INFO success: connect-distributed entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,267 INFO success: logs-to-kafka entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,267 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,268 INFO success: rest-proxy entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:48:37,280 INFO exited: caddy (exit status 2; not expected)
code-kafka-cluster-1  | 2022-07-14 08:48:39,285 INFO spawned: 'caddy' with pid 389
code-kafka-cluster-1  | 2022-07-14 08:48:39,348 INFO exited: caddy (exit status 2; not expected)
code-kafka-cluster-1  | 2022-07-14 08:48:42,444 INFO spawned: 'caddy' with pid 403
code-kafka-cluster-1  | 2022-07-14 08:48:42,450 INFO exited: caddy (exit status 2; not expected)
code-kafka-cluster-1  | 2022-07-14 08:48:42,508 INFO gave up: caddy entered FATAL state, too many start retries too quickly
code-kafka-cluster-1  | 2022-07-14 08:49:04,090 INFO exited: schema-registry (exit status 1; not expected)
code-kafka-cluster-1  | 2022-07-14 08:49:04,099 INFO spawned: 'schema-registry' with pid 485
code-kafka-cluster-1  | 2022-07-14 08:49:05,124 INFO success: schema-registry entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
code-kafka-cluster-1  | 2022-07-14 08:49:35,818 INFO exited: smoke-tests (exit status 0; expected)
code-kafka-cluster-1  | 2022-07-14 08:51:35,933 INFO exited: logs-to-kafka (exit status 0; expected)
code-kafka-cluster-1  | 2022-07-14 08:52:53,146 INFO exited: sample-data (exit status 0; expected)


Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more