similar to: occasional ssh hang

I am using OpenSSH on Redhat 6.2 (Intel) and Solaris 2.6 (Sparc). I have a job on the linux machine that ssh's to the Solaris machine every 20 seconds or so and runs uptime. The problem is that after many iterations of this, ssh will occasionally hang, and require a kill -9 to get rid of the process. The problem happens with both protocol version 1 and 2, but it seems to happened more often

Hello! I've noticed this problem two times now.. last time I fixed it by rebooting the (centos 5.1 x86 32b) xen host/dom0. Symptoms: - Already running domUs (debian 2.6.18-6-xen-686 32b PAE) continue running and working OK - Cannot start new domUs (debian 2.6.18-6-xen-686).. kernel bootup just hangs before running initrd. Same domU with the exact same xen domU cfgfile worked earlier.

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

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

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

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,

I've attached a patch for contrib/solaris package builder to bring it up to date with OpenSSH 2.9p1. The changes are: build-pkg - add libexec/ directory creation (to house sftp-server) cp sftp-server to libexec/ cp sftp.1 to man/man1 cp sftp to bin/ postinstall.in - add RSA key generation and installation/update prototype - add sftp, sftp.1 and sftp-server Btw, 2.9p1 is

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

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

We recently tried upgrading openssh from 2.5.2p2 to 2.9p1 and discovered that it no longer worked to feed the output from a remote command into a pipe, unless the output was short and the pipe was very fast at processing its input. Example 1: ssh remote_machine some_command | less (where "some_command" generates a lot of output) now fails after the first screenful, with a

Hi, I have done some debugging to find out the root cause of bug 1282, which has the following symptoms with paravirtualized guests: - after a live migrate, the time on the guest can jump - after a live migrate, the guest "forgets" to wake up processes - after a domU save, dom0 reboot and domU restore, the time is correct but processes are not woken up from sys_nanosleep The problem

OpenSSH Version 2.9p1 of "ssh-add $HOME/.ssh/id_rsa < /dev/null" fails on the first try of using ssh-askpass before the window manager starts. The second try works. The error message on the first try is "Bad passphrase, try again". This did not occur using OpenSSH-2.5.2p2.tar.gz. I've tested this on both RHL6.2 and RHL7.1, both with all RH rpm updates applied. I

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

Has anyone else running AIX tried this patch? I'm looking for feedback if it should be applied before we release 2.9p1. - Ben ---------- Forwarded message ---------- Date: Tue, 24 Apr 2001 17:22:02 -0800 (AKDT) From: mikem at alaska.net To: openssh-unix-dev at mindrot.org Subject: Functionality bug (possibly) in openssh on AIX 4.3 Hi Folks, While compiling and testing openssh-2.5.2p2 on

Another instance of OpenSSH 2.9p1 hanging on exit. This occurs when connecting to a Solaris 8 box (both from other Solaris 8 hosts and from Linux hosts, all using OpenSSH 2.9p1). This problem doesn't appear to involve active background jobs; it is not fixed by either the bash fix listed in the FAQ or by zsh's "setopt HUP". I do not see the hang-on-exit behavior with the

Hello. I have a Solaris 11/11 x86 box (which I migrated from SolEx 11/10 a couple of weeks ago). Without no obvious reason (at least for me), after an uptime of 1 to 2 days (observed 3 times now) Solaris sets arc_no_grow to 1 and then never sets it back to 0. ARC is being shrunk to less than 1 GB -- needless to say that performance is terrible. There is not much load on this system. Memory

Hi everyone, Apologies in advance, this will be a bit long but I'm hoping to get some guidance and hints on usual practices for using Samba4 AD DC as an Idm for W10 laptops that might be on the road elsewhere.. As much as I have been using samba for file serving, a Samba AD DC is something new to me. I built a small Samba AD DC infrastructure to serve UIDs and Passwords (4 VMs on 4 KVM

I've looked around at the API documents (I'm using python) and I know how to find the cpu active uptime of the domain, but that only increases if the domain is running something. Is there a way to determine when the domain was first launched, either as a date or uptime with idle uptime included? /Amy

Hi folks, I am using Xen on M3A mother board from Assus (64 bit CPU - X4). All the instances are running CentOS 5.1. There is no monitor attached to the server and all the outputs (GRUB, Kernel, Terminals) are sent to the serial console. Everything works fine except when I try to boot up an instance from Dom0, it hangs during the boot sequence occasionally (rather more often than just

Hi, I'm wondering if this is normal asterisk behaviour: asterisk*CLI> sip show channels Peer User/ANR Call ID Format Hold Last Message Expiry Peer 10.12.0.2 (None) 3c2f7ff2975e-wp 0x0 (nothing) No Rx: PUBLISH <guest> 10.12.0.2 (None) 3c2f7f21b71b-9q 0x0 (nothing) No