[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
20030602: McIDAS ADDE and xinetd on RedHat 7.3 Linux
This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
- Subject: 20030602: McIDAS ADDE and xinetd on RedHat 7.3 Linux
- Date: Mon, 02 Jun 2003 15:45:21 -0600
>From: David Fitzgerald <address@hidden>
>Organization: Millersville University
>Keywords: 200306022041.h52KfKLd005455
Hi Dave,
>I give up on this one. None of my services, including my ADDE services, are
>starting up on my linux box.
>My xinetd.conf file has the line: includedir /etc/xinetd.d, and the files
>for the services are located in that directory.
>I can't figure out why these services are not starting. I'm a newbie at
>Linux so would you mind taking a look at this? I probably missed something
>obvious.
>
>I have included my xinetd.conf file, along with debugging output `xinetd
>-d`, /var/log/messages and the three files McIDAS put in /etc/xinetd.d.
>
>To me it loiks like xinetd is choking on something in the /etc/xinetd.d
>files, but I cant see anything wrong!
>
>HELP!
>
>Thanks!
>Dave
>#
># Simple configuration file for xinetd
>#
># Some defaults, and include /etc/xinetd.d/
>
>defaults
>{
> instances = 60
> log_type = SYSLOG authpriv
> log_on_success = HOST PID
> log_on_failure = HOST
> cps = 25 30
>}
>
>includedir /etc/xinetd.d
>#mcidasz (port 112)
>service mcidasz
>{
> log_type = SYSLOG authpriv debug
> flags = REUSE
> socket_type = stream
> protocol = tcp
> wait = no
> user = mcadde
> port = 112
server = /home/mcidas/bin/mcservsh
> server_args = -H /home/mcidas
> log_on_success += USERID HOST DURATION
> log_on_failure += USERID HOST RECORD
>}
>
^
|
This looks OK. --+
>#mccompress (port 503)
>service mccompress
>{
> log_type = SYSLOG authpriv debug
> flags = REUSE
> socket_type = stream
> protocol = tcp
> wait = no
> user = mcadde
> port = 503
> server = /home/mcidas/bin/mcservsh
> server_args = -H /home/mcidas
> log_on_success += USERID HOST DURATION
> log_on_failure += USERID HOST RECORD
>}
^
|
So does this. -----+
>#mcserv (port 500)
>service mcserv
>{
> log_type = SYSLOG authpriv debug
> flags = REUSE
> socket_type = stream
> protocol = tcp
> wait = no
> user = mcadde
> port = 500
> server = /home/mcidas/bin/mcservsh
> server_args = -H /home/mcidas
> log_on_success += USERID HOST DURATION
> log_on_failure += USERID HOST RECORD
>}
^
|
And this. -----+
>[root@twister2 ~]# xinetd -d
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/chargen [line=3D15]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/chargen-udp [line=3D13]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/daytime [line=3D14]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/daytime-udp [line=3D13]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/echo [line=3D14]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/echo-udp [line=3D13]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/finger [line=3D14]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/kotalk [line=3D12]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/ktalk [line=3D12]
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/mccompress [line=3D12]
>03/6/2@16:13:39: WARNING: 2048 {parse_value_list} Bad log_on_failure =
>flag: RECORD [line=3D14]
This is very strange to say the least.
>03/6/2@16:13:39: ERROR: 2048 {identify_attribute} Error parsing =
>attribute log_on_failure - DISABLING SERVICE [line=3D14]
Not good!
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/mcidasz [line=3D16]
>03/6/2@16:13:39: WARNING: 2048 {parse_value_list} Bad log_on_failure =
>flag: RECORD [line=3D14]
>03/6/2@16:13:39: ERROR: 2048 {identify_attribute} Error parsing =
>attribute log_on_failure - DISABLING SERVICE [line=3D14]
Ditto, not good.
>03/6/2@16:13:39: DEBUG: 2048 {handle_includedir} Reading included =
>configuration file: /etc/xinetd.d/mcserv [line=3D16]
>03/6/2@16:13:39: WARNING: 2048 {parse_value_list} Bad log_on_failure =
>flag: RECORD [line=3D14]
>03/6/2@16:13:39: ERROR: 2048 {identify_attribute} Error parsing =
>attribute log_on_failure - DISABLING SERVICE [line=3D14]
Ditto, not good.
I just setup remote ADDE services on one of our RedHat 7.3 Linux systems.
The /etc/xinetd.d/mcserv|mccompress|mcidasz files look identical to the
ones from your system, and the output from 'xinetd -d' is completely
different:
...
03/6/2@15:26:46: DEBUG: {handle_includedir} Reading included configuration
file: /etc/xinetd.d/mccompress [line=12]
03/6/2@15:26:46: DEBUG: {handle_includedir} Reading included configuration
file: /etc/xinetd.d/mcidasz [line=16]
03/6/2@15:26:46: DEBUG: {handle_includedir} Reading included configuration
file: /etc/xinetd.d/mcserv [line=16]
...
Service configuration: mccompress
id = mccompress
flags = REUSE IPv4
socket_type = stream
Protocol (name,number) = (tcp,6)
port = 503
Groups = no
Bind = All addresses.
Server = /home/mcidas/bin/mcservsh
Server argv = mcservsh -H /home/mcidas
Only from: All sites
No access: No blocked sites
Logging to syslog. Facility = authpriv, level = debug
Log_on_success flags = HOST DURATION PID USERID
Log_on_failure flags = HOST RECORD USERID
Service configuration: mcidasz
id = mcidasz
flags = REUSE IPv4
socket_type = stream
Protocol (name,number) = (tcp,6)
port = 112
Groups = no
Bind = All addresses.
Server = /home/mcidas/bin/mcservsh
Server argv = mcservsh -H /home/mcidas
Only from: All sites
No access: No blocked sites
Logging to syslog. Facility = authpriv, level = debug
Log_on_success flags = HOST DURATION PID USERID
Log_on_failure flags = HOST RECORD USERID
Service configuration: mcserv
id = mcserv
flags = REUSE IPv4
socket_type = stream
Protocol (name,number) = (tcp,6)
port = 500
Groups = no
Bind = All addresses.
Server = /home/mcidas/bin/mcservsh
Server argv = mcservsh -H /home/mcidas
Only from: All sites
No access: No blocked sites
Logging to syslog. Facility = authpriv, level = debug
Log_on_success flags = HOST DURATION PID USERID
Log_on_failure flags = HOST RECORD USERID
>Jun 2 16:17:48 twister2 xinetd[842]: Exiting...
>Jun 2 16:17:48 twister2 xinetd: xinetd shutdown succeeded
>Jun 2 16:17:48 twister2 xinetd[2085]: Bad log_on_failure flag: RECORD [line=1
> 4]
>Jun 2 16:17:48 twister2 xinetd[2085]: Error parsing attribute log_on_failure
> - DISABLING SERVICE [line=14]
>Jun 2 16:17:48 twister2 xinetd[2085]: Bad log_on_failure flag: RECORD [line=1
> 4]
>Jun 2 16:17:48 twister2 xinetd[2085]: Error parsing attribute log_on_failure
> - DISABLING SERVICE [line=14]
>Jun 2 16:17:48 twister2 xinetd[2085]: Bad log_on_failure flag: RECORD [line=1
> 4]
>Jun 2 16:17:48 twister2 xinetd[2085]: Error parsing attribute log_on_failure
> - DISABLING SERVICE [line=14]
>Jun 2 16:17:49 twister2 xinetd[2085]: xinetd Version 2.3.11 started with libw
> rap loadavg options compiled in.
>Jun 2 16:17:49 twister2 xinetd[2085]: Started working: 2 available services
>Jun 2 16:17:51 twister2 xinetd: xinetd startup succeeded
So, on your system 'RECORD' is an invalid option for log_on_failure. I
just checked the man page for xinetd.conf on our RH 7.3 system, and do
not see RECORD as a valid option:
% man xinetd.conf
XINETD.CONF(5) XINETD.CONF(5)
NAME
xinetd.conf - Extended Internet Services Daemon configura-
tion file
DESCRIPTION
xinetd.conf is the configuration file that determines the
services provided by xinetd. Any line whose first non-
...
log_on_failure determines what information is logged
when a server cannot be started (either
because of a lack of resources or because
of access control restrictions). The ser-
vice id is always included in the log
entry along with the reason for failure.
Any combination of the following values
may be specified:
HOST logs the remote host address.
USERID logs the user id of the
remote user using the RFC
1413 identification protocol.
This option is available only
for multi-threaded stream
services.
ATTEMPT logs the fact that a failed
attempt was made (this option
is implied by all others).
So, what puzzles me now is not that configuration parameters for
xinetd changed (this is what keeps the Linux guys employed :-(),
but that I don't get the error on my system! Now, I might guess
that completely new installation of RH 7.3 would install things
that weren't backwardly compatible, but the machine that I tested
this on was a clean, inital installation, not an upgrade!
So, I would recommend editing /etc/xinetd.d/mcserv, mccompress, and
mcidasz and removing the RECORD item from the log_on_failure lines
and then trying the 'xinetd -d' test again.
This is a new one on me!
Tom
>From address@hidden Tue Jun 3 11:36:07 2003
>Tom,
>Just to let you know, I removed the RECORD statement from the files in
>/etc/xinetd.d, and that solved the problem.
>Mcserv, mcidasz, and mccompress start uip ok now. Weird you setup works
>WITH it though.
>Thanks for you help!
>Dave
>*********************************************
>David Fitzgerald
>Distributed System Specialist II
>Millersville University
>Millersville PA 17551
>Phone: 717-871-2394
>Fax: 717-871-4725
>E-mail: address@hidden
><mailto:address@hidden>
- Prev by Date: 20030602: McIDAS installation at UFRJ (cont.)
- Next by Date: 20030604: IMG* use of site-developed MSG calibration module
- Previous by thread: 20030602: McIDAS installation at UFRJ (cont.)
- Next by thread: 20030604: IMG* use of site-developed MSG calibration module
- Index(es):