HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials

HowtoForge Forums | HowtoForge - Linux Howtos and Tutorials (http://www.howtoforge.com/forums/index.php)
-   General (http://www.howtoforge.com/forums/forumdisplay.php?f=21)
-   -   MyDNS startup problem (http://www.howtoforge.com/forums/showthread.php?t=36627)

valter 16th June 2009 21:56

MyDNS startup problem
 
SuSE 11.1, latest MyDNS and MyDNSConfig... when I try to add mydns to startup services chkconfig -a mydns I get this error:

Code:

insserv: warning: script 'bastille-firewall' missing LSB tags and overrides
insserv: Default-Start undefined, assuming default start runlevel(s) for script `bastille-firewall'
mydns                    0:off  1:off  2:off  3:on  4:off  5:on  6:off

services is not added and not automatically started. Any idea?

falko 17th June 2009 13:20

That's a problem with the bastille-firewall init script, not with the mydns init script.

valter 17th June 2009 19:49

Yes, I know, but this bastille-firewall comes with MyDNSConfig right? I don't have this firewall on other identical boxes, so it came with MyDNSConfig...

falko 18th June 2009 14:28

Not sure...
What's in the mydns and bastille-firewall init scripts?

valter 18th June 2009 18:15

Here it is

mydns
Code:

#! /bin/sh
# Copyright (c) 1995-2004 SUSE Linux AG, Nuernberg, Germany.
# All rights reserved.
#
# Author: Kurt Garloff
# Please send feedback to http://www.suse.de/feedback/
#
# /etc/init.d/mydns
#  and its symbolic link
# /(usr/)sbin/rcmydns
#
#    This program is free software; you can redistribute it and/or modify
#    it under the terms of the GNU General Public License as published by
#    the Free Software Foundation; either version 2 of the License, or
#    (at your option) any later version.
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program; if not, write to the Free Software
#    Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
#
# Template system startup script for some example service/daemon mydns
#
# LSB compatible service control script; see http://www.linuxbase.org/spec/
#
# Note: This template uses functions rc_XXX defined in /etc/rc.status on
# UnitedLinux (UL) based Linux distributions. If you want to base your
# script on this template and ensure that it works on non UL based LSB
# compliant Linux distributions, you either have to provide the rc.status
# functions from UL or change the script to work without them.
#
### BEGIN INIT INFO
# Provides:          mydns
# Required-Start:    $syslog $remote_fs
# Should-Start: $time ypbind sendmail
# Required-Stop:    $syslog $remote_fs
# Should-Stop: $time ypbind sendmail
# Default-Start:    3 5
# Default-Stop:      0 1 2 6
# Short-Description: mydns XYZ daemon providing ZYX
# Description:      Start mydns to allow XY and provide YZ
#        continued on second line by '#<TAB>'
#        should contain enough info for the runlevel editor
#        to give admin some idea what this service does and
#        what it's needed for ...
#        (The Short-Description should already be a good hint.)
### END INIT INFO
#
# Any extensions to the keywords given above should be preceeded by
# X-VendorTag- (X-UnitedLinux- X-SuSE- for us) according to LSB.
#
# Notes on Required-Start/Should-Start:
# * There are two different issues that are solved by Required-Start
#    and Should-Start
# (a) Hard dependencies: This is used by the runlevel editor to determine
#    which services absolutely need to be started to make the start of
#    this service make sense. Example: nfsserver should have
#    Required-Start: $portmap
#    Also, required services are started before the dependent ones.
#    The runlevel editor will warn about such missing hard dependencies
#    and suggest enabling. During system startup, you may expect an error,
#    if the dependency is not fulfilled.
# (b) Specifying the init script ordering, not real (hard) dependencies.
#    This is needed by insserv to determine which service should be
#    started first (and at a later stage what services can be started
#    in parallel). The tag Should-Start: is used for this.
#    It tells, that if a service is available, it should be started
#    before. If not, never mind.
# * When specifying hard dependencies or ordering requirements, you can
#  use names of services (contents of their Provides: section)
#  or pseudo names starting with a $. The following ones are available
#  according to LSB (1.1):
#        $local_fs                all local file systems are mounted
#                                (most services should need this!)
#        $remote_fs                all remote file systems are mounted
#                                (note that /usr may be remote, so
#                                many services should Require this!)
#        $syslog                        system logging facility up
#        $network                low level networking (eth card, ...)
#        $named                        hostname resolution available
#        $netdaemons                all network daemons are running
#  The $netdaemons pseudo service has been removed in LSB 1.2.
#  For now, we still offer it for backward compatibility.
#  These are new (LSB 1.2):
#        $time                        the system time has been set correctly       
#        $portmap                SunRPC portmapping service available
#  UnitedLinux extensions:
#        $ALL                        indicates that a script should be inserted
#                                at the end
# * The services specified in the stop tags
#  (Required-Stop/Should-Stop)
#  specify which services need to be still running when this service
#  is shut down. Often the entries there are just copies or a subset
#  from the respective start tag.
# * Should-Start/Stop are now part of LSB as of 2.0,
#  formerly SUSE/Unitedlinux used X-UnitedLinux-Should-Start/-Stop.
#  insserv does support both variants.
# * X-UnitedLinux-Default-Enabled: yes/no is used at installation time
#  (%fillup_and_insserv macro in %post of many RPMs) to specify whether
#  a startup script should default to be enabled after installation.
#  It's not used by insserv.
#
# Note on runlevels:
# 0 - halt/poweroff                        6 - reboot
# 1 - single user                        2 - multiuser without network exported
# 3 - multiuser w/ network (text mode)  5 - multiuser w/ network and X11 (xdm)
#
# Note on script names:
# http://www.linuxbase.org/spec/refspecs/LSB_1.3.0/gLSB/gLSB/scrptnames.html
# A registry has been set up to manage the init script namespace.
# http://www.lanana.org/
# Please use the names already registered or register one or use a
# vendor prefix.


# Check for missing binaries (stale symlinks should not happen)
# Note: Special treatment of stop for LSB conformance
MYDNS_BIN=/usr/sbin/mydns
test -x $MYDNS_BIN || { echo "$mydns_BIN not installed";
        if [ "$1" = "stop" ]; then exit 0;
        else exit 5; fi; }

# Check for existence of needed config file and read it
#MYDNS_CONFIG=/etc/sysconfig/mydns
#test -r $MYDNS_CONFIG || { echo "$mydns_CONFIG not existing";
#        if [ "$1" = "stop" ]; then exit 0;
#        else exit 6; fi; }

# Read config
#. $MYDNS_CONFIG

# Source LSB init functions
# providing start_daemon, killproc, pidofproc,
# log_success_msg, log_failure_msg and log_warning_msg.
# This is currently not used by UnitedLinux based distributions and
# not needed for init scripts for UnitedLinux only. If it is used,
# the functions from rc.status should not be sourced or used.
#. /lib/lsb/init-functions

# Shell functions sourced from /etc/rc.status:
#      rc_check        check and set local and overall rc status
#      rc_status        check and set local and overall rc status
#      rc_status -v    be verbose in local rc status and clear it afterwards
#      rc_status -v -r  ditto and clear both the local and overall rc status
#      rc_status -s    display "skipped" and exit with status 3
#      rc_status -u    display "unused" and exit with status 3
#      rc_failed        set local and overall rc status to failed
#      rc_failed <num>  set local and overall rc status to <num>
#      rc_reset        clear both the local and overall rc status
#      rc_exit          exit appropriate to overall rc status
#      rc_active        checks whether a service is activated by symlinks
. /etc/rc.status

# Reset status of this service
rc_reset

# Return values acc. to LSB for all commands but status:
# 0          - success
# 1      - generic or unspecified error
# 2      - invalid or excess argument(s)
# 3      - unimplemented feature (e.g. "reload")
# 4      - user had insufficient privileges
# 5      - program is not installed
# 6      - program is not configured
# 7      - program is not running
# 8--199  - reserved (8--99 LSB, 100--149 distrib, 150--199 appl)
#
# Note that starting an already running service, stopping
# or restarting a not-running service as well as the restart
# with force-reload (in case signaling is not supported) are
# considered a success.

case "$1" in
    start)
        echo -n "Starting mydns "
        ## Start daemon with startproc(8). If this fails
        ## the return value is set appropriately by startproc.
        startproc $MYDNS_BIN

        # Remember status and be verbose
        rc_status -v
        ;;
    stop)
        echo -n "Shutting down mydns "
        ## Stop daemon with killproc(8) and if this fails
        ## killproc sets the return value according to LSB.

        killproc -TERM $MYDNS_BIN

        # Remember status and be verbose
        rc_status -v
        ;;
    try-restart|condrestart)
        ## Do a restart only if the service was active before.
        ## Note: try-restart is now part of LSB (as of 1.9).
        ## RH has a similar command named condrestart.
        if test "$1" = "condrestart"; then
                echo "${attn} Use try-restart ${done}(LSB)${attn} rather than condrestart ${warn}(RH)${norm}"
        fi
        $0 status
        if test $? = 0; then
                $0 restart
        else
                rc_reset        # Not running is not a failure.
        fi
        # Remember status and be quiet
        rc_status
        ;;
    restart)
        ## Stop the service and regardless of whether it was
        ## running or not, start it again.
        $0 stop
        $0 start

        # Remember status and be quiet
        rc_status
        ;;
    force-reload)
        ## Signal the daemon to reload its config. Most daemons
        ## do this on signal 1 (SIGHUP).
        ## If it does not support it, restart.

        echo -n "Reload service mydns "
        ## if it supports it:
        killproc -HUP $MYDNS_BIN
        #touch /var/run/mydns.pid
        rc_status -v

        ## Otherwise:
        #$0 try-restart
        #rc_status
        ;;
    reload)
        ## Like force-reload, but if daemon does not support
        ## signaling, do nothing (!)

        # If it supports signaling:
        echo -n "Reload service mydns "
        killproc -HUP $MYDNS_BIN
        #touch /var/run/mydns.pid
        rc_status -v
       
        ## Otherwise if it does not support reload:
        #rc_failed 3
        #rc_status -v
        ;;
    status)
        echo -n "Checking for service mydns "
        ## Check status with checkproc(8), if process is running
        ## checkproc will return with exit status 0.

        # Return value is slightly different for the status command:
        # 0 - service up and running
        # 1 - service dead, but /var/run/  pid  file exists
        # 2 - service dead, but /var/lock/ lock file exists
        # 3 - service not running (unused)
        # 4 - service status unknown :-(
        # 5--199 reserved (5--99 LSB, 100--149 distro, 150--199 appl.)
       
        # NOTE: checkproc returns LSB compliant status values.
        checkproc $MYDNS_BIN
        # NOTE: rc_status knows that we called this init script with
        # "status" option and adapts its messages accordingly.
        rc_status -v
        ;;
    probe)
        ## Optional: Probe for the necessity of a reload, print out the
        ## argument to this init script which is required for a reload.
        ## Note: probe is not (yet) part of LSB (as of 1.9)

        test /etc/mydns/mydns.conf -nt /var/run/mydns.pid && echo reload
        ;;
    *)
        echo "Usage: $0 {start|stop|status|try-restart|restart|force-reload|reload|probe}"
        exit 1
        ;;
esac
rc_exit


bastille-firewall
Code:

#!/bin/sh
#
# bastille-firewall                Load/unload ipchains rulesets
#
# do not rename this file unless you edit /sbin/bastille-firewall-reset
#
# chkconfig: 2345 5 98
# description: A firewall/packet-filter script for Linux systems \
# that allows the machine to be used as a gateway system
#
# $Id: bastille-firewall,v 1.6 2002/02/24 17:19:14 peterw Exp $
# Copyright (c) 1999-2002 Peter Watkins
#
#    This program is distributed in the hope that it will be useful,
#    but WITHOUT ANY WARRANTY; without even the implied warranty of
#    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
#    GNU General Public License for more details.
#
#    You should have received a copy of the GNU General Public License
#    along with this program; if not, write to the Free Software
#    Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307  USA
#
# Thanks to David Ranch, Brad A, Don G, and others for their suggestions
#
# This script is designed to be used as a SysV-style init script.
#
# It should be run with a "start" argument
#        1) as an rc?.d "S" script, _before_ the "network" script
# [copy this to /etc/rc.d/init.d/bastille-firewall (or your equivalent of
#  /etc/rc.d/init.d) and run 'chkconfig -add bastille-firewall' ]
#        2) any time an interface is brought up or changed, e.g.
#          establishing a PPP conection or renewing a DHCP lease
# [copy 'bastille-firewall-reset', 'bastille-firewall-schedule'
#  and 'ifup-local' to /sbin/]
#
#  Normally you Do Not _Ever_ Want to run this with a "stop" argument!
#
# Note that running this with "stop" will disable the firewall and open
# your system to all network traffic; if you make changes to these rules,
# apply them by running the script again with a "start" argument.
#
# ** As of 0.99-beta1, this script merely kicks off the real script,
#    either /sbin/bastille-ipchains or /sbin/bastille-netfilter

# Default is to use the 'ipchains' script, which will load the
# ipchains compatibility module if you're using a 2.4 kernel
REALSCRIPT=/sbin/bastille-ipchains
PATH=/sbin:/bin:/usr/sbin:/usr/bin

# exit function to be called in place of regular Bourne exit
clean_exit()
{
  rmdir /var/lock/bastille-firewall 2>/dev/null
  exit $1
}

[ ! -d /var/lock ] && mkdir -m 0755 /var/lock

mkdir -m 0700 /var/lock/bastille-firewall 2>/dev/null
if [ $? -ne 0 ]; then
  if [ -n "${BASTILLE_FWALL_QUIET_FAIL}" ]; then exit 0; fi
  echo "ERROR: bastille-firewall currently being reset or lock is stuck."
  echo "To un-stick, remove the directory /var/lock/bastille-firewall"
  exit 1
fi

if [ -n "$(uname -r | awk -F. ' $1 == 2 && $2 > 2 {print}')" ]; then
        # We are using Linux 2.3 or newer; use the netfilter script if available
        if [ -x /sbin/bastille-netfilter ]; then
                REALSCRIPT=/sbin/bastille-netfilter
        fi
fi

if [ ! -x ${REALSCRIPT} ]; then
        echo "ERROR: \"${REALSCRIPT}\" not available!"
        clean_exit 1
fi

${REALSCRIPT} "$1"
bretval=$?

# Use "subsys" locks to indicate our status
case "$1" in
  start|restart|reload)
    if [ $bretval -eq 0 ]; then touch /var/lock/subsys/bastille-firewall; fi
    ;;
  stop)
    rm -f /var/lock/subsys/bastille-firewall
    ;;
esac

clean_exit $bretval


falko 19th June 2009 16:37

I guess you need something like this in bastille-firewall as well:

Code:

### BEGIN INIT INFO
# Provides:          mydns
# Required-Start:    $syslog $remote_fs
# Should-Start: $time ypbind sendmail
# Required-Stop:    $syslog $remote_fs
# Should-Stop: $time ypbind sendmail
# Default-Start:    3 5
# Default-Stop:      0 1 2 6
# Short-Description: mydns XYZ daemon providing ZYX
# Description:      Start mydns to allow XY and provide YZ
#        continued on second line by '#<TAB>'
#        should contain enough info for the runlevel editor
#        to give admin some idea what this service does and
#        what it's needed for ...
#        (The Short-Description should already be a good hint.)
### END INIT INFO


valter 20th June 2009 00:28

Yes, that was the part that was missing. Now that part works, however, mydns tries to start before mysql and of course fails, any idea how can I change startup priority of mysql and mydns?

falko 20th June 2009 12:59

I think you have to rename the symlinks in /etc/rc3.d so that the MyDNS symlink has a higher number than the one for MySQL.

valter 20th June 2009 17:23

I have tried that, but it doesn't work. Since bastille-firewall that comes with MyDNSConfig starts mydns, it doesn't really matter what I do, nothing changes...

till 20th June 2009 17:31

Quote:

Since bastille-firewall that comes with MyDNSConfig starts mydns, it doesn't really matter what I do, nothing changes...
Thats not the case, the bastille firewall does not start mydns. Mydns is only started by the links in the runlevel directories. Make sure that there are only mydns startup links in directories were mysql is started too and that the mydns links are afetr the mysql links when you order them alphabetically.


All times are GMT +2. The time now is 22:18.

Powered by vBulletin® Version 3.8.7
Copyright ©2000 - 2014, vBulletin Solutions, Inc.