-
Notifications
You must be signed in to change notification settings - Fork 12
logparser fails to create RRD directory #40
Comments
@cptMikky I don't think the script should be responsible for creating the directory structure. A better option would be to ensure the directory exists when the global setting is modified. What do you think? |
From @cptMikky on March 8, 2018 21:30 Not sure. Directory structure, especially in /tmp is definitely a responsibility of the owner (the script in this scenario). As for other places, well, hard to tell, I have no single opinion. However, a directory existence test and a (sane) error message would be enough I guess. |
I have the same issue on ubuntu 20.04 with modoboa 16.0. Which folder should I create please? |
@florealcab You can customize the folder in the admin panel (settings). |
I don't see anything related to statistics in the new or old admin. In the old admin I get In the new admin, no tab or option related to statistics. I have followed all the steps in the README (install plugin, modify settings.py, restart gunicorn). |
Nervermind, I was looking at the wrong place. Configuration is in the modoboa menu in the old admin interface. I had to add sudo policy because the cron command
It also created a new file |
From @cptMikky on March 5, 2018 23:14
Impacted versions
Steps to reproduce
Current behavior
RRD storage directory does not exist and logparser probably doesn't even try to create it.
Expected behavior
Parse log and create RRD files. Create the necessary directory structure and fail properly if that isn't possible.
Command works as expected after the directory is created manually.
Copied from original issue: modoboa/modoboa#1424
The text was updated successfully, but these errors were encountered: