Mailing List Archive

Cannot locate resource script
Below are log examples of a shutdown and startup. I
can't figure out where the resource file is an
issue... Any Ideas??

I can run datadisk and httpd by hand and no issues are
observed.


heartbeat: 2003/02/14_14:00:17 info: Heartbeat
shutdown in progress. (5778)
heartbeat: 2003/02/14_14:00:17 info: Giving up all HA
resources.
heartbeat: 2003/02/14_14:00:17 info: Releasing
resource group: clus1 172.17.230.13 datadisk::drbd0
httpd
heartbeat: 2003/02/14_14:00:17 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:00:17 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:00:17 info: Running
/etc/init.d/httpd stop




heartbeat: 2003/02/14_14:15:52 info: Running
/etc/ha.d/resource.d/datadisk drbd0 start
heartbeat: 2003/02/14_14:15:52 info: Running
/etc/init.d/httpd start
heartbeat: 2003/02/14_14:15:54 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:15:54 ERROR: Cannot locate
resource script



__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
Cannot locate resource script [ In reply to ]
It is trying to find a script called start

Matt

-----Original Message-----
From: Rob [mailto:robs_ha_email@yahoo.com]
Sent: Friday, February 14, 2003 4:31 PM
To: ha-list
Subject: Cannot locate resource script



Below are log examples of a shutdown and startup. I
can't figure out where the resource file is an
issue... Any Ideas??

I can run datadisk and httpd by hand and no issues are
observed.


heartbeat: 2003/02/14_14:00:17 info: Heartbeat
shutdown in progress. (5778)
heartbeat: 2003/02/14_14:00:17 info: Giving up all HA
resources.
heartbeat: 2003/02/14_14:00:17 info: Releasing
resource group: clus1 172.17.230.13 datadisk::drbd0
httpd
heartbeat: 2003/02/14_14:00:17 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:00:17 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:00:17 info: Running
/etc/init.d/httpd stop




heartbeat: 2003/02/14_14:15:52 info: Running
/etc/ha.d/resource.d/datadisk drbd0 start
heartbeat: 2003/02/14_14:15:52 info: Running
/etc/init.d/httpd start
heartbeat: 2003/02/14_14:15:54 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:15:54 ERROR: Cannot locate
resource script



__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
Cannot locate resource script [ In reply to ]
Actually.. Ignore that.

Can you include your /etc/ha.d/ha.cf file ? Without that it's not possible
to anywise this problem.

-----Original Message-----
From: Rob [mailto:robs_ha_email@yahoo.com]
Sent: Friday, February 14, 2003 4:31 PM
To: ha-list
Subject: Cannot locate resource script



Below are log examples of a shutdown and startup. I
can't figure out where the resource file is an
issue... Any Ideas??

I can run datadisk and httpd by hand and no issues are
observed.


heartbeat: 2003/02/14_14:00:17 info: Heartbeat
shutdown in progress. (5778)
heartbeat: 2003/02/14_14:00:17 info: Giving up all HA
resources.
heartbeat: 2003/02/14_14:00:17 info: Releasing
resource group: clus1 172.17.230.13 datadisk::drbd0
httpd
heartbeat: 2003/02/14_14:00:17 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:00:17 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:00:17 info: Running
/etc/init.d/httpd stop




heartbeat: 2003/02/14_14:15:52 info: Running
/etc/ha.d/resource.d/datadisk drbd0 start
heartbeat: 2003/02/14_14:15:52 info: Running
/etc/init.d/httpd start
heartbeat: 2003/02/14_14:15:54 ERROR: Cannot locate
resource script
heartbeat: 2003/02/14_14:15:54 ERROR: Cannot locate
resource script



__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
Cannot locate resource script [ In reply to ]
--0-655942385-1045259193=:96446
Content-Type: text/plain; charset=us-ascii
Content-Id:
Content-Disposition: inline

--- "Soffen, Matthew" <msoffen@iso-ne.com> wrote:
> Actually.. Ignore that.
>
> Can you include your /etc/ha.d/ha.cf file ? Without
> that it's not possible
> to anywise this problem.
>


Done

__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
--0-655942385-1045259193=:96446
Content-Type: text/plain; name="ha.cf"
Content-Description: ha.cf
Content-Disposition: inline; filename="ha.cf"

#
# There are lots of options in this file. All you have to have is a set
# of nodes listedJ {"node ...}
# and one of {serial, udp, or mcast}
#
#
# Note on logging:
# If any of debugfile, logfile and logfacility are defined then they
# will be used. If debugfile and/or logfile are not defined and
# logfacility is defined then the respective logging and debug
# messages will be loged to syslog. If logfacility is not defined
# then debugfile and logfile will be used to log messges. If
# logfacility is not defined and debugfile and/or logfile are not
# defined then defaults will be used for debugfile and logfile as
# required and messages will be sent there.
#
# File to wirte debug messages to
#debugfile /var/log/ha-debug
#
#
# File to write other messages to
#
logfile /var/log/ha.log
#
#
# Facility to use for syslog()/logger
#
logfacility local0
#
#
# keepalive: how many seconds between heartbeats
#
keepalive 2
#
# deadtime: seconds-to-declare-host-dead
#
deadtime 10
#
#
# Very first dead time (initdead)
#
# On some machines/OSes, etc. the network takes a while to come up
# and start working right after you've been rebooted. As a result
# we have a separate dead time for when things first come up.
# It should be at least twice the normal dead time.
#
#initdead 120
#
#
# The default is "off", which means that it WILL fail
# back to the node which is declared as primary in haresources
#
# "on" means that resources only move to new nodes when
# the nodes they are served on die. This is deemed as a
# "nice" behavior (unless you want to do active-active).
#
nice_failback on
#
# hopfudge maximum hop count minus number of nodes in config
#hopfudge 1
#
# serial serialportname ...
serial /dev/ttyS0
#
#
# Baud rate for serial ports...
#
baud 19200
#
# What UDP port to use for communication?
#
udpport 694
#
# What interfaces to heartbeat over?
#
udp eth2
#
# Set up a multicast heartbeat medium
# mcast [dev] [mcast group] [port] [ttl] [loop]
#
# [dev] device to send/rcv heartbeats on
# [mcast group] multicast group to join (class D multicast address
# 224.0.0.0 - 239.255.255.255)
# [port] udp port to sendto/rcvfrom (no real reason to differ
# from the port used for broadcast heartbeats)
# [ttl] the ttl value for outbound heartbeats. this effects
# how far the multicast packet will propagate. (0-255)
# [loop] toggles loopback for outbound multicast heartbeats.
# if enabled, an outbound packet will be looped back and
# received by the interface it was sent on. (0 or 1)
#
#
mcast eth2 225.0.0.1 694 1 1
#
# Watchdog is the watchdog timer. If our own heart doesn't beat for
# a minute, then our machine will reboot.
#
#watchdog /dev/watchdog
#
# "Legacy" STONITH support
# Using this directive assumes that there is one stonith
# device in the cluster. Parameters to this device are
# read from a configuration file. The format of this line is:
#
# stonith <stonith_type> <configfile>
#
# NOTE: it is up to you to maintain this file on each node in the
# cluster!
#
#stonith baytech /etc/ha.d/conf/stonith.baytech
#
# STONITH support
# You can configure multiple stonith devices using this directive.
# The format of the line is:
# stonith_host <hostfrom> <stonith_type> <params...>
# <hostfrom> is the machine the stonith device is attached
# to or * to mean it is accessible from any host.
# <stonith_type> is the type of stonith device (a list of
# supported drives is in /usr/lib/stonith.)
# <params...> are driver specific parameters. To see the
# format for a particular device, run:
# stonith -l -t <stonith_type>
#
#
# Note that if you put your stonith device access information in
# here, and you make this file publically readable, you're asking
# for a denial of service attack ;-)
#
#
#stonith_host * baytech 10.0.0.3 mylogin mysecretpassword
#stonith_host ken3 rps10 /dev/ttyS1 kathy 0
#stonith_host kathy rps10 /dev/ttyS1 ken3 0

#stonith_host clus1 apcsmart /dev/ttyS1 clus2 0
#stonith_host clus2 apcsmart /dev/ttyS1 clus1 0

#
# Tell what machines are in the cluster
# node nodename ... -- must match uname -n
#node ken3
#node kathy
node clus1
node clus2

--0-655942385-1045259193=:96446
Content-Type: text/plain; name=haresources
Content-Description: haresources
Content-Disposition: inline; filename=haresources

#
# This is a list of resources that move from machine to machine as
# nodes go down and come up in the cluster. Do not include
# "administrative" or fixed IP addresses in this file.
#
# We refer to this file when we're coming up, and when a machine is being
# taken over after going down.
#
# You need to make this right for your installation, then install it in
# /etc/ha.d
#
# These resources in this file are either IP addresses, or the name
# of scripts to run to "start" or "stop" the given resource.
#
# The format is like this:
#
#node-name resource1 resource2 ... resourceN
#
# If the resource name contains an :: in the middle of it, the
# part after the :: is passed to the resource script as an argument.
# Multiple arguments are separated by the :: delimeter
#
# In the case of IP addresses, the resource script name IPaddr is
# implied.
#
# For example, the IP address 135.9.8.7 could also be represented
# as IPaddr::135.9.8.7
#
# THIS IS IMPORTANT!! vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
#
# The given IP address is directed to an interface which has a route
# to the given address. This means you have to have a net route
# set up outside of the High-Availability structure. We don't set it
# up here -- we key off of it.
#
# The broadcast address for the IP alias that is created to support
# an IP address defaults to the highest address on the subnet.
#
# The netmask for the interface that is brought up on this IP address
# defaults to the same netmask as the route that it selected in
# in the step above.
#
# If you want to specify that this IP address is to be brought up
# on a subnet with a netmask of 255.255.255.0, you would specify
# this as IPaddr::135.9.8.7/8 .
#
# If you wished to tell it that the broadcast address for this subnet
# was 135.9.8.210, then you would specify that this way:
# IPaddr::135.9.8.7/8/135.9.8.210
#
# The IP addresses you list in this file are called "service" addresses,
# since they're they're the publicly advertised addresses that clients
# use to get at highly available services.
#
# For a hot/standby (non load-sharing) 2-node system with only
# a single service address,
# you will probably only put one system name and one IP address in here.
# The name you give the address to is the name of the default "hot"
# system.
#
# Where the nodename is the name of the node which "normally" owns the
# resource. If this machine is up, it will always have the resource
# it is shown as owning.
#
# The string you put in for nodename must match the uname -n name
# of your machine. Depending on how you have it administered, it could
# be a short name or a FQDN.
#
#-------------------------------------------------------------------
#
# Simple case: One service address, default subnet and netmask
# No servers that go up and down with the IP address
#
#just.linux-ha.org 135.9.216.110
#
#-------------------------------------------------------------------
#
# Assuming the adminstrative addresses are on the same subnet...
# A little more complex case: One service address, default subnet
# and netmask, and you want to start and stop http when you get
# the IP address...
#
#just.linux-ha.org 135.9.216.110 http
#-------------------------------------------------------------------
#
# A little more complex case: Three service addresses, default subnet
# and netmask, and you want to start and stop http when you get
# the IP address...
#
#just.linux-ha.org 135.9.216.110 135.9.215.111 135.9.216.112 httpd
#-------------------------------------------------------------------
#
# One service address, with funny subnet and bcast addr
# Stop and start httpd service with the subnet address
#
#just.linux-ha.org 135.9.216.3/4/135.9.216.12 httpd
#
#-------------------------------------------------------------------
#
# An example where a shared filesystem is to be used.
# Note that multiple aguments are passed to this script using
# the delimiter '::' to separate each argument.
#
#node1 10.0.0.170 Filesystem::/dev/sda1::/data1::ext2
clus1 172.17.230.13 datadisk::drbd0 httpd

--0-655942385-1045259193=:96446--
Cannot locate resource script [ In reply to ]
--0-1042751390-1045259501=:18857
Content-Type: text/plain; charset=us-ascii
Content-Id:
Content-Disposition: inline

--- Rob <robs_ha_email@yahoo.com> wrote:
> --- "Soffen, Matthew" <msoffen@iso-ne.com> wrote:
> > Actually.. Ignore that.
> >
> > Can you include your /etc/ha.d/ha.cf file ?
> Without
> > that it's not possible
> > to anywise this problem.
> >
>
>
> Done
>

Here's my drbd.conf:


__________________________________________________
Do you Yahoo!?
Yahoo! Shopping - Send Flowers for Valentine's Day
http://shopping.yahoo.com
--0-1042751390-1045259501=:18857
Content-Type: text/plain; name="drbd.conf"
Content-Description: drbd.conf
Content-Disposition: inline; filename="drbd.conf"

#
# Comment lines.
#

# global {
# use this if you want to define more resources later
# without reloading the module.
# by default we load the module with exactly as many devices
# as configured mentioned in this file.
# minor_count=5

# this is for people which set up a drbd device via the
# loopback network interface or between two VMs on the same
# box, for testing/simulating/presentation
# otherwise it could trigger a run_tasq_queue deadlock.
# disable_io_hints
# }

#
# this need not be drbd#, you may use phony resource names,
# like "resource web" or "resource mail", too
#

resource drbd0 {

protocol = B
fsckcmd = fsck -p -y

# if inittimeout is positive will fore primary status if
# connection could not be established within that time
# (seconds). *this may compromise your data integrity*
#
# a negative value indicates that drbd should stay WFConnection
# secondary/unknown and just continue the boot process, thus
# leaving the decision to the cluster manager
#
# not given/0: wait until the partner node shows up, or
# some operator intervenes; do not timeout.

# inittimeout=60

# skip-wait is actually skip-wait-for-sync ...
# we wait for connection regardless (but see inittimeout above)

# skip-wait

# load-only: load the configuration data to the module only.
# if you have a reasonably intelligent cluster manager,
# you may want to use this instead of a negative
# inittimeout for an unattended setup. this will not slow
# down the boot process even if the partner node is not
# seen.

# load-only

# what should be done in case the cluster starts up in
# degraded mode, but knows it has inconsistent data
# the default is: do nothing here, but leave it to the
# cluster manager/operator.

# incon-degr-cmd=halt -f

disk {
do-panic
disk-size = 4096543
}

# you can reconfigure the sync rate at runtime using
# drbdsetup on the primary.

net {
# skip-sync
# sync-min
# sync-rate # synonym for sync-max
# sync-nice = -18 # if synchronization is high priority for you
# sync-max = 100M # if you don't care about network saturation
sync-max = 250M
tl-size = 5000
timeout = 60
connect-int = 10
ping-int = 10
}

on clus1 {
device = /dev/nb0
disk = /dev/sdc1
address = 192.168.12.1
port = 7788
}

on clus2 {
device = /dev/nb0
disk = /dev/sdc1
address = 192.168.12.2
port = 7788
}
}

--0-1042751390-1045259501=:18857--