[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050805: Installing LDM on Fedora Core 3 64-bit (cont.)

>From: Nancy Selover <address@hidden>
>Organization: ASU
>Keywords: 200507190034.j6J0Ywjo000855 LDM install

Nancy,

re:
>In the ldmadmin-pl.conf file it says 

>$ip_addr = "149.169.178.66";  

>and in the original: it says the same thing.

The $ip_addr setting should be configured _only_ if you are trying to
run the LDM on a single interface on a machine that has multiple Ethernet
interfaces:

<from ldmadmin-pl.conf>

"
# The IP address of the network interface to be used by the LDM server.  If not
# set, then the LDM server will use all available network interfaces.
"

>Is that supposed to be Godzilla's IP address?

If you are trying to limit the LDM to working on a single interface in
a multi-interface system, this would be set to the IP address of the
interface you want the LDM to use.  If you only have a single interface
in your machine, it would be best to simply comment out this setting.

>Because when I start LDM, the log says Couldn't
>obtain local address 149.169.178.66:388 for server.   That is NOT
>Godzilla's IP address.  Is it supposed to be??

It is set to the IP address of a interface on your machine when there
are multiple interfaces.  You can see all of the interfaces that exist
on your system by running:

/sbin/ifconfig -a

Look at the listings marked as ethx.  Here is an example on a system
running Fedora Core 3 and that has one interface:

~: /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:10:5A:11:50:43
          inet addr:128.117.140.169  Bcast:128.117.140.255  Mask:255.255.255.0
          inet6 addr: fe80::210:5aff:fe11:5043/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:1229059516 errors:15 dropped:0 overruns:151 frame:19
          TX packets:770305359 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:4192477025 (3.9 GiB)  TX bytes:3632518570 (3.3 GiB)
          Interrupt:169 Base address:0xe800

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10955 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10955 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4817682 (4.5 MiB)  TX bytes:4817682 (4.5 MiB)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

In this example, the 'eth0' entry shows the IP address as 128.117.140.169.

Here is a similar example on a 64-bit system running Fedora Core 3
64-bit that has multiple interfaces:

[ldm@uni1 ~]$ /sbin/ifconfig -a
eth0      Link encap:Ethernet  HWaddr 00:09:3D:00:95:66
          inet addr:128.117.140.111  Bcast:128.117.140.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:12878512552 errors:1 dropped:0 overruns:0 frame:1
          TX packets:16896599083 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8343292578439 (7.5 TiB)  TX bytes:16350078831306 (14.8 TiB)
          Interrupt:177

eth1      Link encap:Ethernet  HWaddr 00:09:3D:00:95:67
          BROADCAST MULTICAST  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:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:185

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:10842 errors:0 dropped:0 overruns:0 frame:0
          TX packets:10842 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:1077271 (1.0 MiB)  TX bytes:1077271 (1.0 MiB)

lo:3      Link encap:Local Loopback
          inet addr:128.117.140.3  Mask:255.255.255.255
          UP LOOPBACK RUNNING  MTU:16436  Metric:1

tunl0     Link encap:IPIP Tunnel  HWaddr
          inet addr:192.52.106.21  Mask:255.255.255.255
          UP RUNNING NOARP  MTU:1480  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:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

In this example, eth0's IP address is 128.117.140.111, and eth1's IP
address is not set.

>Then it keeps timing out without making a connection.

If the address you sent along is not the IP address of an interface
on your system, then the LDM will continually timeout since it will
not be able to open the interace.

RECOMMENDATION:  comment out the $ip_addr entry in your ldmadmin-pl.conf
file and stop and restart your LDM.

Cheers,

Tom
--
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.

>From address@hidden  Fri Aug  5 13:28:36 2005

>Tom,
>Okay - that was it.  LDM is working now, and the speed is scary
>when I view the ldmadmin watch.  Now I will see if Gempak can find
>everything.
>Thank you.

>Nancy