How long server running

Three others and myself make up the department. We are all aware of the very minimal risks here. I get an email when ever anyone attempts something out of the ordinary.

If you are saying that unix systems are more reliable and can keep working especially in comparison to Windows servers — that is a known fact. Patching is required for security reasons and is one of the most disruptive things you can do to a system — you need to make sure your services will survive a reboot.

I would much rather know that my system will recover when I have time to troubleshoot, rather during a disaster. One of our Unix systems soon to be taken off-line reports a rather incredible uptime. Having said that, we moved offices about three years ago and had to shutdown the server and drive it to the new office where it was started up again…. So I assume my stats simply mean that the server never crashed, but controlled shutdowns and startups were performed during the period of uptime……..

I personally reboot all my servers at least once a week. It makes us wonder WHY Microsoft brags about their reboot count. Full stop. Much like the MS OSes. Much like my daily tasks at work I so consciously try and change. And hopefully you smile with me please and not be angered here, because guess what?

Sanity involves patching and disaster recovery trials and sleeping at night with the knowing not hoping and guessing that a recovery is a couple of clicks away. Sanity also involves funny crazy things like my systems uptime — which infact is longer than yours — so THERE!!! Maybe people are bored with the games we play. What about MS start with uptime and we start to see how many reboots we can get in a day.

See if we can reboot like 6 times over lunch time while nobody got affected? Sometimes life makes no sense, but at least that makes sense, all because of uptime if you know what I mean. When I checked, the boot time was and the uptime command was run at I do know what the problem was, but that is another story.

On the nights like this, when I have been up all night applying patches and updates, I wish I could report longer uptimes so I would not have to sacrifice my down time. But in the end, I think the patching and updates are worth it in the long run. The truth is, I usually use the uptime command to see the load, the other info may be nice, but does not really mean that much to me. You should see something maybe NTP related in your bootlog — that is if you were interested in the time shift.

Such is the life of an active SysAdmin. That would be Awesome!! I have seen uptime of days and not more than…but days is really Oh My God!!!! I have one OpenBSD 4. On the one hand long uptime is good since it shows the stability of the OS, but security threats grow with time so it is wise to ensure systems are protected which of course requires planned downtime.

With the technology available in latest Solaris releases this in practice need take no longer than a reboot. No problems, just you did not update security kernel patches and your system may be hack…. As of today all I want is to make it through Sandy — so far so good, 20 or 30 hours and maybe they will let me go home after they open the roads. Since I switched back to the dark side application support about 15 months ago nothing has been booted or updated But I have 2 managers here?

I guess they can cover the conference calls. Darwin host 7. Darwin host 9. My longest uptime was from a server that has since been decommissioned. Kris Where those the HP line? Amazing hardware. I think so, but they were decommissioned a year or so ago and I do not remember for certain.

My longest uptime was from a Sun server, uptime duration is more than 3 years. Its OS is Solaris 8. Ours was more than 3 years as the server was the Linux and it was meant for transporting displays. As long as a server is doing its job reliably why would it be a bad idea for it to not reboot it every now and then?

But generally the only time I have found that a server really needs to be rebooted is : 1. Linux : after actively swapping I have found that performance degrades slowly and a reboot is generally the only thing that will get that performance back. NOTE: i did not upgrade kernel during of these two years and it is not good! When they thought of migrating systems from that dc the admins were scared on what they might encounter considering the system had not been rebooted for such a long time!

Still going with this older Fedora box. I hate to do it though…. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account.

We'll send a magic link to your inbox. Email Address. All Sign in options. Enter a Email Address. Choose your interests Get the latest news, expert insights and market research, sent straight to your inbox.

Newsletter Topics Select minimum 1 topic. Operating Systems. Anonymous October 12, 0 Comments. Anonymous Posted October 12, 0 Comments. Doug Monroe Posted October 12, 0 Comments. On that note, have you taken your backup tapes to some clean iron, reloaded, and booted lately? Brian Masinick Posted October 12, 0 Comments. Brian Masinick masinick at yahoo dot com. Paul Pedant Posted October 12, 0 Comments. This is second-hand, but… While the millennium bug was the big story, I worked in a start-up company in the Hewlett Packard factory in South Queensferry, Edinburgh.

Andrew Montalvo Posted October 12, 0 Comments. Jack Miller Posted October 12, 0 Comments. NormH83 Posted October 13, 0 Comments. If you cant remove those, definitely you need to reboot. Hope this helps. Ashoka Posted October 13, 0 Comments. Anonymous Posted October 13, 0 Comments. Jaco Bezuidenhout. Do you want to know, how long your Linux system has been running without downtime?

It should be zero downtime because if there is any down time then it will impact badly to millions of users. If you want to collect Linux system uptime reports once a month, see the following bash script.

As we told many commands are available to check server uptime in Linux. In this tutorial we are going teach you how to check this using below 11 methods. The below commands will print how long the system has been running and up. It also shows some additional information.

It gives a one line display of the following information. It is a metric used to denote the performance of a server. Server uptime is monitored and measured by server monitoring tools. Uptime and availability are quite often used interchangeably even though they are not the same thing.

Uptime is the amount of time a server works properly and is expressed in years, months, days, hours, minutes and seconds. However, availability is the percentage of time, in a specific time interval, during which a server can be used for its intended purpose. The SLA defines what the end users should expect in terms of things like system availability, among other details of service delivery.

An SLA is important for a service provider to drive its internal processes by setting clear and measurable performance standards. A server availability SLA specifies the maximum amount of downtime a server can undergo during a certain period of time, such as a year, for example.

According to TechTarget :. When a server is capable of remaining available and functional for a very high percentage of time, it is called a high-availability server.

This type of server is typically used for business-critical applications in an organization.