Re: xinetd problems
2002-08-05 01:09:39
On Sunday 04 August 2002 23:32, Paul G. Allen wrote:
>I'm not real familiar with xinetd (nor am I familiar with inetd as
> I usually avoid both for security reasons).
[...]
>Amanda Backup Client Hosts Check
>--------------------------------
>WARNING: keroon: selfcheck request timed out. Host down?
>WARNING: ista: selfcheck request timed out. Host down?
>Client check: 2 hosts checked in 29.999 seconds, 2 problems found
>
>(brought to you by Amanda 2.4.2p2)
>
>
>Looking at /var/log/messages, I see many many errors from xinetd
> when it tries to start the Amanda services:
>
>Aug 4 20:04:11 ista xinetd[11746]: {bad_signal} Received 10
> signals in 1 seconds. Exiting...
>Aug 4 20:04:11 ista xinetd[11747]: {general_handler} (11747)
> Unexpected signal: 11 (Segmentation fault)
>Aug 4 20:04:11 ista last message repeated 9 times
>Aug 4 20:04:11 ista xinetd[11747]: {bad_signal} Received 10
> signals in 1 seconds. Exiting...
>Aug 4 20:04:11 ista xinetd[11748]: {general_handler} (11748)
> Unexpected signal: 11 (Segmentation fault)
>Aug 4 20:04:11 ista last message repeated 9 times
>Aug 4 20:04:11 ista xinetd[11748]: {bad_signal} Received 10
> signals in 1 seconds. Exiting...
>Aug 4 20:04:11 ista xinetd[11749]: {general_handler} (11749)
> Unexpected signal: 11 (Segmentation fault)
>Aug 4 20:04:11 ista last message repeated 9 times
>Aug 4 20:04:11 ista xinetd[11749]: {bad_signal} Received 10
> signals in 1 seconds. Exiting...
>Aug 4 20:04:11 ista xinetd[11750]: {general_handler} (11750)
> Unexpected signal: 11 (Segmentation fault)
>Aug 4 20:04:11 ista last message repeated 9 times
>Aug 4 20:04:11 ista xinetd[11750]: {bad_signal} Received 10
> signals in 1 seconds. Exiting...
>Aug 4 20:04:11 ista xinetd[11751]: {general_handler} (11751)
> Unexpected signal: 11 (Segmentation fault)
>Aug 4 20:04:11 ista last message repeated 9 times
>Aug 4 20:04:11 ista xinetd[11751]: {bad_signal} Received 10
> signals in 1 seconds. Exiting...
>Aug 4 20:04:11 ista xinetd[11558]: Deactivating service amanda
> due to excessive incoming connections. Restarting in 30 seconds.
> Aug 4 20:04:41 ista xinetd[11558]: Activating service amanda
>
>
>
>Here's my xinetd config file for the amanda service:
>
># default: on
>service amanda
>{
> socket_type = dgram
> protocol = udp
> wait = yes
> user = root
> group = disk
> server = /usr/local/libexec/amandad
> only_from = 192.168.1.4 192.168.1.5 192.168.1.10
>192.168.1.11
> no_access = 192.168.1.1
> log_type = SYSLOG
> log_on_success = PID HOST USERID DURATION EXIT
> log_on_failure = HOST USERID ATTEMPT RECORD
> disable = no
>}
>
>
>The two hosts that are failing are the Amanda tape server (ista)
> and 192.168.1.4.
>
>PGA
Actually, there are 3 pieces of amanda related files in xinetd.d, or
they can be merged into one file.
You can add your special stuff from above to this one if you'd like,
its the one I've been running for about a year:
----------------------------------------
# default = off
#
# description: Part of the Amanda server package
# This is the list of daemons & such it needs
service amanda
{
disable = no
socket_type = dgram
protocol = udp
wait = yes
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amandad
}
service amandaidx
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amindexd
}
service amidxtape
{
disable = no
socket_type = stream
protocol = tcp
wait = no
user = amanda
group = disk
groups = yes
server = /usr/local/libexec/amidxtaped
}
-----------------------------------
The above file must be owner:group=amanda:disk
I see you are trying to run amanda as user root from your amanda
file, and that won't fly at all. Amanda will do her own suid when
she needs to, and she checks to see who she is and exits if she is
root at launch time.
--
Cheers, Gene
AMD K6-III@500mhz 320M
Athlon1600XP@1400mhz 512M
99.10% setiathome rank, not too shabby for a WV hillbilly
|
|
|