dockerized docspell resulting jobs in waiting forever #2564
Comments
|
Hello @damjankumin, it could be that the two components (joex and server) are not seeing each other. Can you check whether you can connect from one to the other? The timeout exception also indicates some connection problems. Of course, just a guess. Can you create accounts and log in successfully? If so, then the postgres connection is good. If the job is in state |
|
So i could create username, also generate organisation.. in the startup of containers I could also see that database connection is successfully done. I made sure that all containers are on the same docker network (its the network where all containers are residing) - only difference is the restserver that also has traefik network attached so that it is also accessible from outside docker network. Now I just exec into restserver and ran suggested command, and here is the result: Seems that notification is just fine. Also just double confirmed, all containers are on the same net, even IP addresses go one after another (as created).. |
|
Ok so that means joex should be correctly notified, if it has the correct base-url configured. After you initiated this curl, has the job in the job queue been picked up and processed? Do you see any interesting logs for joex? |
|
once submitted notification, the jobs have not progresses in pipeline... nothing happened actually. In logs, the only thing I see what I posted above, that was from restserver - joex has nothing, apart from regular startup log entries, all i see is |
|
Hm, very strange to me. So just to re-assure I understood correctly: there is a job in the queue in state "waiting", after running this curl, joex didn't print any logs and the job is still there in state "waiting"? Can you perhaps restart joex with more logging enabled, maybe set this env variable for joex: DOCSPELL_SERVER_LOGGING_LEVELS_DOCSPELL="Debug"After restarting, joex should also pick up this job. |
|
OK, so I added the variable. After restart, job is still in waiting - look at the attached image for proof. In the logs, there is this: The rest server log is long and attached. |
|
I think we can leave the restserver aside for now. It seems that joex can't pick up this job. It could be that the processing threads are occupied. There are system jobs also running. If you create an account |
|
I am sorry - I do not get it, what am I do to? Login in docspell or docker host? In any case, there is nothing happening, I also gave all containers free reign for resources, and host is like 36core/128GB on U.2 disks - no one is using it - there is only one dest doc uploaded (which is still in waiting from yesterday) to the docspell system itself |
|
What I meant is creating a new account in the docspell app, name it |
|
Man I do not know - I must be doing something wrong... I created as you requested - nothing changes, visually or processing(ly).. take a look at screenshots.. 
|
|
When you login as user |
|
above screenshots are taken as logged user |
|
Hm, ok so this means you also uploaded a document as user Can you perhaps share exactly how you are running and accessing docspell? So I could try to reproduce it here. Or maybe you can try with the provided docker-compose if that also yields this problem? I couldn't reproduce it this way at least, but there has to be some cause :-) |
|
Indeed, I saw no jobs as I can try running it on test environment as default compose, no changes or anything. After that I can post my compose here. Give me short time to test |
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. This only applies to 'question' issues. Always feel free to reopen or create new issues. Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hello,
i have deployed this fantastic piece of software on my central docker server. I used docker compose approach with minor modifications (aded traefik for front). The application(s) containers come up, no errors in starting, no errors with loading. Once in, I choose to load one 3 page document and - nothing. then go check jobs and all I see is job waiting for like 30min now. Nothing moves ahead. In logs, I see no errors in any of containers, the only thing that comes up periodically is in the restserver:
service.txt
Beyond that error, there is nothing. I see tmp/ folder getting populated but that is about it.
Any insight to what to check at all, what to do or try to repair? The compose file I use is attached to this post.
Thanks in advance!
NOTE: the database is externally hosted pg
The text was updated successfully, but these errors were encountered: