You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks a lot for all the enhancements, which i am testing atm. I am right now using the OCR-D-Manager and the OCR-D-Monitor as seperate Docker applications and not as part of a meta repository and i am struggling with some things in the current Master.
The current version of the manager is using the Mongo Database which is started by the compose-file of the Monitor container.
I had the Monitor to join the Docker network of the Manager in order to be able to communicate between the two. Right now it is therefor not possible to use the Manager standalone since it is depending on an running Monitor.
2) It seems like the Shell Script in the Manager is storing Jobs inside the Mongo collection OcrdJobs
but the Monitor is getting the job data from the collection MongoOcrdJobs.
The monitor can therefor not find OcrdJobs which are stored in a different collection.
3. I changed the OCR-D-Manager to store jobs to the MongoOcrdJob collection as well. I then get data in the job overview, but there seems to be another problem as i get a lot of errors which crash the application. The code in /ocrd-monitor/ocrdmonitor/server/jobs.py and the Jinja template try to access a property ocrd_job on the OcrdJob dataclass, but this property does not seem to exist in the class. Maybe i am missing something
I have not yet tested the retrieval of data from the controller in the job overview so i commented out those checks. What happens if the controller is not reachable: is it still possible to list the jobs (without current statuses from the controller of course) or would the overview fail?
The text was updated successfully, but these errors were encountered:
In the latest master point 2 and 3 already seem to be adressed. Regarding 4.: The job overview might fail if the ssh request for the pid returns an empty string:
Hi,
Thanks a lot for all the enhancements, which i am testing atm. I am right now using the OCR-D-Manager and the OCR-D-Monitor as seperate Docker applications and not as part of a meta repository and i am struggling with some things in the current Master.
I had the Monitor to join the Docker network of the Manager in order to be able to communicate between the two. Right now it is therefor not possible to use the Manager standalone since it is depending on an running Monitor.
2) It seems like the Shell Script in the Manager is storing Jobs inside the Mongo collectionOcrdJobs
but the Monitor is getting the job data from the collectionMongoOcrdJobs
.The monitor can therefor not find OcrdJobs which are stored in a different collection.3. I changed the OCR-D-Manager to store jobs to theMongoOcrdJob
collection as well. I then get data in the job overview, but there seems to be another problem as i get a lot of errors which crash the application. The code in/ocrd-monitor/ocrdmonitor/server/jobs.py
and the Jinja template try to access a propertyocrd_job
on the OcrdJob dataclass, but this property does not seem to exist in the class. Maybe i am missing somethingThe text was updated successfully, but these errors were encountered: