action #165617
closed
[alert] openqa-trigger-from-obs pull: RPC failed, expected flush after ref listing size:S
Added by jbaier_cz 3 months ago.
Updated 3 months ago.
Description
Observation¶
E-mail notification from ariel (cron)
Cron <geekotest@ariel> git -C /opt/openqa-trigger-from-obs pull --quiet --rebase origin master
error: RPC failed; curl 18 Transferred a partial file
fatal: expected flush after ref listing
Suggestions¶
- Do some research on the error message
- Retry if nothing else works
- Subject changed from [alert] openqa-trigger-from-obs pull: RPC failed, expected flush after ref listing to [alert] openqa-trigger-from-obs pull: RPC failed, expected flush after ref listing size:S
- Description updated (diff)
- Status changed from New to Workable
- Status changed from Workable to Resolved
- Assignee set to livdywan
Based on what I've read it seems these two settings should help avoid this:
git config --global http.postBuffer 524288000
git config --global http.version HTTP/1.1
Both of which I've run on o3 now. And I guess adding retry is easy enough so I updated the command in /etc/cron.d/openqa-trigger-from-obs-update-git to:
-*/3 * * * * geekotest retry -- git -C /opt/openqa-trigger-from-obs pull --quiet --rebase origin master
livdywan wrote in #note-2:
And I guess adding retry is easy enough so I updated the command in /etc/cron.d/openqa-trigger-from-obs-update-git to:
-*/3 * * * * geekotest retry -- git -C /opt/openqa-trigger-from-obs pull --quiet --rebase origin master
If I read the crontab correctly, that command is running every 3 minutes, now in case of problems it will retry 3 times after 3 seconds every 3 minutes :) Afaik, this will still send a mail even after the first failure as the retry is generating output and the mail will be issued if there is any output, so maybe the retry here is not so useful.
-*/3 * * * * geekotest retry -- git -C /opt/openqa-trigger-from-obs pull --quiet --rebase origin master
If I read the crontab correctly, that command is running every 3 minutes, now in case of problems it will retry 3 times after 3 seconds every 3 minutes :) Afaik, this will still send a mail even after the first failure as the retry is generating output and the mail will be issued if there is any output, so maybe the retry here is not so useful.
Fair point. I removed the retry again.
- Status changed from Resolved to Workable
Feels like this needs to be revisited. Not sure if it means the setting was reverted or it was ineffective:
fatal: unable to access 'https://github.com/os-autoinst/os-autoinst-needles-openQA/': HTTP/2 stream 1 was not closed cleanly before end of the underlying connection
livdywan wrote in #note-2:
Based on what I've read it seems these two settings should help avoid this:
git config --global http.postBuffer 524288000
git config --global http.version HTTP/1.1
Both of which I've run on o3 now.
Hm, as which user did you do this? The .gitconfig of geekotest has a timestamp of 2016
Hm, as which user did you do this? The .gitconfig of geekotest has a timestamp of 2016
Seems like I mixed up --global and --system so it was only applied for my user rather than the default for all users (c.f. 8.1 Customizing Git - Git Configuration). I couldn't find a way to verify the effective configuration but git config --get --global http.version is empty for geekotest at least.
So this time I applied this:
git config --system http.version 524288000
git config --system http.version HTTP/1.1
su geekotest
git config --get --global http.postBuffer
524288000
git config --get --system http.version
HTTP/1.1
- Status changed from Workable to Feedback
So this time I applied this:
And please don't mind the errors in recent emails. The cron jobs are running very often and I was not quick enough to fix it to avoid those but my previous comment holds true 😉
- Status changed from Feedback to Resolved
I think we no longer see related errors so I'm resolving this again.
Seems like I mixed up --global and --system so it was only applied for my user rather than the default for all users (c.f. 8.1 Customizing Git - Git Configuration). I couldn't find a way to verify the effective configuration but git config --get --global http.version is empty for geekotest at least.
For future reference: git config http.version works to check the effective configuration and shows the expected values for geekotest. Not sure how I ended up thinking this wouldn't work.
Also available in: Atom
PDF