summaryrefslogtreecommitdiff
path: root/doc/forum/Shared_connection_to_xxx_closed.
diff options
context:
space:
mode:
Diffstat (limited to 'doc/forum/Shared_connection_to_xxx_closed.')
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_1_b0db2468e86d29deac6167363f88cfdc._comment16
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_2_fa080c190da730dfd023e96ca4000b93._comment9
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_3_1beb3b93a20111af8f736a7581b46d6c._comment8
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_4_bc60f392f8a73ac7bc54f5c3a4670590._comment13
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment20
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_6_2798a6806afd2d04cf6c7744ad633133._comment13
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment19
-rw-r--r--doc/forum/Shared_connection_to_xxx_closed./comment_8_cf2215bc51ed57558c76beb5226cf5fa._comment26
8 files changed, 124 insertions, 0 deletions
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_1_b0db2468e86d29deac6167363f88cfdc._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_1_b0db2468e86d29deac6167363f88cfdc._comment
new file mode 100644
index 00000000..da332234
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_1_b0db2468e86d29deac6167363f88cfdc._comment
@@ -0,0 +1,16 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 1"""
+ date="2015-09-15T15:38:13Z"
+ content="""
+Propellor uses a shared ssh connection to the remote host to avoid
+the overhead of multiple ssh connections. ssh will sometimes say "shared
+connection ... closed" when taking down such a connection.
+
+Propellor only reuses such a shared connection for up to 10 minutes; it it
+finds an old one (perhaps from a previous run of propellor), it will ask
+ssh to close the old connection.
+
+I don't think it's anything to worry about unless propellor is failing to
+work for some reason.
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_2_fa080c190da730dfd023e96ca4000b93._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_2_fa080c190da730dfd023e96ca4000b93._comment
new file mode 100644
index 00000000..57ebef84
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_2_fa080c190da730dfd023e96ca4000b93._comment
@@ -0,0 +1,9 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 2"
+ date="2015-09-15T15:51:15Z"
+ content="""
+Ok I understand but in my case, the connection was closed when propellor should have connect as root to the host and execute the spin action.
+
+So it only push to the central repository (ok) but did not proceed to the host installation.
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_3_1beb3b93a20111af8f736a7581b46d6c._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_3_1beb3b93a20111af8f736a7581b46d6c._comment
new file mode 100644
index 00000000..3c2e407d
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_3_1beb3b93a20111af8f736a7581b46d6c._comment
@@ -0,0 +1,8 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 3"""
+ date="2015-09-15T17:19:54Z"
+ content="""
+Well, I'd expect propellor would exit nonzero if it fails to connect to the
+host to spin it. Did this not happen?
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_4_bc60f392f8a73ac7bc54f5c3a4670590._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_4_bc60f392f8a73ac7bc54f5c3a4670590._comment
new file mode 100644
index 00000000..41ad0fc3
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_4_bc60f392f8a73ac7bc54f5c3a4670590._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 4"
+ date="2015-09-17T06:59:44Z"
+ content="""
+[2015-09-17 08:57:49 CEST] call: ssh [\"-o\",\"ControlPath=/home/picca/.ssh/propellor/xxxx.sock\",\"-o\",\"ControlMaster=auto\",\"-o\",\"ControlPersist=yes\",\"-t\",\"root@xxx\",\"sh -c 'cd /usr/local/propellor && ./propellor --continue '\\"'\\"'SimpleRun \\"xxx\\"'\\"'\\"''\"]
+Shared connection to xxxxx closed.
+picca@ORD03037:~/.propellor$ echo $?
+0
+
+
+so it seems thaht there is no error but the share connection was closed before running propellor on the host.
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment
new file mode 100644
index 00000000..15c06336
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_5_7be9e5912ef4165bf193f65f51b8216b._comment
@@ -0,0 +1,20 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 5"""
+ date="2015-09-21T19:47:17Z"
+ content="""
+So here's the code that runs that ssh command:
+
+ unlessM (boolSystem "ssh" (map Param $ cacheparams ++ ["-t", sshtarget, shellWrap runcmd])) $
+ error "remote propellor failed"
+
+I'm surprised it didn't fail with the error. This seems to say that ssh
+exited 0, but without running the command.
+
+Also, ssh seems to have decided to take down the shared connection of its
+own accord, which seems strange. Normally it should leave the shared
+connection open.
+
+If you're able to reproduce this reliably, look into whether making
+`sshCachingParams` return [] and thus get rid of this ssh connection caching somehow avoids the problem?
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_6_2798a6806afd2d04cf6c7744ad633133._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_6_2798a6806afd2d04cf6c7744ad633133._comment
new file mode 100644
index 00000000..e07a58f9
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_6_2798a6806afd2d04cf6c7744ad633133._comment
@@ -0,0 +1,13 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 6"
+ date="2015-09-23T11:44:21Z"
+ content="""
+I did the test without the cache system and it was not better (same error message).
+Then I removed /usr/local/propellor and run propellor from scratch-> it worked :)
+
+So now I have a working propellor directory and a non working one.
+I checked that putting back the old /usr/local/propellor cause the same trouble.
+
+If you want I can send you in private both version of the directory.
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment
new file mode 100644
index 00000000..eb951ca6
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_7_dbf3e1aab2a21b796992d959a82b9fc2._comment
@@ -0,0 +1,19 @@
+[[!comment format=mdwn
+ username="joey"
+ subject="""comment 7"""
+ date="2015-09-23T16:52:12Z"
+ content="""
+Ah, that makes much more sense; rather than a strange ssh problem,
+propellor is apparently exiting 0 w/o doing anything when run
+with `./propellor --continue 'SimpleRun "xxx"'` or something close to that.
+
+So, this might have to do with the old propellor not supporting SimpleRun,
+which was added back in 0.4.0.
+
+Or, more likely, it's broken in some way that makes it not do anything when
+asked to so a SimpleRun for a particular host.
+
+You can probably try running the old propellor with that SimpleRun parameter and
+the command line and get a better feel for what it's doing, and if desired,
+bisect or otherwise instrument the program to see why it behaved this way.
+"""]]
diff --git a/doc/forum/Shared_connection_to_xxx_closed./comment_8_cf2215bc51ed57558c76beb5226cf5fa._comment b/doc/forum/Shared_connection_to_xxx_closed./comment_8_cf2215bc51ed57558c76beb5226cf5fa._comment
new file mode 100644
index 00000000..948ccba9
--- /dev/null
+++ b/doc/forum/Shared_connection_to_xxx_closed./comment_8_cf2215bc51ed57558c76beb5226cf5fa._comment
@@ -0,0 +1,26 @@
+[[!comment format=mdwn
+ username="picca"
+ subject="comment 8"
+ date="2015-09-24T08:41:50Z"
+ content="""
+Good
+root@xxxx:/usr/local/propellor.good/dist/build/propellor-config# ls -l
+-rwxr-xr-x 1 root root 6359256 sept. 23 09:34 propellor-config
+drwxr-xr-x 4 root root 4096 sept. 23 09:34 propellor-config-tmp
+
+Bad
+root@xxxx:/usr/local/propellor.bad/dist/build/propellor-config# ls -l
+total 4
+-rwxr-xr-x 1 root root 0 sept. 14 14:05 propellor-config
+drwxr-xr-x 4 root root 4096 sept. 14 14:05 propellor-config-tmp
+
+ok so it seems that propellor-config is empty ??? for the bad version.
+
+Now I understand better why nothing happened :)
+So maybe the power outrage was done during the compilation of the propellor-config executable.
+Maybe something can be done in order to avoid producing this empty file.
+Maybe just keep the old version of propellor-config until the new propellor-config is ready to replace it.
+
+
+
+"""]]