On Jul 18, 2014, at 2:13 PM, Gene Heskett <[email protected]> wrote:
> On Friday 18 July 2014 14:51:39 Debra S Baddorf did opine > And Gene did reply: >> On Jul 18, 2014, at 11:25 AM, Gene Heskett <[email protected]> wrote: >>> 14/7/18@12:09:37: ERROR: 3859 {activate_normal} bind failed (Address >>> already in use (errno = 98)). service = amanda >>> 14/7/18@12:09:37: ERROR: 3859 {cnf_start_services} Service amanda >>> failed to start and is deactivated. >>> 14/7/18@12:09:37: DEBUG: 3859 {cnf_start_services} mask_max = 0, >>> services_started = 0 >>> 14/7/18@12:09:37: CRITICAL: 3859 {init_services} no services. >>> Exiting... >> >> I don’t like this part of your earlier email. >> Does tail /var/log/messages say anything about an error? >> After I use root and restart xinetd >> >> /sbin/service xinetd restart >> Stopping xinetd: [ OK ] >> Starting xinetd: [ OK ] >> >> >> >> my /var/log/messages file says >> >> Jul 18 13:50:47 adback2 xinetd[32427]: Exiting... >> Jul 18 13:50:47 adback2 xinetd[32468]: xinetd Version 2.3.14 started >> with libwrap loadavg labeled-networking options compiled in. Jul 18 >> 13:50:47 adback2 xinetd[32468]: Started working: 8 available services >> >> >> Does yours say there are ANY services successfully running? >> Deb > > Nothing about xinetd in dmesg, or in messages. > > Cheers, Gene Heskett Hmmm. Do we have a running xinet ? ps auxww | grep net root 2758 0.0 0.0 2852 884 ? Ss Jul11 0:00 xinetd -stayalive -pidfile /var/run/xinetd.pid /sbin/chkconfig --list xinetd xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off this tells what phases of reboot to start it with. The “ps” will say if it is running NOW. If you find “inetd” instead (or whatever the older name was?) THEN we can proceed down that path. Deb Baddorf
