2 issues I am seeing

[ngpollock]

I am having two different issues using the gpu docker compose file. I moved the correct .env file into place and even though I am running everything locally, I added redis, ollama and web to the /etc/hosts files in my ubuntu. I then ran the following command:
docker compose -f docker-compose.gpu.yml up --build

The build is nearly complete when I get an error that says that the celery app cannot connect to redis, although redis is running and using nc to connect and test the port, a ping returns pong.
I also try to access the web interface using localhost:8000 and I get an error of but then all I see is "Pretty-Print" followed by {"detail":"Not Found"}. You can see the result in the screenshot.
The logs for the fastapi container show the following:
INFO: Will watch for changes in these directories: ['/app']

INFO: Uvicorn running on http://0.0.0.0:8000 (Press CTRL+C to quit)
INFO: Started reloader process [27] using WatchFiles
INFO: Started server process [29]
INFO: Waiting for application startup.
INFO: Application startup complete.
a
a
a
INFO: 172.18.0.1:36968 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:36968 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:60764 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:60764 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:60754 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:60754 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:36368 - "GET / HTTP/1.1" 404 Not Found

I like the sound of this application, but cannot see where the issue is. Any help would be appreciated.

[choinek]

Hello :)

Not found

not found is default response for / page , try http://localhost:8000/docs#/

->

Redis

I don't see information about redis in your log.

Readme

Please read README.md you'll se some endpoints and examples of usage like

curl -X POST -H "Content-Type: multipart/form-data" -F "file=@examples/example-mri.pdf" -F "strategy=marker" -F "ocr_cache=true" -F "prompt=" -F "model=" "http://localhost:8000/ocr/upload" 

[ngpollock]

Thank you for the quick reply. Here is the screenshot of the screen that comes up for the link you sent:

Where do I go to create that folder?

Thank you

[choinek]

Redis, please provide:

1. how you test it (keep in mind that in doo]cker setup you should test connection from container and not from host)
2. whats your .env configuration
3. Im not sure what do you mean by running everything localy - if you run docker ports are forwarded to host, but containers cant connect to localhost - they must connect to redis host, i mean exacly redis:6379 not localhost or 127.0.0.1

If you set up /etc/hosts on your host machine, it doesn't matter from Docker's point of view.

[ngpollock]

1. I tested using nc redis 6379. After connection, I type ping and get a response of +PONG. I do this from wsl ubuntu against the running docker container.
2. Here is the .env
   #APP_ENV=production # sets the app into prod mode, othervise dev mode with auto-reload on code changes
   REDIS_CACHE_URL=redis://localhost:6379/1
   LLAMA_VISION_PROMPT="You are OCR. Convert image to markdown."

CLI settings

OCR_URL=http://localhost:8000/ocr/upload
OCR_UPLOAD_URL=http://localhost:8000/ocr/upload
OCR_REQUEST_URL=http://localhost:8000/ocr/request
RESULT_URL=http://localhost:8000/ocr/result/
CLEAR_CACHE_URL=http://localhost:8000/ocr/clear_cach
LLM_PULL_API_URL=http://localhost:8000/llm_pull
LLM_GENEREATE_API_URL=http://localhost:8000/llm_generate

CELERY_BROKER_URL=redis://localhost:6379/0
CELERY_RESULT_BACKEND=redis://localhost:6379/0
OLLAMA_HOST=http://localhost:11434
APP_ENV=development # Default to development mode

STORAGE_PROFILE_PATH=../storage_profiles

AWS S3

#AWS_ACCESS_KEY_ID=your-access-key-id
#AWS_SECRET_ACCESS_KEY=your-secret-access-key
#AWS_REGION=your-region
#AWS_S3_BUCKET_NAME=your-bucket-name

3. I should have left that out. I just mean that I am running everything on a local docker config running on my home machine. Here is my hosts file:

This file was automatically generated by WSL. To stop automatic generation of this file, add the following entry to /etc/wsl.conf:

[network]

generateHosts = false

127.0.0.1 localhost
127.0.1.1 Razer. Razer
127.0.0.1 redis
127.0.0.1 ollama
127.0.0.1 web

The following lines are desirable for IPv6 capable hosts

::1 ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters

[ngpollock]

Also, here is some of the error message from the celery worker container log:
[2025-01-12 18:57:59,085: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 32.00 seconds... (16/100)
[2025-01-12 18:58:31,122: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 32.00 seconds... (16/100)
[2025-01-12 18:59:03,160: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 32.00 seconds... (16/100)
[2025-01-12 18:59:35,197: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 32.00 seconds... (16/100)
[2025-01-12 19:00:07,235: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 32.00 seconds... (16/100)
[2025-01-12 19:00:39,272: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 32.00 seconds... (16/100)
[2025-01-12 19:01:11,310: CRITICAL/MainProcess] Unrecoverable error: OperationalError('Error 111 connecting to localhost:6379. Connection refused.')
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/kombu/transport/virtual/base.py", line 951, in create_channel
return self._avail_channels.pop()
IndexError: pop from empty list
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/lib/python3.10/dist-packages/redis/connection.py", line 357, in connect
sock = self.retry.call_with_retry(
File "/usr/local/lib/python3.10/dist-packages/redis/retry.py", line 62, in call_with_retry
return do()
File "/usr/local/lib/python3.10/dist-packages/redis/connection.py", line 358, in
lambda: self._connect(), lambda error: self.disconnect(error)
File "/usr/local/lib/python3.10/dist-packages/redis/connection.py", line 730, in _connect
raise err
File "/usr/local/lib/python3.10/dist-packages/redis/connection.py", line 718, in _connect
sock.connect(socket_address)
ConnectionRefusedError: [Errno 111] Connection refused

[ngpollock]

I restarted the celery_worker, logged into the celery_worker container, installed netcat and did nc redis 6379 and typed ping and received a reply of +PONG

Here is a truncated version of the current log file:
return self.ensure_connected(
File "/usr/local/lib/python3.10/dist-packages/celery/worker/consumer/consumer.py", line 527, in ensure_connected
conn = conn.ensure_connection(
File "/usr/local/lib/python3.10/dist-packages/kombu/connection.py", line 406, in ensure_connection
self._ensure_connection(*args, **kwargs)
File "/usr/local/lib/python3.10/dist-packages/kombu/connection.py", line 458, in _ensure_connection
with ctx():
File "/usr/lib/python3.10/contextlib.py", line 153, in exit
self.gen.throw(typ, value, traceback)
File "/usr/local/lib/python3.10/dist-packages/kombu/connection.py", line 476, in _reraise_as_library_errors
raise ConnectionError(str(exc)) from exc
kombu.exceptions.OperationalError: Error 111 connecting to localhost:6379. Connection refused.

== CUDA ==

CUDA Version 11.8.0
Container image Copyright (c) 2016-2023, NVIDIA CORPORATION & AFFILIATES. All rights reserved.
This container image and its contents are governed by the NVIDIA Deep Learning Container License.
By pulling and using the container, you accept the terms and conditions of this license:
https://developer.nvidia.com/ngc/nvidia-deep-learning-container-license
A copy of this license is made available in this container at /NGC-DL-CONTAINER-LICENSE for your convenience.
a
a
a

-------------- celery@4eb98468b6cb v5.4.0 (opalescent)
--- ***** -----
-- ******* ---- Linux-5.15.167.4-microsoft-standard-WSL2-x86_64-with-glibc2.35 2025-01-13 00:21:58

• *** --- * ---
• ** ---------- [config]
• ** ---------- .> app: app:0x7fc7708e8400
• ** ---------- .> transport: redis://localhost:6379/0
• ** ---------- .> results: redis://localhost:6379/0
• *** --- * --- .> concurrency: 16 (solo)
  -- ******* ---- .> task events: OFF (enable -E to monitor tasks in this worker)
  --- ***** -----
  -------------- [queues]
  .> celery exchange=celery(direct) key=celery

[tasks]
. tasks.ocr_task
[2025-01-13 00:21:58,714: WARNING/MainProcess] /usr/local/lib/python3.10/dist-packages/celery/worker/consumer/consumer.py:508: CPendingDeprecationWarning: The broker_connection_retry configuration setting will no longer determine
whether broker connection retries are made during startup in Celery 6.0 and above.
If you wish to retain the existing behavior for retrying connections on startup,
you should set broker_connection_retry_on_startup to True.
warnings.warn(
[2025-01-13 00:21:58,716: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 2.00 seconds... (1/100)
[2025-01-13 00:22:00,720: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..
Trying again in 4.00 seconds... (2/100)
[2025-01-13 00:22:04,726: ERROR/MainProcess] consumer: Cannot connect to redis://localhost:6379/0: Error 111 connecting to localhost:6379. Connection refused..

[choinek]

You are testing the connection to redis on port 6379 from the container, and it works. However, your logs and configuration show connections to localhost on port 6379. This means you have misconfigurd host. Your application is trying to connect to localhost, not redis. You need to adjust your config to match what your application is using. Change the host in your configuration from localhost to redis, which is the default setup unless you have overridden it (as you seem to have done)

You are not using local environment. You are using docker environment.
Local = Getting started
Docker = Getting started with docker

[ngpollock]

You were correct. I mistakenly used the incorrect .env file. Rather than continue patching and changing individual docker containers, I decided to start from scratch, following the Docker docs and install as a gpu version. I deleted all associated containers and text-extract-api folder. I also deleted the ollama image to force a fresh update. I did not change any mount points for the storage as suggested in the docs may be needed. I reran everything in the docs and the build now completed with no errors.

fastapi container - I connect to the webpage and it looks exactly as it did yesterday even after clearing the browser cache and the logs have the following when I connect to it. What is the cause for the Not Found errors:
INFO: 172.18.0.1:50234 - "GET /docs HTTP/1.1" 200 OK
INFO: 172.18.0.1:50234 - "GET /openapi.json HTTP/1.1" 200 OK
INFO: 172.18.0.1:50250 - "GET /favicon.ico HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:50250 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:54942 - "GET / HTTP/1.1" 404 Not Found
INFO: 172.18.0.1:52864 - "GET /docs HTTP/1.1" 200 OK
INFO: 172.18.0.1:52864 - "GET /openapi.json HTTP/1.1" 200 OK
INFO: 172.18.0.1:37646 - "GET / HTTP/1.1" 404 Not Found

Docker shows an unhealthy ollama container, but I ran the following:
docker exec -it ollama ollama run llama3
and I was able to ask ollama questions so I don't know why there is an unhealthy status. There is nothing in the logs that would indicate an issue.

Thank you for pointing out that I used the incorrect .env, we are closer now. Any ideas on the cause of the fastapi web page not rendering?

Current screenshots showing statuses after this latest build:

[choinek]

@ngpollock the reason for the "not found" errors is that you're trying to access localhost:8000/, but currently, there's nothing running on that endpoint (/.

You should use the endpoints provided in the documentation, like /ocr/request

https://github.com/CatchTheTornado/text-extract-api

@pkarw this leads me to consider that it might be worth route / to docs page, or if its not easy in FastAPI then do redirect from / to docs ;)

[ngpollock]

Thank you. For some reason I also thought there was a web page front end in addition to using curl to access the APIs. It appears my configuration is working, but I will test the APIs and provide feedback.

The only other concern is that ollama has a status of Unhealthy in docker, yet it is operating correctly.

Thank you very much for your help.

[choinek]

Ok, good to hear that everything is working as intended.

Except for this unhealthy Ollama – it should only check test: test: ["CMD", "curl", "-f", "http://localhost:11434/"], which responds with status 200 curl -i localhost:11434 > HTTP/1.1 200 OK . Currently I can't reproduce, but I'll try in a few days with diffrent setup.

A simple webpage frontend is on the roadmap. :)

Thanks for your interest, looking forward to your feedback!