Prodigy logs

[eroux]

I tried to look at the logs of prodigy but couldn't really find anything useful in journalctl -u prodigy_bdrc_crop_images.service, I'm not sure where prodigy logs errors, info, etc. but it should be instructed to do so in a file in /usr/local/prodigy/logs/

[ta4tsering]

Both error and info log of the bdrc_crop_images.py recipe is at the /usr/local/prodigy/logs/bdrc_crop_images.log.

logs path in recipe

below is the log file

bdrc_crop_images.log

[eroux]

yes, I'm aware of that, I was referring to the prodigy logs in general

[ta4tsering]

so I have introduced the Environment=PRODIGY_LOOGING=verbose in the /etc/systemd/system/prodigy_bdrc_crop_images.service as per the Documentaion and when I do sudo journalctl -u prodigy_bdrc_crop_images.service and go to the page, all the logs are available but I couldn't instruct it to write the logs at the /usr/local/prodigy/logs. I tried by adding "log_file": "/usr/local/prodigy/logs/prodigy.log" in the /usr/local/prodigy/prodigy-tools/configuration/bdrc_crop_images.json but after restarting the server. there is still no prodigy.log file in the /usr/local/prodigy/logs
below is the image of the page after the command sudo journalctl -u prodigy_bdrc_crop_images.service

p.s I have tested all through making changes in the .service file at the server. if the addition of the Environment=PRODIGY_LOGGING=verbose looks good, then I will commit it in the prodigy-tools/install-scripts/prodigy_bdrc_crop_images.service and push the commit.

[eroux]

thanks for the investigation! I'm sure we can find a way to get the logs somehow. If you're rally stuck you can look on the Prodigy forum and ask a new question if you don't find anything, they seem to answer usually

[ta4tsering]

sure, I will post the question on the forum.