How long have you run your raspi for?

Simple question - what is the longest uptime anyone has achieved with their raspi?

Having finally cracked the power/wireless issue yesterday, I have set my t'internet facing raspi up to see how long it will go.
As well as running a tiny website on a lighttpd install Its got a 10 second ping to 8.8.8.8 (Google running) thats it - uptime is 20 hours - no hiccups, no WLAN down no anything.
And my plan is it will stay like that until it either dies or needs to be moved .

So who's gone the furthest so far?

done 5 days.. I only restarted it cos I was messing with it.. no hickups

I think it's safe to assume no-one will have an uptime of 6 months yet

I think it's safe to assume no-one will have an uptime of 6 months yet

clearly...
so 5 days it is so far... anyone else?

Mine's been on constantly since I got it on Thursday (2 full days) with no issues, I've been running compiles (for SimH) and also did a RSX-11M Pluss SYSGEN operation inside SimH PDP-11 (roughly analogous to a Kernel compile in Linux) which had the CPU running mostly pegged at 100% for a good hour. No issues so far (knocks on several pieces of wood) - CPU has never got hotter than hot to the touch. Very impressed on the performance-per-Watt front

Set mine up and finished 2 days ago, running smoothly since then

More changes tonight though to organise the dynamicdns etc. but so far only one piece of downtime and couldnt find out what caused it

I haven't had time to tinker with it recently, so it's been sitting with XBMC running on it for about a week now.

Code: Select all

$ uptime
 10:14:45 up 7 days, 3 min,  2 users,  load average: 0.00, 0.01, 0.05


I do experience intermittent lockups though (well, not during the past week I suppose)... I think they may be related to SD card I/O. The lockups happen when I'm writing a lot to the SD card (e.g. compiling, updating software), and after a restart, many of the files that were being written during the crash have size 0. Haven't been able to diagnose further than that. It's an 8GB SD card, not sure what type.

The current uptime on mine is 7 days, but unfortunately I need to reboot it now.

I've been at 10 days before (well 9 days and 22 hours) but I had to reboot as I was rebuilding the Desktop computer that was power the raspi. Right now, I'm back at 3 days after the rebuild.

someone disturbed my pi last week, now back to...
22:13:58 up 2 days, 11:03, 1 user, load average: 0.00, 0.01, 0.05 - http://raspi.stevenicklin.com/cgi-bin/about
Fingers crossed,

Hi there, just my $0.50

Code: Select all

apt-get install uptimed

this also starts up and adds the uptimed daemon.

Code: Select all

uprecords

prints a table to look up your times and records and

Code: Select all

/etc/uptimed.conf

has some self explanatory settings.

Example output looks like this

Code: Select all

     #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
->   1     8 days, 11:52:04 | Linux 3.1.9+              Tue May 29 11:14:37 2012
----------------------------+---------------------------------------------------
NewRec     8 days, 11:52:03 | since                     Tue May 29 11:14:37 2012
    up     8 days, 11:52:04 | since                     Tue May 29 11:14:37 2012
  down     0 days, 00:00:00 | since                     Tue May 29 11:14:37 2012
   %up              100.000 | since                     Tue May 29 11:14:37 2012


Hope this helps in your quests to find out about uptime records

Running 3 day for now. I don't know why but it sometimes freezes and need to be restarted.

As I said above reply it just froze and set my uptime to 0

I think I am going to install Arch instead of Debian because my guess is that my pi freezes because of load and lack of memory. I ended up with this conclusion because it freezes when I start transmission client.

uprecords
# Uptime | System Boot up
----------------------------+---------------------------------------------------
-> 1 5 days, 22:02:45 | Linux 3.1.9+ Thu Jan 1 01:00:00 1970
----------------------------+---------------------------------------------------
NewRec 5 days, 22:02:44 | since Fri Jun 1 11:58:44 2012
up 5 days, 22:02:45 | since Thu Jan 1 01:00:00 1970
down 0 days, 00:00:00 | since Thu Jan 1 01:00:00 1970
%up 100.000 | since Thu Jan 1 01:00:00 1970
^ however my uprecords don't last over a reboot.
this is on latest debian

previous to this it was 4days then it kernel panicked ;-(

My longest so far is ~3.5 days, I leave it on so I can ssh in as well as test the performance of Apache/MySQL/PHP. I just rebooted it a few minutes ago after running an update via pacman and seeing a new kernel version pop in. (For those new to Arch Linux, get used to low uptime numbers; it's a bleeding-edge distro and you'll get kernel updates within hours of upstream commits.)

I'm really enjoying just having my own ~1W tiny web server! I have other, bigger projects in mind but for now I can ssh in from my WP7 phone during downtime at work, play around with HTML, CSS and PHP files, and see the changes in my phone's browser. Nerdy fun of course, but fun all the same!

My pi was running debian smooth for 2 days, then i woke up this morning to find it unresponsive =(.

Upon further investigation it seemed to be caused by a brute force ssh password hack attempt on my poor little pi =( over 10,000 log on attempts made it fall over.

skiddies didn't get in though, anyone else experiencing strange lock-ups might like to check their logs too, /var/log/auth.log

Nice program aXon, thanks

My pi was running debian smooth for 2 days, then i woke up this morning to find it unresponsive =(.

Upon further investigation it seemed to be caused by a brute force ssh password hack attempt on my poor little pi =( over 10,000 log on attempts made it fall over.

skiddies didn't get in though, anyone else experiencing strange lock-ups might like to check their logs too, /var/log/auth.log

Hmmm. . . Just been and checked mine. Still up, 20 days in BUT mine too has been slammed to some extent - all manner of attacks recorded since 17th June, but hanging in there

Hmmm. . . Just been and checked mine. Still up, 20 days in BUT mine too has been slammed to some extent - all manner of attacks recorded since 17th June, but hanging in there

Glad to hear such a long uptime is achievable, my pi is replacing my n900 which used to be a small webserver and ssh proxy for me. so I'm hoping for the same level of reliability (my n900 was solid as a rock, until the usb charging port died)

In the meantime I've moved my ssh onto a non standard port, and emailed a complaint to the owner of the attacking ip =)

Spoke to somebody at work. His Pi has been running for three months now. It replaces an old PC he had as file server and other network stuff. He calculated from the power savings alone it will earn itself back before the year. And no noise!

I have the same problem with uprecords:

Code: Select all

     #               Uptime | System                                     Boot up
----------------------------+---------------------------------------------------
     1     4 days, 03:54:26 | Linux 3.1.9+              Sat Jun 23 18:35:10 2012
->   2     0 days, 13:43:22 | Linux 3.1.9+              Thu Jan  1 01:00:00 1970
----------------------------+---------------------------------------------------
no1 in     3 days, 14:11:05 | at                        Wed Jul  4 00:40:04 2012
    up     4 days, 17:37:48 | since                     Thu Jan  1 01:00:00 1970
  down   15514 days, 02:51: | since                     Thu Jan  1 01:00:00 1970
   %up                0.031 | since                     Thu Jan  1 01:00:00 1970

I'm a bit dissapointed in uprecords

I had my pi running for approx. 3 weeks now.
Yesterday I had to reboot my Fritzbox and I forgot about the pi. So I switched of the fuse instead of trying to find the power adapter for the fritzbox (which is kind of complicated so using the fuse is like 100 times easier).

So pi was down, but now uprecords acts like the pi has never been running before.
Maybe thats due to not shutting it down properly, but anyway that stinks.

New uptime: 16 Hours....

uptimed works fine and as expected on wheezy

Due to an enforced business trip to the us I haven't had three chance to tinker with either of my two pi's but a quick check of Webmin whilst i sit here in the airport at Boston tells me they have been up for 30 days and they are still talking to each other! I'll be playing with them again tomorrow and may get around to posting a note about my current project once I've got it fully running