search for: uptimes

I came in this morning to find all the servers all locked up solid: # passenger-status ----------- General information ----------- max = 20 count = 20 active = 20 inactive = 0 Waiting on global queue: 236 ----------- Domains ----------- /etc/puppet/rack: PID: 2720 Sessions: 1 Processed: 939 Uptime: 9h 22m 18s PID: 1615 Sessions: 1 Processed: 947 Uptime: 9h 23m

Now this is what I call uptime... minipbx*CLI> show uptime System uptime: 41 years, 7 weeks, 6 days, 3 hours, 26 minutes, 46 seconds Last reload: 8 hours, 3 minutes, 51 seconds Bizarre bug? root at minipbx:~# asterisk -V Asterisk 1.4.37 root at minipbx:~# uname -a Linux minipbx 2.6.32-dockstar #2 Thu Nov 25 18:03:25 UTC 2010 armv5tel GNU/Linux root at minipbx:~# uptime 03:29:27 up 5 days,

Hi, I just upgraded from 1.2 to 1.4. In 1.2, when I did a "show uptime" I used to see a second line telling me the time since the last reload. Has this been removed in 1.4? The following is the output of my two test boxes: Connected to Asterisk 1.4.18.1 currently running on voip2 (pid = 10605) Verbosity is at least 3 voip2*CLI> show uptime System uptime: 15 hours, 55 seconds

Package: xen Version: 4.0.1-2 Severity: normal /proc/uptime shows idle bigger than uptime: dom0: % cat /proc/uptime 518389.91 944378.70 % one domU: % cat /proc/uptime 417536.22 764826.15 % another domU: % cat /proc/uptime 426960.17 795800.89 % This is normal on multicore / ht cpu, but this is old amd: % lscpu Architecture: i686 CPU(s): 1 Thread(s) per core: 1

Hi, We can give multiple domains to the following commands. But, the help messages of the commands are explained to be able to give a single domain. # xm vcpu-list vm1 vm2 Name ID VCPU CPU State Time(s) CPU Affinity vm1 1 0 0 r-- 1409.3 any cpu vm2 2 0 0 r-- 1255.8

...are still stable and have no problems, also top shows no zombie processes or such, but maybe it's better for the hardware (like ext3 disk checks f.e.) to reboot every six months... btw this uptime really confirms me how stable Centos 4.x really is and so I wonder how long some people's uptimes on the list are ;) rmc -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.centos.org/pipermail/centos/attachments/20070213/91da37ae/attachment.html>

Working on the Dell R420 today, got most of it working, even the broadcom ethernet cards! However, I get the following when I reboot the system: Syncing disks, vnodes remaining...4 Sleeping thread (tid 100107, pid 9) owns a non-sleepable lock KDB: stack backtrace of thread 100107: sched_switch() at sched_switch+0x19f mi_switch() at mi_switch+0x208 sleepq_switch() at sleepq_switch+0xfc

On Mon, June 15, 2015 11:16 am, Pete Geenhuizen wrote: > Enable it in /usr/share/logwatch/default.conf/services/zz-runtime.conf Thanks a lot! Helps you to be aware that you definitely missed something important if you haven't the box rebooted during more than 45-60 days... Valeri > > Pete > > On 06/15/15 09:58, James B. Byrne wrote: >> CentOS-6.6 >> >> Can

Hello, I encountered the following bug when migrating a Linux-2.6.32.54 PV domain on Xen-3.4.3 between different hosts, whose uptime differs by several minutes (3 hosts, each ~5 minutes apart): When migrating from a host with lower uptime to a host with higher uptime, the VM looses it''s network connection for some time and then continues after some minutes (roughly equivalent to the

Hey folks. Currently, I am working on an accounting-solution for Private Cloud with Eucalyptus as my bachelor-thesis. Eucalyptus bases on libvirt providing the KVM machines. Part of the thesis is kind of measurement for the uptimes of each instance in the cloud. As Eucalyptus is based on libvirt, i want to know if there is kind of tool already setup for monitoring a vm in terms of uptimes, cputimes and disk i/o. If not, can anyone give me a hint, how i could grep these facts? I found a tool called "virt-top" whi...

Hi, my Asterisk on debian lenny died after 80 days. server kernel: [7572666.186852] asterisk[3673]: segfault at 10 ip 7f3b8e90b4aa sp 40bf5f00 error 4 in l ibpthread-2.7.so[7f3b8e903000+16000] Anything what can be done to find out the reason? best regards Thomas

Sorry, forgot to change the subject on my first posting. I was reading a comment this morning about something Microsoft had published to the effect that there were vendors guaranteeing 99.9% uptime for NT. The guy who wrote the reply did the math for what that means, and the results are very interesting. Quote below: OK, now what does a 99.9% uptime guarantee mean? Well, it means that at

We manage hypervisors (VMWare ESXi/vCenter, KVM, XEN, Hyper-V) by remote Libvirt API, in our case we need to get the host uptime via the same libvirt interface. Is there a way get this info now for all the aforementioned hypervisor types? The APIs virConnectGetSysinfo(), virNodeGetInfo() provide host info but it doesn't include the system uptime. The virNodeGetCPUStats() can returns CPU

--- tests/Makefile.am | 6 ++++ tests/test-info-conntime.sh | 65 +++++++++++++++++++++++++++++++++++ tests/test-info-time.sh | 68 +++++++++++++++++++++++++++++++++++++ tests/test-info-uptime.sh | 65 +++++++++++++++++++++++++++++++++++ 4 files changed, 204 insertions(+) diff --git a/tests/Makefile.am b/tests/Makefile.am index 5a65db7..abcce94 100644 --- a/tests/Makefile.am +++

...atches up with the uptime of the old host! While waiting for the uptime to catch up, gettimeofday always returns the same value. Conversely, if a guest migrates from a host with a lower uptime to a host with a higher uptime, the system time in the guest advances by the difference between the two uptimes. I can think of a few possible fixes for this issue: 1) have system_time in the hypervisor start at unix epoch 0 (january 1st 1970) instead of at boot time - this may require some magic to sync_cmos_clock(), sync_xen_wallclock() and/or other functions so dom0 does not get too confused w...

On 9/28/19 3:02 PM, Richard W.M. Jones wrote: > --- > tests/Makefile.am | 6 ++++ > tests/test-info-conntime.sh | 65 +++++++++++++++++++++++++++++++++++ > tests/test-info-time.sh | 68 +++++++++++++++++++++++++++++++++++++ > tests/test-info-uptime.sh | 65 +++++++++++++++++++++++++++++++++++ > 4 files changed, 204 insertions(+) > > +# Test the info

https://bugzilla.netfilter.org/show_bug.cgi?id=991 Bug ID: 991 Summary: Exactly after 24h of uptime system hungs Product: netfilter/iptables Version: unspecified Hardware: sparc64 OS: Debian GNU/Linux Status: NEW Severity: blocker Priority: P5 Component: ip_tables (kernel)

CentOS-6.6 Can logwatch be configured to display the system uptime as part of the reporting prologue? If not then what would be the recommended way of including this information in a daily logwatch report? -- *** e-Mail is NOT a SECURE channel *** Do NOT transmit sensitive data via e-Mail James B. Byrne mailto:ByrneJB at Harte-Lyne.ca Harte & Lyne

Hmm.. All the hp/ux of the 10.x era has that set in the configure.ac. - Ben ---------- Forwarded message ---------- Date: Tue, 9 Jul 2002 05:40:35 +1000 (EST) From: bugzilla-daemon at mindrot.org To: openssh-unix-dev at mindrot.org Subject: [Bug 345] New: w (uptime) command still indicates user is logged in after logout http://bugzilla.mindrot.org/show_bug.cgi?id=345 Summary: w

I checked the archives and /usr/src/UPDATING and didn't see anything relating to this, and I might have easily missed it in the digest. I've got two different boxes that are running a recent -stable, and recently they both started spitting out the error message uptime: /dev/:0: No such file or directory before printing out the results. This may have actually started some time ago, as