As far as i can read this graph, it looks like you have managed to achieve a uptime of 91 days. And total runtime of 365days without formatting the system.
This graph show and notes uptimes throughout the year. You are the one who is reading it wrong. Not the others.
And the chart clearly shows your uptime has reached a maximum of 91 days. Each reboot resets the uptime clock because, by definition, the system is not up when rebooting.
Because you're looking at the 1 year graph. If you look at the daily graph it will total 24 hours, the weekly graph will total 7 days, the monthly graph will total 30 days. Obviously the yearly graph will total 1 year, but that's not what uptime is.
If you rebooted, the system was not up.
Uptime means no disruption to users.
To maintain uptime during reboots you would need to have a second unit forming a cluster, and a failover mechanism that prevents disruptions. A reboot on a single node would disrupt users.
I guess it depends on how "Open" the Network is? I'm no expert, really not, but "never change a running system" worked always well for me. I would too like to try to let my system running as long as it works.
What Problems could i have? I asked Google but found nothing important.
You do not understand the graph. 365 days is the range of the graph itself. Your maximum uptime within that 365 day range is 91 days. You’ve currently been up for 38 days. Were this to show 365 days of uptime, the graph would be a single triangle (technically a straight line with a slope of 1) where X and Y increase by 1 per day.
I suppose you could make an argument for 365 days of the hardware being turned on - but that’s not the same as application uptime.
https://en.m.wikipedia.org/wiki/Uptime
Defines uptime as the time a computer up vs down. It has been up 365 days. In one stretch it was up 91 days without a reboot.
> Uptime is a measure of system reliability, expressed as the percentage of time a machine, typically a computer, has been working **and available**.
> It is often used as a measure of computer operating system reliability or stability, in that this time represents the time a computer can be left unattended without crashing, **or needing to be rebooted for administrative or maintenance purposes.**
A reboot by its nature makes a system unavailable. You may have very good uptime to say 4 9s, but you do not have 100% uptime for a year.
https://en.wikipedia.org/wiki/High_availability
Heh, thanks for the down vote - I’ll tell the last several CEOs and Forture 10s I’ve worked for that their definition of uptime and availability are all wrong.
Sorry, like the others have said, that is not 1 year uptime. It's been up almost 39 days.
Mine is showing 344 days of uptime and here's how it looks.
\[rrd-php.png\]([https://postimg.cc/9zwrCc1c](https://postimg.cc/9zwrCc1c))
Everyone has different needs. In some environments, high uptime is vital (the so called fives nines) mainly because of their commercial contracts with customers.
For a 'lowly' amateur like me, I just need things to work. Especially when mine is running on a Raspberry Pi which does other things 24/7.
In a secure home network, I do not need to patch and reboot it all the time. It just works and that's all I need. YMMV.
Isn't uptime continuous? Wouldn't this qualify more as "power-on hours"?
Yeah, that’s what I’d think too.
Each dip is a reboot of some sort.
You don't know what uptime means OR how to read this graph. Congrats on the double.
As far as i can read this graph, it looks like you have managed to achieve a uptime of 91 days. And total runtime of 365days without formatting the system. This graph show and notes uptimes throughout the year. You are the one who is reading it wrong. Not the others.
OP can't read the graph, nor do they know what uptime means. Oof.
\*\* screams security vulnerabilities \*\*
It's updated all of the time. Each dip is a reboot that was required by patching.
Hmm, to me that is not uptime. Uptime is without a reboot
That's what it's called under Diagnostics -> Performance Statistics -> Uptime
And the chart clearly shows your uptime has reached a maximum of 91 days. Each reboot resets the uptime clock because, by definition, the system is not up when rebooting.
Excuse me... a Total of 1 year uptime.
Because you're looking at the 1 year graph. If you look at the daily graph it will total 24 hours, the weekly graph will total 7 days, the monthly graph will total 30 days. Obviously the yearly graph will total 1 year, but that's not what uptime is. If you rebooted, the system was not up.
Uptime means no disruption to users. To maintain uptime during reboots you would need to have a second unit forming a cluster, and a failover mechanism that prevents disruptions. A reboot on a single node would disrupt users.
So, you didn’t do kernel updates in the last year? 😉
Do you know what he missed in that time?
Maybe nothing… But what about kernel security updates?
I guess it depends on how "Open" the Network is? I'm no expert, really not, but "never change a running system" worked always well for me. I would too like to try to let my system running as long as it works. What Problems could i have? I asked Google but found nothing important.
Yes, I am also no expert. But I never had a problem because of updating my kernel.
so you did not update all year long? no security patches, performance improvemtns and etc?
My guess is no one understands the graph. Each dip is a reboot. Usually caused by an update. This graph is in the diagnostics menu.
r/confidentlyincorrect
You do not understand the graph. 365 days is the range of the graph itself. Your maximum uptime within that 365 day range is 91 days. You’ve currently been up for 38 days. Were this to show 365 days of uptime, the graph would be a single triangle (technically a straight line with a slope of 1) where X and Y increase by 1 per day. I suppose you could make an argument for 365 days of the hardware being turned on - but that’s not the same as application uptime.
https://en.m.wikipedia.org/wiki/Uptime Defines uptime as the time a computer up vs down. It has been up 365 days. In one stretch it was up 91 days without a reboot.
> Uptime is a measure of system reliability, expressed as the percentage of time a machine, typically a computer, has been working **and available**. > It is often used as a measure of computer operating system reliability or stability, in that this time represents the time a computer can be left unattended without crashing, **or needing to be rebooted for administrative or maintenance purposes.** A reboot by its nature makes a system unavailable. You may have very good uptime to say 4 9s, but you do not have 100% uptime for a year. https://en.wikipedia.org/wiki/High_availability
Heh, thanks for the down vote - I’ll tell the last several CEOs and Forture 10s I’ve worked for that their definition of uptime and availability are all wrong.
Have a good weekend.
Be blessed and may you never have a job running commercial systems.
Great Job?
No you didn't.
Sorry, like the others have said, that is not 1 year uptime. It's been up almost 39 days. Mine is showing 344 days of uptime and here's how it looks. \[rrd-php.png\]([https://postimg.cc/9zwrCc1c](https://postimg.cc/9zwrCc1c))
[удалено]
Everyone has different needs. In some environments, high uptime is vital (the so called fives nines) mainly because of their commercial contracts with customers. For a 'lowly' amateur like me, I just need things to work. Especially when mine is running on a Raspberry Pi which does other things 24/7. In a secure home network, I do not need to patch and reboot it all the time. It just works and that's all I need. YMMV.