patchwork.ipfire.org didn't get last two patches

patchwork.ipfire.org didn't get last two patches

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 220 bytes --]

Hi,

my last two commits, sent with "git send-email ..." (and pushed) don't
show up on patchwork.ipfire.org.

Sending to development list is OK, but nothing can be seen on patchwork.

Can anyone confirm?

Best,
Matthias

Re: patchwork.ipfire.org didn't get last two patches

[ummeegge]

[-- Attachment #1: Type: text/plain, Size: 475 bytes --]

Hi Matthias,
did send also two patches but the last entry in Patchwork is the Squid
update from 2018-07-17 . So yes i can confirm it here too.

Greetings,

Erik
 
Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
> Hi,
> 
> my last two commits, sent with "git send-email ..." (and pushed)
> don't
> show up on patchwork.ipfire.org.
> 
> Sending to development list is OK, but nothing can be seen on
> patchwork.
> 
> Can anyone confirm?
> 
> Best,
> Matthias

Re: patchwork.ipfire.org didn't get last two patches

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 791 bytes --]

Thanks for letting me know.

I just spent two hours to debug this fe**cking thing. It was a
configuration issue that was caused by the migration.

It's working again and I manually imported the patches.

Best,
-Michael

On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
> Hi Matthias,
> did send also two patches but the last entry in Patchwork is the Squid
> update from 2018-07-17 . So yes i can confirm it here too.
> 
> Greetings,
> 
> Erik
>  
> Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
> > Hi,
> > 
> > my last two commits, sent with "git send-email ..." (and pushed)
> > don't
> > show up on patchwork.ipfire.org.
> > 
> > Sending to development list is OK, but nothing can be seen on
> > patchwork.
> > 
> > Can anyone confirm?
> > 
> > Best,
> > Matthias

Re: patchwork.ipfire.org didn't get last two patches

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 932 bytes --]

And this at these temperatures...

Thanks! :-)

On 04.08.2018 15:54, Michael Tremer wrote:
> Thanks for letting me know.
> 
> I just spent two hours to debug this fe**cking thing. It was a
> configuration issue that was caused by the migration.
> 
> It's working again and I manually imported the patches.
> 
> Best,
> -Michael
> 
> On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
>> Hi Matthias,
>> did send also two patches but the last entry in Patchwork is the Squid
>> update from 2018-07-17 . So yes i can confirm it here too.
>> 
>> Greetings,
>> 
>> Erik
>>  
>> Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
>> > Hi,
>> > 
>> > my last two commits, sent with "git send-email ..." (and pushed)
>> > don't
>> > show up on patchwork.ipfire.org.
>> > 
>> > Sending to development list is OK, but nothing can be seen on
>> > patchwork.
>> > 
>> > Can anyone confirm?
>> > 
>> > Best,
>> > Matthias
> 
> 

Re: patchwork.ipfire.org didn't get last two patches

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]

It's lovely isn't it?

On Sat, 2018-08-04 at 18:04 +0200, Matthias Fischer wrote:
> And this at these temperatures...
> 
> Thanks! :-)
> 
> On 04.08.2018 15:54, Michael Tremer wrote:
> > Thanks for letting me know.
> > 
> > I just spent two hours to debug this fe**cking thing. It was a
> > configuration issue that was caused by the migration.
> > 
> > It's working again and I manually imported the patches.
> > 
> > Best,
> > -Michael
> > 
> > On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
> > > Hi Matthias,
> > > did send also two patches but the last entry in Patchwork is the Squid
> > > update from 2018-07-17 . So yes i can confirm it here too.
> > > 
> > > Greetings,
> > > 
> > > Erik
> > >  
> > > Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
> > > > Hi,
> > > > 
> > > > my last two commits, sent with "git send-email ..." (and pushed)
> > > > don't
> > > > show up on patchwork.ipfire.org.
> > > > 
> > > > Sending to development list is OK, but nothing can be seen on
> > > > patchwork.
> > > > 
> > > > Can anyone confirm?
> > > > 
> > > > Best,
> > > > Matthias
> > 
> > 
> 
> 

Re: patchwork.ipfire.org didn't get last two patches

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1264 bytes --]


On 04.08.2018 19:58, Michael Tremer wrote:
> It's lovely isn't it?

Hu!?

You're sitting in a fridge, right? ;-)

> On Sat, 2018-08-04 at 18:04 +0200, Matthias Fischer wrote:
>> And this at these temperatures...
>> 
>> Thanks! :-)
>> 
>> On 04.08.2018 15:54, Michael Tremer wrote:
>> > Thanks for letting me know.
>> > 
>> > I just spent two hours to debug this fe**cking thing. It was a
>> > configuration issue that was caused by the migration.
>> > 
>> > It's working again and I manually imported the patches.
>> > 
>> > Best,
>> > -Michael
>> > 
>> > On Sat, 2018-08-04 at 13:57 +0200, ummeegge wrote:
>> > > Hi Matthias,
>> > > did send also two patches but the last entry in Patchwork is the Squid
>> > > update from 2018-07-17 . So yes i can confirm it here too.
>> > > 
>> > > Greetings,
>> > > 
>> > > Erik
>> > >  
>> > > Am Samstag, den 04.08.2018, 10:00 +0200 schrieb Matthias Fischer:
>> > > > Hi,
>> > > > 
>> > > > my last two commits, sent with "git send-email ..." (and pushed)
>> > > > don't
>> > > > show up on patchwork.ipfire.org.
>> > > > 
>> > > > Sending to development list is OK, but nothing can be seen on
>> > > > patchwork.
>> > > > 
>> > > > Can anyone confirm?
>> > > > 
>> > > > Best,
>> > > > Matthias
>> > 
>> > 
>> 
>> 
> 
> 

git.ipfire =>very slow loading (was: Re: patchwork.ipfire.org didn't get last two patches)

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 342 bytes --]

On 04.08.2018 15:54, Michael Tremer wrote:
> I just spent two hours to debug this fe**cking thing. It was a
> configuration issue that was caused by the migration.

Besides, since a few days loading git.ipfire.org takes about 15-20
seconds. FF shows "Transferring data from git.ipfire.org" and nothing
happens...

Migration!?

Best,
Matthias

Re: git.ipfire =>very slow loading (was: Re: patchwork.ipfire.org didn't get last two patches)

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]

Errr, no. This is not migrating any more, but has been migrated.

Since we are having some things we can do better with our many web
servers, I started using haproxy on our primary firewall and everything
else is now being proxies from there to the right internal server.

That means, that the git repositories are now coming directly from the
server where they are hosted and are not being transferred over NFS
first. Same goes for downloads. That puts quite a bit less load on the
servers and makes the downloads slightly faster.

I also moved Gitweb to a new server which is now running Apache and not
nginx any more. However, apache doesn't correctly cache the index page.
I don't know why that is, but it is just being stupid. Hence the slight
delay to render the page.

Best,
-Michael

On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
> On 04.08.2018 15:54, Michael Tremer wrote:
> > I just spent two hours to debug this fe**cking thing. It was a
> > configuration issue that was caused by the migration.
> 
> Besides, since a few days loading git.ipfire.org takes about 15-20
> seconds. FF shows "Transferring data from git.ipfire.org" and nothing
> happens...
> 
> Migration!?
> 
> Best,
> Matthias

Re: git.ipfire =>very slow loading

[Matthias Fischer]

[-- Attachment #1: Type: text/plain, Size: 1661 bytes --]

Hi,

On 05.08.2018 12:24, Michael Tremer wrote:
> Errr, no. This is not migrating any more, but has been migrated.

As it seems - it migrated "very far away".

First try gives me:

...
XML Parsing Error: no root element found Location:
https://git.ipfire.org/ Line Number 27, Column 1:

^
...

Second try:
A white page with "git://git.ipfire.org" and a project search box.

Third try:
Same as first: "XML Parsing error..."

Any one else?

Best,
Matthias

> Since we are having some things we can do better with our many web
> servers, I started using haproxy on our primary firewall and everything
> else is now being proxies from there to the right internal server.
> 
> That means, that the git repositories are now coming directly from the
> server where they are hosted and are not being transferred over NFS
> first. Same goes for downloads. That puts quite a bit less load on the
> servers and makes the downloads slightly faster.
> 
> I also moved Gitweb to a new server which is now running Apache and not
> nginx any more. However, apache doesn't correctly cache the index page.
> I don't know why that is, but it is just being stupid. Hence the slight
> delay to render the page.
> 
> Best,
> -Michael
> 
> On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
>> On 04.08.2018 15:54, Michael Tremer wrote:
>> > I just spent two hours to debug this fe**cking thing. It was a
>> > configuration issue that was caused by the migration.
>> 
>> Besides, since a few days loading git.ipfire.org takes about 15-20
>> seconds. FF shows "Transferring data from git.ipfire.org" and nothing
>> happens...
>> 
>> Migration!?
>> 
>> Best,
>> Matthias
> 
> 

Re: git.ipfire =>very slow loading

[Peter Müller]

[-- Attachment #1: Type: text/plain, Size: 1911 bytes --]

Hello,

same here... Sometimes with, sometimes without an XML parsing error.

Best regards,
Peter Müller
> Hi,
> 
> On 05.08.2018 12:24, Michael Tremer wrote:
>> Errr, no. This is not migrating any more, but has been migrated.
> 
> As it seems - it migrated "very far away".
> 
> First try gives me:
> 
> ...
> XML Parsing Error: no root element found Location:
> https://git.ipfire.org/ Line Number 27, Column 1:
> 
> ^
> ...
> 
> Second try:
> A white page with "git://git.ipfire.org" and a project search box.
> 
> Third try:
> Same as first: "XML Parsing error..."
> 
> Any one else?
> 
> Best,
> Matthias
> 
>> Since we are having some things we can do better with our many web
>> servers, I started using haproxy on our primary firewall and everything
>> else is now being proxies from there to the right internal server.
>>
>> That means, that the git repositories are now coming directly from the
>> server where they are hosted and are not being transferred over NFS
>> first. Same goes for downloads. That puts quite a bit less load on the
>> servers and makes the downloads slightly faster.
>>
>> I also moved Gitweb to a new server which is now running Apache and not
>> nginx any more. However, apache doesn't correctly cache the index page.
>> I don't know why that is, but it is just being stupid. Hence the slight
>> delay to render the page.
>>
>> Best,
>> -Michael
>>
>> On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
>>> On 04.08.2018 15:54, Michael Tremer wrote:
>>>> I just spent two hours to debug this fe**cking thing. It was a
>>>> configuration issue that was caused by the migration.
>>>
>>> Besides, since a few days loading git.ipfire.org takes about 15-20
>>> seconds. FF shows "Transferring data from git.ipfire.org" and nothing
>>> happens...
>>>
>>> Migration!?
>>>
>>> Best,
>>> Matthias
>>
>>
> 

-- 
"We don't care.  We don't have to.  We're the Phone Company."


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

Re: git.ipfire =>very slow loading

[Michael Tremer]

[-- Attachment #1: Type: text/plain, Size: 3084 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

I created a ticket to have a look at it later:

  https://bugzilla.ipfire.org/show_bug.cgi?id=11818

- -Michael

On Sun, 2018-08-12 at 09:10 +0200, Peter Müller wrote:
> Hello,
> 
> same here... Sometimes with, sometimes without an XML parsing error.
> 
> Best regards,
> Peter Müller
> > Hi,
> > 
> > On 05.08.2018 12:24, Michael Tremer wrote:
> > > Errr, no. This is not migrating any more, but has been migrated.
> > 
> > As it seems - it migrated "very far away".
> > 
> > First try gives me:
> > 
> > ...
> > XML Parsing Error: no root element found Location:
> > https://git.ipfire.org/ Line Number 27, Column 1:
> > 
> > ^
> > ...
> > 
> > Second try:
> > A white page with "git://git.ipfire.org" and a project search box.
> > 
> > Third try:
> > Same as first: "XML Parsing error..."
> > 
> > Any one else?
> > 
> > Best,
> > Matthias
> > 
> > > Since we are having some things we can do better with our many web
> > > servers, I started using haproxy on our primary firewall and everything
> > > else is now being proxies from there to the right internal server.
> > > 
> > > That means, that the git repositories are now coming directly from the
> > > server where they are hosted and are not being transferred over NFS
> > > first. Same goes for downloads. That puts quite a bit less load on the
> > > servers and makes the downloads slightly faster.
> > > 
> > > I also moved Gitweb to a new server which is now running Apache and not
> > > nginx any more. However, apache doesn't correctly cache the index page.
> > > I don't know why that is, but it is just being stupid. Hence the slight
> > > delay to render the page.
> > > 
> > > Best,
> > > -Michael
> > > 
> > > On Sat, 2018-08-04 at 21:39 +0200, Matthias Fischer wrote:
> > > > On 04.08.2018 15:54, Michael Tremer wrote:
> > > > > I just spent two hours to debug this fe**cking thing. It was a
> > > > > configuration issue that was caused by the migration.
> > > > 
> > > > Besides, since a few days loading git.ipfire.org takes about 15-20
> > > > seconds. FF shows "Transferring data from git.ipfire.org" and nothing
> > > > happens...
> > > > 
> > > > Migration!?
> > > > 
> > > > Best,
> > > > Matthias
> > > 
> > > 
> 
> 
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEE5/rW5l3GGe2ypktxgHnw/2+QCQcFAltz5aAACgkQgHnw/2+Q
CQekFA//V8LYupgPNjIiyhrFndtGQgmUeT+wN+quLdQDN5rB14IwLKDlmHzRfXlr
mCEDT7Z02ejLo/FAUlvn946iX6uF/qibhO6UQ0OG0Xe2c3vMEYfJM9toKnN7Ghhk
9M3wEtawliV0+qNTTfc/0RsJbcTJQB0GaQory4e7zuFCL0oQslq6UODIzqQGkMl5
x3Uqg7vrKXeETpHeI94ktKsD0znEH44ih9pvdB6+KqvzGBVqmnan4LxgGOdboAYW
j363TCM95vFbiS2CxC9wUwsb3A9eHDT6acg+grDDt/aA4v6AIcSh0z+4aJppDTXZ
+YcAuklRaXW9XAPTPn58Mjx6IYMJvKfdGlJpRTNkCWOMuAzNuVfPmf88GcWAqKdj
08kTPa42YAqqoilv/vsasmowgel2Ze7VsQ1tCPYzSmdHoeSM42YY482nOcWjnhu8
Cb6U0VEami1OT9pSoXwVYgwpFOYchFAcsIynReJdkbX+lZk5jfh9zwJQmS9kYYD3
k4dZ00IjHahhRIh8mYz//19Q1NrAmPCT7peX2EeENKsfTlo/qMHLLCrUPP8LSHO9
l0rPp0MHWbtqGsgpRvR0KK8jYvuuzzPDC5HSLQZTyshiMck9BmNEqeWFtzI4cp/o
8ygw4J6qWk2DLei7AG6I+SzXvB7FHmI3gSEOqwyze+Oh6NtQwxM=
=VrTQ
-----END PGP SIGNATURE-----