New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lib389 logging tools #1763
Comments
Comment from firstyear (@Firstyear) at 2016-04-27 10:16:42 attachment |
Comment from firstyear (@Firstyear) at 2016-04-27 10:18:12 This will be really useful for things like 48007 where we need to detect lines like:
|
Comment from spichugi (@droideck) at 2016-05-03 17:47:20 Hi William, '''dirsrv_log_test.py::test_access_log''' fails with an assertion error:
|
Comment from firstyear (@Firstyear) at 2016-05-04 09:22:57 Fix for test case |
Comment from firstyear (@Firstyear) at 2016-05-04 09:23:24 This should fix the test case. |
Comment from spichugi (@droideck) at 2016-05-04 20:29:19 Thank you, William. Looks good to me. Only one thing. Could you please disable verbose?
|
Comment from firstyear (@Firstyear) at 2016-05-09 11:15:47 commit 47b9a51c013225790b575dd03a01b8944c589139 |
Comment from mreynolds (@mreynolds389) at 2016-05-13 21:52:03 There is something lacking from this implementation that I'd like to see addressed before the next respin of lib389: The log matching only works for the current log, not for rotated logs of that type. For example, it should be able to search "all" the access logs for a pattern, not just the current access log. In some of my tests the value we need might be in a rotated log, so still need an option to allow for searching rotated logs. Thanks! |
Comment from firstyear (@Firstyear) at 2016-05-16 09:53:16 Supplementary patch to add support for multiple files. |
Comment from mreynolds (@mreynolds389) at 2016-05-16 19:33:02 Thanks for adding the ability to check compressed and rotated logs! One issue I noticed, you have a sleep of 60 seconds for log buffering, but log buffering is set to 30 seconds by default. So we can probably reduce this sleep time. Also, it might be best to ignore the rotationinfo files when processing multiple files: access.rotationinfo I have another side request(we/I can do this in a separate ticket if you want), and that is to have the ability grab log output for debugging. If there is a failure in a test, it would be nice to be able to grab the last ## lines from the errors log, etc. Thanks, |
Comment from firstyear (@Firstyear) at 2016-05-17 06:24:14 Replying to [comment:10 mreynolds389]:
Actually, what would be smarter is to disable logbuffering.
This is ignored already by the pattern match "%s.-" on the files.
Ohhhh, I like that idea. I think that might need to go in a fixture somewhere though ..... Definitely a separate ticket item. |
Comment from firstyear (@Firstyear) at 2016-05-17 06:24:54 Disable log buffering to speed up the test. |
Comment from firstyear (@Firstyear) at 2016-05-18 11:38:41 |
Comment from firstyear (@Firstyear) at 2016-05-18 11:39:01 Latest update adds timestamp parsing code. |
Comment from mreynolds (@mreynolds389) at 2016-05-18 19:36:08 Looks good! Ack, but you could have used this function for disablign the log - they are both one liners so I guess it doesn't really matter: standalone.setAccessLogBuffering(True/False) |
Comment from firstyear (@Firstyear) at 2016-05-19 05:52:59 commit f320ad53d2b1c973fbc674e0a18705d5ebcfd49a Thanks man, I think I need to write up a design doc, but I want to sit and have a revamp of a few parts of the lib389 library soon, so I'll leave the access log change for the moment .... |
Comment from firstyear (@Firstyear) at 2016-06-01 08:55:29 attachment |
Comment from firstyear (@Firstyear) at 2016-06-02 04:15:05 commit 924de2f2cf94ba149368475aae2798d8dd52e672 Compressing objects: 100% (6/6), done. |
Comment from firstyear (@Firstyear) at 2017-02-11 23:05:07 Metadata Update from @Firstyear:
|
Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/48434
Lib389 should be able to read, process and interpret log outputs as part of it's tests. We should be integrating log pipe facilities to lib389 to enable this.
The text was updated successfully, but these errors were encountered: