RE: rsync gives me error 12
Wayne: When I run this command on my Windows machine: echo hi | ssh r...@marketing.propfinancing.com cat I get back: hi When I run this command: rsync --debug=ALL --msgs2stderr -M--msgs2stderr r...@marketing.propfinancing.com:/var/www/svnDumps /cygdrive/c/Tmp I get this output: opening connection using: ssh -l root marketing.propfinancing.com rsync --server --sender -e.LsfxCIvu --msgs2stderr --msgs2stderr . /var/www/svnDumps (12 args) rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.3] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(228) [Receiver=3.2.4dev] [Receiver] _exit_cleanup(code=12, file=io.c, line=228): about to call exit(12) I put the rsync-debug script in /tmp on the server and then ran this command on my Windows machine: rsync -av --rsync-path=/tmp/rsync-debug r...@marketing.propfinancing.com:/var/www/svnDumps /cygdrive/c/Tmp I got the same output on my local machine. On the server, I got a /tmp/rsync-3191.out file which I am attaching here. I can't make sense of what it is trying to tell me. Thank you, Neil -- Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com We offer 30 year loans on single family houses! rsync-3191.out Description: Binary data -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: rsync gives me error 12
On Fri, Mar 25, 2022 at 10:37 AM Neil Aggarwal wrote: > I still get an error: > rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] > rsync error: error in rsync protocol data stream (code 12) at io.c(226) > [Receiver=3.1.3] > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(228) > [sender=3.2.4dev] As the rsync issues & debugging page mentions, you should try forcing errors to stderr to see if it makes the remote rsync report its error to you: --msgs2stderr -M--msgs2stderr It also mentions an rsync-debug script that you can put on the remote host and use to get the strace output of what is happening and get a core dump (if it is dumping core). https://rsync.samba.org/issues.html Also, try running the following test command and make sure you see the word "hi" and nothing else: echo hi | ssh r...@marketing.propfinancing.com cat ..wayne.. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[ANNOUNCEMENT] Updated: mintty 3.6.0
I have uploaded mintty 3.6.0 with the following changes: Highlights * Optional feature: Reflow terminal lines when resizing terminal width. * Visual feedback of numeric or composed character input. * New themes helmholtz and luminous (contributed by Andy Koppe). * Setting helmholtz theme as default colour scheme. Window handling * Reflow terminal lines when resizing terminal width (#82, #219, mintty/wsltty#154). Terminal features * Tweak pending auto-wrap state affected when switching wrap modes. * Fixed unscroll (CSI +T) in case width has changed meanwhile. * Visual feedback of numeric or composed character input. Keyboard handling * Support user-defined mappings for Super-/Hyper-modified character keys. * Support optional user-defined mappings for Control-/Alt-modified character keys (#399, #252, #523, #602, #645, ~#524, ~#817, ~#451). * Suspend shortcut handling during numeric character input. * Revise and fix numeric character input. * Distinct Unicode vs. hexadecimal numeric character input. * Menu key opens menu inside terminal, also stops numeric input. * Fixed Compose sequences with more than 2 characters (broken since 3.1.5). Font rendering * Right-to-left font fallback (#1148). * Fixed auto-widening of ambiguous-width letters (broken since 3.4.4). * Speedup rendering of replacement indication of invalid character codes (#1145). * Extend cell zoom to some Geometric Shapes U+25E2.., Dingbats U+1F67C.., and Symbols U+1FB00..U+1FBB3. Startup * Trimming irrelevant and possibly confusing environment variables before child invocation (xterm). Configuration * New themes helmholtz and luminous (contributed by Andy Koppe). * Setting helmholtz theme as default colour scheme. * New option -Rt to report the tty name of the child process / shell. * New option ShootFoot (#399, #252, #523, #602, #645, ~#524, ~#817, ~#451). * New option RewrapOnResize (#82), interactive (Options dialog). * New user-definable function unicode-char. * Updated X11-derived data: compose sequences and colour names. The homepage is at http://mintty.github.io/ It also links to the issue tracker. -- Thomas -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Updated: mintty 3.6.0
I have uploaded mintty 3.6.0 with the following changes: Highlights * Optional feature: Reflow terminal lines when resizing terminal width. * Visual feedback of numeric or composed character input. * New themes helmholtz and luminous (contributed by Andy Koppe). * Setting helmholtz theme as default colour scheme. Window handling * Reflow terminal lines when resizing terminal width (#82, #219, mintty/wsltty#154). Terminal features * Tweak pending auto-wrap state affected when switching wrap modes. * Fixed unscroll (CSI +T) in case width has changed meanwhile. * Visual feedback of numeric or composed character input. Keyboard handling * Support user-defined mappings for Super-/Hyper-modified character keys. * Support optional user-defined mappings for Control-/Alt-modified character keys (#399, #252, #523, #602, #645, ~#524, ~#817, ~#451). * Suspend shortcut handling during numeric character input. * Revise and fix numeric character input. * Distinct Unicode vs. hexadecimal numeric character input. * Menu key opens menu inside terminal, also stops numeric input. * Fixed Compose sequences with more than 2 characters (broken since 3.1.5). Font rendering * Right-to-left font fallback (#1148). * Fixed auto-widening of ambiguous-width letters (broken since 3.4.4). * Speedup rendering of replacement indication of invalid character codes (#1145). * Extend cell zoom to some Geometric Shapes U+25E2.., Dingbats U+1F67C.., and Symbols U+1FB00..U+1FBB3. Startup * Trimming irrelevant and possibly confusing environment variables before child invocation (xterm). Configuration * New themes helmholtz and luminous (contributed by Andy Koppe). * Setting helmholtz theme as default colour scheme. * New option -Rt to report the tty name of the child process / shell. * New option ShootFoot (#399, #252, #523, #602, #645, ~#524, ~#817, ~#451). * New option RewrapOnResize (#82), interactive (Options dialog). * New user-definable function unicode-char. * Updated X11-derived data: compose sequences and colour names. The homepage is at http://mintty.github.io/ It also links to the issue tracker. -- Thomas
RE: rsync gives me error 12
Adam: I tried doing an upload using this command: rsync test.xml r...@marketing.propfinancing.com:/tmp I still get an error: rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [Receiver=3.1.3] rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(228) [sender=3.2.4dev] Could it be the rsync versions are somehow incompatible? Would it help if I create a login for you on the server so you can try doing an rsync yourself? Thank you, Neil -- Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com We offer 30 year loans on single family houses! -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: rsync gives me error 12
Adam: > this reads to me like the remote > server is closing the connection When I run this command on my Windows machine: rsync --debug=ALL r...@marketing.propfinancing.com:/var/www/svnDumps /cygdrive/c/Tmp I get this output on the screen: opening connection using: ssh -l root marketing.propfinancing.com rsync --server --sender -e.LsfxCIvu . /var/www/svnDumps (10 args) rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.3] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(228) [Receiver=3.2.4dev] [Receiver] _exit_cleanup(code=12, file=io.c, line=228): about to call exit(12) It is connecting to the Linux server and immediately disconnecting, here is what I see in /var/log/secure: Mar 25 12:11:00 marketing sshd[43597]: Postponed publickey for root from 99.137.191.183 port 64715 ssh2 [preauth] Mar 25 12:11:00 marketing sshd[43597]: Accepted publickey for root from 99.137.191.183 port 64715 ssh2: RSA SHA256:[removed] Mar 25 12:11:00 marketing sshd[43597]: pam_unix(sshd:session): session opened for user root by (uid=0) Mar 25 12:11:00 marketing sshd[43600]: Received disconnect from 99.137.191.183 port 64715:11: disconnected by user Mar 25 12:11:00 marketing sshd[43600]: Disconnected from user root 99.137.191.183 port 64715 Mar 25 12:11:00 marketing sshd[43597]: pam_unix(sshd:session): session closed for user root I'm stumped at this point. Thank you, Neil -- Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com We offer 30 year loans on single family houses! -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: pipe hang issue when running as SYSTEM
On Fri, 25 Mar 2022, Takashi Yano wrote: > I will submit v3 patch shortly. I applied your v3 patch to 3.3.4 in https://github.com/msys2/msys2-runtime/pull/88 and re-ran my test action, and it worked as expected this time. I've put out a call to test on the msys2-runtime issue to confirm that it also solves the real-world cases. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: rsync gives me error 12
Adam: > Looking slightly closer at the logs, this reads to me like the remote > server is closing the connection, so I expect you'll need help from > whoever provides/supports that remote server to work out why it's doing > that. I am responsible for the remote server. I will look into that. Thank you for putting me on the right track! Thank you, Neil -- Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com We offer 30 year loans on single family houses! -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: rsync gives me error 12
On Fri, Mar 25, 2022 at 08:25:16AM -0500, Neil Aggarwal wrote: > > I suspect the `-e ssh` part is the problem here. That's supposed to > > specify the remote shell, not the method for connecting. What are you > > attempting to achieve with that? > > I am trying to do the sync over an SSH connection. > > When I remove it: > rsync --debug=ALL r...@marketing.propfinancing.com:/var/www/svnDumps > /cygdrive/c/Tmp > > I still get the error: > opening connection using: ssh -l root marketing.propfinancing.com > rsync --server --sender -e.LsfxCIvu . /var/www/svnDumps (10 args) > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > rsync error: error in rsync protocol data stream (code 12) at io.c(226) > [sender=3.1.3] > rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] > rsync error: error in rsync protocol data stream (code 12) at io.c(228) > [Receiver=3.2.4dev] > [Receiver] _exit_cleanup(code=12, file=io.c, line=228): about to call > exit(12) Works just fine for me. (Indeed, it works just fine even if I add `-e ssh`, which surprised me -- clearly I have the wrong impression of what that `-e` argument is for!) Looking slightly closer at the logs, this reads to me like the remote server is closing the connection, so I expect you'll need help from whoever provides/supports that remote server to work out why it's doing that. -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
RE: rsync gives me error 12
> I suspect the `-e ssh` part is the problem here. That's supposed to > specify the remote shell, not the method for connecting. What are you > attempting to achieve with that? I am trying to do the sync over an SSH connection. When I remove it: rsync --debug=ALL r...@marketing.propfinancing.com:/var/www/svnDumps /cygdrive/c/Tmp I still get the error: opening connection using: ssh -l root marketing.propfinancing.com rsync --server --sender -e.LsfxCIvu . /var/www/svnDumps (10 args) rsync: connection unexpectedly closed (0 bytes received so far) [sender] rsync error: error in rsync protocol data stream (code 12) at io.c(226) [sender=3.1.3] rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: error in rsync protocol data stream (code 12) at io.c(228) [Receiver=3.2.4dev] [Receiver] _exit_cleanup(code=12, file=io.c, line=228): about to call exit(12) Thanks, Neil -- Neil Aggarwal, (972) 834-1565, http://www.propfinancing.com We offer 30 year loans on single family houses! -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
[PATCH v3] Cygwin: pipe: Avoid deadlock for non-cygwin writer.
- As mentioned in commit message of the commit b531d6b0, if multiple
writers including non-cygwin app exist, the non-cygwin app cannot
detect pipe closure on the read side when the pipe is created by
system account or the the pipe creator is running as service.
This is because query_hdl which is held in write side also is a
read end of the pipe, so the pipe still alive for the non-cygwin
app even after the reader is closed.
To avoid this problem, this patch lets all processes in the same
process group close query_hdl using newly introduced internal signal
__SIGNONCYGCHLD when non-cygwin app is started to avoid the problem.
Addresses: https://cygwin.com/pipermail/cygwin/2022-March/251097.html
---
winsup/cygwin/sigproc.cc | 9 +
winsup/cygwin/sigproc.h | 1 +
winsup/cygwin/spawn.cc | 12 +++-
3 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/winsup/cygwin/sigproc.cc b/winsup/cygwin/sigproc.cc
index d3f2b0c6a..9a2f75861 100644
--- a/winsup/cygwin/sigproc.cc
+++ b/winsup/cygwin/sigproc.cc
@@ -1477,6 +1477,15 @@ wait_sig (VOID *)
clearwait = true;
}
break;
+ case __SIGNONCYGCHLD:
+ cygheap_fdenum cfd (false);
+ while (cfd.next () >= 0)
+ if (cfd->get_dev () == FH_PIPEW)
+ {
+ fhandler_pipe *pipe = (fhandler_pipe *)(fhandler_base *) cfd;
+ pipe->close_query_handle ();
+ }
+ break;
}
if (clearwait && !have_execed)
proc_subproc (PROC_CLEARWAIT, 0);
diff --git a/winsup/cygwin/sigproc.h b/winsup/cygwin/sigproc.h
index 23287c85b..d037eaec3 100644
--- a/winsup/cygwin/sigproc.h
+++ b/winsup/cygwin/sigproc.h
@@ -24,6 +24,7 @@ enum
__SIGSETPGRP = -(_NSIG + 9),
__SIGTHREADEXIT = -(_NSIG + 10),
__SIGPENDINGALL = -(_NSIG + 11),
+ __SIGNONCYGCHLD = -(_NSIG + 12),
};
#endif
diff --git a/winsup/cygwin/spawn.cc b/winsup/cygwin/spawn.cc
index fb3d09d84..3b65d32c8 100644
--- a/winsup/cygwin/spawn.cc
+++ b/winsup/cygwin/spawn.cc
@@ -28,6 +28,7 @@ details. */
#include "tls_pbuf.h"
#include "winf.h"
#include "ntdll.h"
+#include "shared_info.h"
static const suffix_info exe_suffixes[] =
{
@@ -645,8 +646,17 @@ child_info_spawn::worker (const char *prog_arg, const char
*const *argv,
&& (fd == fileno_stdout || fd == fileno_stderr))
{
fhandler_pipe *pipe = (fhandler_pipe *)(fhandler_base *) cfd;
- pipe->close_query_handle ();
pipe->set_pipe_non_blocking (false);
+
+ tty_min dummy_tty;
+ dummy_tty.ntty = (fh_devices) myself->ctty;
+ dummy_tty.pgid = myself->pgid;
+ tty_min *t = cygwin_shared->tty.get_cttyp ();
+ if (!t) /* If tty is not allocated, use dummy_tty instead. */
+ t = _tty;
+ /* Emit __SIGNONCYGCHLD to let all processes in the
+ process group close query_hdl. */
+ t->kill_pgrp (__SIGNONCYGCHLD);
}
else if (cfd->get_dev () == FH_PIPER && fd == fileno_stdin)
{
--
2.35.1
Re: pipe hang issue when running as SYSTEM
On Fri, 25 Mar 2022 00:09:59 -0700 (PDT) Jeremy Drake wrote: > On Fri, 25 Mar 2022, Takashi Yano wrote: > > > I can confirm the sample script hangs indeed if the script is > > running as SYSTEM account. However, in my test, the patch solves > > the issue. > > > > It would be very helpfull if a simple github repository with > > github actions, which can reproduce the issue, is provided. > > After much fighting with docker on windows, > https://github.com/jeremyd2019/msys2-pipe-hang-test/runs/5688176578?check_suite_focus=true Thanks much! I could reproduce the issue even with the patch. I also noticed what is the cause. The problem is that the command: docker run msys2-base c:\msys64\usr\bin\bash -lc "/c/test.sh" does not allocate tty. Therefore, kill_pgrp(__SIGNONCYGCHLD) is not called. If you use: docker run -t msys2-base c:\msys64\usr\bin\bash -lc "/c/test.sh" the problem does not occur. I will submit v3 patch shortly. -- Takashi Yano -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: rsync gives me error 12
On Thu, Mar 24, 2022 at 12:22:12AM -0500, Neil Aggarwal wrote: > I am trying to use rsync to pull all backups from a linux server > to my local Windows machine. > > I tried this rsync command: > > $ rsync --debug=ALL -e ssh r...@marketing.propfinancing.com:/var/www/svnDumps > /cygdrive/c/Tmp > > Here is the output: > > opening connection using: ssh -l root marketing.propfinancing.com rsync > --server --sender -e.LsfxCIvu . /var/www/svnDumps (10 args) > > rsync: connection unexpectedly closed (0 bytes received so far) [sender] > > rsync error: error in rsync protocol data stream (code 12) at io.c(226) > [sender=3.1.3] > > rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] > > rsync error: error in rsync protocol data stream (code 12) at io.c(228) > [Receiver=3.2.4dev] > > [Receiver] _exit_cleanup(code=12, file=io.c, line=228): about to call > exit(12) > > From what I can find online, code 12 is insufficient disk space, missing > remote > rsync, or a connection error. I don’t think any of those are the case > here and the > debug output is not helping me. > > Any ideas what could be happening? I suspect the `-e ssh` part is the problem here. That's supposed to specify the remote shell, not the method for connecting. What are you attempting to achieve with that? -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: [ITP] cygfuse
Hi Jon,
Thanks for the helpful review comments. More below.
Jon Turney wrote:
On 10/03/2022 06:16, Mark Geisert wrote:
[...]> A few small comments on the cygport file
HOMEPAGE="https://github.com/mgeisert/cygfuse;
#SRC_URI="http://maxrnd.com/~mark/cygwin/x86_64/release/cygfuse/cygfuse-${PV}.tar.xz;
#NOT YET: GIT_URI="https://github.com/mgeisert/cygfuse.git;
#NOT YET: GIT_TAG="v$VERSION"
#NOT YET: inherit git
It's unclear where the upstream source tarball comes from...
Things were in flux and are now straightened out. There's just a SRC_URI now.
# take over these activities from cygport..
_CYGPORT_RESTRICT_strip_=1
This should be written 'RESTRICT=strip', I think.
Yep, thanks.
src_compile()
{
# fix source tree glitch.. (maybe 'prep' stumbling or bad tarfile layout?)
if [ -e ${S}/src ]; then
mv ${S}/src/cygfuse ${S}
rmdir ${S}/src
fi
I think this can be handled with 'SRC_DIR=src/cygfuse' (and suitable adjustment to
paths throughout)
I had tried several variations on this before the initial ITP post. I tried again
after your comment. I'm still having issues with source layout.
I think my trouble is I'm bootstrapping my own source tree and there seem to be
conventions (that I don't know) on how it should be laid out. It seems the source
tarball generated by cygport doesn't match the layout of my own source tree.
Should my original source be in directory "src" or "src/cygfuse"? If the latter,
should there be a version number as part of the directory name? Should my original
source be placed under "origsrc" or "src"? These questions pertain to layout
before cygport is run to generate the first-ever package tarballs.
Currently the build, install, package steps seem to run to completion. But doing
a fetch and prep of the tarball has got me stymied (in the prep step). Error is
SRC_DIR is not correctly defined
I have been perusing /usr/share/cygport/*.cygpart but haven't found a solution.
Thanks,
..mark
Re: pipe hang issue when running as SYSTEM
Hi, Takashi Yano wrote: [SNIP] Just got another report to MSYS2 of this behavior, this time from a Gitlab CI runner that is running as a service and trying to pipe output from Microsoft cl.exe while running configure. This user reports that 3.3.4 with your "[PATCH v2] Cygwin: pipe: Avoid deadlock for non-cygwin writer." applied to it does not solve the problem. https://github.com/msys2/MSYS2-packages/issues/2893 I can confirm the sample script hangs indeed if the script is running as SYSTEM account. However, in my test, the patch solves the issue. It would be very helpfull if a simple github repository with github actions, which can reproduce the issue, is provided. In my environment with AD user account: $ cmd.exe /c "type big_file" | : The process tried to write to a nonexistent pipe. $ cat big_file | : *** starting debugger for pid NNN tid K $ uname -a CYGWIN_NT-10.0 ZZZ 3.3.4(0.341/5/3) 2022-01-31 19:35 x86_64 Cygwin Remarks: - no way to debug - no error if run as administrator Regards, Roumen Petrov -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
Re: pipe hang issue when running as SYSTEM
On Fri, 25 Mar 2022, Takashi Yano wrote: > I can confirm the sample script hangs indeed if the script is > running as SYSTEM account. However, in my test, the patch solves > the issue. > > It would be very helpfull if a simple github repository with > github actions, which can reproduce the issue, is provided. After much fighting with docker on windows, https://github.com/jeremyd2019/msys2-pipe-hang-test/runs/5688176578?check_suite_focus=true -- Problem reports: https://cygwin.com/problems.html FAQ: https://cygwin.com/faq/ Documentation:https://cygwin.com/docs.html Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple
