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

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

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

Nancy,

>       We made a few changes in our set-up and we no longer get the
>killall error.

I am curious bout the changes you made. Can you pass this information
along?  It may shed light on other problems you are experiencing.

>It now says it is starting LDM.  However, it never does.
>No processed run.

So, a 'ps -u ldm' shows no programs running?  If yes, I suspect a
typo in ~ldm/etc/ldmd.conf.

>       Here are the configure.log and make.log and install.log  (from
>make install).
>
>We are having no luck, however, under the steps to perform as root
>before installing, we saw the instruction to "disable" selinux, and we
>cannot do that.

In order to use syslogd to log the LDM messages, SELINUX must be
disabled.  Without log messages, troubleshooting your installation
problems will be very difficult.  In particular, you say that:

  "It now says it is starting LDM.  However, it never does.
   No processed run."

A situation like this can be caused by an error in the
~ldm/etc/ldmd.conf file.  The error will be written to the local0
facility which is setup to be handled by syslogd.  Because FC3 has the
SELINUX facility that is enabled to not allow use of syslogd logging,
it should be turned off at least until you learn what is causing the
startup failure.  I propose that you do the following:

- edit /etc/selinux/config and set selinux=disabled
- reboot
- get LDM logging working
- try starting the LDM
- learn why it is not starting by reading the ~ldm/logs/ldmd.log file
- fixing the problem which may be as simple as a typo in ~ldm/etc/ldmd.conf
- disable selinux
- reboot

Even though we have not tried it, setting selinux to permissive in
/etc/selinux/config may be sufficient to allow the LDM to use syslogd
for logging.

>I can't believe we are the only people with Fedora 3
>that have security issues.

We run Fedora Core 3 and are VERY attentive to security.  We control
our security through the machine's firewall (/etc/sysconfig/iptables),
not through selinux.

>Perhaps LDM-6.4.0 or LDM-6.4.1 might resolve our problem.

I don't think so, but I don't have enough information to say for sure.

>We are running the 2.6 kernel on an I 686 machine.

We are running the 2.6 kernel on lots of machines: 32-bit Intel, 32-bit
AMD, 64-bit Intel, 64-bit AMD, and single and dual processors.  We
have not had any problems with FC3 64-bit on any of our 64-bit
machines.  We have turned off selinux on all of these machines and
have had no problems controlling access via the IPtables firewall.

>Lots of things are new here.

>Nancy <<make.log>>  <<install.log>>  <<configure.log>>=20

I don't see anyting in your log files that sheds light on the problem
your are seeing.  Because of this, my hunch is that you have a typo in
~ldm/etc/ldmd.conf.

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.