Hello,
Any ideas why:
marius@marius:~/dev/sip-router$ git pull --rebase ssh: connect to host git.sip-router.org port 22: Connection timed out fatal: The remote end hung up unexpectedly
marius@marius:~/dev/sip-router$ ping git.sip-router.org PING git.sip-router.org (78.46.218.34) 56(84) bytes of data. ^C --- git.sip-router.org ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3025ms
Seems the host is down :(
Marius
On Monday 12 September 2011, marius zbihlei wrote:
Any ideas why:
marius@marius:~/dev/sip-router$ git pull --rebase ssh: connect to host git.sip-router.org port 22: Connection timed out fatal: The remote end hung up unexpectedly
marius@marius:~/dev/sip-router$ ping git.sip-router.org PING git.sip-router.org (78.46.218.34) 56(84) bytes of data. ^C --- git.sip-router.org ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3025ms
Seems the host is down :(
Hi marius,
indeed, i just started to look into it.
Best regards,
Henning
On Monday 12 September 2011, Henning Westerholt wrote:
Seems the host is down :(
indeed, i just started to look into it.
Should be back online. Please report if you encounter any further issues.
The server just went down again, investigating at the moment.
Best regards,
Henning
On Monday 12 September 2011, Henning Westerholt wrote:
Seems the host is down :(
indeed, i just started to look into it.
Should be back online. Please report if you encounter any further issues.
The server just went down again, investigating at the moment.
As you probably already noticed, the server is now available again (since yesterday evening). The reason for the outtage was a hardware failure, the replacement and subsequent smaller adaptions of the configuration took some time.
Henning
Hello,
On 9/13/11 12:16 PM, Henning Westerholt wrote:
On Monday 12 September 2011, Henning Westerholt wrote:
Seems the host is down :(
indeed, i just started to look into it.
Should be back online. Please report if you encounter any further issues.
The server just went down again, investigating at the moment.
As you probably already noticed, the server is now available again (since yesterday evening). The reason for the outtage was a hardware failure, the replacement and subsequent smaller adaptions of the configuration took some time.
thanks for sorting all out!
Cheers, Daniel
-
Daniel-Constantin Mierla -
Henning Westerholt -
marius zbihlei