![]() The time errors occur or when they were fixed can assist some techs. For illustration, if Bill reinstalled the NIS services because they repeatedly locked up, then Casey knows that another reinstallation will not fix the same issue that is occurring the next day. Knowing why a particular software or hardware is being updated, repaired, and so on, may help narrow down future issue origins when finding the source of an error. Also, if the reason techs are checking the server is because of reports of Samba issues, then the Samba services probably need to be completely reinstalled (remove /usr/local/samba and run pkg_add -r samba35). If there is a network connection issue and the Ethernet devices have already been replaced a few times, then it may be safe to assume the problem lies somewhere else. IT techs may find it helpful to keep track of what other techs are fixing. If the server always tends to break after Andrew makes changes to the server, it may be best to investigate the issue. If Bill, the IT tech, was the last one to fix it, it may be best to have Bill check the issue again since he is familiar with it or to ask Bill for suggestions. Assume the server is having errors with the NTP services again. This helps keep track of all who may be aware of an error. ![]() It helps to keep a written record of all IT techs that have dealt with the server. This log should include a list of all files changed, software installed, and hardware repaired along with answers to the following questions – who, what, why, when, where, and how. It is best to keep a physical log in the server room or some other secure storage location. If the server has problems booting up, the network’s or company’s performance may suffer. It is important to occasionally browse the output of the dmesg command, because sometimes errors may start occurring with the hardware or boot-up process. When searching for entries concerning the USB system, for instance, try the below command. This command will allow the administrator to scroll through the boot messages. The command below displays the contents of /var/run/dmesg.boot. There is a command specifically for viewing the boot-up log seen below. A server maintainer may use a command like the above to search the boot-up logs for lines containing the word “Ethernet” when there appears to be an Ethernet issue. ![]() Grep SOME_ISSUE_TO_SEARCH /var/log/httpd-error.logįor example, when searching for a connection error, search for words like “connection”, “failed”, “404” (HTTP connection error number), and other similar terms. If the HTTP services are having specific issues and the IT tech does not want to spend a lot of time searching through the Apache log, then the tech can do a specific search like below. If a log cannot be found, check in Root’s home folder or read the application’s manual for the log location. Some applications (rarely) store logs in the current user’s home folder. For example, the Samba log would be /var/log/smb.log. The logs are given names that easily identify their content or purpose. When an error is spotted, the administrator should take the time to investigate and prevent future disasters. Most applications/services have a log that lists the software’s status and errors. ![]() Thankfully, many servers have a log system. When maintaining a server, it is best to prevent issues before problems arise. I am using FreeBSD v9.1 for my descriptions and examples, but this article is valid for any BSD distro and many Linux/Unix operating systems. When dealing with servers, the two most important directories that all administrators should thoroughly understand and learn are /etc/ and /var/. Clearly, it is important to keep the servers healthy and the data safe and secure. If the data is lost, this means the company loses more profits. This means that the company loses money until the server is back online. Also, if the server is used to host a website that sells products, customers cannot make purchases until the server is fixed. If the server(s) goes down, a part of or the entire company is unable to continue or perform well until the server is back up. Many server administrators may understand how to set up a FreeBSD server, but once it is up, can they keep it running? Many companies may store business transactions on servers like stock lists and item prices. Many sites and handbooks explain how to install servers, but once a server is running, can an administrator keep it that way? This article will cover the basics of maintaining a BSD server.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |