# Data Extraction Service (tika/openresty) crashes on second container start

**URL:** <https://discuss.elastic.co/t/data-extraction-service-tika-openresty-crashes-on-second-container-start/383519>\
**Category:** Elasticsearch\
**Tags:** docker, connectors\
**Created:** [November 18, 2025, 3:30pm UTC](https://discuss.elastic.co/t/data-extraction-service-tika-openresty-crashes-on-second-container-start/383519 "2025-11-18T15:30:16Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![SPRINGPEACHVINH](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/springpeachvinh/32/145767_2.png) [@SPRINGPEACHVINH](https://discuss.elastic.co/u/SPRINGPEACHVINH)\
**Post date:** [November 18, 2025, 3:30pm UTC](https://discuss.elastic.co/t/data-extraction-service-tika-openresty-crashes-on-second-container-start/383519/1 "2025-11-18T15:30:16Z")

</div>

Hi guys

I’m encountering a repeatable issue with the data-extraction-service (0.3.5) when running it via Docker Compose.

The service (tika + openresty inside the container) starts fine the first time I bring the stack up, but after I stop and start the containers again (without changing anything), the extraction-service container reports both tika and openresty as crashed.

Subsequent restarts keep failing until I recreate the container from scratch (docker compose down -v && up).  
Here are my configuration

Docker-compose:

```yaml
  extraction-service:
    depends_on:
      elasticsearch:
        condition: service_healthy
    image: docker.elastic.co/integrations/data-extraction-service:0.3.5
    container_name: extraction-service
    ports:
      - 8090:8090
    volumes:
      - ./elastic-connectors/files:/app/files
    healthcheck:
      test: ["CMD", "wget", "--no-verbose", "--tries=1", "--spider", "http://localhost:8090/ping"]
      interval: 10s
      timeout: 5s
      retries: 5
      start_period: 30s
    restart: unless-stopped

```

Logs:

```auto
Service 'All': Status

Service `hwdrivers' needs non existent service `dev'

Service `machine-id' needs non existent service `dev'

 * Caching service dependencies ... [ok]

Runlevel: sysinit

Runlevel: nonetwork

Runlevel: default

Runlevel: shutdown

Runlevel: boot

Dynamic Runlevel: hotplugged

Dynamic Runlevel: needed/wanted

Dynamic Runlevel: manual

 * service tika added to runlevel boot

 * service openresty added to runlevel boot

Service 'Tika': Starting ...

 * Starting tika ... [ok]

Service 'Openresty': Starting ...

 * Starting openresty ... [ok]

Service 'All': Status

Runlevel: sysinit

Runlevel: nonetwork

Runlevel: default

Runlevel: shutdown

Runlevel: boot

 tika [crashed]

 openresty [crashed]

Dynamic Runlevel: hotplugged

Dynamic Runlevel: needed/wanted

Dynamic Runlevel: manual

 * rc-update: tika already installed in runlevel `boot'; skipping

 * rc-update: openresty already installed in runlevel `boot'; skipping

Service 'Tika': Starting ...

```

Related S3 connector config:

```yaml
connectors:
-
  connector_id: "${S3CONFIG_CONNECTOR_ID}"
  service_type: "s3"

extraction_service:
  host: http://host.docker.internal:${ES_LOCAL_EXTRACTION_PORT} #8090
  timeout: 30
  use_file_pointers: false
  stream_chunk_size: 65536
  shared_volume_dir: '/app/files'

elasticsearch:
  host: "http://host.docker.internal:${ES_LOCAL_PORT}" #9200
  username: "${ES_LOCAL_USERNAME}"
  password: "${ES_LOCAL_PASSWORD}"
  log_level: INFO
  request_timeout: 120
  max_wait_duration: 60

```

s3 connector logs:

```auto
[FMWK][15:12:12][CRITICAL] Expected to find a running instance of data extraction service at http://host.docker.internal:8090⁠ but failed. Server disconnected.

```

The images I’m using are:

```yaml
elasticsearch/elasticsearch:8.17.1
integrations/elastic-connectors:8.17.1
integrations/data-extraction-service:0.3.5⁠

```

Please tell me how can I fix this, thank you very much.

---

<div class="post-metadata">

**Author:** ![carly.richmond](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/carly.richmond/32/104935_2.png) [@carly.richmond](https://discuss.elastic.co/u/carly.richmond)\
**Post date:** [November 20, 2025, 10:08am UTC](https://discuss.elastic.co/t/data-extraction-service-tika-openresty-crashes-on-second-container-start/383519/2 "2025-11-20T10:08:27Z")

</div>

Hi @SPRINGPEACHVINH,

Can you share any error/ warning messages in the Tika and Openresty logs? The paths are available [here](https://github.com/elastic/data-extraction-service?tab=readme-ov-file#logging).

Let us know!

---

<div class="post-metadata">

**Author:** ![SPRINGPEACHVINH](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/springpeachvinh/32/145767_2.png) [@SPRINGPEACHVINH](https://discuss.elastic.co/u/SPRINGPEACHVINH)\
**Post date:** [November 28, 2025, 8:50am UTC](https://discuss.elastic.co/t/data-extraction-service-tika-openresty-crashes-on-second-container-start/383519/3 "2025-11-28T08:50:38Z")

</div>

Hi @carly.richmond, I’m sorry for the late response.

I opened those log files with `docker exec` but they were empty.

```auto
> docker exec extraction-service cat /var/log/openresty.log
> docker exec extraction-service cat /var/log/tika.log     

```

```auto
/var/log # ls -la
total 12
drwxr-xr-x 1 root root 4096 Nov 28 08:44 .
drwxr-xr-x 1 root root 4096 Apr 4 2022 ..
-rw-r----- 1 root root 0 Nov 28 08:44 openresty.log
-rw-r----- 1 root root 0 Nov 28 08:44 tika.log

```

I also used extension `container` on Visual Studio Code to open log files and they were still empty.

Please let me know what else can I provide, thank you!