summaryrefslogtreecommitdiff
path: root/doc/todo/spin_failure_HEAD.mdwn
blob: 39b64cbdecc9ad5d2b24636e9b949292eaece1ee (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
Seen recently on 2 hosts:

	Sending privdata (73139 bytes) to kite.kitenet.net ... done
	fatal: Couldn't find remote ref HEAD
	propellor: <stdout>: hPutStr: illegal operation (handle is closed)
	fatal: The remote end hung up unexpectedly
	Sending git update to kite.kitenet.net ... failed

Despite the error, HEAD seems to be updated to the commit that is being spun,
but the rest of the propellor runs doesn't happen. --[[Joey]]

> This was happening spinning kite at my Mom's, but not from home.

> Earlier, it was happening spinning clam from home, when clam had debian
> oldstable on it (new install).
> 
> So, transient and/or network-related.. --[[Joey]]

> > Happening again spinning kite over satelite, but not other hosts. 
> > I enabled propellor.debug, and here's what it showed on kite:

	Sending privdata (73139 bytes) to kite.kitenet.net ... done
	[2017-06-18 16:01:08 EDT] received marked PRIVDATA 
	[2017-06-18 16:01:08 EDT] requested marked GITPUSH
	[2017-06-18 16:01:11 EDT] received marked GITPUSH
	[2017-06-18 16:01:11 EDT] command line:  GitPush 11 12
	fatal: Couldn't find remote ref HEAD
	propellor: <stdout>: hPutStr: illegal operation (handle is closed)
	fatal: The remote end hung up unexpectedly
	Sending git update to kite.kitenet.net ... failed

> > Seem that what's failing is "git fetch" when propellor
> > runs it with --upload-pack used to run propellor --gitpush.
> > 
> > The "fatal: Couldn't find remote ref HEAD" comes from git fetch,
> > I think when no HEAD is in the list of remote refs.
> > 
> > The hPutStr error was a red herring; errorMessage was using
> > outputConcurrent. After I fixed it to use errorConcurrent,
> > it displayed the "git fetch from client failed" error message instead.
> > 
> > Next step is probably to enable `GIT_TRACE_PACKET` debugging.
> > I did so on kite, but then propellor --spin succeeded.
> > Here's the debug output I got when it worked, for later comparison
> > next time it fails. Note the HEAD ref is given first thing.

<pre>
Sending privdata (73139 bytes) to kite.kitenet.net ... done
[2017-06-18 16:27:12 EDT] received marked PRIVDATA 
[2017-06-18 16:27:12 EDT] requested marked GITPUSH
[2017-06-18 16:27:13 EDT] received marked GITPUSH
[2017-06-18 16:27:13 EDT] command line:  GitPush 11 12
16:27:13.953638 pkt-line.c:80           packet:        fetch< 3a3c8a731d169a2768dd243581803dcb7b275049 HEAD\0multi_ack thin-pack side-band side-band-64k ofs-delta shallow deepen-since deepen-not deepen-relative no-progress include-tag multi_ack_detailed symref=HEAD:refs/heads/joeyconfig agent=git/2.11.0
(omitted 364 lines of refs)
16:27:14.352945 pkt-line.c:80           packet:        fetch< 0000
From .
 * branch              HEAD       -> FETCH_HEAD
16:27:14.379922 pkt-line.c:80           packet:        fetch> 0000
Sending git update to kite.kitenet.net ... done
</pre>