forked from ufal/clarin-dspace
-
Notifications
You must be signed in to change notification settings - Fork 2
Open
Labels
Description
We frequently get "Could not read resource cocoon" in the cocoon logs:
cyp@fido /project/lindat-dspace/installation/log $ grep "ERROR.*Could not read resource" cocoon.log* | tail -20
cocoon.log.2017-06-19:2017-06-19 04:58:12,299 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-19:2017-06-19 05:00:38,644 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-19:2017-06-19 10:56:49,220 ERROR cocoon.handled - Could not read resource cocoon://DRI/3/submit/825b143e0b552a2429494d23533d475634536226.continue
cocoon.log.2017-06-19:2017-06-19 10:57:56,342 ERROR cocoon.handled - Could not read resource cocoon://DRI/3/submit/825b143e0b552a2429494d23533d475634536226.continue
cocoon.log.2017-06-19:2017-06-19 16:34:51,818 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1060/license/agree
cocoon.log.2017-06-20:2017-06-20 07:41:11,983 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-20:2017-06-20 09:34:08,970 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-20:2017-06-20 12:32:01,399 ERROR cocoon.handled - Could not read resource cocoon://DRI/3/submit/616826351a4f6a0218155114541d7368410e464a.continue
cocoon.log.2017-06-20:2017-06-20 14:37:39,706 ERROR cocoon.handled - Could not read resource cocoon://DRI/3/submit/436b0d4c4a1065784d1f3621477a5a3726304582.continue
cocoon.log.2017-06-21:2017-06-21 07:15:40,845 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-21:2017-06-21 08:01:20,432 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-21:2017-06-21 13:10:40,125 ERROR cocoon.handled - Could not read resource cocoon://DRI/3/submit/8958757a2a201a1672695c1415652d4379178805.continue
cocoon.log.2017-06-21:2017-06-21 14:22:02,085 ERROR cocoon.handled - Could not read resource cocoon://DRI/3/submit/256a6c714a403e2620465c1d721b5e52297e1d4d.continue
cocoon.log.2017-06-21:2017-06-21 14:34:26,229 ERROR cocoon.handled - Could not read resource cocoon://DRI/1/handle/11356/1024/workflow
cocoon.log.2017-06-21:2017-06-21 14:43:31,694 ERROR cocoon.handled - Could not read resource cocoon://DRI/1/handle/11356/1024/workflow
cocoon.log.2017-06-21:2017-06-21 20:48:42,420 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1061/license/agree
cocoon.log.2017-06-22:2017-06-22 08:16:25,721 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-22:2017-06-22 08:24:54,916 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1049/license/agree
cocoon.log.2017-06-22:2017-06-22 12:15:01,709 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1042/license/agree
cocoon.log.2017-06-22:2017-06-22 20:57:11,246 ERROR cocoon.handled - Could not read resource cocoon://DRI/8/handle/11356/1060/license/agree
It might not be important to solve this, but would be good to at least know what causes it and if and how it affects users.