Using Samba Robert Eckstein, David Collier-Brown, Peter Kelly 1st Edition November 1999 1-56592-449-5, Order Number: 4495 416 pages, $34.95 Chapter 9...
This question has been answered
Question

Unit 5 Assignment: Troubleshooting an Infrastructure Service                 

No matter how good the operating system is there are going to be times when the services that the infrastructure depends upon like Networking, DHCP, DNS. Apache web server and the other vital services just stop working for various reasons. It these times that administrators want to pull their hair out.

This course has asked you to do some research on the how these vital services work and to make sure they continue to work every day. This assignment will look at when these things do not work effectively and to discover how resolve these issues.

Directions: For this assignment, you will be asked to choose a Linux Infrastructure service and write a step by step troubleshooting guide to resolve potential issues with your service. The requirement is that you should include as part of your research how to use the log files to help in this troubleshooting of your service. You will visit https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-site-issues-on-a-linux-server (Links to an external site.) and compile a handout of methods of troubleshooting applications.

Write a one-page report in the form of a handout in which you describe the steps that you would use to troubleshoot your service. You may need to search the public web using a search engine like Google or Bing to find description of the commands. Cite any sources you use in APA format; this includes sources for any screenshots that are not your own.

Additional Resources

  • Troubleshooting Common Apache Issueshttps://www.linode.com/docs/troubleshooting/troubleshooting-common-apache-issues (Links to an external site.)
  • Troubleshooting Sambahttp://www.oreilly.com/openbook/samba/book/ch09_01.html (Links to an external site.)
  • Linux Networking Troubleshootinghttp://unix.stackexchange.com/questions/50098/linux-network-troubleshooting-and-debugging (Links to an external site.)


4 Attachments
Using Samba Robert Eckstein, David Collier-Brown, Peter Kelly 1st Edition November 1999 1-56592-449-5, Order Number: 4495 416 pages, $34.95 Chapter 9 9. Troubleshooting Samba Contents: The Tool Bag The Fault Tree Extra Resources Samba is extremely robust. Once you've got everything set up the way you want, you'll probably forget that it is running. When trouble occurs, it's typically during installation or when you're trying to add something new to the server. Fortunately, there are a wide variety of resources that you can use to diagnose these troubles. While we can't describe in detail the solution to every problem that you might encounter, you should be able to get a good start at a resolution by following the advice given in this chapter. The first section of the chapter lists the tool bag, a collection of tools available for troubleshooting Samba; the second section is a detailed how-to, and the last section lists extra resources you may need to track down particularly stubborn problems. 9.1 The Tool Bag Sometimes Unix seems to be made up of a handful of applications and tools. There are tools to troubleshoot tools. And of course, there are several ways to accomplish the same task. When you are trying to solve a problem related to Samba, a good plan of attack is to check the following: 1. Samba logs 2. Fault tree 3. Unix utilities 4. Samba test utilities 5. Documentation and FAQs
Background image of page 1
6. Searchable archives 7. Samba newsgroups Let's go over each of these one by one in the following sections. 9.1.1 Samba Logs Your first line of attack should always be to check the log files. The Samba log files can help diagnose the vast majority of the problems that beginning to intermediate Samba administrators are likely to face. Samba is quite flexible when it comes to logging. You can set up the server to log as little or as much as you want. Substitution variables that allow you to isolate individual logs for each machine, share, or combination thereof. By default, logs are placed in samba_directory /var/smbd.log and samba_directory /var/nmbd.log , where samba_directory is the location where Samba was installed (typically, /usr/local/samba ). As we mentioned in Chapter 4, Disk Shares , you can override the location and name using the log file configuration option in smb.conf . This option accepts all of the substitution variables mentioned in Chapter 2, Installing Samba on a Unix System , so you could easily have the server keep a separate log for each connecting client by specifying the following in the [global] section of smb.conf : log file = %m.log Alternatively, you can specify a log directory to use with the -l flag on the command line. For example: smbd -l /usr/local/var/samba Another useful trick is to have the server keep a log for each service (share) that is offered, especially if you suspect a particular share is causing trouble. Use the %S variable to set this up in the [global] section of the configuration file: log file = %S.log 9.1.1.1 Log levels The level of logging that Samba uses can be set in the smb.conf file using the global log level or debug level option; they are equivalent. The logging level is an integer which ranges from 0 (no logging), and increases the logging to voluminous by log level = 3 . For example, let's assume that we are going to use a Windows client to browse a directory on a Samba server. For a small amount of log information, you can use log level = 1 , which instructs Samba to show only cursory information, in this case only the connection itself: 105/25/98 22:02:11 server (192.168.236.86) connect to service public as user pcguest (uid=503,gid=100) (pid 3377) Higher debug levels produce more detailed information. Usually you won't need any more than level 3; this is more than adequate for most Samba administrators. Levels above 3 are for use by the developers and dump enormous amounts of cryptic information. Here is example output at levels 2 and 3 for the same operation. Don't worry if you don't understand the intricacies of an SMB connection; the point is simply to show you what types of information are shown at the different logging levels: /* Level 2 */ Got SIGHUP
Background image of page 2

End of preview

Contents Share Twitter Facebook Google+ Hacker News Share Twitter Facebook Google+ Hacker News × Sign up for our newsletter. Get the latest tutorials on SysAdmin and open source topics. Sign Up Thanks for signing up! Sign Up Log In submit Tutorials Questions Projects Meetups Main Site DigitalOcean Community Menu Tutorials Questions Projects Meetups Main Site Sign Up Log In
Background image of page 01
submit View All Results By: Justin Ellingwood Subscribe Subscribed Share Contents Contents We hope you find this tutorial helpful. In addition to guides like this one, we provide simple cloud infrastructure for developers. Learn more → 11 How To Troubleshoot Common Site Issues on a Linux Server Posted May 9, 2014 83k views Linux Basics Apache Nginx Introduction Everyone has problems with their web server or site at one time or another. Learning where to look when you come across a problem and which components are the likely culprits will help you fix these problems quickly with less frustration. In this guide, we'll be discuss how to troubleshoot these issues so that you can get your site up and running like normal. What Types of Problems are Typical? While occasionally some issues that might arise that are atypical, the vast majority of problems that you'll encounter when trying to get your site up and running fall into a very predictable spectrum. We will go over these in more depth in the sections below, but for now, here's a simple checklist of items to look into: Is your web server installed? Is the web server running? Is the syntax of your web server configuration files correct? Are the ports you configured open (not blocked by a firewall)? Are your DNS settings directing you to the correct place? Does the document root point to the location of your files? Is your web server serving the correct index files? Are the permissions and ownership of the file and directory structures correct? Are you restricting access through your configuration files? If you have a database backend, is it running?
Background image of page 02

End of preview

Background image of page 1
Toggle navigation Features Pricing Add-ons Resources Getting Started Migrating to Linode Hosting a Website Guides & Tutorials API StackScripts Mobile CLI Chat Community Forum Blog System Status Speed Test About Us Contact Support | Log in Sign up Sign up 1. Guides & Tutorials 2. Troubleshooting 3. Troubleshooting Common Apache Issues Troubleshooting Common Apache Issues Updated Thursday, August 1st, 2013 by Linode Use promo code DOCS10 for $10 Credit on a new account. Try this Guide Contribute on GitHub View Project | View File | Edit File This article provides troubleshooting guidelines for the Apache web server . Apache is a highly customizable tool for serving HTTP traffic. Because it allows for so many different configurations and settings in so many different places, sometimes Apache configuration can befuddle even advanced users. In this guide, you’ll start with some basic troubleshooting steps and then proceed to more advanced techniques that can help you untangle conflicting directives. We recommend starting at the beginning of this guide and going through it in order. By the time you’re done, you should be able to debug your
Background image of page 1
Apache installation. Is Apache Running? First, check whether Apache is running. Follow the process in this Troubleshooting Guide . If it isn’t, go ahead and restart Apache, as explained in the next section. You may also want to investigate the possibility of memory issues , if Apache is stopping unexpectedly. Restarting Apache Even if Apache is running, it can be useful to restart the server. This will let you read the Apache startup message. If you get an error, you can use the text of the error in an online search to help you find more details and solutions. Restarting the server may produce several seconds of downtime. Debian and Ubuntu: 1 sudo service apache2 restart Fedora and CentOS: 1 sudo service httpd restart You can use one of the following three commands instead, depending on your Linux distribution: 1 2 3 4 5 /etc/init.d/httpd restart /etc/init.d/apache2 restart /etc/rc.d/httpd restart Reloading Apache Restarting or reloading Apache is also useful if you’ve recently made changes to your server, but they don’t seem to be taking effect. This is true for changes made directly in the Apache configuration files, as well as for changes you’ve made to the configuration for a dynamic language like mod_python , mod_rails (for example, Phusion Passenger, or mod_rack ), mod_ruby , etc. These interfaces cache code internally, and do not reread scripts on new requests. Reloading makes Apache reread its configuration files and incorporate the changes without a full restart, which avoids web server downtime. To reload Apache’s configuration, run the following command: Debian and Ubuntu: 1 /etc/init.d/apache2 reload Fedora and CentOS: 1 /etc/init.d/httpd reload
Background image of page 2

End of preview

Answered by Expert Tutors

ng eli

risus ante, dapibus a molestie consequat, ultrices ac magna. Fusce dui lectus, congue vel laoreet ac, dictum vitae odio. Donec aliquet. Lorem ipsum dolor sit amet, consectetur adipiscing elit. Nam lacinia pulvinar tortor nec facilisis. Pellentesque dapibus efficitur laoreet. Nam risus ante, dapibus a molestie consequat, ul
1 Attachment
Troubleshooting an Infrastructure Service.docx
docx
The student who asked this rated it
Get unstuck

445,696 students got unstuck by Course
Hero in the last week

step by step solutions

Our Expert Tutors provide step by step solutions to help you excel in your courses