Bug#313205: persist not redialing on hangup

2005-06-12 Thread hacker
 12 08:22:45 localhost pppd[5632]: rcvd [IPCP ConfAck id=0x2
   ]
Jun 12 08:22:45 localhost pppd[5632]: Cannot determine ethernet
address for proxy ARP
Jun 12 08:22:45 localhost pppd[5632]: local  IP address 
Jun 12 08:22:45 localhost pppd[5632]: remote IP address 
Jun 12 08:22:45 localhost pppd[5632]: primary   DNS address 
Jun 12 08:22:45 localhost pppd[5632]: secondary DNS address 
Jun 12 08:22:45 localhost pppd[5632]: Script /etc/ppp/ip-up started (pid 5651)
Jun 12 08:22:49 localhost pppd[5632]: Connection speed is 49333
Jun 12 08:22:49 localhost pppd[5632]: Script /etc/ppp/ip-up finished
(pid 5651), status = 0x0
Jun 12 08:23:01 localhost pppd[5632]: sent [LCP EchoReq id=0x1 magic=0xcafaec3c]
Jun 12 08:23:02 localhost pppd[5632]: rcvd [LCP EchoRep id=0x1 magic=0x768bdc4c]
. snipped .
.. here's the hangup, which is detected by lcp echo failures 
Jun 12 08:33:48 localhost pppd[5632]: sent [LCP EchoReq id=0x27
magic=0xcafaec3c]
Jun 12 08:34:05 localhost pppd[5632]: sent [LCP EchoReq id=0x28
magic=0xcafaec3c]
Jun 12 08:34:22 localhost pppd[5632]: sent [LCP EchoReq id=0x29
magic=0xcafaec3c]
Jun 12 08:34:28 localhost pppd[5632]: Hangup (SIGHUP)
Jun 12 08:34:28 localhost pppd[5632]: Modem hangup
Jun 12 08:34:28 localhost pppd[5632]: Connect time 11.8 minutes.
Jun 12 08:34:28 localhost pppd[5632]: Sent 290126 bytes, received 1523313 bytes.
Jun 12 08:34:28 localhost pppd[5632]: Script /etc/ppp/ip-down started (pid 5774)
Jun 12 08:34:28 localhost pppd[5632]: Connection terminated.
Jun 12 08:34:30 localhost pppd[5632]: Script /etc/ppp/ip-down finished
(pid 5774), status = 0x0
Jun 12 08:34:58 localhost pppd[5632]: tcgetattr: No such device or
address (line 909)
Jun 12 08:34:59 localhost pppd[5632]: tcsetattr: No such device or
address (line 1003)
Jun 12 08:34:59 localhost pppd[5632]: Exit.

Maybe the problem relates to the tcgetattr line??

BTW, when I'm making a connection, the 'persist' option does seem to
work, because a failed connection will keep redialing until a
successful connection occurs.  It's just he 'modem handup' situation
when 'persist' fails to reconnect that is a problem.

hacker



Bug#310739: rsync fails to connect on kernel-2.6

2005-05-25 Thread hacker
Package: rsync
Version: 2.6.4-6

I've successfully used rsync (2.6.4-6) to transfer files over a plip
connection via a cable connecting the parallel ports of my desktop and
laptop, using kernel 2.4.27.

Now, I'm trying to use kernel 2.6.10 (and 2.6.11) and rsync won't
establish a connection.

root #: rsync mydesktop::
rsync: failed to connect to mydesktop: Connection refused (111)
rsync error: error in socket IO (code 10 at clientserver.c(99)

I'm guessing the problem is the ipv6 in 2.6.x.  For 2.6.x, ifconfig
shows an inet6 line that isn't there under 2.4.27:

under 2.4.27:

plip0 Link encap:Ethernet  HWaddr FC:FC:C0:A8:01:01
 inet addr:192.168.1.1  P-t-P:192.168.1.2  Mask:255.255.255.0
 UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
 collisions:0 txqueuelen:10
 RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 Interrupt:7 Base address:0x378

with 2.6.x:

plip0 Link encap:Ethernet  HWaddr FC:FC:C0:A8:01:01
 inet addr:192.168.1.1  P-t-P:192.168.1.2  Mask:255.255.255.0
 inet6 addr: fe80::fefc:c0ff:fea8:101/64 Scope:Link
 UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:1 dropped:0 overruns:0 carrier:1
 collisions:0 txqueuelen:10
 RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 Interrupt:7 Base address:0x378

In fact, I can't even ping with this.  So, I thought I'd try to
disable ipv6 on this link.  I added 'del 192.168.1.2' at the end of my
ifconfig to disable ipv6 (per man ifconfig) and now get:

root #: ifconfig

plip0 Link encap:Ethernet  HWaddr FC:FC:C0:A8:01:01
 inet addr:192.168.1.1  P-t-P:192.168.1.2  Mask:255.255.255.0
 inet6 addr: fe80::fefc:c0ff:fea8:101/64 Scope:Link
 UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
 RX packets:0 errors:0 dropped:0 overruns:0 frame:0
 TX packets:0 errors:1 dropped:0 overruns:0 carrier:1
 collisions:0 txqueuelen:10
 RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
 Interrupt:7 Base address:0x378

plip0:0   Link encap:Ethernet  HWaddr FC:FC:C0:A8:01:01
 inet addr:192.168.1.2  P-t-P:192.168.1.2  Mask:255.255.255.0
 UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
 Interrupt:7 Base address:0x378

Apparently, the plip0:0 listing is the subtraction of ipv6.  Now I can
successfully ping:

root :~# ping -c1 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.144 ms

--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.144/0.144/0.144/0.000 ms

'man rsync' says to add '-4' to the options to get the daemon use
ipv4, and I did this in /etc/defaults/rsync and it works:

root :~# ps aux |grep rsync
root  8349  0.0  0.3   1912   672 ?Ss   11:02   0:00
/usr/bin/rsync --no-detach --daemon --config/etc/rsyncd.conf -4

However, when I try rsync with or without the '-4' option, on my
laptop, it still fails:

root #: rsync -4 mydesktop::
rsync: failed to connect to mydesktop: Connection refused (111)
rsync error: error in socket IO (code 10 at clientserver.c(99)

When I look in my /var/log/rsyncd logfile on the host, there is no
entry for the attempted connection.

I went back to my original ifconfig, and tried rsync with the '-6'
option, but it also failed.

This makes rsync unusable on 2.6.10/11 for me.



Bug#310739: rsync fails to connect on kernel-2.6

2005-05-26 Thread hacker
On 5/25/05, Paul Slootman <[EMAIL PROTECTED]> wrote:
> On Wed 25 May 2005, hacker wrote:
> >
> > Now, I'm trying to use kernel 2.6.10 (and 2.6.11) and rsync won't
> > establish a connection.
> >
> > root #: rsync mydesktop::
> > rsync: failed to connect to mydesktop: Connection refused (111)
> > rsync error: error in socket IO (code 10 at clientserver.c(99)
> >
> > I'm guessing the problem is the ipv6 in 2.6.x.  For 2.6.x, ifconfig
> 
> That could indeed be the cause.
 
Do you think I should file this against the 2.6 kernel then?  I read
the plip module documentation, but there were no hints of problems
with ipv6.

> > 'man rsync' says to add '-4' to the options to get the daemon use
> > ipv4, and I did this in /etc/defaults/rsync and it works:
> >
> > root :~# ps aux |grep rsync
> > root  8349  0.0  0.3   1912   672 ?Ss   11:02   0:00
> > /usr/bin/rsync --no-detach --daemon --config/etc/rsyncd.conf -4
> 
> I hope it's a cut & paste error, but I miss a space between --config and
> /etc/rsyncd.conf .

Yes, it's word wrap right at the end of the word config, that I cut
and pasted wrong.  There is indeed a space.

> 
> Could you do an "lsof -p 8349", to see what rsync is listening to?

Today, it's process 1984 and 'lsof -p 1984' returns to the prompt
(nothing identified) on the next line.

> 
> Paul Slootman
> 

hacker



Bug#310739: rsync fails to connect on kernel-2.6

2005-05-30 Thread hacker
On 5/30/05, Paul Slootman <[EMAIL PROTECTED]> wrote:
> On Thu 26 May 2005, hacker wrote:
> > >
> > > Could you do an "lsof -p 8349", to see what rsync is listening to?
> >
> > Today, it's process 1984 and 'lsof -p 1984' returns to the prompt
> > (nothing identified) on the next line.
> 
> That's wrong, at the very least it should show things like shared libs.
> Were you root at the time?
> 
> 
> Paul Slootman
> 

I don't recall whether I was root at the time, but today it's process
5864 and I get a reply whether root or user:

root:~# lsof -p 5864
COMMAND  PID USER   FDTYPE DEVICESIZE   NODE NAME
rsync   5864 root  cwd   DIR3,6 680  2  /
rsync   5864 root  rtd   DIR3,6 680  2  /
rsync   5864 root  txt   REG3,6  241324 100890  /usr/bin/rsync
rsync   5864 root  mem   REG3,6 1254500  18082 
/lib/tls/i686/cmov/libc-2.3.2.so
rsync   5864 root  mem   REG3,664924   18096 
/lib/tls/i686/cmov/libresolv-2.3.2.so
rsync   5864 root  mem   REG3,6266243141  /lib/libpopt.so.0.0.0
rsync   5864 root  mem   REG3,690248 104637  /lib/ld-2.3.2.so
rsync   5864 root0u   CHR1,32328  /dev/null
rsync   5864 root1u   CHR1,32328  /dev/null
rsync   5864 root2u   CHR1,32328  /dev/null
rsync   5864 root4u  IPv49944 TCP *:rsync (LISTEN)

had to transcribe this by hand, so could have a typo.

hacker



Bug#308733: rsync 2.6.4 server fails with rsync error in rsync protocol data stream (code 12) at io.c(570)

2005-05-11 Thread hacker
Package: rsync
Version: 2.6.4-4
Severity: grave
Justification: renders package unusable

I upgraded from 2.6.4-2 to 2.6.4-4 on my local network server and now
my client gets an error:

$ rsync mydesktop::

rsync: read error: Connection reset by peer (104)
rsync error: error in rsync protocol data stream (code 12) at io.c(570)
_exit_cleanup(cope=3D12), file=3Dio.c, line=3D570): about to call exit(12)

Also, I've upgraded my server to 2.6.4-5 and have same error.

So, I've downgraded my server to 2.6.4-2 and now can rsync ok.  I've
tried all 3 versions (2.6.4-2,4,5) on my client, and all work ok on
the client side.

The only server that I can get working is 2.6.4-2.  With this version,
I successfully use the following rsync commands:

$ rsync mydesktop::
$ rsync -avz --progress --delete mydesktop::rootdir/home/golfbuf/work/ work/
$ rsync -avz --progress mydesktop::rootdir/home/golfbuf/myfile.txt mydir/

[EMAIL PROTECTED]

-- System Information:
Debian Release: 3.1
 APT prefers unstable
 APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.4.27-2-686
Locale: LANG=3Den_US, LC_CTYPE=3Den_US (charmap=3DISO-8859-1)

Versions of packages rsync depends on:
ii  libc6   2.3.2.ds1-21 GNU C Library: Shared libraries an
ii  libpopt01.7-5lib for parsing cmdline parameters

-- no debconf information



Bug#578998: gtkparasite: Missing executable

2010-04-24 Thread Hyper Hacker
Package: gtkparasite
Version: 0+git20090907-1
Severity: grave
Tags: sid
Justification: renders package unusable

The package seems to be missing the actual `gtkparasite` executable. The 
program's website describes this executable, but it is not present after 
installing.

-- System Information:
Debian Release: squeeze/sid
  APT prefers unstable
  APT policy: (500, 'unstable')
Architecture: i386 (i686)

Kernel: Linux 2.6.32-3-686 (SMP w/1 CPU core)
Locale: LANG=en_CA.UTF-8, LC_CTYPE=en_CA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gtkparasite depends on:
ii  libatk1.0-0   1.30.0-1   The ATK accessibility toolkit
ii  libc6 2.10.2-6   Embedded GNU C Library: Shared lib
ii  libcairo2 1.8.10-3   The Cairo 2D vector graphics libra
ii  libfontconfig12.8.0-2generic font configuration library
ii  libfreetype6  2.3.11-1   FreeType 2 font engine, shared lib
ii  libglib2.0-0  2.24.0-1   The GLib library of C routines
ii  libgtk2.0-0   2.20.0-2   The GTK+ graphical user interface 
ii  libpango1.0-0 1.26.2-2   Layout and rendering of internatio
ii  python-dev2.5.4-9Header files and a static library 
ii  python2.5 2.5.5-6An interactive high-level object-o

gtkparasite recommends no packages.

gtkparasite suggests no packages.

-- no debconf information



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#310739: rsync fails to connect on kernel-2.6

2005-07-19 Thread hacker (of golf)
This bug is solved.  Please withdraw it from your buglist.

It turns out that I was loading the parport_pc module with specific
irq and address, and the 2.6.x kernels didn't recognize it.  So, now I
just 'modprobe parport_pc' and it works.  It had nothing to do with
rsync!

Thanks,