Am Freitag, 12. April 2013, 13:00:22 schrieb Henning Westerholt:
Am Freitag, 12. April 2013, 12:52:17 schrieb Mikko Lehto:
Yesterday I got "fatal: read error: Connection reset by peer" to my "git pull" command. I thought it was only temporary network error, but same problem still exist today.
I can however access other remote git repositories succesfully from the same host.
I just had a look to the server. It works ok, but has a bit high load from the git web access application. I'll configure this a bit more restrictive, that it not cause this high load spikes.
Hello,
I've decreased the runs of the cron runs for the doxygen generation, the load should be much less now. I'll do a few more system maintenance tasks, sip- router.org will be therefore not available for a few minutes. I'll announce when I've finished the maintenance.
Henning
Am Freitag, 12. April 2013, 16:43:29 schrieb Henning Westerholt:
I've decreased the runs of the cron runs for the doxygen generation, the load should be much less now. I'll do a few more system maintenance tasks, sip- router.org will be therefore not available for a few minutes. I'll announce when I've finished the maintenance.
Hello,
sip-router.org is up again, all services should be available.
Best regards,
Henning Westerholt
2013-04-12 (Fri) 16:49 UTC +0200 Henning Westerholt hw@kamailio.org:
sip-router.org is up again, all services should be available.
Thanks, unfortunately still the same:
--- $ git pull fatal: read error: Connection reset by peer $ ---
I noticed Juha Heinänen also reported same on sr-dev.
Anything else I can do or should I just use new clone?
Hello,
try with a new clone and see if it works to pull afterwards.
Otherwise I cannot think of anything else than looking at network traffic to see if something is wrong there.
Cheers, Daniel
On 4/15/13 7:50 AM, Mikko Lehto wrote:
2013-04-12 (Fri) 16:49 UTC +0200 Henning Westerholt hw@kamailio.org:
sip-router.org is up again, all services should be available.
Thanks, unfortunately still the same:
$ git pull fatal: read error: Connection reset by peer $
I noticed Juha Heinänen also reported same on sr-dev.
Anything else I can do or should I just use new clone?
2013-04-15 (Mon) 23:45 UTC +0200 Daniel-Constantin Mierla miconda@gmail.com:
try with a new clone and see if it works to pull afterwards.
Otherwise I cannot think of anything else than looking at network traffic to see if something is wrong there.
New clone seem to pull fine. Maybe we troubleshoot more if this reoccurs.
On 4/19/13 11:43 AM, Mikko Lehto wrote:
2013-04-15 (Mon) 23:45 UTC +0200 Daniel-Constantin Mierla miconda@gmail.com:
try with a new clone and see if it works to pull afterwards.
Otherwise I cannot think of anything else than looking at network traffic to see if something is wrong there.
New clone seem to pull fine. Maybe we troubleshoot more if this reoccurs.
Something was, indeed, I got it in one case -- but no time to look deeper at it so far, a new clone seem to work fine.
Cheers, Daniel