List Info

Thread: emerge sync not working




emerge sync not working
user name
2006-04-04 13:23:01
I want to use `emerge sync` instead of `emerge-websync` but
`emerge 
sync` not working.

Here is output after `emerge sync`

 >>> starting rsync with
rsync://137.226.34.228/gentoo-portage...
 >>> checking server timestamp ...
rsync: failed to connect to 137.226.34.228: Connection timed
out
rsync error: error in socket IO (code 10) at
clientserver.c(88)
 >>> retry ...



The computer is posing as firewall.
OUTPUT firewall policy is set to ACCEPT (even FORWARD policy
has 
873/tcp, 873/udp enabled).

I've been trying different rsync servers (I got
confirmation that one I 
used is properly working).



emerge sync not working
user name
2006-04-04 15:35:10
On Tue, Apr 04, 2006 at 03:23:01PM +0200 or thereabouts,
Mari?n Hercek wrote:
> The computer is posing as firewall.
> OUTPUT firewall policy is set to ACCEPT (even FORWARD
policy has 
> 873/tcp, 873/udp enabled).

Drop the firewall temporarily.  Does 'emerge sync' now
work?  If so, go fix
your firewall scripts.

--kurt
emerge sync not working
user name
2006-04-05 04:55:38
I did drop firewall many times, but no effect.

Here is another output:

 >>> starting rsync with
rsync://140.105.134.102/gentoo-portage...
 >>> checking server timestamp ...
rsync: failed to connect to 140.105.134.102: Connection
timed out
rsync error: error in socket IO (code 10) at
clientserver.c(88)
 >>> retry ...

 >>> Starting retry 1 of 3 with
rsync://137.226.34.228/gentoo-portage
 >>> checking server timestamp ...


As you can see, `emerge sync` tries different rsync servers
(they should 
be up and running).

`emerge sync` hangs for awhile when "checking server
timestamp ..."

Kurt Lieber wrote:
> On Tue, Apr 04, 2006 at 03:23:01PM +0200 or
thereabouts, Mari?n Hercek wrote:
>> The computer is posing as firewall.
>> OUTPUT firewall policy is set to ACCEPT (even
FORWARD policy has 
>> 873/tcp, 873/udp enabled).
> 
> Drop the firewall temporarily.  Does 'emerge sync'
now work?  If so, go fix
> your firewall scripts.
> 
> --kurt
emerge sync not working
user name
2006-04-05 06:38:07
Marián Hercek <hercekstudent.ucm.sk> said:
> I did drop firewall many times, but no effect.

hhm, i'd still say it is most likely your firewall (or a
firewall between 
you and the net)

give us the ouput of iptables -L, if you like...

regards
Thilo
emerge sync not working
user name
2006-04-05 07:21:51
Here it is:

Chain INPUT (policy DROP)
target     prot opt source               destination
ACCEPT     tcp  --  0.0.0.0/0            193.87.59.9        
tcp dpt:25
ACCEPT     tcp  --  0.0.0.0/0            193.87.59.9        
tcp dpt:20
ACCEPT     tcp  --  0.0.0.0/0            193.87.59.9        
tcp dpt:21
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0          
tcp dpt:80
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0          
tcp dpt:143
ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0          
tcp dpt:443
--some snipped out---

Chain FORWARD (policy DROP)
ACCEPT     udp  --  192.168.1.0/24       0.0.0.0/0          
udp dpt:53
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:20
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:21
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:80
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:110
ACCEPT     udp  --  192.168.1.0/24       0.0.0.0/0          
udp dpt:110
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:123
ACCEPT     udp  --  192.168.1.0/24       0.0.0.0/0          
udp dpt:123
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:443
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:873
ACCEPT     udp  --  192.168.1.0/24       0.0.0.0/0          
udp dpt:873
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:993
ACCEPT     udp  --  192.168.1.0/24       0.0.0.0/0          
udp dpt:993
ACCEPT     tcp  --  192.168.1.0/24       0.0.0.0/0          
tcp dpt:995
ACCEPT     udp  --  192.168.1.0/24       0.0.0.0/0          
udp dpt:995
--some snipped out---

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

------------------------------------------------------------
-------------
Table NAT

Chain PREROUTING (policy ACCEPT)
target     prot opt source               destination

Chain POSTROUTING (policy ACCEPT)
target     prot opt source               destination
SNAT       all  --  192.168.1.0/24       anywhere    
to:--snipped out

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination


Thilo Bangert wrote:
> Marián Hercek <hercekstudent.ucm.sk> said:
>> I did drop firewall many times, but no effect.
> 
> hhm, i'd still say it is most likely your firewall (or
a firewall between 
> you and the net)
> 
> give us the ouput of iptables -L, if you like...
> 
> regards
> Thilo
emerge sync not working
user name
2006-04-05 07:42:55


On 4/5/06, Marián Hercek <student.ucm.sk">hercekstudent.ucm.sk> wrote:
Here it is:

Chain INPUT (policy DROP)
target &nbsp; &nbsp; prot opt source&nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; destination
ACCEPT&nbsp; &nbsp;  tcp &nbsp;--&nbsp; 0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp;  193.87.59.9 &nbsp; &nbsp; &nbsp;   tcp dpt:25
ACCEPT &nbsp;   tcp &nbsp;--&nbsp; 0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp;  193.87.59.9 &nbsp; &nbsp; &nbsp;   tcp dpt:20
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp; 0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp;   193.87.59.9 &nbsp; &nbsp;   ;  tcp dpt:21
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp; 0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:80
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp;  0.0.0.0/0 &nbsp; &nbsp; &nbsp; &nbsp;   0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:143
ACCEPT &nbsp;   tcp &nbsp;--&nbsp; 0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:443
--some snipped out---

Chain FORWARD (policy DROP)
ACCEPT &nbsp; &nbsp; udp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; udp dpt:53
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp;  192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:20
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0 &nbsp; &nbsp; &nbsp; &nbsp;   tcp dpt:21
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:80
ACCEPT &nbsp; &nbsp; tcp &nbsp;--&nbsp;  192.168.1.0/24 ; &nbsp; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:110
ACCEPT &nbsp;   udp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; udp dpt:110
ACCEPT   ;  tcp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:123
ACCEPT &nbsp;   udp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; udp dpt:123
ACCEPT &nbsp;   tcp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:443
ACCEPT &nbsp;   tcp &nbsp;--&nbsp;  192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:873
ACCEPT &nbsp;   udp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0 &nbsp; &nbsp; &nbsp; &nbsp;   udp dpt:873
ACCEPT &nbsp;   tcp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:993
ACCEPT &nbsp;   udp &nbsp;--&nbsp;  192.168.1.0/24 ; &nbsp; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; udp dpt:993
ACCEPT &nbsp;   tcp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; tcp dpt:995
ACCEPT   ;  udp &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  0.0.0.0/0  ; &nbsp; &nbsp; &nbsp; &nbsp; udp dpt:995
--some snipped out---

Chain OUTPUT (policy ACCEPT)
target &nbsp;   prot opt source&nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; destination

-------------------------------------------------------------------------
Table NAT

Chain PREROUTING (policy ACCEPT)
target &nbsp;   prot opt source&nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; destination

Chain POSTROUTING (policy ACCEPT)
target   ;  prot opt source&nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; destination
SNAT ; &nbsp; &nbsp;  all &nbsp;--&nbsp; 192.168.1.0/24   ; &nbsp;  anywhere&nbsp; &nbsp;  to:--snipped out

Chain OUTPUT (policy ACCEPT)
target &nbsp;   prot opt source&nbsp; &nbsp; &nbsp; &nbsp;   ; &nbsp; &nbsp; destination

Try to drop firewall rules AND set default policy in INPUT chain to ACCEPT too.
emerge sync not working
user name
2006-04-05 07:47:25
I did, no effect.

David Karban wrote:

  Try to drop firewall rules AND set default policy in INPUT
chain to ACCEPT
> too.
> 
emerge sync not working
user name
2006-04-05 10:37:28
Solved: INPUT chain must have dport 873 enabled.

Marián Hercek wrote:
> I did, no effect.
> 
> David Karban wrote:
> 
>  Try to drop firewall rules AND set default policy in
INPUT chain to ACCEPT
>> too.
>>
[1-8]

about | contact  Other archives ( Real Estate discussion Medical topics )