On 08/25/2014 12:58 PM, Dan Johansson wrote:
> On 24.08.2014 23:37, Nikolaus Rath wrote:
>> On 08/24/2014 07:25 AM, Dan Johansson wrote:
>>> Hi All,
>>>
>>> After upgrading to 2.10.1 I encounter the following error each time I
>>> try to do anything (fsck, s3qladm upgrade):
>>>
>>> # /usr/bin/fsck.s3ql --no-ssl --batch s3://abcdef.dmj.nu
>>> Using CONNECT proxy proxy.dmj.nu:8080
>>> Encountered ConnectionError exception (Tunnel connection failed: 403
>>> Forbidden), retrying call to Backend.open_read for the 3-th time...
>>> Encountered ConnectionError exception (Tunnel connection failed: 403
>>> Forbidden), retrying call to Backend.open_read for the 4-th time...
>>>
>>> Running the same command from a second machine (not yet upgraded) works
>>> fine:
>>>
>>> # /usr/bin/fsck.s3ql --no-ssl --batch s3://abcdef.dmj.nu
>>> Starting fsck of s3://test.dmj.nu
>>> Using cached metadata.
>>> Checking DB integrity...
>>> Creating temporary extra indices...
>>> --- 8< ---
>>> Completed fsck of s3://abcdef.dmj.nu
>>>
>>> Both machines are in the same network and use the same proxy.
>>>
>>> What's happening?
>>
>> Looks like you can't connect to the proxy from the first machine. Are
>> you sure you are using this proxy on the second machine? Note the
>> conspicuous absence of the "Using CONNECT proxy proxy.dmj.nu:8080" in
>> your second quoted output.
> 
> I can connect to the proxy allright:
> # wget www.google.com
> --2014-08-25 21:54:29--  http://www.google.com/
> Resolving proxy.dmj.nu (proxy.dmj.nu)... 192.168.1.1
> Connecting to proxy.dmj.nu (proxy.dmj.nu)|192.168.1.1|:8080... connected.
[...]

Not relevant, sorry. wget doesn't use CONNECT proxying.


Best,
-Nikolaus

-- 
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F

             »Time flies like an arrow, fruit flies like a Banana.«

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to