Re: [Mayan EDMS: 1955] Re: Questions About Installing Mayan 2.6
Hi Mark, Enjoy your trip! We'll talk later. On Monday, July 31, 2017 at 1:24:38 AM UTC-4, Mark Phillips wrote: > > Roberto, > > I will try in a week or so. Headed to Puerto Vallarta for some sun and > scuba diving with the family. Be back in a week! > > Mark > > On Fri, Jul 28, 2017 at 10:27 PM, Roberto Rosario < > roberto.rosario.gonza...@gmail.com> wrote: > >> Please pull the latest version of the container, version 2.6.4-4 and try >> again with that one. >> >> >> On Friday, July 28, 2017 at 4:18:44 PM UTC-4, Roberto Rosario wrote: >>> >>> Hahaha! Good one :D >>> >>> Only thing I can think of is the a few changes to the 'initialsetup' >>> signal, I think start there. Thanks for helping track this down. >>> >>> On Friday, July 28, 2017 at 11:59:30 AM UTC-4, Mark Phillips wrote: Sorry, Roberto, but the error.log file is empty...size 0. I always strive to run an error-free environment;) root@orca:/home/mark/mayan2-docker# docker exec -ti mayan-edms /bin/bash root@51cbdb670142:/# cat /usr/local/lib/python2.7/dist-packages/mayan/error.log root@51cbdb670142:/# root@51cbdb670142:/# ls -alh /usr/local/lib/python2.7/dist-packages/mayan/error.log -rw-r--r-- 1 www-data www-data 0 Jul 26 07:16 /usr/local/lib/python2.7/dist-packages/mayan/error.log root@51cbdb670142:/# find . -name error.log ./usr/local/lib/python2.7/dist-packages/mayan/error.log ./var/log/nginx/error.log root@51cbdb670142:/# cat ./var/log/nginx/error.log root@51cbdb670142:/# root@51cbdb670142:/# ls -alh ./var/log/nginx/error.log -rw-r- 1 www-data adm 0 Jul 26 07:09 ./var/log/nginx/error.log root@51cbdb670142:/# Mark On Thu, Jul 27, 2017 at 11:04 PM, Roberto Rosario < roberto.rosario.gonza...@gmail.com> wrote: > Thanks Mark, > > Indeed no error at all... > > Try this: > > docker exec -ti test-mayan-edms sh -c "cat > /usr/local/lib/python2.7/dist-packages/mayan/error.log" > > Version 2.6 added a feature to do extra logging of errors in > production for situations like this. Let's see if this log caught > something. > > > > On Friday, July 28, 2017 at 1:45:25 AM UTC-4, Mark Phillips wrote: >> >> Roberto, >> >> I have attached the log file you requested. There is no "Superuser >> created successfully" entry, and no error around the log segment you >> sent >> in your email >> >> Applying sources.0015_auto_20170206_0835... OK >> Applying sources.0016_auto_20170630_2040... OK >> Applying statistics.0001_initial... OK >> Applying tags.0001_initial... OK >> Applying tags.0002_tag_selection... OK >> Applying tags.0003_remove_tag_color... OK >> Applying tags.0004_auto_20150717_2336... OK >> Applying tags.0005_auto_20150718_0616... OK >> Applying tags.0006_documenttag... OK >> Applying tags.0007_auto_20170118_1758... OK >> Deleting 'suit/css/suit.css' >> Deleting 'suit/css/filer.css' >> Deleting 'suit/css/djangocms.css' >> Deleting 'suit/less/mixins.less' >> Deleting 'suit/less/suit.less' >> Deleting 'suit/less/left-column.less' >> Deleting 'suit/less/footer.less' >> Deleting 'suit/less/print.less' >> Deleting 'suit/less/variables.less' >> >> and then much later (still no errors...) >> >> 686 static files copied to >> '/usr/local/lib/python2.7/dist-packages/mayan/media/static'. >> 2017-07-27 16:05:49,339 CRIT Supervisor running as root (no user in >> config file) >> 2017-07-27 16:05:49,339 WARN Included extra file >> "/etc/supervisor/conf.d/beat.conf" during parsing >> 2017-07-27 16:05:49,339 WARN Included extra file >> "/etc/supervisor/conf.d/nginx.conf" during parsing >> 2017-07-27 16:05:49,339 WARN Included extra file >> "/etc/supervisor/conf.d/redis.conf" during parsing >> 2017-07-27 16:05:49,340 WARN Included extra file >> "/etc/supervisor/conf.d/uwsgi.conf" during parsing >> 2017-07-27 16:05:49,340 WARN Included extra file >> "/etc/supervisor/conf.d/workers.conf" during parsing >> 2017-07-27 16:05:49,423 INFO RPC interface 'supervisor' initialized >> 2017-07-27 16:05:49,423 CRIT Server 'unix_http_server' running >> without any HTTP authentication checking >> 2017-07-27 16:05:49,423 INFO supervisord started with pid 1 >> 2017-07-27 16:05:50,426 INFO spawned: 'mayan-worker-medium' with pid >> 80 >> 2017-07-27 16:05:50,430 INFO spawned: 'mayan-worker-slow' with pid 81 >> 2017-07-27 16:05:50,433 INFO spawned: 'celery-beat' with pid 82 >> 2017-07-27 16:05:50,437 INFO spawned: 'mayan-worker-fast' with pid 83 >> 2017-07-27 16:05:50,442 INFO spawned: 'redis' with pid 84 >> 2017-07-27 16:05:50,449 INFO spawned: 'nginx' with pid 85 >> 2017-07-27 16:05:50,454 INFO spawned: 'uwsgi' with pid 86
Re: [Mayan EDMS: 1953] Re: Questions About Installing Mayan 2.6
Roberto, I will try in a week or so. Headed to Puerto Vallarta for some sun and scuba diving with the family. Be back in a week! Mark On Fri, Jul 28, 2017 at 10:27 PM, Roberto Rosario < roberto.rosario.gonza...@gmail.com> wrote: > Please pull the latest version of the container, version 2.6.4-4 and try > again with that one. > > > On Friday, July 28, 2017 at 4:18:44 PM UTC-4, Roberto Rosario wrote: >> >> Hahaha! Good one :D >> >> Only thing I can think of is the a few changes to the 'initialsetup' >> signal, I think start there. Thanks for helping track this down. >> >> On Friday, July 28, 2017 at 11:59:30 AM UTC-4, Mark Phillips wrote: >>> >>> Sorry, Roberto, but the error.log file is empty...size 0. I always >>> strive to run an error-free environment;) >>> >>> root@orca:/home/mark/mayan2-docker# docker exec -ti mayan-edms /bin/bash >>> root@51cbdb670142:/# cat /usr/local/lib/python2.7/dist- >>> packages/mayan/error.log >>> root@51cbdb670142:/# >>> root@51cbdb670142:/# ls -alh /usr/local/lib/python2.7/dist- >>> packages/mayan/error.log >>> -rw-r--r-- 1 www-data www-data 0 Jul 26 07:16 >>> /usr/local/lib/python2.7/dist-packages/mayan/error.log >>> root@51cbdb670142:/# find . -name error.log >>> ./usr/local/lib/python2.7/dist-packages/mayan/error.log >>> ./var/log/nginx/error.log >>> root@51cbdb670142:/# cat ./var/log/nginx/error.log >>> root@51cbdb670142:/# >>> root@51cbdb670142:/# ls -alh ./var/log/nginx/error.log >>> -rw-r- 1 www-data adm 0 Jul 26 07:09 ./var/log/nginx/error.log >>> root@51cbdb670142:/# >>> >>> Mark >>> >>> On Thu, Jul 27, 2017 at 11:04 PM, Roberto Rosario < >>> roberto.rosario.gonza...@gmail.com> wrote: >>> Thanks Mark, Indeed no error at all... Try this: docker exec -ti test-mayan-edms sh -c "cat /usr/local/lib/python2.7/dist-packages/mayan/error.log" Version 2.6 added a feature to do extra logging of errors in production for situations like this. Let's see if this log caught something. On Friday, July 28, 2017 at 1:45:25 AM UTC-4, Mark Phillips wrote: > > Roberto, > > I have attached the log file you requested. There is no "Superuser > created successfully" entry, and no error around the log segment you sent > in your email > > Applying sources.0015_auto_20170206_0835... OK > Applying sources.0016_auto_20170630_2040... OK > Applying statistics.0001_initial... OK > Applying tags.0001_initial... OK > Applying tags.0002_tag_selection... OK > Applying tags.0003_remove_tag_color... OK > Applying tags.0004_auto_20150717_2336... OK > Applying tags.0005_auto_20150718_0616... OK > Applying tags.0006_documenttag... OK > Applying tags.0007_auto_20170118_1758... OK > Deleting 'suit/css/suit.css' > Deleting 'suit/css/filer.css' > Deleting 'suit/css/djangocms.css' > Deleting 'suit/less/mixins.less' > Deleting 'suit/less/suit.less' > Deleting 'suit/less/left-column.less' > Deleting 'suit/less/footer.less' > Deleting 'suit/less/print.less' > Deleting 'suit/less/variables.less' > > and then much later (still no errors...) > > 686 static files copied to '/usr/local/lib/python2.7/dist > -packages/mayan/media/static'. > 2017-07-27 16:05:49,339 CRIT Supervisor running as root (no user in > config file) > 2017-07-27 16:05:49,339 WARN Included extra file > "/etc/supervisor/conf.d/beat.conf" during parsing > 2017-07-27 16:05:49,339 WARN Included extra file > "/etc/supervisor/conf.d/nginx.conf" during parsing > 2017-07-27 16:05:49,339 WARN Included extra file > "/etc/supervisor/conf.d/redis.conf" during parsing > 2017-07-27 16:05:49,340 WARN Included extra file > "/etc/supervisor/conf.d/uwsgi.conf" during parsing > 2017-07-27 16:05:49,340 WARN Included extra file > "/etc/supervisor/conf.d/workers.conf" during parsing > 2017-07-27 16:05:49,423 INFO RPC interface 'supervisor' initialized > 2017-07-27 16:05:49,423 CRIT Server 'unix_http_server' running without > any HTTP authentication checking > 2017-07-27 16:05:49,423 INFO supervisord started with pid 1 > 2017-07-27 16:05:50,426 INFO spawned: 'mayan-worker-medium' with pid 80 > 2017-07-27 16:05:50,430 INFO spawned: 'mayan-worker-slow' with pid 81 > 2017-07-27 16:05:50,433 INFO spawned: 'celery-beat' with pid 82 > 2017-07-27 16:05:50,437 INFO spawned: 'mayan-worker-fast' with pid 83 > 2017-07-27 16:05:50,442 INFO spawned: 'redis' with pid 84 > 2017-07-27 16:05:50,449 INFO spawned: 'nginx' with pid 85 > 2017-07-27 16:05:50,454 INFO spawned: 'uwsgi' with pid 86 > 2017-07-27 16:05:52,376 INFO success: redis entered RUNNING state, > process has stayed up for > than 1 seconds (startsecs) > 2017-07-27 16:05:52,376 INFO success: nginx entered RUNNING state, > process has stayed up for > than 1 seconds (startsecs) > 2017-07-27
[Mayan EDMS: 1952] Re: Database is locked
I would start by restarting the instance. Did you deploy through Docker? -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1951] Database is locked
Hello, I want to upload pdf documents to EDMS but I am getting "Database is locked" error but the files appear in document_storage folder. What can i do for this error. Thank you Best Regards -- --- You received this message because you are subscribed to the Google Groups "Mayan EDMS" group. To unsubscribe from this group and stop receiving emails from it, send an email to mayan-edms+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[Mayan EDMS: 1950] Index view - item count
Good afternoon,
First thanks for this amazing piece of software. Originally I wanted to
manage my household bills, statements, etc with it, but I found that it is
an awesome software for also managing my ebook library (obviously in its
own document type!).
I really enjoy the index feature, and it has been the opportunity to learn
a bit of django templating - my documents which had not the Publisher
metadata defined were not appearing in the index, and I solved that by
setting a template of the form:
{% if document.metadata_value_of.Publisher %} {{
document.metadata_value_of.Publisher }} {% else %} VARIOUS {% endif %}
Now, I have the following request:
The items count of an index only report the number of nodes in the next
level of tree template
Would it be complex to add an additional column 'Documents' showing the
number of documents in the last level of the tree template? Currently for
instance my first 5 first nodes only report 1 item, but it would be great
to know how many documents are under this one item!
Again appreciate that your backlog is full of many requests, but I am not
sure that it is really complex for someone who can navigate the code easily.
Kind regards.
--
---
You received this message because you are subscribed to the Google Groups
"Mayan EDMS" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to mayan-edms+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
