||Home||Switchboard||Unix Administration||Red Hat||TCP/IP Networks||Neoliberalism||Toxic Managers|
|(slightly skeptical) Educational society promoting "Back to basics" movement against IT overcomplexity and bastardization of classic Unix|
|Recommended Books||Recommended Links||Installation Checklist||Reference|
This is RHEL abandonware that used to be supported from version 4.5 to 5.0. Now migrated to Fedora project to die a slow death....
Red Hat Linux Manuals - Sysreport
Sysreport is a system utility created to collect important system data, in order to assist the Red Hat Technical Support and Development Teams in solving customer problems. Sysreport gathers as much system information as is possible, while avoiding certain actions: the creation of a very large file; the invasion of the user's privacy; and the collection of information that could be detrimental to the integrity of the system.
To start Sysreport, you must be logged in as root. As root, at a shell prompt type the command sysreport.
You will then see the following message:This utility will go through and collect some detailed information about the hardware and setup of your Red Hat Linux system. This information will be used to diagnose problems with your system, and will be considered confidential information. Red Hat will use this information for diagnostic purposes ONLY. Please wait while we collect information about your system. This process may take awhile to complete.... No changes will be made to your system during this process. NOTE: You can safely ignore a failed message.This only means a file we were checking for did not exist. Press ENTER to continue, or CTRL-C to quit.
As the message says, ignore any failed messages. Sysreport checks for all possible Red Hat Linux system packages. If you do not have every Red Hat Linux package installed, you will see failed messages.
After pressing [Enter], Sysreport will gather information about your system's configuration. When it is finished, you will see the following message:Enter your first initial and last name with no spaces (example: jsmith):
Enter the information requested, and press
[Enter]. Sysreport will place a compressed TAR file in the /tmp directory beginning with the initial and last name you just entered. You will see a message telling you to email this file to the Red Hat support team. However, even if you do not need support, you can use this information to back up most of your system's configuration.
Use the command tar ztvf filename with the name of the compressed TAR file that you created to display a list of its contents.
checksysreport performs some automatic tests against a directory containing an untarred Red Hat Enterprise Linux sysreport.
checksysreport project can perform some automatic tests against a directory containing an untarred Red Hat Enterprise Linux sysreport.
You will need a valid Red Hat Network login in order to use it, as it fetches information from RHN using the RHN API (see https://rhn.redhat.com/rpc/api/).
A graphical tool , yadarh, is also included: it uses the cache generated by checksysreport to display RPMs in a given channel and lets you browse them to have a list of errata and new entries in changelogs that come with other versions of the same package.
What's New in This Release: [ read full changelog ]
∑ coping with funny lsmod output.
∑ telling explicitely there's something wrong with installed-rpms
∑ when dying because it cannot be parsed.
∑ checksysreport_wrapper.py now use mandatory plugins if any are set.
∑ Fix some issues where 'package_release' can not be converted from
∑ ascii to unicode. Thanks to Niels de Vos.
∑ RHEL6′sosreport are supported \o/
∑ RHEL3 base channel changed to ELS channels in yadarh.
∑ using pgdb instead of _pg so there s no need to escape sql sentences.
∑ Both checksysreport server and client are now only supported on RHEL6.
∑ download_rhn_package rename downloaded file without long url extension.
∑ plugin's "package" hook is ran even when the current installed package
∑ version/release does not exist in the current channel.
∑ configuration setting can end up with a space.
Sysreport is a utility that gathers information about a system's hardware and configuration. The information can then be used for diagnostic purposes and debugging. Sysreport is commonly used to help support technicians and developers by providing a "snapshot" of a system's current layout.
It is part of Fedora Core. A new version is under active development at https://sos.108.redhat.com/
What is a sysreport and how do I run it in Red Hat Enterprise Linux - Red Hat Customer Portal
29 Oct 2009
The support tech I was working with asked me to run a sysreport, what is a sysreport and how do I run it?
Red Hat Enterprise Linux 4.5 and earlier, Red Hat Enterprise Linux 5.0 (not in later releases of RHEL 5)
"sysreport" is a script that collects information about a system, such as what kernel is running, what drivers are loaded, and various configuration files for common services. It has been depreciated in favor of the new and improved sosreport.
To run a sysreport you will first need to have the sysreport package installed. If you have registered the system with Red Hat Network (RHN) it can be installed using up2date command for Red Hat Enterprise Linux 4:# up2date sysreport
If you do not have your system registered with RHN, you can install the sysreport package from your CDs using RPM:# rpm -Uvh sysreport-<version>.<arch>.rpm
Once the package has been installed, issue the following command as root user:# sysreport
Once completed, sysreport will generate a compressed tar file in /tmp. Provide this file to your support representative.
WARNING: During the running of the command sysreport you will be prompted for your name and/or case number, use ONLY letters and/or numbers when filling out this field. Adding other characters could damage the system or render the sysreport unusable!
Google matched content
Sysreport 1.4.4 - Fedora Core 9 RPM
Linux_explorer --Well written in shell alternative script to consider:
Groupthink : Two Party System as Polyarchy : Corruption of Regulators : Bureaucracies : Understanding Micromanagers and Control Freaks : Toxic Managers : Harvard Mafia : Diplomatic Communication : Surviving a Bad Performance Review : Insufficient Retirement Funds as Immanent Problem of Neoliberal Regime : PseudoScience : Who Rules America : Neoliberalism : The Iron Law of Oligarchy : Libertarian Philosophy
War and Peace : Skeptical Finance : John Kenneth Galbraith :Talleyrand : Oscar Wilde : Otto Von Bismarck : Keynes : George Carlin : Skeptics : Propaganda : SE quotes : Language Design and Programming Quotes : Random IT-related quotes : Somerset Maugham : Marcus Aurelius : Kurt Vonnegut : Eric Hoffer : Winston Churchill : Napoleon Bonaparte : Ambrose Bierce : Bernard Shaw : Mark Twain Quotes
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient markets hypothesis : Political Skeptic Bulletin, 2013 : Unemployment Bulletin, 2010 : Vol 23, No.10 (October, 2011) An observation about corporate security departments : Slightly Skeptical Euromaydan Chronicles, June 2014 : Greenspan legacy bulletin, 2008 : Vol 25, No.10 (October, 2013) Cryptolocker Trojan (Win32/Crilock.A) : Vol 25, No.08 (August, 2013) Cloud providers as intelligence collection hubs : Financial Humor Bulletin, 2010 : Inequality Bulletin, 2009 : Financial Humor Bulletin, 2008 : Copyleft Problems Bulletin, 2004 : Financial Humor Bulletin, 2011 : Energy Bulletin, 2010 : Malware Protection Bulletin, 2010 : Vol 26, No.1 (January, 2013) Object-Oriented Cult : Political Skeptic Bulletin, 2011 : Vol 23, No.11 (November, 2011) Softpanorama classification of sysadmin horror stories : Vol 25, No.05 (May, 2013) Corporate bullshit as a communication method : Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
Fifty glorious years (1950-2000): the triumph of the US computer engineering : Donald Knuth : TAoCP and its Influence of Computer Science : Richard Stallman : Linus Torvalds : Larry Wall : John K. Ousterhout : CTSS : Multix OS Unix History : Unix shell history : VI editor : History of pipes concept : Solaris : MS DOS : Programming Languages History : PL/1 : Simula 67 : C : History of GCC development : Scripting Languages : Perl history : OS History : Mail : DNS : SSH : CPU Instruction Sets : SPARC systems 1987-2006 : Norton Commander : Norton Utilities : Norton Ghost : Frontpage history : Malware Defense History : GNU Screen : OSS early history
The Peter Principle : Parkinson Law : 1984 : The Mythical Man-Month : How to Solve It by George Polya : The Art of Computer Programming : The Elements of Programming Style : The Unix Haterís Handbook : The Jargon file : The True Believer : Programming Pearls : The Good Soldier Svejk : The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society : Ten Commandments of the IT Slackers Society : Computer Humor Collection : BSD Logo Story : The Cuckoo's Egg : IT Slang : C++ Humor : ARE YOU A BBS ADDICT? : The Perl Purity Test : Object oriented programmers of all nations : Financial Humor : Financial Humor Bulletin, 2008 : Financial Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related Humor : Programming Language Humor : Goldman Sachs related humor : Greenspan humor : C Humor : Scripting Humor : Real Programmers Humor : Web Humor : GPL-related Humor : OFM Humor : Politically Incorrect Humor : IDS Humor : "Linux Sucks" Humor : Russian Musical Humor : Best Russian Programmer Humor : Microsoft plans to buy Catholic Church : Richard Stallman Related Humor : Admin Humor : Perl-related Humor : Linus Torvalds Related humor : PseudoScience Related Humor : Networking Humor : Shell Humor : Financial Humor Bulletin, 2011 : Financial Humor Bulletin, 2012 : Financial Humor Bulletin, 2013 : Java Humor : Software Engineering Humor : Sun Solaris Related Humor : Education Humor : IBM Humor : Assembler-related Humor : VIM Humor : Computer Viruses Humor : Bright tomorrow is rescheduled to a day after tomorrow : Classic Computer Humor
The Last but not Least Technology is dominated by two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt. Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP) without any remuneration. This document is an industrial compilation designed and created exclusively for educational use and is distributed under the Softpanorama Content License. Original materials copyright belong to respective owners. Quotes are made for educational purposes only in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains copyrighted material the use of which has not always been specifically authorized by the copyright owner. We are making such material available to advance understanding of computer science, IT technology, economic, scientific, and social issues. We believe this constitutes a 'fair use' of any such copyrighted material as provided by section 107 of the US Copyright Law according to which such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free) site written by people for whom English is not a native language. Grammar and spelling errors should be expected. The site contain some broken links as it develops like a living tree...
|You can use PayPal to to buy a cup of coffee for authors of this site|
Last modified: March, 29, 2020