Hi,
This somehow drifted off the list. Let's try to keep it there.
On Thu, Feb 14, 2008 at 10:18:32AM -0500, [EMAIL PROTECTED] wrote:
> Ok more info.
>
> I added the pid parameter through the gui and it does show in
> /var/lib/heartbeat/crm/cib.xml:
>
> <primitive class="ocf" type="mysql" provider="heartbeat"
> id="mysql_repl">
> <instance_attributes id="mysql_repl_instance_attrs">
> <attributes>
> <nvpair name="target_role" id="mysql_repl_target_role"
> value="started"/>
> <nvpair id="de970238-7dfb-4505-b623-5f316b3432454"
> name="datadir" value="/replicated/mysql/data"/>
> <nvpair id="b5dd43ba-297c-493a-999f-85ceb5f3f72f" name="pid"
> value="/var/run/mysqld/mysqld.pid"/>
> </attributes>
> </instance_attributes>
> </primitive>
>
> However when running by hand still getting this:
How did you run it by hand? Did you add the new OCF_RESKEY_pid
parameter too? That should work.
> Looking at the 2.1.2 OCF it used to have this:
>
> : ${OCF_RESKEY_pid="/var/run/mysqld/mysqld.pid"}
>
> The 2.1.3 OCF now has this:
>
> OCF_RESKEY_pid_default="/var/mysql/mysqld.pid"
That's actually for OpenBSD. But still I can see that the default
was changed to
OCF_RESKEY_pid_default="/var/run/mysql/mysqld.pid"
which is a regression.
> While it shouldn't be a problem to just set the parameter it
> does make it impossible to run 2 different versions of the
> heartbeat at the same time while doing a gradual upgrade (ie
> one machine in production and one machine out of production
> getting upgraded).
>
> Should this be reported as a bug? While I can work around it it
> does mean potential production downtime while switching servers
> around.
Sorry about that. Perhaps it should be reverted back to what has
been there before. A bugzilla entry would be good too.
Thanks,
Dejan
>
> Thanks,
>
> Amy
>
>
>
> -----Original Message-----
> From: Dejan Muhamedagic <[EMAIL PROTECTED]>
> Sent: Thursday, February 14, 2008 7:05am
> To: [EMAIL PROTECTED]
> Subject: Re: FW: Re: [Linux-HA] mysql OCF issue on CentOS 5.1 after upgrading
> to heartbeat 2.1.3-3
>
> Hi,
>
> On Wed, Feb 13, 2008 at 02:54:38PM -0500, [EMAIL PROTECTED] wrote:
> > Dejan,
> >
> > Just a thought after reading other posts. Could the pacemaker
> > packages be needed as their functionality has been seperated
> > out?
>
> Not with the Heartbeat release 2.1.3. That release includes the
> CRM (pacemaker).
>
> > passwd and group both in the stard location /etc
> >
> > nssswitch.conf
> > passwd: files
> > shadow: files
> > group: files
>
> OK, this rules out a network delay.
>
> > Here is the output from the command line before I end it after getting
> > stuck at the same place:
> >
> > # OCF_RESKEY_datadir="/replicated/mysql/data" sh -x
> > /usr/lib/ocf/resource.d/heartbeat/mysql start
> > + . /usr/lib/ocf/resource.d/heartbeat/.ocf-shellfuncs
> [snip]
> > + /sbin/restorecon /var/log/mysqld.log
> > + '[' 0 -a '!' -d /replicated/mysql/data/mysql ']'
> > + /usr/bin/safe_mysqld --defaults-file=/etc/my.cnf
> > --pid-file=/var/run/mysql/mysqld.pid --socket=/var/lib/mysql/mysql.sock
> > --datadir=/replicated/mysql/data --user=mysql
> > + rc=0
> > + '[' 0 '!=' 0 ']'
>
> It looks as if mysql started here...
>
> > + start_wait=1
> > + '[' 1 = 1 ']'
> > + mysql_status
> > + '[' '!' -e /var/run/mysql/mysqld.pid ']'
> > + ocf_log debug 'MySQL is not running'
>
> but the status reports that it is not because it can't find the
> pid file. Please check where's the pid file and if mysql is
> running or not. This looks like a mysql setup problem.
>
> Thanks,
>
> Dejan
>
>
>
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
