Test 4.0rc3: Problem with adding documents [SOLVED]

When things don't work as they should.
Post Reply
qra
Posts: 32
Joined: Fri Oct 25, 2019 9:08 pm

Test 4.0rc3: Problem with adding documents [SOLVED]

Post by qra »

Testing environment:
1. Ubuntu 20.04 Server (clean installation)
2. Mayan EDMS 4.0 rc3 (basic deployment without advanced deployment; https://docs.mayan-edms.com/chapters/deploying.html)

Problem:
1. I added some documents but I can't see them in the system.
2. Next, I added a document using the function: http://127.0.0.1:8000/api/v4/documents/upload/
The document has been created but the file and version are missing.
3. Finally, I added the file to the created document (http://127.0.0.1:8000/api/v4/documents/1/files/). I also tried to add a file from the GUI. It didn't help. File and version cannot be seen in GUI.


Note: Directories "document_storage" and "document_cache" are not created.


Refers to item 1.
mayan_4.0_rc3_screenshot_2-1.png
mayan_4.0_rc3_screenshot_2-1.png (44.98 KiB) Viewed 126 times

Refers to item 1.
mayan_4.0_rc3_screenshot_2-2.png
mayan_4.0_rc3_screenshot_2-2.png (47.87 KiB) Viewed 113 times

Refers to item 2.
mayan_4.0_rc3_screenshot_2-4.png
mayan_4.0_rc3_screenshot_2-4.png (45.13 KiB) Viewed 113 times

Refers to item 3.
mayan_4.0_rc3_screenshot_2-5.png
mayan_4.0_rc3_screenshot_2-5.png (62.82 KiB) Viewed 116 times

Refers to item 3.
mayan_4.0_rc3_screenshot_2-6.png
mayan_4.0_rc3_screenshot_2-6.png (65.52 KiB) Viewed 116 times

Refers to item 3.
mayan_4.0_rc3_screenshot_2-3.png
mayan_4.0_rc3_screenshot_2-3.png (57.3 KiB) Viewed 116 times

mayan-edms-gunicorn-stderr---supervisor-56qkk96t.log

Code: Select all

[2021-05-14 18:23:55 +0000] [14920] [INFO] Starting gunicorn 20.0.4
[2021-05-14 18:23:55 +0000] [14920] [INFO] Listening at: http://0.0.0.0:8000 (14920)
[2021-05-14 18:23:55 +0000] [14920] [INFO] Using worker: sync
[2021-05-14 18:23:55 +0000] [14926] [INFO] Booting worker with pid: 14926
[2021-05-14 18:23:55 +0000] [14927] [INFO] Booting worker with pid: 14927
[2021-05-14 18:23:55 +0000] [14928] [INFO] Booting worker with pid: 14928
[2021-05-14 19:44:40 +0000] [14927] [INFO] Autorestarting worker after current request.
[2021-05-14 19:44:40 +0000] [14927] [INFO] Worker exiting (pid: 14927)
[2021-05-14 19:44:40 +0000] [18249] [INFO] Booting worker with pid: 18249
[2021-05-14 19:51:38 +0000] [14926] [INFO] Autorestarting worker after current request.
[2021-05-14 19:51:38 +0000] [14926] [INFO] Worker exiting (pid: 14926)
[2021-05-14 19:51:39 +0000] [18552] [INFO] Booting worker with pid: 18552
[2021-05-14 20:00:14 +0000] [14928] [INFO] Autorestarting worker after current request.
[2021-05-14 20:00:14 +0000] [14928] [INFO] Worker exiting (pid: 14928)
[2021-05-14 20:00:15 +0000] [18921] [INFO] Booting worker with pid: 18921

supervisord.log

Code: Select all

2021-05-14 16:47:11,060 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2021-05-14 16:47:11,061 WARN No file matches via include "/etc/supervisor/conf.d/*.conf"
2021-05-14 16:47:11,113 INFO RPC interface 'supervisor' initialized
2021-05-14 16:47:11,118 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2021-05-14 16:47:11,121 INFO supervisord started with pid 5515
2021-05-14 18:23:53,632 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2021-05-14 18:23:53,633 INFO Included extra file "/etc/supervisor/conf.d/mayan.conf" during parsing
2021-05-14 18:23:53,649 INFO RPC interface 'supervisor' initialized
2021-05-14 18:23:53,650 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2021-05-14 18:23:53,651 INFO supervisord started with pid 14905
2021-05-14 18:23:54,656 INFO spawned: 'mayan-edms-celery-beat' with pid 14915
2021-05-14 18:23:54,660 INFO spawned: 'mayan-edms-worker_a' with pid 14916
2021-05-14 18:23:54,665 INFO spawned: 'mayan-edms-worker_b' with pid 14917
2021-05-14 18:23:54,691 INFO spawned: 'mayan-edms-worker_c' with pid 14918
2021-05-14 18:23:54,699 INFO spawned: 'mayan-edms-worker_d' with pid 14919
2021-05-14 18:23:54,810 INFO spawned: 'mayan-edms-gunicorn' with pid 14920
2021-05-14 18:23:55,755 INFO success: mayan-edms-gunicorn entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2021-05-14 18:24:05,457 INFO success: mayan-edms-celery-beat entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2021-05-14 18:24:05,463 INFO success: mayan-edms-worker_a entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2021-05-14 18:24:05,463 INFO success: mayan-edms-worker_b entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2021-05-14 18:24:05,464 INFO success: mayan-edms-worker_c entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
2021-05-14 18:24:05,465 INFO success: mayan-edms-worker_d entered RUNNING state, process has stayed up for > than 10 seconds (startsecs)
User avatar
michael
Developer
Developer
Posts: 135
Joined: Sun Apr 19, 2020 6:21 am

Re: Test 4.0rc3: Problem with adding documents

Post by michael »

Seems like the document queue tasks are not running. There is one task responsible for processing new document files. However I have not been able to recreate this.

There were some last minute updates to the workers and queues. Create Mayan's supervisor config file again to get the latest queue configuration.

Check for the new folders: document_file_page_image_cache, document_file_storage and document_version_page_image_cache. These replace the fodlers: document_storage and document_cache

Thanks a lot for the reports!
qra
Posts: 32
Joined: Fri Oct 25, 2019 9:08 pm

Re: Test 4.0rc3: Problem with adding documents

Post by qra »

I installed version 4.0 today according to the new manual (https://docs.mayan-edms.com/chapters/deploying.html). Problem has been solved :D.
Post Reply