Load Ingest Data
Results 1 to 1 of 1

Thread: Daemon could not be started on the TANDEM machine

  1. #1
    Costi Zaboura is offline World Wide Support Manager
    Join Date
    Aug 2006
    Posts
    300
    Rep Power
    14

    Daemon could not be started on the TANDEM machine

    Problem

    Could not start the daemon on the Tandem platform

    After installing the product we created a start obey file with the following contents:

    DELETE DEFINE =TCPIP^PROCESS^NAME
    ADD DEFINE =TCPIP^PROCESS^NAME, FILE $ZB01C
    RUN $PROD1.NAVROOT.NAVLOGIN
    PARAM ACPWDPRT 1
    FUP PURGEDATA IRPCDLOG
    RUN $PROD1.NAVROOT.IRPCD -l 192.x.x.x:5010 START
    In the daemon log - we are seeing the following error messages

    Attunity Server Daemon

    Failed bind brodcast socket error is 4106.

    [C084] Cannot set up a broadcast listener (warning)
    [C026] Failed to bind server to port 5010
    [C026] [EADDRNOTAVAIL] Can't assign requested address.
    [C007] Server initialization failed
    Closing log file

    Answer

    The error from Tandem means that the IP address is invalid (implicitly: for the TCPIP process named $ZB01C) and that is what needs to be resolved.

    Tips for resolving the problem
    -----------------------------------------

    Most likely, the TCPIP process name used is not the correct one.

    The following command can show what’s going on:


    14> scf

    SCF - T9082G02 - (04MAY04) (07APR04) - 01/15/2008 09:27:53 System \NONAME

    (C) 1986 Tandem (C) 2004 Hewlett Packard Development Company, L.P.
    (Invoking \NONAME.$SYSTEM.KIT.SCFCSTM)

    1-> assume process $ztc0
    2-> listopens $ztc0,detail

    TCPIP Detailed Listopens PROCESS \NONAME.$ZTC0

    Opener $Z9N0 Ppid 0,345 Bpid Plfn 4 Blfn 0
    Proto TCP State LISTEN SendQ 0 RecvQ 0
    Laddr 192.x.x.x Lport 3828
    Faddr 0.0.0.0 Fport *

    Opener $Z9L0 Ppid 0,522 Bpid Plfn 4 Blfn 0
    Proto TCP State LISTEN SendQ 0 RecvQ 0
    Laddr 192.x.x.x Lport 3714
    Note the IP address 192.x.x.x above – that is a valid IP address. If done on the $ZB01C, one would find that the address is not the same as was given to the daemon.

    If we take for example a different TCPIP process name such as $ZB01A we may get something like this:

    TCPIP Detailed Listopens PROCESS \NONAME.$ZB01A

    Opener $ZN01A Ppid 0,320 Bpid Plfn 2 Blfn 0
    Proto TCP State LISTEN SendQ 0 RecvQ 0
    Laddr 0.0.0.0 Lport telnet
    Faddr 0.0.0.0 Fport *

    Opener $ZP01A Ppid 0,319 Bpid Plfn 3 Blfn 0
    Proto TCP State LISTEN SendQ 0 RecvQ 0
    Laddr 0.0.0.0 Lport 1089
    Faddr 0.0.0.0 Fport *
    Where there is no real local IP address to bind to, hence the error.
    Last edited by DrorHarari; 01-15-2008 at 02:19 PM.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •