{"id":13149,"date":"2019-04-01T03:31:05","date_gmt":"2019-04-01T03:31:05","guid":{"rendered":"http:\/\/www.appservgrid.com\/paw92\/?p=13149"},"modified":"2019-04-01T03:31:05","modified_gmt":"2019-04-01T03:31:05","slug":"trouble-maker-breaks-your-linux-machine-and-ask-you-to-fix-broken-linux","status":"publish","type":"post","link":"https:\/\/www.appservgrid.com\/paw92\/index.php\/2019\/04\/01\/trouble-maker-breaks-your-linux-machine-and-ask-you-to-fix-broken-linux\/","title":{"rendered":"Trouble Maker \u2013 Breaks Your Linux Machine and Ask You to Fix Broken Linux"},"content":{"rendered":"

Fixing a broken\u00a0Linux System<\/strong>\u00a0can be a cumbersome job if you don\u2019t have the idea of what exactly is going on. What most of us do when we gets a broken Linux system? Most of us searches the forum and\/or google about the problem. While we hate troubles, how about installing a \u2018Trouble Maker<\/strong>\u2018 application, which essentially creates troubles, gives you hard time and want you to fix broken system.<\/p>\n

This is a nice way of learning to fix a broken Linux System. For this purpose, there is a special\u00a0Linux Distro<\/strong>available called \u2018Damn Vulnerable Linux\u2019\u00a0<\/strong>(DVL<\/strong>), it\u2019s bundled with ill-configured, outdated and exploitable tools which trains administrators to industry standard.<\/p>\n

\n

\"Install<\/a><\/p>\n

Trouble-Maker \u2013 We break it and You fix it<\/p>\n<\/div>\n

However, no any distribution or tool is a replacement for clearly understanding the Linux and experience in dealing with unknown problems. This is where,\u00a0Trouble-Maker<\/strong>\u00a0comes into the picture. With this \u201cTrouble Maker<\/strong>\u201d you can train Yourself on any standard Linux distribution and hence no specific distro is required.<\/p>\n

In fact, you will never underestimate\u00a0DVL<\/strong>\u00a0distribution. The\u00a0DVL<\/strong>\u00a0distro contains a lot of broken applications and bugs whereas \u201cTrouble Maker<\/strong>\u201d, will provide you with\u00a016 different modules<\/strong>.<\/p>\n

Trouble Maker Components<\/h3>\n

Trouble Maker consists of three main components and they are:<\/p>\n

    \n
  1. The\u00a0trouble-engine<\/strong>\u00a0is developed in a cross platform way, so it can run on as many target platforms as feasible .<\/li>\n
  2. The\u00a0trouble-modules<\/strong>\u00a0are developed so as to denote which machines they apply to, and what requirements they have.<\/li>\n
  3. The\u00a0trouble-module-builder<\/strong>\u00a0is an extra module (optional) system designed to clarify packaging trouble-module files into certain modules. Currently not implemented.<\/li>\n<\/ol>\n

    At this time, only\u00a0RedHat Enterprise Linux<\/strong>,\u00a0CentOS<\/strong>,\u00a0Fedora<\/strong>\u00a0and\u00a0SUSE Linux Enterprise Server<\/strong>\u00a0are supported. When you install and run the \u201cTrouble Maker<\/strong>\u201d first time, it will randomly choose a problem from its set of modules and ask you to deal with\u00a0boot problem<\/strong>,\u00a0configuration problem<\/strong>,\u00a0hardware problem<\/strong>\u00a0and\u00a0user reporting problem<\/strong>.<\/p>\n

    It is Strongly recommended not to install \u201cTrouble Maker<\/strong>\u201d on your\u00a0Primary<\/strong>\/Production<\/strong>\u00a0Machine. Better use it on any of the \u2018virtual machine<\/strong>\u2018 in order to remain away from any trouble or data loss.<\/p>\n

    Installation of Trouble-Maker in Linux<\/h3>\n

    The application is a cross\u00ad-platform project and hence don\u2019t come bundled with OS specific files\/application. The project is developed in\u00a0Perl<\/strong>\u00a0programming language. Of course you need\u00a0Perl<\/strong>\u00a0installed on your Linux\u00a0server, before using the application.<\/p>\n

    To install required\u00a0Perl<\/strong>\u00a0modules, you need to install and enable third party\u00a0RPMForge<\/strong>\u00a0repository under your systems. Please use the following article to enable repository.<\/p>\n

    Install and Enable RPMForge Repository in RHEL\/CentOS<\/a><\/p>\n

    Once you\u2019ve enabled\u00a0RPMForge<\/strong>\u00a0repository, you can run the following command to install required\u00a0Perl<\/strong>\u00a0modules.<\/p>\n

    # yum install perl-Archive-Tar perl-YAML<\/pre>\n
    Now, download the latest\u00a0Trouble-Maker<\/strong>\u00a0application using the following download link or you may use the\u00a0wget command<\/strong>\u00a0to download it as shown.<\/p>\n
    http:\/\/sourceforge.net\/projects\/trouble\u00admaker\/files\/<\/a><\/p>\n
    # cd \/tmp\r\n# wget http:\/\/kaz.dl.sourceforge.net\/project\/trouble-maker\/trouble-maker\/0.11\/trouble-maker-0.11.tgz\r\n# cd \/\r\n# tar -zxvf \/tmp\/trouble-maker-0.11.tgz\r\n# \/usr\/local\/trouble-maker\/bin\/trouble-maker.pl --version=RHEL_6<\/pre>\n
    How to Run Trouble-Maker in Linux<\/h3>\n
    The default mode for running\u00a0trouble-maker<\/strong>\u00a0is very easy to use. Simply run the following command with the version flag. For example, on\u00a0RedHat Enterprise Linux 6<\/strong>, run the command as shown.<\/p>\n
    # \/usr\/local\/trouble-maker\/bin\/trouble-maker.pl --version=RHEL_6<\/pre>\n
    To run a specified module.<\/p>\n
    # \/usr\/local\/trouble\u00admaker\/bin\/trouble\u00admaker.pl \u2013version=RHEL_6 \u2013selection=module_name<\/pre>\n
    Trouble-Maker Problem Modules<\/h3>\n
    Having a look at some of the System breaks, arising as a result of running Trouble Maker.<\/p>\n
    1. No GUI! Only command Line<\/h6>\n
    Area to see<\/strong>: Your Runlevel has been modified from 5 to 3 in \/etc\/inittab file.<\/p>\n
    2. User \u2018gdm\u2019 don\u2019t exist<\/h6>\n
    Area to see<\/strong>: Modification in \/etc\/passwd file.<\/p>\n
    3. INIT: No more process in the runlevel<\/h6>\n
    Area to see<\/strong>: Problem with \/etc\/inittab file.<\/p>\n
    4. Switchroot: Mount Failed: No such file or directory<\/h6>\n
    Area to see<\/strong>: Location of root partition is modified. You need to change \/boot\/grub\/grub.conf<\/p>\n
    5. Can\u2019t log in as root<\/h6>\n
    Area to see<\/strong>: You need to check file \/etc\/pam.d\/login file.<\/p>\n
    6. initrd file not found<\/h6>\n
    Area to see<\/strong>: correct \/boot\/grub\/grub.conf<\/p>\n
    7. Network is not working<\/h6>\n
    Area to see<\/strong>: You have to see at number of places. Check if \u2018ifconfig\u2019 command is working or not followed by looking into the file \/etc\/sysconfig\/network file.<\/p>\n
    8. Log in to root denied, in console<\/h6>\n
    Area to see<\/strong>: check \/etc\/pam.d\/login file and \/etc\/security file and correct either or both of them.<\/p>\n
    9. FTP is not working<\/h6>\n
    Area to see<\/strong>: check for errors in the ftp configuration file, \/etc\/hosts.allow and \/etc\/hosts.deny.<\/p>\n
    10. SSH not working<\/h6>\n
    Area to see<\/strong>: Fix SSH configuration file.<\/p>\n
    Conclusion<\/h3>\n
    I already describe\u00a010 modules<\/strong>\u00a0above, out of\u00a016 modules<\/strong>\u00a0of trouble maker, and leaving remaining\u00a06 modules<\/strong>\u00a0for you to explore. To be true\u00a01 module<\/strong>\u00a0is dummy hence you are left with\u00a05 modules<\/strong>\u00a0to explore and a total of\u00a015 modules<\/strong>\u00a0and\u00a01 dummy module<\/strong>\u00a0available in \u2018Trouble Maker\u2019<\/strong>. Run the program at your own risk. We are not responsible for any damage to your\u00a0System<\/strong>\/Server<\/strong>.<\/p>\n
    Reference Links<\/h3>\n
      \n
    1. Product\u2019s Homepage<\/a><\/li>\n
    2. Product\u2019s Documentation<\/a><\/li>\n<\/ol>\n
      Hope you people would love the writing and tell us about your experience with \u2018Trouble Maker\u2019<\/strong>. That\u2019s all for now and don\u2019t forget to provide us with your valuable feedback in the comment section.<\/p>\n
      Source<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
      Fixing a broken\u00a0Linux System\u00a0can be a cumbersome job if you don\u2019t have the idea of what exactly is going on. What most of us do when we gets a broken Linux system? Most of us searches the forum and\/or google about the problem. While we hate troubles, how about installing a \u2018Trouble Maker\u2018 application, which … <\/p>\n
      Continue reading “Trouble Maker \u2013 Breaks Your Linux Machine and Ask You to Fix Broken Linux”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-13149","post","type-post","status-publish","format-standard","hentry","category-linux"],"_links":{"self":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/13149","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/comments?post=13149"}],"version-history":[{"count":1,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/13149\/revisions"}],"predecessor-version":[{"id":13150,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/posts\/13149\/revisions\/13150"}],"wp:attachment":[{"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/media?parent=13149"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/categories?post=13149"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.appservgrid.com\/paw92\/index.php\/wp-json\/wp\/v2\/tags?post=13149"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}