Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Idle timeout reached for #1257

Open
cmargiotta opened this issue Dec 9, 2024 · 1 comment
Open

Idle timeout reached for #1257

cmargiotta opened this issue Dec 9, 2024 · 1 comment

Comments

@cmargiotta
Copy link

Hi, thanks a lot for developing this tool!

I am having a lot of troubles while trying to use scrapers, every request I do ends in a "Idle timeout reached for ...", I tested the xpath as written in the wiki and it works, I tried to ping the web service from the running container and the connection does not have any issue.

The scraper I am trying to use is based on openlibrary.org, but I get this error even on the examples from the wiki or using github.com as address.

I am in a docker swarm environment, this is the service I am using:

koillection:
        image: koillection/koillection:1.5.16
        ports:
            - 8167:80
        networks:
            - internal
        environment:
            - APP_ENV=prod
            - APP_DEBUG=0
            - DB_DRIVER=pdo_pgsql
            - DB_NAME=koillection
            - DB_HOST=postgresql
            - DB_PORT=5432
            - DB_USER=postgres
            - DB_PASSWORD=postgres
            - DB_VERSION=15
            - PHP_TZ=Europe/Rome
            - UPLOAD_MAX_FILESIZE=50M
            - PHP_MEMORY_LIMIT=512M
            - HTTPS_ENABLED=0
        volumes:
            - /data/data/koillection:/uploads

Everything else seems to work well.

Thanks in advance!

@cmargiotta
Copy link
Author

The problem was that DNS resolution was slow with the default resolv.conf (~5sec), I injected a new resolv.conf that gives priority to an external DNS server but now postgresql name resolution is slow, so I had to reach postgres using its LAN IP address.

It is working now, but maybe some defaults can be tweaked to avoid that?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant