From 19d7083ed8759d8b76420186f34e31fb46e869d8 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 13:05:08 -0400 Subject: comment --- .../comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment | 10 ++++++++++ 1 file changed, 10 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment b/doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment new file mode 100644 index 00000000..0eb98f6c --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_1_8598e38bc60fd25ebecb7b3b09d74940._comment @@ -0,0 +1,10 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 1""" + date="2016-03-06T17:00:02Z" + content=""" +I think I've been seeing this too, recently. + +I had not put together that it involves the ssh control socket. +And am not 100% sure it does yet. +"""]] -- cgit v1.3-2-g0d8e From 3db71c4f83da6a20c040a44e4fe0cf64c5303190 Mon Sep 17 00:00:00 2001 From: "mithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a82" Date: Sun, 6 Mar 2016 17:39:34 +0000 Subject: Added a comment --- .../comment_2_5c0bb1b38a92ff17277f514703ce2761._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment b/doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment new file mode 100644 index 00000000..0b545262 --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_2_5c0bb1b38a92ff17277f514703ce2761._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="mithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a82" + nickname="mithrandi" + subject="comment 2" + date="2016-03-06T17:39:34Z" + content=""" +Yes, it's possible I misdiagnosed the problem; I've never had the issue spinning twice in a row, but there may be other factors at play. +"""]] -- cgit v1.3-2-g0d8e From 82d0473dd00401004fe996a6a1349d976fe979a7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 13:57:50 -0400 Subject: comment --- .../comment_3_8347b69df64b737f4e5df854c55d4e92._comment | 15 +++++++++++++++ 1 file changed, 15 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment b/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment new file mode 100644 index 00000000..adc64e5d --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_3_8347b69df64b737f4e5df854c55d4e92._comment @@ -0,0 +1,15 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 3""" + date="2016-03-06T17:54:20Z" + content=""" +It also seemed to affect the first spin and not the second one when I was +seeing it. But that was 1-2 weeks ago, and I am not currently reproducing +the issue. + +If you can reproduce it consistently, it would be good to check if the +concurrent output layer, which involves intercepting all command output and +serializing it, might be involved. If you edit +`src/Utility/Process/Shim.hs` and make it simply `import System.Process as X` +and remove the other import, that will bypass the concurrent output layer. +"""]] -- cgit v1.3-2-g0d8e From 15d628d6da29700bffcc24d8d959db7d82f1fe7e Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 14:56:45 -0400 Subject: comment --- ...ent_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment | 22 ++++++++++++++++++++++ 1 file changed, 22 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment b/doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment new file mode 100644 index 00000000..2ffdcbac --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_4_2fbb97cb5bca3a0e2835e7667aff7a00._comment @@ -0,0 +1,22 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 4""" + date="2016-03-06T18:43:37Z" + content=""" +Added some debugging, I found that processes run by concurrent-output tend to +alternate between running foreground and background. So, when the socket +exists and is old, it will run one more process than otherwise to +stop ssh on that socket, and this will change which run method is +used for subsequent processes. + +However, it really shouldn't matter if a process starts in the background; +concurrent-output shoud notice when the output lock frees up, and start +displaying the processes's output. + +So, this theory explains why the ssh socket seems to be involved, perhaps, +but it doesn't really explain what's happening to prevent the remote +propellor output from being shown. + +Unless some other foreground process is hanging around and keeping +the output lock. Or some bug in concurrent-output.. +"""]] -- cgit v1.3-2-g0d8e From b809f529d52e78043c675961b83e16b1085815cb Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 16:44:03 -0400 Subject: comment --- .../comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment b/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment new file mode 100644 index 00000000..72315aa0 --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_5_bfbcb2a81bff6b6432217c72a5e54576._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 5""" + date="2016-03-06T19:57:03Z" + content=""" +Managed to reproduce the hang once, and the ssh was indeed being run as +bgProcess. However, I didn't manage to see what foreground process, if any, +was running when that happened. And had no luck reproducing it again. + +I added some more `PROPELLOR_DEBUG` output around this, so it'll tell +when a process is being run by fgProcess or bgProcess. +"""]] -- cgit v1.3-2-g0d8e From 85e3d4c169ca81f47113cedb65c2c4a643a91b12 Mon Sep 17 00:00:00 2001 From: "mithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a82" Date: Sun, 6 Mar 2016 21:27:18 +0000 Subject: Added a comment --- .../comment_6_d6c4f22f48c5f0b6d06e9a155e8e5f69._comment | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_6_d6c4f22f48c5f0b6d06e9a155e8e5f69._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_6_d6c4f22f48c5f0b6d06e9a155e8e5f69._comment b/doc/forum/Weird_SSH_issue/comment_6_d6c4f22f48c5f0b6d06e9a155e8e5f69._comment new file mode 100644 index 00000000..7d01913b --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_6_d6c4f22f48c5f0b6d06e9a155e8e5f69._comment @@ -0,0 +1,8 @@ +[[!comment format=mdwn + username="mithrandi@311efa1b2b5c4999c2edae7da06fb825899e8a82" + nickname="mithrandi" + subject="comment 6" + date="2016-03-06T21:27:18Z" + content=""" +Might it have something to do with how ssh forks (but doesn't double fork or \"daemonize\") to start the control master, if one isn't already running? +"""]] -- cgit v1.3-2-g0d8e From 3a9c23d6463c15c1fc5568df4c0ec212c2a84cd7 Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Sun, 6 Mar 2016 19:00:49 -0400 Subject: response --- .../comment_7_77d2d330846c80ed463644860e49f184._comment | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 doc/forum/Weird_SSH_issue/comment_7_77d2d330846c80ed463644860e49f184._comment (limited to 'doc/forum/Weird_SSH_issue') diff --git a/doc/forum/Weird_SSH_issue/comment_7_77d2d330846c80ed463644860e49f184._comment b/doc/forum/Weird_SSH_issue/comment_7_77d2d330846c80ed463644860e49f184._comment new file mode 100644 index 00000000..ab82a6c1 --- /dev/null +++ b/doc/forum/Weird_SSH_issue/comment_7_77d2d330846c80ed463644860e49f184._comment @@ -0,0 +1,9 @@ +[[!comment format=mdwn + username="joey" + subject="""comment 7""" + date="2016-03-06T22:59:31Z" + content=""" +I don't see how that could be relevant, but if you want to, edit +src/Propellor/Ssh.hs and make sshCachingParams return [] and +see if that changes it. +"""]] -- cgit v1.3-2-g0d8e