similar to: rsync sleeps ( long sleep times )

hi guys We use rsync extensively in keeping the site resources in synch across redundant infrastructure. While attempting rsync for one of the boxes we find that the rsync process simply sleeps. The situation remains the same even if we have sync very small contents of the order of 4 KB. The same run with the -an flag runs without any issues. We run rsync over ssh on solaris boxes. To debug the

I hope I'm sending this report to the right place. I recently upgraded the rsync binaries in a bunch of our Solaris 9 systems from rsync 2.6.9 to rsync 3.0.5 . I have a script that runs in each machine that syncs the file systems from an active drive to a backup drive. Wihtin 3 days, this script had hung in two of the ~20 hosts that I had updated with the new rsync. Those two hosts

I have a program where the process seems to be sleeping a lot (waiting on something) What would be the right approach to figure out via dtrace where it is sleeping and why it is sleeping? In my current process, using truss -D shows that it reaches pollsys and the whole process sleeps for 1.5 - 1.8 seconds before it awakes again. Its the only significant process running on this two CPU

https://bugzilla.samba.org/show_bug.cgi?id=3488 Summary: writefd_unbuffered failed to write 4096 bytes: phase "unknown" [generator]: Broken pipe (32) Product: rsync Version: 2.6.6 Platform: Sparc OS/Version: Solaris Status: NEW Severity: major Priority: P3 Component: core

https://bugzilla.samba.org/show_bug.cgi?id=1937 Summary: timeout in data send/receive Product: rsync Version: 2.6.2 Platform: Sparc OS/Version: Solaris Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: ade.rixon@big-bubbles.fluff.org

> OpenSSH_3.4p1, SSH protocols 1.5/2.0, OpenSSL 0x0090607f > AIX 4.3.3.0 Maintenance Level 10. > > I have run a test on my boxes and found the following: > > > scp test <remote_machine>:~/test > test 100% |*****************************| 16000 > 00:00 > > > > scp works fine, but when I tried to redirect stdio/stderr to files they >

Hi out there, we have detected a bug in Samba-2.2.5, full details are in the attached files, but apparently the follwing snippet is the most important part of it: [common] comment = Common Tree Rev 1.3 path = /var/samba/common/%a msdfs root = true read only = no public = no browseable = yes

Greetings, I'm using rsync to keep multiple nfs filesystems on two emc nfs serves in sync. Here are the six file systems and their info: Filesystem kbytes used avail capacity Mounted on Number of files burd1p0:/nettmp 258120 37144 220976 15% /nfs/burd1p0/nettmp 2102 burd1p0:/user 29443776 16160480 13283296 55%

http://bugzilla.mindrot.org/show_bug.cgi?id=404 Summary: getnameinfo failed Product: Portable OpenSSH Version: -current Platform: All OS/Version: Linux Status: NEW Severity: normal Priority: P2 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: pmartinez at heraldo.es

Is this a known issue? (ignore the pervasive MS-outlook capitalization) Ssh-agent /bin/ksh Ssh-add /root/.ssh/id_rsa Blah blah Ssh -vvv some_server date ... debug1: ssh_rsa_verify: signature correct debug1: kex_derive_keys debug1: newkeys: mode 1 debug1: Enabling compression at level 6. debug1: SSH2_MSG_NEWKEYS sent debug1: waiting for SSH2_MSG_NEWKEYS debug1: newkeys: mode 0 debug1:

using openssh-3.8.1p1 from sunfreeware.com on a SunOS XXX 5.8 Generic_117000-03 sun4u sparc SUNW,Sun-Fire-V240. sshd seems to ignore or miss SIGCLD. this is a rare behaviour we observe about once per week in a ssh intensive environment. the process hangs here: truss: 24453: poll(0xFFBEEF28, 2, -1) (sleeping...) gcore, mdb: libc.so.1`_poll+4(b, 0, 0, ffbeef38, 6fc40,

Hi, I am fairly new to DTrace, and wanted to ask something regarding synchronization objects. I have a multithreaded C++ program in which I use semaphores (POSIX version) for synchronization. I was interested in using DTrace to figure out the total time for which each thread in my application sleeps, blocked on a semaphore, i.e., as a result of sem_wait() call. In order to measure this, I

Again, apologies for my ignorance - are you suggesting that if the NUT application was built against openusb this would probably be fixed? If so I'm happy to give this a try - any idea how can I tell NUT to build against openusb instead of libusb? Regards, Richard On Sun, Apr 5, 2015 at 2:28 AM Charles Lepple <clepple at gmail.com> wrote: > On Apr 4, 2015, at 8:53 PM, Richard

I have a simple small AD DC setup. Two DC's, a member server and a couple of W7 machines. Because I am so small. My DC's do not work very hard therefore I chose two P4 computers. (Remember the day when a P4 was a "hot rod!") I could by them refurbished for cheap. I have been using Louis' scripts for some time now. I like them. These scripts set up an AD DC system. With some

Package: xen-utils-common Version: 4.1.3-4 Function check_running in /etc/init.d/xendomains incorrectly detects a not running domain as running. As a consequence thereof "/etc/init.d/xendomains stop" needs more than XENDOMAINS_STOP_MAXWAIT * "number of xen domains known to xend" seconds to run. Here is a pseudo call trace: do_stop_shutdown() { ... while read id name

Dear Developers First of all I would love to thank you for a nice tool I had been using rsync within backuppc project to backup my remote hosts. It had been working fine until the moment (as I think) whenever I moved RAID to another box and now the source directory (/raid/research) is now actually NFS mounted. Now backup (rsync process) stalls and sleeps indefinitely On the backup server:

I've got an rsync job which is consistently failing, but I've been unable to diagnose the problem. FAQ/Google/docs/etc. checked and no luck. Basically, it looks like the rsync process invoked on the far end is exiting, and then the local process waits until the timeout and exits. Both systems are Sun boxes, Ultra 10 or better with 256+ MB of memory. Rsync version is 2.5.0 on the local

An old problem has started to reappear with our Solaris (2.8) Samba (3.0.23b). This was after an upgrade from 3.0.22 in which the problem was worse. Occasionally an smbd process will go "rogue" and start consuming CPU cycles until killed. I did a truss of the process and got back this tight loop. fcntl(27, F_SETLKW64, 0xFFBEEF98) = 0 fcntl(27, F_SETLKW64, 0xFFBEF010)

On Apr 4, 2015, at 8:53 PM, Richard Flint <richard.flint at gmail.com> wrote: > I have used the truss command as directed. I have attached both the driver output and the last few sections of truss output leading to the hang. Both outputs end at the CTRL+C i pressed when i was forced to end the processes. > > Hope this is helpful. Please bear with me if i didn't run it with the

I've run into a bug in the IO handling when reading a file. Suppose I have a file that lives on an NFS filesystem. That filesystem is NOT being exported with auth=0 permissions. So, if I try to access a file as root, it successfully opens the file, but subsequent reads fail with EACCES. This produces a destination file full of null bytes. I noticed this with 2.5.7, but checked 2.6.2 as