couldn't reach oberon: error(111, 'Connection refused')
I've just tried to push to my repo {{{ basti@phoenix:~/src/python-amazon-product-api/tests$ hg push Übertrage nach https://basti@bitbucket.org/basti/python-amazon-product-api/ Suche nach Änderungen HTTP-Autorisation benötigt Bereich: Bitbucket.org HTTP Benutzer: basti Passwort: adding changesets adding manifests adding file changes added 1 changesets with 34 changes to 34 files bb/acl: basti is allowed. accepted payload. couldn't reach oberon: error(111, 'Connection refused') couldn't reach oberon: error(111, 'Connection refused') }}}
Trying immediately afterwards again workd fine {{{ basti@phoenix:~/src/python-amazon-product-api/tests$ hg push Übertrage nach https://basti@bitbucket.org/basti/python-amazon-product-api/ Suche nach Änderungen Keine Änderungen gefunden
basti@phoenix:~/src/python-amazon-product-api/tests$ date -R Wed, 09 Jun 2010 09:23:10 +0200 }}}
Comments (27)
-
-
- changed component to repository
Same issue just now when pushing to repository: http authorization required realm: Bitbucket.org HTTP user: SSveS_Editor pushing to https://xxxxxx@bitbucket.org/xxxxxx/xxxxxx searching for changes 2 changesets found remote: adding changesets remote: adding manifests remote: adding file changes remote: added 2 changesets with 176 changes to 175 files remote: bb/acl: SSveS_Editor is allowed. accepted payload. remote: couldn't reach oberon: error(111, 'Connection refused') [command completed successfully Wed Jul 21 15:49:55 2010]
A subsequent push yielded "no changes found"
[edit]Why are linebreaks removed ?[/edit]
-
Bump!
-
We see this too - anybody know why we get these Oberon connection failed messages?
-
Same quirky message here... Doesn't seem to affect the push though.
-
Issue
#2068was marked as a duplicate of this issue. -
Issue
#2040was marked as a duplicate of this issue. -
Issue
#1976was marked as a duplicate of this issue. -
Issue
#1961was marked as a duplicate of this issue. -
- changed status to open
-
I get the same message sometimes, and whenever I get this message, my Email and Email Diff services don't work for that push.
-
Bump!
-
Has this been spotted in the wild recently?
-
Just got this message, however it seems that pushing was successful.
-
- changed status to resolved
Should be gone now.
-
Isn't gone. Just got the same message a moment ago.
-
- changed status to open
┌─(leleobhz@astra Ter, 24 Ago 10)─(/home/leleobhz/Documentos/USP/Public_Repo_HG)──(11:17)─> hg push executando ssh bitbucket "hg -R leleobhz/usp_files serve --stdio" Enter passphrase for key '/home/leleobhz/.ssh/id_rsa': enviando revisões para ssh:bitbucket/leleobhz/usp_files procurando por mudanças 1 revisões encontradas remoto: adding changesets remoto: adding manifests remoto: adding file changes remoto: added 1 changesets with 1 changes to 1 files remoto: bb/acl: leleobhz is allowed. accepted payload. remoto: couldn't reach oberon: error(111, 'Connection refused') remoto: couldn't reach oberon: error(111, 'Connection refused') remoto: couldn't reach oberon: error(111, 'Connection refused')
Its still here.
-
Same for me some minutes ago. My change didn't appear on the issue tracker.
-
Bump!
-
pushing to https://mahcuz:***@bitbucket.org/mahcuz/win-gdi searching for changes remote: adding changesets remote: adding manifests remote: adding file changes remote: added 2 changesets with 4 changes to 4 files remote: bb/acl: mahcuz is allowed. accepted payload. remote: couldn't reach oberon: error(111, 'Connection refused')
Just got this a minute ago.
-
pushing to https://dcarrigg:***@bitbucket.org/dcarrigg/retroaffect searching for changes 6 changesets found remote: adding changesets remote: adding manifests remote: adding file changes remote: added 6 changesets with 8 changes to 7 files remote: bb/acl: dcarrigg is allowed. accepted payload. remote: couldn't reach oberon: error(111, 'Connection refused') remote: couldn't reach oberon: error(111, 'Connection refused')
Just got the same error message.
-
Also receiving the same error message on every push: couldn't reach oberon: error(111, 'Connection refused')
-
here as well; from the help I understand that oberon is the service integration daemon, which would explain why my issue tracker and email diff aren't working on a push. Is there any fix for this yet?
-
Not yet. Fix coming.
-
- changed status to resolved
Fix rolled out. Batch script to fix all repos running, T-10 minutes.
-
Issue
#2134was marked as a duplicate of this issue. -
- removed component
Removing component: repository (automated comment)
- Log in to comment
I've met the same problem recently. Is Oberon the message bus of bitbucket?