Error Cannot Locate Resource Script Mysql
Administrators Archives Installation and Configuration Archives High Availability problems Zarafa is hiring!We are looking for new team members at Zarafa! Are you (or do you know) a C++ expert, a JavaScript specialist or a testing guru? Check out our careers page to learn more and apply. Results 1 to 4 of 4 Thread: High Availability problems Thread Tools Show Printable Version Email this Page… Subscribe to this Thread… Search Thread Advanced Search Display Linear Mode Switch to Hybrid Mode Switch to Threaded Mode 25-09-2009,10:12 AM #1 Ewout View Profile View Forum Posts Private Message Junior Member Join Date Sep 2009 Posts 3 High Availability problems Hello, I followed the manual http://download.zarafa.com/zarafa/relea ... per.en.pdf located on your site. Mysql replication works fine, thats not the problem, but when node1 is shutdown, node 2 doesn't take over the ipadres of node1. Also i cannot logon to webaccess on node2. Probably the sam problem. Some xtra information ha.cf file: debugfile /var/log/ha-debug logfile /var/log/ha-log logfacility local0 keepalive 10 deadtime 60 initdead 90 udpport 694 bcast eth1 auto_failback no node zarafa1.*.local node zarafa2.*.local authkeys: auth 2 2 sha1 ****** haresources: zarafa1.*.local 10.1.1.1 failover (ip is private ip of node1) failover Code: #! /bin/sh export PATH="${PATH:+$PATH:}/usr/sbin:/sbin" case "$1" in start) ifconfig eth0:1 192.168.3.30 netmask 255.255.255.0 (IP is public ip node1) /etc/init.d/zarafa-gateway start /etc/init.d/zarafa-ical start /etc/init.d/zarafa-monitor start /etc/init.d/zarafa-server start /etc/init.d/zarafa-spooler start ;; stop) /etc/init.d/networking restart /etc/init.d/zarafa-gateway stop /etc/init.d/zarafa-ical stop /etc/init.d/zarafa-monitor stop /etc/init.d/zarafa-server stop /etc/init.d/zarafa-spooler stop ;; restart) $0 stop $0 start echo "." ;; *) echo "Usage: /etc/init.d/failover {start|stop|restart}" exit 1 esac exit 0 Ha-log gives these errors ResourceManager[7247]: 2009/09/25_11:10:59 ERROR: Cannot locate resource script failover ResourceManager[7247]: 2009/09/25_11:10:59 ERROR: Cannot locate resource script failover I think i found the error, probably the location of my fai
sorted by: [ date ] [ thread ] [ subject ] [ author ] Hi Everyone, For some reason, when heartbeat is started, it logs an error over and over and over in the logs about failing to find the resource https://forums.zarafa.com/showthread.php?3010-High-Availability-problems script lava2042 (lava2042 is the hostname of the machine). Here's the error I'm seeing: May 2 16:31:54 lava2042 ResourceManager[10454]: [10640]: ERROR: Cannot locate resource script lava2042 May 2 16:31:54 lava2042 ResourceManager[10454]: [10641]: ERROR: Cannot locate resource http://lists.linux-ha.org/pipermail/linux-ha/2007-May/025053.html script lava2042 May 2 16:31:55 lava2042 ResourceManager[10454]: [10644]: info: Retrying failed stop operation [lava2042] and here is my /etc/ha.d/haresources: lava2042 10.5.140.42 DxnasDb lava2042 10.5.140.42 DxnasServer and my ha.cf file: bcast eth1 keepalive 2 warntime 10 deadtime 30 initdead 120 udpport 694 auto_failback on node lava2042 node lava2138 Why is it looking for a script named after the hostname? It should be looking after the DxnasDb and DxnasServer scripts. - Lee Hinman Previous message: [Linux-HA] DRAC4 Stonith Plugin Next message: [Linux-HA] Cannot locate resource script
> > i have got a problem with heartbet on a Suse Linux Enterprise Server > 9. > (heartbeat installed by latest SuSe rpm file) i.e. http://osdir.com/ml/linux.highavailability.user/2004-11/msg00070.html heartbeat-1.2.2-0.6, works fine 4 me > > Heartbeat starts normal and the ip change of my 2 nodes runs normal. > But the init Scripts for my services, e.g. http://wiki.kolmisoft.com/index.php/Heartbeat_configuration apache, don`t run. > > There is always the following Message in the heartbeat log: > > heartbeat: 2004/11/05_10:54:00 ERROR: Cannot locate resource script > apache > > The error cannot original apache script rom heartbeat is in the resource directory > of hearbet and has the correct rights. > (-rwxr-xr-x 1 root root 8301 Oct 27 2003 apache) > > The other scripts in the resource directory don`t run work with > heartbeat, too. > And my own scripts don`t work, too. > > Does somebody know, how i error cannot locate can solve this problem? You might check whether the corresponding variables in /etc/ha.d/shellfuncs are set correctly: : ${HA_DIR=/etc/ha.d} : ${HA_RESOURCEDIR=$HA_DIR/resource.d} and your collegue didn't comment out in /etc/init.d/heartbeat: . $HA_DIR/shellfuncs If the virtual IP allready works, does IPaddr2::
a given measurement period. Lets say you have two servers 'A' and 'B' with MOR installed, MySQL is running replication between them. By default all trafic comming to server 'A' is monitored by server 'B', so when server 'A' fails, server 'B' stands in its position by given time. So allmost no data is lost, and your users will be happy with your services. What is Heartbeat? Heartbeat is software which implements these monitoring and availability features for your servers. It must be carrefully installed, configured and tested on both servers to ensure correct producing of services. What do you need to know before starting Please review once more the provided above scheme. It represents a typical Linux Heartbeat configuration. Before starting you have to be aware of 4 main points: 1. All public IP addresses have to be on same subnet. 2. Virtual IP has to be free (not assigned to any device on the network) and the last octet of the address (in this case .4 is the last octet) has to be the highest in the configuration. Server A and B have to be on "lower" IP, in this case .2 and .3 (the last octet). 3. Never use servers when they are off-line as it will ruin the MySQL replication. 4. After heartbeat configuration has been made, do not change the addressing scheme or the host-names of the servers. Installation Hearbeat 2.99 has been full tested on Centos 5.2 only, there is no guarantee that it will work on older versions or distros. Download mor install scripts from svn. in both servers. Run /usr/src/mor/sh_scripts/install_heartbeat.sh in both servers Script will: * download special file, then yum automaticaly install correct heartbeat files for your system. * install pacemaker, its future only. * configure /etc/ha.d/authkeys so you don't need to change anything here * configure /etc/ha.d/ha.cf file, but you still need adjust it by hand (how? later on this page). * configure /etc/ha.d/haresources file, but you still need to change few bits there, also, later on this page. * add 2 lines to /etc/hosts, but just for testing purporses only, so you will have to change ips here. ATTENTION: if you installed Heartbeat