dlandon Posted December 27, 2015 Author Share Posted December 27, 2015 Update with RobJ modifications incorporated. You will need to go to the settings page and click default to get the colors set to default or remove and re-install the plugin. Further suggestions welcome. EDIT: RobJ, I've attached the latest match file and would appreciate you reviewing and making suggestions. may i ask why you don't update the release notes every time you make a change? thanks I'll take it out of beta in a few days and then start posting release notes then. Quote Link to comment
John_M Posted January 5, 2016 Share Posted January 5, 2016 I have an AOC-SASLP-MV8 which produces false positives, the second and third lines below being highlighted as errors, presumably by the presence of the word "error". Is there a way to filter this out, please? Jan 5 00:31:16 Lapulapu kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Jan 5 00:31:16 Lapulapu kernel: sas: ata9: end_device-1:0: dev error handler Jan 5 00:31:16 Lapulapu kernel: sas: ata10: end_device-1:1: dev error handler Thanks for making the highlight colours customisable. Some of the default pastel shades look too similar to my eyes. Quote Link to comment
dlandon Posted January 5, 2016 Author Share Posted January 5, 2016 I have an AOC-SASLP-MV8 which produces false positives, the second and third lines below being highlighted as errors, presumably by the presence of the word "error". Is there a way to filter this out, please? Jan 5 00:31:16 Lapulapu kernel: sas: Enter sas_scsi_recover_host busy: 0 failed: 0 Jan 5 00:31:16 Lapulapu kernel: sas: ata9: end_device-1:0: dev error handler Jan 5 00:31:16 Lapulapu kernel: sas: ata10: end_device-1:1: dev error handler Thanks for making the highlight colours customisable. Some of the default pastel shades look too similar to my eyes. Yes. I'll fix in the next release. Quote Link to comment
John_M Posted January 6, 2016 Share Posted January 6, 2016 I downloaded the latest version and it is indeed fixed. Many thanks. Quote Link to comment
John_M Posted January 10, 2016 Share Posted January 10, 2016 Jan 10 18:20:50 Lapulapu kernel: xor: automatically using best checksumming function: Jan 10 18:20:50 Lapulapu kernel: r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] Both are being flagged as Minor issues. Is it the word "checksumming" that's causing the false positive, for some reason? Quote Link to comment
dlandon Posted January 10, 2016 Author Share Posted January 10, 2016 Jan 10 18:20:50 Lapulapu kernel: xor: automatically using best checksumming function: Jan 10 18:20:50 Lapulapu kernel: r8169 0000:04:00.0 eth0: jumbo features [frames: 9200 bytes, tx checksumming: ko] Both are being flagged as Minor issues. Is it the word "checksumming" that's causing the false positive, for some reason? It's actually the match "checksum" that is marking the lines, but those should be marked as system, not minor issue. "checksumming" should be checked first and it should be marked as "system" according to the original unmenu matching file. I'll fix in next release. Quote Link to comment
John_M Posted January 14, 2016 Share Posted January 14, 2016 False positives resulting from pre-clear reports: Jan 13 21:40:33 Northolt preclear_disk-diff[52582]: #011#011#011#011#011without error or no self-test has ever Jan 13 21:40:33 Northolt preclear_disk-diff[52582]: #011#011#011#011#011SCT Error Recovery Control supported. Jan 13 21:40:33 Northolt preclear_disk-diff[52582]: ID# ATTRIBUTE_NAME FLAG VALUE WORST THRESH TYPE UPDATED WHEN_FAILED RAW_VALUE Jan 13 21:40:33 Northolt preclear_disk-diff[52582]: SMART Error Log Version: 1 Jan 13 21:40:33 Northolt preclear_disk-diff[52582]: # 1 Short offline Completed without error 00% 89 - I guess it's the word "error" that's being caught as an Error, and the word "WHEN_FAILED" that's being caught as a Minor Issue. Quote Link to comment
John_M Posted January 21, 2016 Share Posted January 21, 2016 I'm getting a false positive from the mover. It indicates as a Minor Issue and I'm guessing it's triggered by the question mark in the folder name. Jan 20 18:52:36 Lapulapu logger: ./Public/Shared Videos/EyeTV Archive/Manchester's Serial Killer?.eyetv/000000001c4ef6f8.mpg Jan 20 18:52:36 Lapulapu logger: >f+++++++++ Public/Shared Videos/EyeTV Archive/Manchester's Serial Killer?.eyetv/000000001c4ef6f8.mpg Jan 20 18:52:36 Lapulapu logger: ./Public/Shared Videos/EyeTV Archive/Manchester's Serial Killer?.eyetv Quote Link to comment
dlandon Posted January 21, 2016 Author Share Posted January 21, 2016 Or could be by "Kill" in Killer Yes, it is 'kill'. I'll have to take a look at blocking the false positives. Quote Link to comment
_K9 Posted June 8, 2016 Share Posted June 8, 2016 As i'm relatively new to unRaid and I started on 6.2.0, is there any benefits to using this over the stock log which already has color coding? I'm not sure if this meant to cover a gap in previous versions. Quote Link to comment
dlandon Posted February 19, 2017 Author Share Posted February 19, 2017 Just to let everyone know this plugin is still alive and well. It just hasn't needed any updates, but is still working with unRAID 6.3. Quote Link to comment
John_M Posted February 19, 2017 Share Posted February 19, 2017 I use it in preference to the stock syslog viewer because it's more customisable (I find the red (error) and the orange (login) highlights too similar in the built-in viewer) and because it has better filtering and therefore fewer false indications. Quote Link to comment
dlandon Posted February 19, 2017 Author Share Posted February 19, 2017 Glad to hear you are using it. Someone mentioned that there wasn't a posting for quite a while and they thought the plugin might have been abandoned or dead. Not so. I too like making my own choices for the colors. I have a color deficiency and some of the colors I have trouble discerning. Quote Link to comment
Vr2Io Posted February 19, 2017 Share Posted February 19, 2017 Just to let everyone know this plugin is still alive and well. It just hasn't needed any updates, but is still working with unRAID 6.3. Thanks, love this plugin . Quote Link to comment
Vr2Io Posted February 22, 2017 Share Posted February 22, 2017 May I know below update will affect any access of built-in Syslog, thanks enhanced.log 2017.02.19 Replace the built-in Syslog with the enhanced Syslog. Quote Link to comment
dlandon Posted February 22, 2017 Author Share Posted February 22, 2017 4 hours ago, Benson said: May I know below update will affect any access of built-in Syslog, thanks enhanced.log 2017.02.19 Replace the built-in Syslog with the enhanced Syslog. It replaces it. Quote Link to comment
Oxxy Posted July 18, 2017 Share Posted July 18, 2017 I have had this running for a while, i *think* it worked when i first started setting up unraid, but this has no logs at all. So obviously, I have broken something, or something else is borked. So log screen has no logs, I have also downloaded the logs, and i have an empty file. Had a skim through this thread and not sure i have seen anything relevant to my issue. Shall I reinstall or is there something else i can do to troubleshoot? Cheers! Quote Link to comment
dlandon Posted July 18, 2017 Author Share Posted July 18, 2017 18 minutes ago, Oxxy said: I have had this running for a while, i *think* it worked when i first started setting up unraid, but this has no logs at all. So obviously, I have broken something, or something else is borked. So log screen has no logs, I have also downloaded the logs, and i have an empty file. Had a skim through this thread and not sure i have seen anything relevant to my issue. Shall I reinstall or is there something else i can do to troubleshoot? Cheers! Remove the plugin and see if you can view the log with the built in log viewer. If not, then there is an unRAID issue. Quote Link to comment
Oxxy Posted July 19, 2017 Share Posted July 19, 2017 Thanks for the reply. The remove plugin seems a bit greyed out, certainly when i click on it nothing happens. I stopped the array to see if that needed to be done prior to removal, then the GUI hung. So I used command line to restart it as cleanly as i could. Upon restart, the logs seem to be working. Now the logs are working, seems i have more issues to address! Thanks for the assistance dlandon (and the hard work you do around here). If this happens again, shall i report back? Quote Link to comment
dlandon Posted July 19, 2017 Author Share Posted July 19, 2017 18 minutes ago, Oxxy said: Thanks for the reply. The remove plugin seems a bit greyed out, certainly when i click on it nothing happens. I stopped the array to see if that needed to be done prior to removal, then the GUI hung. So I used command line to restart it as cleanly as i could. Upon restart, the logs seem to be working. Now the logs are working, seems i have more issues to address! Thanks for the assistance dlandon (and the hard work you do around here). If this happens again, shall i report back? Keep an eye on the log space. You may have filled it. Quote Link to comment
Oxxy Posted July 19, 2017 Share Posted July 19, 2017 Does it log to the cache drive? If so, that was choc full. Mover wasn't moving anything out of it. I moved everything off manually just ealier today. For some silly reason i didnt think to mention it (sorry, juggling a lot) Would that explain it? Quote Link to comment
trurl Posted July 19, 2017 Share Posted July 19, 2017 8 hours ago, Oxxy said: Does it log to the cache drive? If so, that was choc full. Mover wasn't moving anything out of it. I moved everything off manually just ealier today. For some silly reason i didnt think to mention it (sorry, juggling a lot) Would that explain it? It logs to a limited space reserved in RAM. On the Dashboard near lower left you can check on the space used on flash : log : docker. Quote Link to comment
JohanSF Posted September 27, 2017 Share Posted September 27, 2017 Any chance of an option to reverse the order the log is viewed? It's tiresome to have to scroll so far down everytime I want to view what just happened. Quote Link to comment
dlandon Posted September 27, 2017 Author Share Posted September 27, 2017 4 hours ago, JohanSF said: Any chance of an option to reverse the order the log is viewed? It's tiresome to have to scroll so far down everytime I want to view what just happened. Ctrl-End takes you to the bottom of the log. Quote Link to comment
John_M Posted October 1, 2017 Share Posted October 1, 2017 On 27/09/2017 at 10:02 PM, dlandon said: Ctrl-End takes you to the bottom of the log. Or you can click the Log button at the top right of any page of the GUI to pop-up a window showing the last few lines of the log. It's a core unRIAD feature that works independently of this plugin and I find it very useful. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.