Details
-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: 4.7.0
-
Fix Version/s: 4.12.0-b1
-
Component/s: Plugins, Staff Interface
-
Labels:None
Description
The System Status plugin widget checks for various common issues. One issue that people have been having is that the Blesta logs (../logs_blesta defined under Settings > System > General) may not be writable.
This can typically happen if the web server runs as a different user than the cron. We should detect that some how and display an alert in the System Status widget.
This may require a cron task for the plugin that attempts to write something to a log file, and the widget through the browser can attempt to write also to the same file. If either fail then we alert with error. This error should include indicate what user the cron is running as, and what user the web server is running as if they are different.
OR better yet, what we can do is look at the ownership of the files in the logs_blesta directory, and if any are owned by a user other than the user we are running as show a message and doc points on the graph.
Activity
Field | Original Value | New Value |
---|---|---|
Rank | Ranked higher |
Rank | Ranked lower |
Rank | Ranked higher |
Description |
The System Status plugin widget checks for various common issues. One issue that people have been having is that the Blesta logs (../logs_blesta defined under Settings > System > General) may not be writable.
This can typically happen if the web server runs as a different user than the cron. We should detect that some how and display an alert in the System Status widget. This may require a cron task for the plugin that attempts to write something to a log file, and the widget through the browser can attempt to write also to the same file. If either fail then we alert with error. This error should include indicate what user the cron is running as, and what user the web server is running as if they are different. |
The System Status plugin widget checks for various common issues. One issue that people have been having is that the Blesta logs (../logs_blesta defined under Settings > System > General) may not be writable.
This can typically happen if the web server runs as a different user than the cron. We should detect that some how and display an alert in the System Status widget. -This may require a cron task for the plugin that attempts to write something to a log file, and the widget through the browser can attempt to write also to the same file. If either fail then we alert with error. This error should include indicate what user the cron is running as, and what user the web server is running as if they are different.- OR better yet, what we can do is look at the ownership of the files in the logs_blesta directory, and if any are owned by a user other than the user we are running as show a message and doc points on the graph. |
Story Points | 3 |
Fix Version/s | 4.12.0-b1 [ 11502 ] | |
Fix Version/s | Short Term [ 10800 ] |
Sprint | 4.12.0 Sprint 3 [ 115 ] |
Rank | Ranked lower |
Assignee | Jonathan Reissmueller [ jonathan ] |
Status | Open [ 1 ] | In Progress [ 3 ] |
Status | In Progress [ 3 ] | In Review [ 5 ] |
Resolution | Fixed [ 1 ] |
Remaining Estimate | 0 minutes [ 0 ] | |
Time Spent | 1 hour, 11 minutes [ 4260 ] | |
Worklog Id | 14003 [ 14003 ] |
Time Spent | 1 hour, 11 minutes [ 4260 ] | 1 hour, 27 minutes [ 5220 ] |
Worklog Id | 14007 [ 14007 ] |
Time Spent | 1 hour, 27 minutes [ 5220 ] | 1 hour, 49 minutes [ 6540 ] |
Worklog Id | 14009 [ 14009 ] |
Time Spent | 1 hour, 49 minutes [ 6540 ] | 2 hours, 17 minutes [ 8220 ] |
Worklog Id | 14013 [ 14013 ] |
Status | In Review [ 5 ] | Closed [ 6 ] |