| Anonymous | Login | 2024-04-26 09:08 MDT |
| Main | My View | View Issues | Change Log | Roadmap | Repositories |
| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
| 0013441 | ClearOS | yum | public | 2017-03-04 16:58 | 2017-08-11 12:48 | ||||
| Reporter | dloper | ||||||||
| Assigned To | dloper | ||||||||
| Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
| Status | closed | Resolution | unable to reproduce | ||||||
| Platform | OS | OS Version | |||||||
| Product Version | 7.3.0 | ||||||||
| Target Version | 7.3.1 Updates | Fixed in Version | |||||||
| Summary | 0013441: journalctl performs too many log entries after update | ||||||||
| Description | https://www.clearos.com/clearfoundation/social/community/clearos-7-3-any-rough-eta [^] see comment by Matthew Lichtenberger "For what it's worth, I found this post because my system updated to 7.3 and I started receiving the mass errors every five minutes in journalctl. The fix is to edit /usr/clearos/apps/base/deploy/servicewatch and remove the services there that aren't on the system (in my case, it was zarafa-*, ibvpn, eziod, and vpnwatchd)." | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files | |||||||||
 Relationships |
|
 Relationships |
|
Notes |
|
|
(0004971) user2 2017-03-07 09:40 |
Unable to duplicate. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2017-03-04 16:58 | dloper | New Issue | |
| 2017-03-06 12:36 | dloper | Target Version | 7.3.1 => 7.3.1 Updates |
| 2017-03-07 09:40 | user2 | Note Added: 0004971 | |
| 2017-03-07 09:40 | user2 | Status | new => feedback |
| 2017-08-11 12:48 | dloper | Status | feedback => closed |
| 2017-08-11 12:48 | dloper | Assigned To | => dloper |
| 2017-08-11 12:48 | dloper | Resolution | open => unable to reproduce |
|
Issue History |