From builds at travis-ci.org Mon Mar 12 18:20:54 2018 From: builds at travis-ci.org (Travis CI) Date: Mon, 12 Mar 2018 18:20:54 +0000 Subject: [sos-devel] Passed: BryanQuigley/sos#60 (nslcd - 8e32455) In-Reply-To: Message-ID: <5aa6c506a5994_43fd0e89f3ed82289765@e7b85fcd-2755-4d57-b4e3-4907fb01400f.mail> Build Update for BryanQuigley/sos ------------------------------------- Build: #60 Status: Passed Duration: 3 minutes and 41 seconds Commit: 8e32455 (nslcd) Author: Bryan Quigley Message: [ldap] Collect nslcd.conf like RH does This collects nslcd.conf and also removes the bindpw from it. Signed-off-by: Bryan Quigley View the changeset: https://github.com/BryanQuigley/sos/compare/dc3f1f851eaf...8e3245573b19 View the full build log and details: https://travis-ci.org/BryanQuigley/sos/builds/352474466?utm_source=email&utm_medium=notification -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications This email was sent to sos-devel at redhat.com (mailto:sos-devel at redhat.com) unsubscribe from this list (http://clicks.travis-ci.com/track/unsub.php?u=14313403&id=163acd68cf9f4183b98eebc8382af808.%2FYqzSCHAsdWln5FGm29T5Bl3oBI%3D&r=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Dsos-devel%2540redhat.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: From builds at travis-ci.org Fri Mar 16 10:07:34 2018 From: builds at travis-ci.org (Travis CI) Date: Fri, 16 Mar 2018 10:07:34 +0000 Subject: [sos-devel] Passed: psachin/sos#52 (doc-patch-1 - f7c73be) In-Reply-To: Message-ID: <5aab9765eb5d6_43f92a159d5d0104005e@564be00b-7d38-433e-afc4-e0b0d2508635.mail> Build Update for psachin/sos ------------------------------------- Build: #52 Status: Passed Duration: 2 minutes and 13 seconds Commit: f7c73be (doc-patch-1) Author: Sachin Patil Message: [docs] Fixed errors while generating docs. I see below errors when generating docs using `make`. Decided to cleanup a bit. The docstring look better than previous and no more errors when generating docs. ``` /home/psachin/github/sos/sos/plugins/__init__.py:docstring of sos.plugins.Plugin.add_journal:5: ERROR: Unexpected indentation. /home/psachin/github/sos/sos/plugins/__init__.py:docstring of sos.plugins.Plugin.add_journal:6: WARNING: Block quote ends without a blank line; unexpected unindent. /home/psachin/github/sos/sos/plugins/__init__.py:docstring of sos.plugins.Plugin.add_journal:13: WARNING: Definition list ends without a blank line; unexpected unindent. /home/psachin/github/sos/sos/plugins/__init__.py:docstring of sos.plugins.Plugin.add_journal:15: ERROR: Unexpected indentation. /home/psachin/github/sos/sos/plugins/__init__.py:docstring of sos.plugins.Plugin.add_journal:16: WARNING: Block quote ends without a blank line; unexpected unindent. /home/psachin/github/sos/sos/plugins/__init__.py:docstring of sos.plugins.Plugin.add_journal:18: WARNING: Definition list ends without a blank line; unexpected unindent. ``` Let me know if anything else needs cleanup in `sos/sos/plugins/__init__.py` Signed-off-by: Sachin Patil View the changeset: https://github.com/psachin/sos/commit/f7c73be6285a View the full build log and details: https://travis-ci.org/psachin/sos/builds/354241913?utm_source=email&utm_medium=notification -- You can configure recipients for build notifications in your .travis.yml file. See https://docs.travis-ci.com/user/notifications This email was sent to sos-devel at redhat.com (mailto:sos-devel at redhat.com) unsubscribe from this list (http://clicks.travis-ci.com/track/unsub.php?u=14313403&id=352482598eb946aeb6844ba8ba00e4e6.%2FYqzSCHAsdWln5FGm29T5Bl3oBI%3D&r=https%3A%2F%2Fmandrillapp.com%2Funsub%3Fmd_email%3Dsos-devel%2540redhat.com) -------------- next part -------------- An HTML attachment was scrubbed... URL: From carl.heymann at netronome.com Fri Mar 23 13:31:23 2018 From: carl.heymann at netronome.com (Carl Heymann) Date: Fri, 23 Mar 2018 15:31:23 +0200 Subject: [sos-devel] question about ethtool dumps In-Reply-To: <7910c6b0-55e3-a831-e104-1478d9445592@netronome.com> References: <7910c6b0-55e3-a831-e104-1478d9445592@netronome.com> Message-ID: Hi, is it currently possible to create ethtool debug dumps with sosreport? E.g. a command such as: ?ethtool -W && ethtool -w data /dev/stdout for all (or some) netdevs. If this is not currently possible, would it be seen as a desirable feature? One might want to exclude dumps if they are larger than some threshold. After setting the flag parameter, the size can be seen (before generating the actual dump output) with e.g.: $ ethtool -W eth0 0 $ ethtool -w eth0 flag: 0, version: 1, length: 8192 Some config might also be useful, to enable such debug dumps for specific PCI vendor IDs, with a set of flags to use. Regards Carl Heymann From bmr at redhat.com Fri Mar 23 13:50:32 2018 From: bmr at redhat.com (Bryn M. Reeves) Date: Fri, 23 Mar 2018 13:50:32 +0000 Subject: [sos-devel] question about ethtool dumps In-Reply-To: References: <7910c6b0-55e3-a831-e104-1478d9445592@netronome.com> Message-ID: <20180323135032.GF13696@localhost.localdomain> On Fri, Mar 23, 2018 at 03:31:23PM +0200, Carl Heymann wrote: > Hi, > > is it currently possible to create ethtool debug dumps with sosreport? E.g. a command such as: > > ?ethtool -W && ethtool -w data /dev/stdout For ethtool commands you can find out what is collected by just running sosreport and then looking in the 'sos_commands/networking' directory in the generated report: # ls sos_commands/networking/ethtool_*wlp3s0 | cat sos_commands/networking/ethtool_-a_wlp3s0 sos_commands/networking/ethtool_-c_wlp3s0 sos_commands/networking/ethtool_-d_wlp3s0 sos_commands/networking/ethtool_-g_wlp3s0 sos_commands/networking/ethtool_-i_wlp3s0 sos_commands/networking/ethtool_-k_wlp3s0 sos_commands/networking/ethtool_-S_wlp3s0 sos_commands/networking/ethtool_-T_wlp3s0 sos_commands/networking/ethtool_wlp3s0 These commands are collected for every interface on the system (I filtered the above list for one NIC just to avoid clutter). We do not currently perform the type of operation you describe: we have a fairly strict policy of not modifying the system that sos is running on and that is communicated to users in the text displayed when sos starts: "The generated archive may contain data considered sensitive and its content should be reviewed by the originating organization before being passed to any third party. No changes will be made to system configuration." The problem with this is that even if we added steps to revert our changes we cannot be certain they will succeed: sos could crash or be killed by the administrator leaving the system in an unknown state (this is especially a problem with tools like abrt, which has a habbit of kill -9ing a running sos at times). > for all (or some) netdevs. > > If this is not currently possible, would it be seen as a desirable feature? It would be preferable if we could request the dump in a somewhat atomic fashion: set the flag, get the dump, clear the flag. I'm inclined at the moment to think that this would belong more in some external network diagnostic tool that sos would then run to collect output. Regards, Bryn.