https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #3 from Yaniv Kaul ---
BTW, it doesn't happen on a single host. For example:
https://build.gluster.org/job/smoke/43219/console
23:39:01 Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote
call to
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #6 from M. Scherer ---
And it happen since a long time too, so unlikely to be the upgrade, if the
error in the log is the same as the one reported.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugzilla.redhat.com/show_bug.cgi?id=1564149
Worker Ant changed:
What|Removed |Added
Status|NEW |POST
--- Comment #35 from Worker Ant
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #8 from M. Scherer ---
yeah, I wanted to explore that road too by doing *cough* load testing of the
git server on the staging env, but no git port (or I am not awake enough).
--
You are receiving this mail because:
You are on
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
M. Scherer changed:
What|Removed |Added
CC||msche...@redhat.com
--- Comment #4 from
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #9 from Yaniv Kaul ---
(In reply to Yaniv Kaul from comment #7)
> (In reply to M. Scherer from comment #4)
> > So not wanting to say network is perfect, but this started since the upgrade
> > to new gerrit, no ? Could it be some
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #7 from Yaniv Kaul ---
(In reply to M. Scherer from comment #4)
> So not wanting to say network is perfect, but this started since the upgrade
> to new gerrit, no ? Could it be some issue where gerrit drop if there is too
> much
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #5 from M. Scherer ---
[root@gerrit-new logs]# grep 'reset by peer' error_log |wc -l
18
Seems it happen quite often :/
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #10 from M. Scherer ---
I did and didn't found anything that did seemed relevant. I may have missed
something however, and Nigel is also looking. That's a transient issue, so not
easy to diagnose.
--
You are receiving this mail
https://bugzilla.redhat.com/show_bug.cgi?id=1620243
Vijay Bellur changed:
What|Removed |Added
CC||vbel...@redhat.com
--- Comment #1
https://bugzilla.redhat.com/show_bug.cgi?id=1620243
M. Scherer changed:
What|Removed |Added
CC||msche...@redhat.com
--- Comment #2 from
https://bugzilla.redhat.com/show_bug.cgi?id=1620358
Bug ID: 1620358
Summary: smoke job failures
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Assignee: b...@gluster.org
Reporter: atumb...@redhat.com
One more piece that's missing is when we'll restart the physical servers.
That seems to be entirely missing. The rest looks good to me and I'm happy
to add an item to next sprint to automate the node rebooting.
On Tue, Aug 21, 2018 at 9:56 PM Michael Scherer wrote:
> Hi,
>
> so that's kernel
https://bugzilla.redhat.com/show_bug.cgi?id=1620377
Bhumika Goyal changed:
What|Removed |Added
Summary|Coverity scan setup for |Coverity scan setup for
https://bugzilla.redhat.com/show_bug.cgi?id=1620358
Nigel Babu changed:
What|Removed |Added
CC||nig...@redhat.com
--- Comment #1 from
https://bugzilla.redhat.com/show_bug.cgi?id=1620377
Bug ID: 1620377
Summary: Coverity scan setup for gluster-block and realated
projects
Product: GlusterFS
Version: 3.12
Component: project-infrastructure
Assignee:
https://bugzilla.redhat.com/show_bug.cgi?id=1620243
--- Comment #3 from M. Scherer ---
So Nigel did restart Gerrit, and this seems to be working now.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #13 from M. Scherer ---
So I pushed a fix, should deploy (unless the wifi break in my train).
So the good news is that we can claim that we did made so more productivity
progress that we did hit the limit, so that's positive :p
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #11 from M. Scherer ---
So, Nigel pointed out that git is done by xinetd, and the log show nothing
except some ipv6 errors. While it might be related, i think it is not,
especially since taht's only for the rackspace builder, not
https://bugzilla.redhat.com/show_bug.cgi?id=1619838
--- Comment #12 from M. Scherer ---
Mhhh:
août 21 20:39:36 gerrit-new.rht.gluster.org xinetd[16437]: FAIL: git
per_source_limit from=:::8.43.85.181
Suspect that it might be the cause. 8.43.85.181 is the firewall ip.
Several solution:
-
https://bugzilla.redhat.com/show_bug.cgi?id=1620243
Bug ID: 1620243
Summary: Gerrit is non-responsive (503)
Product: GlusterFS
Version: mainline
Component: project-infrastructure
Severity: urgent
Assignee: b...@gluster.org
21 matches
Mail list logo
