Hi,
Please clarify the TCP socket connection between the
dumper and amandad. Let me know which one is acting as
a server and client. If we specify the entry in the
DLE like this 222.222.222.222 /home root-tar.
chunker: stream_accept: connection from
127.0.0.1.45601
dumper: stream_client: connected to 127.0.0.1.784
chunker: try_socksize: receive buffer size is 32768
dumper: stream_client: our side is 0.0.0.0.45601
dumper: try_socksize: send buffer size is 65536
dumper: bind_portrange2: trying port=778
dumper: dgram_bind: socket bound to 0.0.0.0.778
dumper: stream_client: connected to 192.61.224.88.778
dumper: stream_client: our side is 0.0.0.0.35926
dumper: try_socksize: send buffer size is 65536
dumper: try_socksize: receive buffer size is 65536
Why the chunker and dumper is using three IP addresses
in the above log data?
The dumper is creating the previlgied prot no like 778
for data and one for mesg and one for index.
what is the other port no
35926.
Why the chunker is trying to connect to the port no?
chunker: try_socksize: receive buffer size is 65536
chunker: bind_portrange2: trying port=784
chunker: stream_server: waiting for connection:
0.0.0.0.784
driver: result time 4.778 from chunker0: PORT 784
Please clarify me the TCP communication between
amandad, dumper and chunker processes ?
I am totally confused, even debugging is also
difficult.
Thanks & Regards,
Silpakala
--- Paul Bijnens <paul.bijnens AT xplanation DOT com> wrote:
>
> [ Please keep the information on the list -- other
> people
> may help too. ]
>
>
>
> On 2006-07-10 11:56, silpa kala wrote:
> > Hi,
> >
> > I need some clarification on Amanda Internals.
> >
> > Driver will initiate the chunker process and
> driver
> > will provide some information to the chunker
> process
> > like name of the file for holding disk, hostname,
> > level, datastamp etc.,
> > How the driver will send the information to the
> > chunker? either through pipes ?I copied some lines
>
> Assuming you are using amanda 2.5.0p2...
>
> By UNIX sockets, see server-src/driverio.c lines 169
> et.seq.
>
>
> > from the amdump logfile.
> >
> > driver: send-cmd time 4.768 to chunker0:
> PORT-WRITE
> > 00-00001
> >
>
/home/20060705194408/hostname._home_amanda-2.5.0p1-20060428_server-src.1
> > hostname fffffeff9ffeffff07
> > /home/amanda-2.5.0p1-20060428/ server-src 1
> > 2006:7:6:0:42:13 1048576 GNUTAR 6624
> > |;auth=BSD;no-record;index;
> >
> >
> > chunker is trying to connect to one privileged
> port
> > no. Driver will initiate the dumper process and
> driver
> > will provide some information to dumper port no to
> > connect(what chunker initiated for the particular
> > port), hostname etc.,
> >
> > driver: send-cmd time 4.778 to dumper0: PORT-DUMP
> > 00-00001 784 hostname fffffeff9ffeffff07
> > /home/amanda-2.5.0p1-20060428/server-src NODEVICE
> 1
> > 2006:7:6:0:42:13 GNUTAR
> |;auth=BSD;no-record;index;
> >
> >
> > Is there any socket communication is required
> between
> > the chunker and driver ? I got so much of
> confusion
>
> Chunker needs to be able to communicate some result
> back.
> Did the dump succeed? Need more diskspace? etc.
> See all the calls to putresult() in chunker.c
>
>
> > with the amdump.1 log file. The contents i am
> sending
> > here from the log file
> >
> > chunker: stream_accept: connection from
> > 127.0.0.1.45601
> > dumper: stream_client: connected to 127.0.0.1.784
> > chunker: try_socksize: receive buffer size is
> 32768
> > dumper: stream_client: our side is 0.0.0.0.45601
> > dumper: try_socksize: send buffer size is 65536
> >
> > What is the significance of this. Please explain?
>
> I'm still not sure what is unclear to you here.
> First you have to understand that there are multiple
> chunkers/dumpers. And the output of these is not
> sequential
> but intermingled in this single log file.
> Not perfect, indeed -- AAPW (all applicable patches
> welcome).
> Is that where the confusion is coming from?
>
> In the beginning all dumpers/chunkers are starting
> almost
> at once. Resulting in a lot of intermingled
> messages from
> all these processes.
>
> To get less confusion, start a backup with
> "inparralel 1".
> Then you get only one instance of each
> process, making the sequence much easier to follow.
>
>
> >
> > I need these clarifications. Please help me out to
> > understand these funda.
>
> Did you have a look at the source code?
> I assume you are not satisfied with the use of the
> sockets as is now.
> What exactly are you trying to solve/fix ?
>
>
>
>
> --
> Paul Bijnens, xplanation Technology Services
> Tel +32 16 397.511
> Technologielaan 21 bus 2, B-3001 Leuven, BELGIUM
> Fax +32 16 397.512
> http://www.xplanation.com/ email:
> Paul.Bijnens AT xplanation DOT com
>
***********************************************************************
> * I think I've got the hang of it now: exit, ^D,
> ^C, ^\, ^Z, ^Q, ^^, *
> * F6, quit, ZZ, :q, :q!, M-Z, ^X^C, logoff, logout,
> close, bye, /bye, *
> * stop, end, F3, ~., ^]c, +++ ATH, disconnect, halt,
> abort, hangup, *
> * PF4, F20, ^X^X, :D::D, KJOB, F14-f-e, F8-e, kill
> -1 $$, shutdown, *
> * init 0, kill -9 1, Alt-F4, Ctrl-Alt-Del,
> AltGr-NumLock, Stop-A, ... *
> * ... "Are you sure?" ... YES ... Phew ...
> I'm out *
>
***********************************************************************
>
>
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
|
