text:
10 U.S. Code § 987 - Terms of consumer credit extended to members and dependents: limitations
prev | next
(a) Interest.— A creditor who extends consumer credit to a covered member of the armed forces or a dependent of such a member shall not require the member or dependent to pay interest with respect to the extension of such credit, except as—
(b) Annual Percentage Rate.— A creditor described in subsection (a) may not impose an annual percentage rate of interest greater than 36 percent with respect to the consumer credit extended to a covered member or a dependent of a covered member.
(c) Mandatory Loan Disclosures.—
(1) Information required.— With respect to any extension of consumer credit (including any consumer credit originated or extended through the internet) to a covered member or a dependent of a covered member, a creditor shall provide to the member or dependent the following information orally and in writing before the issuance of the credit:
(d) Preemption.—
(1) Inconsistent laws.— Except as provided in subsection (f)(2), this section preempts any State or Federal law, rule, or regulation, including any State usury law, to the extent that such law, rule, or regulation is inconsistent with this section, except that this section shall not preempt any such law, rule, or regulation that provides protection to a covered member or a dependent of such a member in addition to the protection provided by this section.
(2) Different treatment under state law of members and dependents prohibited.— States shall not—
(A) authorize creditors to charge covered members and their dependents annual percentage rates of interest for loans higher than the legal limit for residents of the State; or
(e) Limitations.— It shall be unlawful for any creditor to extend consumer credit to a covered member or a dependent of such a member with respect to which—
(1) the creditor rolls over, renews, repays, refinances, or consolidates any consumer credit extended to the borrower by the same creditor with the proceeds of other credit extended to the same covered member or a dependent;
(2) the borrower is required to waive the borrower's right to legal recourse under any otherwise applicable provision of State or Federal law, including any provision of the Servicemembers Civil Relief Act;
(3) the creditor requires the borrower to submit to arbitration or imposes onerous legal notice provisions in the case of a dispute;
(5) the creditor uses a check or other method of access to a deposit, savings, or other financial account maintained by the borrower, or the title of a vehicle as security for the obligation;
(6) the creditor requires as a condition for the extension of credit that the borrower establish an allotment to repay an obligation; or
(f) Penalties and Remedies.—
(1) Misdemeanor.— A creditor who knowingly violates this section shall be fined as provided in title 18, or imprisoned for not more than one year, or both.
(2) Preservation of other remedies.— The remedies and rights provided under this section are in addition to and do not preclude any remedy otherwise available under law to the person claiming relief under this section, including any award for consequential and punitive damages.
(3) Contract void.— Any credit agreement, promissory note, or other contract prohibited under this section is void from the inception of such contract.
(4) Arbitration.— Notwithstanding section 2 of title 9, or any other Federal or State law, rule, or regulation, no agreement to arbitrate any dispute involving the extension of consumer credit shall be enforceable against any covered member or dependent of such a member, or any person who was a covered member or dependent of that member when the agreement was made.
(5) Civil liability.—
(A) In general.— A person who violates this section with respect to any person is civilly liable to such person for—
(B) Costs of the action.— In any successful action to enforce the civil liability described in subparagraph (A), the person who violated this section is also liable for the costs of the action, together with reasonable attorney fees as determined by the court.
(C) Effect of finding of bad faith and harassment.— In any successful action by a defendant under this section, if the court finds the action was brought in bad faith and for the purpose of harassment, the plaintiff is liable for the attorney fees of the defendant as determined by the court to be reasonable in relation to the work expended and costs incurred.
(D) Defenses.— A person may not be held liable for civil liability under this paragraph if the person shows by a preponderance of evidence that the violation was not intentional and resulted from a bona fide error notwithstanding the maintenance of procedures reasonably adapted to avoid any such error. Examples of a bona fide error include clerical, calculation, computer malfunction and programming, and printing errors, except that an error of legal judgment with respect to a person's obligations under this section is not a bona fide error.
(E) Jurisdiction, venue, and statute of limitations.— An action for civil liability under this paragraph may be brought in any appropriate United States district court, without regard to the amount in controversy, or in any other court of competent jurisdiction, not later than the earlier of—
(i) two years after the date of discovery by the plaintiff of the violation that is the basis for such liability; or
(6) Administrative enforcement.— The provisions of this section (other than paragraph (1) of this subsection) shall be enforced by the agencies specified in section 108 of the Truth in Lending Act (15 U.S.C. 1607) in the manner set forth in that section or under any other applicable authorities available to such agencies by law.
(g) Servicemembers Civil Relief Act Protections Unaffected.— Nothing in this section may be construed to limit or otherwise affect the applicability of section 207 of the Servicemembers Civil Relief Act (50 App. U.S.C. 527).
(h) Regulations.—
(2) Such regulations shall establish the following:
(A) Disclosures required of any creditor that extends consumer credit to a covered member or dependent of such a member.
(B) The method for calculating the applicable annual percentage rate of interest on such obligations, in accordance with the limit established under this section.
(C) A maximum allowable amount of all fees, and the types of fees, associated with any such extension of credit, to be expressed and disclosed to the borrower as a total amount and as a percentage of the principal amount of the obligation, at the time at which the transaction is entered into.
(D) Definitions of "creditor" under paragraph (5) and "consumer credit" under paragraph (6) of subsection (i), consistent with the provisions of this section.
(3) In prescribing regulations under this subsection, and not less often than once every two years thereafter, the Secretary of Defense shall consult with the following:
(i) Definitions.— In this section:
(1) Covered member.— The term "covered member" means a member of the armed forces who is—
(2) Dependent.— The term "dependent", with respect to a covered member, means a person described in subparagraph (A), (D), (E), or (I) of section 1072 (2) of this title.
(3) Interest.— The term "interest" includes all cost elements associated with the extension of credit, including fees, service charges, renewal charges, credit insurance premiums, any ancillary product sold with any extension of credit to a servicemember or the servicemember's dependent, as applicable, and any other charge or premium with respect to the extension of consumer credit.
(4) Annual percentage rate.— The term "annual percentage rate" has the same meaning as in section 107 of the Truth and Lending Act (15 U.S.C. 1606), as implemented by regulations of the Board of Governors of the Federal Reserve System. For purposes of this section, such term includes all fees and charges, including charges and fees for single premium credit insurance and other ancillary products sold in connection with the credit transaction, and such fees and charges shall be included in the calculation of the annual percentage rate.
(5) Creditor.— The term "creditor" means a person—
(A) who—
(6) Consumer credit.— The term "consumer credit" has the meaning provided for such term in regulations prescribed under this section, except that such term does not include
(B) a loan procured in the course of purchasing a car or other personal property, when that loan is offered for the express purpose of financing the purchase and is secured by the car or personal property procured.
Source(Added Pub. L. 109–364, div. A, title VI, § 670(a),Oct. 17, 2006, 120 Stat. 2266; amended Pub. L. 112–239, div. A, title VI, §§ 661(a), (b), 662 (a), (b), 663,Jan. 2, 2013, 126 Stat. 1785, 1786.)
Amendment of Subsection (d)(2)
Pub. L. 112–239, div. A, title VI, § 661(a), (c),Jan. 2, 2013, 126 Stat. 1785, provided that, one year after Jan. 2, 2013, or such earlier date as the Secretary of Defense shall specify in the modification of regulations required by § 661(c)(1) ofPub. L. 112–239, subsection (d)(2) of this section is amended— (1) in subparagraph (A), by inserting "any consumer credit or" before "loans"; and (2) in subparagraph (B), by inserting "covering consumer credit" after "State consumer lending protections". See 2011 Amendment notes below.
References in Text
The Truth in Lending Act, referred to in subsec. (c)(1)(B), (2), is title I of Pub. L. 90–321, May 29, 1968, 82 Stat. 146, as amended, which is classified generally to subchapter I (§ 1601 et seq.) of chapter 41 of Title 15, Commerce and Trade. For complete classification of this Act to the Code, see Short Title note set out under section 1601 of Title 15 and Tables.
The Servicemembers Civil Relief Act, referred to in subsecs. (e)(2) and (g), is act Oct. 17, 1940, ch. 888, 54 Stat. 1178, as amended, which is classified to section 501 et seq. of Title 50, Appendix, War and National Defense. For complete classification of this Act to the Code, see section 501 of Title 50, Appendix, and Tables.
2013—Subsec. (d)(2)(A). Pub. L. 112–239, § 661(a)(1), inserted "any consumer credit or" before "loans".
Subsec. (d)(2)(B). Pub. L. 112–239, § 661(a)(2), inserted "covering consumer credit" after "State consumer lending protections".
Subsec. (f)(5), (6). Pub. L. 112–239, § 662(a), (b), added pars. (5) and (6).
Subsec. (h)(3). Pub. L. 112–239, § 661(b)(1), inserted "and not less often than once every two years thereafter," after "under this subsection," in introductory provisions.
Subsec. (h)(3)(E). Pub. L. 112–239, § 661(b)(2), added subpar. (E) and struck out former subpar. (E) which read as follows: "The Office of Thrift Supervision."
Subsec. (i)(2). Pub. L. 112–239, § 663, amended par. (2) generally. Prior to amendment, par. (2) defined the term "dependent".
Effective Date of 2013 Amendments
Pub. L. 112–239, div. A, title VI, § 661(c),Jan. 2, 2013, 126 Stat. 1785, provided that:
"(1) Modification of regulations.—The Secretary of Defense shall modify the regulations prescribed under subsection (h) ofsection 987 of title 10, United States Code, to take into account the amendments made by subsection (a) [amending this section].
"(2) Effective date.—The amendments made by subsection (a) shall take effect on—
"(A) the date that is one year after the date of the enactment of this Act [Jan. 2, 2013]; or
"(B) such earlier date as the Secretary shall specify in the modification of regulations required by paragraph (1).
"(3) Publication of earlier date.—If the Secretary specifies an earlier effective date for the amendments made by subsection (a) pursuant to paragraph (2)(B), the Secretary shall publish notice of such earlier effective date in the Federal Register not later than 90 days before such earlier effective date."
Pub. L. 112–239, div. A, title VI, § 662(c),Jan. 2, 2013, 126 Stat. 1786, provided that: "The amendment made by subsection (a) [amending this section] shall apply with respect to consumer credit extended on or after the date of the enactment of this Act [Jan. 2, 2013]."
Effective Date
Pub. L. 109–364, div. A, title VI, § 670(c),Oct. 17, 2006, 120 Stat. 2269, provided that:
"(1) In general.—Except as provided in paragraph (2), section 987 of title 10, United States Code, as added by subsection (a), shall take effect on October 1, 2007, or on such earlier date as may be prescribed by the Secretary of Defense, and shall apply with respect to extensions of consumer credit on or after such effective date.
"(2) Authority to prescribe regulations.—Subsection (h) of such section shall take effect on the date of the enactment of this Act [Oct. 17, 2006].
"(3) Publication of earlier effective date.—If the Secretary of Defense prescribes an effective date for section 987 of title 10, United States Code, as added by subsection (a), earlier than October 1, 2007, the Secretary shall publish that date in the Federal Register. Such publication shall be made not less than 90 days before that earlier effective date."
Interim Regulations
Pub. L. 109–364, div. A, title VI, § 670(d),Oct. 17, 2006, 120 Stat. 2269, provided that: "The Secretary of Defense may prescribe interim regulations as necessary to carry out such section [this section]. For the purpose of prescribing such interim regulations, the Secretary is excepted from compliance with the notice-and-comment requirements of section 553 of title 5, United States Code. All interim rules prescribed under the authority of this subsection that are not earlier superseded by final rules shall expire no later than 270 days after the effective date of section 987 of title 10, United States Code [see Effective Date note above], as added by this section."
LII has no control over and does not endorse any external Internet site that contains links to or references LII.


text:
And God Created Woman (1988)
Drama, Comedy, Romance
French director Roger Vadim pillages his own grave in this nominal re-make of his 1956 creamy sensation And God Created Woman -- the film that made Brigitte Bardot an international star. Unfortunately, he is unable to do the same thing for the cool and cryptic Rebecca DeMornay in this version. DeMornay plays an escaped convict who lands in the limousine of New Mexico gubernatorial candidate Frank Langella and seduces him. For some inexplicable reason, she turns into a hot singing act. DeMornay also seduces innocent stud carpenter Vincent Spano along the way and suckers the poor guy into marrying her so that she can get an early parole. But the joke is on him when she announces that their marriage does not include sexual relations.~ Paul Brenner, All Movie Guide
Cast: Frank Langella, Donovan Leitch, Rebecca De Mornay, Vincent Spano, Judith Chapman
Produced by:
Directed by: Roger Vadim
Written by: R.J. Stewart
Running time: 1hr 34min
Opens: Jan 01, 1988
|Theaters for Today
Pick a day
on this day.

subset: commoncrawl


text:
Check out the setlist and reviews from last night's co-headlining gig with Widespread Panic at the Summerfest in On The Road. Also check out the Milwaukee Journal Sentinel's review and photos at www.jsonline.com.
Check Out Photos From The Last Shows Of The North American Tour Including Berkeley, San Diego, Santa Barbara And Many More In On The Road. The Addition Of These Photos Brings The Total Count To More Than 500. Keep 'em Coming!
Check out the setlist from tonight's show at the Torhout Werchter Festival in Belgium in the Setlist Archive or post your review in On The Road.


text:
If you have followed the instructions but your replication setup is not working, the first thing to do is check the error log for messages. Many users have lost time by not doing this soon enough after encountering problems.
If you cannot tell from the error log what the problem was, try the following techniques:
Verify that the master has binary logging enabled by issuing a
SHOW MASTER STATUS statement.
If logging is enabled,
Position is nonzero.
If binary logging is not enabled, verify that you are running
the master with the
Verify that the master and slave both were started with the
--server-id option and that the
ID value is unique on each server.
Verify that the slave is running. Use
SHOW SLAVE STATUS to check
whether the
Slave_IO_Running and
Slave_SQL_Running values are both
Yes. If not, verify the options that were
used when starting the slave server. For example,
--skip-slave-start prevents the
slave threads from starting until you issue a
START SLAVE statement.
If the slave is running, check whether it established a
connection to the master. Use
PROCESSLIST, find the I/O and SQL threads and check
State column to see what they
display. See
Section 17.2.1, "Replication Implementation Details". If the
I/O thread state says
Connecting to master,
check the following:
Verify the privileges for the user being used for replication on the master.
Check that the host name of the master is correct and that
you are using the correct port to connect to the master.
The port used for replication is the same as used for
client network communication (the default is
3306). For the host name, ensure that
the name resolves to the correct IP address.
Check that networking has not been disabled on the master
or slave. Look for the
skip-networking option in
the configuration file. If present, comment it out or
remove it.
If the master has a firewall or IP filtering configuration, ensure that the network port being used for MySQL is not being filtered.
Check that you can reach the master by using
ping or
to reach the host.
If the slave was running previously but has stopped, the reason usually is that some statement that succeeded on the master failed on the slave. This should never happen if you have taken a proper snapshot of the master, and never modified the data on the slave outside of the slave thread. If the slave stops unexpectedly, it is a bug or you have encountered one of the known replication limitations described in Section 17.4.1, "Replication Features and Issues". If it is a bug, see Section 17.4.5, "How to Report Replication Bugs or Problems", for instructions on how to report it.
If a statement that succeeded on the master refuses to run on the slave, try the following procedure if it is not feasible to do a full database resynchronization by deleting the slave's databases and copying a new snapshot from the master:
Determine whether the affected table on the slave is
different from the master table. Try to understand how
this happened. Then make the slave's table identical to
the master's and run
If the preceding step does not work or does not apply, try to understand whether it would be safe to make the update manually (if needed) and then ignore the next statement from the master.
If you decide that the slave can skip the next statement from the master, issue the following statements:
SET GLOBAL sql_slave_skip_counter =mysql>
The value of
N should be 1 if
the next statement from the master does not use
AUTO_INCREMENT or
Otherwise, the value should be 2. The reason for using a
value of 2 for statements that use
AUTO_INCREMENT or
LAST_INSERT_ID() is that
they take two events in the binary log of the master.
See also Section 220.127.116.11, "SET GLOBAL sql_slave_skip_counter Syntax".
If you are sure that the slave started out perfectly synchronized with the master, and that no one has updated the tables involved outside of the slave thread, then presumably the discrepancy is the result of a bug. If you are running the most recent version of MySQL, please report the problem. If you are running an older version, try upgrading to the latest production release to determine whether the problem persists.
|Posted by [name withheld] on May 17 2002 2:24am
|[Delete] [Edit]
Note that if you client does not do a "USE
dbname", binlog-do-db=dbname will not binlog a
query like: "update in dbname.foobar set foo=1"
You explicitly have to do a USE before a query in
order to have your query binlogged, it looks
like. Replication on the slave side can do
wildcard matches .. but the master cannot (a la
binlog-wild-do-table=dbname.%). So make sure your
clients do a use, if you plan to replicate those
tables it updates.
|Posted by [name withheld] on May 17 2002 2:24am
|[Delete] [Edit]
for MySQL v3.23.28:
When you attempt to use a certain master-
user/master-password combo to connect to the
mysql master, and you later change my.cnf to
attempt to connect with a new user, you must
update master.info to reflect the changes.
Since my master.info file only had one entry in
it (the slave only has one master), I simply
deleted the file. Upon restarting the slave
daemon, a new master.info was automatically
|Posted by Ed McGuigan on May 17 2002 2:24am
|[Delete] [Edit]
If you need to roll your own log file rotation
script as I did, and you are familiar with Perl,
look at the Log::Rotate module on CPAN rather
than reinventing the wheel.
|Posted by Renato Golin on May 17 2002 2:24am
|[Delete] [Edit]
If you intend to use "load table from master" you need to have access to that table to "rep" user, unlike this sections says of only having to set "File_priv" to "rep" user for all bases.
|Posted by Jesse Thompson on May 17 2002 2:24am
|[Delete] [Edit]
Above on this page where it talks about "properly
modularized and abstracted code" and refers to
safe_reader_query() and safe_writer_query(), I'd
like to put forth the proposition that different
abstracted functions for reading and writing need
not be nessessary for compliance with replication.
We currently have all of our queries running
through One safe-sql envelope, and we intend to
keep this architecture as we move to replication
by telling our envelope to send any queries that
begin with /\s+select/i to the slave, and
anything else to the master. We are running under
the assumption that all "read queries" are
selects. I can't think of any that aren't. If
there were they would probably be nominal in
performace draw (we use many complex select
statements :) and wouldn't do any harm being
handled by the master anyway.
So far as multi-statement queries, are code
doesn't, and won't, mix selects in the same query
with non-selects, or probably even use more than
one select per query, since we're not certain
what results could be returned in such a
circumstance. Thus reading and writing should
never get mixed up in the same query, and all
reads should start with the word "Select".
If you feel that my theory holds water then give
it a go, if you see a flaw in my logic before I
do mail me and lemme know, eh? 10x :)
- - Jess
|Posted by Jeff Allen on May 17 2002 2:24am
|[Delete] [Edit]
When I started up my slave the first time, I had
been using binary logging for some time on the
master. I had already removed $hostname-bin.001
long ago. The slave complained about not being
able to find the first log and would not start
replaying transactions. To fix this, I stopped
the master, made a new snapshot, moved "*-bin.*"
to another directory, and started the master
again. Then when I put the snapshot on the slave
and started it, everything worked correctly.
|Posted by Jonathon Padfield on May 17 2002 2:24am
|[Delete] [Edit]
If you want your slaves to connect to the
replication server with a unique username &
password and minimal privileges, you need to grant
just the FILE privilege to your replication user.
Similarly, if your slaves have no local updates
made on them, just lots of selects, its a very
good idea to connect with a user that cannot
update the data. This stops dead any chance of
mistakenly connecting to the wrong DB and losing
|Posted by joshua paul on May 17 2002 2:24am
|[Delete] [Edit]
With verion 3.23.41 - I couldn't get replication
to work following the instructions about.
Specifically I got errors when I created
the "repl" user before copying data to the slave.
I could only get replication to work if I created
the "repl" user after copying data to the slave -
and obviously starting both servers...
|Posted by [name withheld] on May 17 2002 2:24am
|[Delete] [Edit]
Note: If you are running WinMySQLAdmin, you will
have to make the changes in the my.ini file as
well. It took me a while to realize this.
|Posted by Chad Kouse on May 17 2002 2:24am
|[Delete] [Edit]
incredibly helpful page. I do have one issue to
raise - I have two servers doing 2-way
replication. One is on Linux, and one is on
Windows. There is an issue of case-sensitivity
in that if case is not taken into consideration
on the windows machine, the slave on the linux
machine stops. I'd love to hear any fixes to
this: firstname.lastname@example.com
|Posted by [name withheld] on May 17 2002 2:24am
|[Delete] [Edit]
I also had the problem Allen pointed out above,
in my case I had not actually deleted any of the
binary log files which the slave still required
to update from (I knew this courtesy of "show
slave status" command). But I had deleted several
log files it had finished with. I was able to fix
this without making a brand new snapshot (which
in my case took a larger outage that I would
like) What I did was edit the file (in the
Masters logs directory) $hostname-bin.index and
edited entries to show exact filenames of my
remaining binary log files.(ie: removing the
entries matching ones I had deleted manually from
the file system) I quickly did a mysql stop and
mysql start after that and I performed the
command "slave stop; slave start;" on the slave
and it started replicating again. I am running
version 3.23.41
|Posted by David Dombek on January 30 2003 7:17am
|[Delete] [Edit]
Mysql 3.23.49
When a slave is running you have a master.info file. If you change the slave to become the master you must delete the master.info file or you may get errors such as this:
030130 10:57:03 Slave thread: error connecting to master: Unknown MySQL Server Host '' (4) (107), retry in 60 sec
It will keep retrying every 60 sec. Just deleting the master.info file worked for me.
|Posted by [name withheld] on February 5 2003 11:59pm
|[Delete] [Edit]
I wouldn't suggest running replication on machines with different os. I had win2000 running MySQL server as well a RedHat Linux 7.3 with MySQL server as well. When the client code on Linux tried to connect to win2000 MySQL server, the server died, with win2000 reporting it has terminated.
Still haven't figure out what happened
|Posted by Christopher Everett on November 2 2003 8:12pm
|[Delete] [Edit]
Do NOT allow your replication master to run out of space in
the partition where you put your binlogs. One of two things
will happen:
1) the binlog will get truncated in the middle of an event, and the IO thread on the replication slave(s) will halt.
2) A series of transactions will go unrecorded on the master
Either way, you'll have to reload the data from the replication master to the slave.
|Posted by Vittal Aithal on March 8 2004 11:10am
|[Delete] [Edit]
Having pulled my hair out with this error when getting a slave to replicate:
040308 13:38:01 Slave: reconnected to master 'repl@master:3306',replication resumed in log 'master-bin.011' at position 8379225
040308 13:38:01 Error reading packet from server: Access denied for user: 'repl@slave' (Using password: YES) (server_errno=1045)
it turns out that I'd installed Mysql, then changed the hostname of the slave server - *however*, the slave server's mysql.user table still contained the old slave server's hostname.
Changing the host for the root user in the slave's mysql.user table to the correct hostname, then restarting the slave process fixed it all.
|Posted by James Day on October 3 2004 4:57am
|[Delete] [Edit]
If you get a "Could not parse relay log event entry" error in a working replication setup and other slaves are fine, use STOP SLAVE; CHANGE MASTER TO master_log_file='(insert the value from Relay_Master_Log_File)', master_log_pos=(insert the value from Exec_master_log_pos); START SLAVE; . The slave will re-fetch from the master with no risk of losing a transaction. You should also look at the error log, in case it wasn't just a damaged network packet the first time.
|Posted by Don Hejna on October 11 2005 10:52pm
|[Delete] [Edit]
SELinux can interfer with replication and be difficult to track down. This can sometimes occur after you have extracted files using TAR in the mysql data directory as is often instructed in replication examples because it can modify file properties tracked by SELinux. (Encountered using FC-4 SELinux and MySQL 4.1.11)
If you encounter the following error on the replication slave:
[ERROR] Slave I/O thread: error connecting to master 'email@example.com:3306': Error: 'Can't connect to MySQL server on '192.168.7.11' (13)' errno: 2003 retry-time: 60 retries: 86400
check that you can login using:
mysql -u "replication_username" -h "replication_hostname" -p
if you can login using the above but replication fails to connect it may be SELinux policies restricting mysqld's access to ports, sockets, and files.
Check or grep /var/log/audit/audit.log and /var/log/messages for messages pertaining to mysqld like the following:
type=AVC msg=audit(1126806889.640:14244693): avc: denied { name_connect } for pid=2561 comm="mysqld" dest=3306 scontext=system_u:system_r:mysqld_t tcontext=system_u:object_r:mysqld_port_t tclass=tcp_socket type=SYSCALL msg=audit(1126806889.640:14244693): arch=40000003 syscall=102 success=no exit=-13 a0=3 a1=b139a130 a2=2 a3=0 items=0 pid=2561 auid=4294967295 uid=27 gid=27 euid=27 suid=27 fsuid=27 egid=27 sgid=27 fsgid=27 comm="mysqld" exe="/usr/libexec/mysqld"
To confirm SELinux is the cause, try turning off SE Linux from the root account using the following command:
# setenforce 0
# /etc/init.d/mysqld restart
If replication then starts working you know SELinux is the cause. On FC-4, running the following can shed light on this:
# audit2allow -i /var/log/audit/audit.log -l
allow mysqld_t mysqld_port_t:tcp_socket name_connect;
allow mysqld_t self:tcp_socket connect;
allow mysqld_t var_lib_t:dir { add_name read remove_name write };
allow mysqld_t var_lib_t:file { append create getattr lock read unlink write };
allow mysqld_t var_lib_t:sock_file { create getattr };
and running
# restorecon -R -v /var/lib/mysql
can fix problem associated with changing files in the MySQL directory
Since this post is about identifying the MySQL problems and not a tutorial about SELinux you should see also for details:
http://fedora.redhat.com/docs/selinux-apache-fc3/sn-debugging-and-customizing.html (which describes how to update the SELinux policies)
|Posted by Daniel Chen on June 16 2006 6:26am
|[Delete] [Edit]
The master and slave must have the same value of global variable "collation_server", if not, slave io process can not be started.
|Posted by [name withheld] on January 12 2007 4:13pm
|[Delete] [Edit]
If the slave was running previously but has stopped, the
reason usually is that some statement that succeeded on the
master failed on the slave. This should never happen if you
have taken a proper snapshot of the master, and never
modified the data on the slave outside of the slave thread.
AND you have never issued a statement on the MASTER which references a file or database that doesn't exist on the SLAVE.
For example:
INSERT INTO replicated_table SELECT stuff FROM master_only_db.table
|Posted by Chris Wiegand on May 17 2007 7:53pm
|[Delete] [Edit]
Do not use BIT types in sprocs if you're using replication. I pulled out a good 2" (5cm) of hair because I couldn't figure out why the binlog showed a ^@ where it should be a 1 (or some other way of indicating a bit). Finally figured out that most places I'm using TINYINT(1), but I was using a BIT in that sproc. Replaced, manually replayed those statements that were affected, and didn't have the problem again.
|Posted by James Green on July 25 2007 10:27am
|[Delete] [Edit]
We just went from 5.0.26 to 5.0.45 and replication broke. Somehow the HOSTNAME-bin.index file stopped recording binary log file names as ./HOSTNAME-bin.0000001, etc., and started recording them with absolute paths like /usr/lib/mysql/data/HOSTNAME-bin.0000036
This resulted in the slave error log having a line saying:
[ERROR] Got fatal error 1236: 'Could not find first log file name in binary log index file' from master when reading data from binary log
Don't panic. You need to manually edit the master's HOSTNAME-bin.index file and change all ./ relative paths to the absolute path (matching the ones created since the upgrade). Don't do this with the master running for obvious reason. Once you've restarted the master, restart the slave and the slave should catch up. Well, it did for me.
Assumes you haven't explicitly changed where binary logs are going during the upgrade of course.
|Posted by Richard Armstrong on August 1 2007 11:17am
|[Delete] [Edit]
If the Binlog becomes corrupt, due to lack of space, or a network glitch.
re-copy the binary log file from the master to the slave, changing the name as necessary.
Shutdown mysqld
Start mysqld again.
> start slave;
For some reason, the daemon held on to the old version of the binary log file, despite me telling it to refresh logs via mysqladmin.
Stop/start of the mysqld daemon followed by a "slave start" worked wonders.
|Posted by Matija Nalis on December 16 2007 7:34pm
|[Delete] [Edit]
if you keep getting "Access denied; you need the REPLICATION SLAVE privilege for this operation" on your slave despite the fact that you HAVE done "GRANT REPLICATION SLAVE ON *.*" the problem might be that you haven't got the newest mysql privilege tables (for example if master was upgraded before 4.1 or similar).
You can check for this problem if command:
show grants for "replicate"@"your.slave.host";
does NOT have "REPLICATION SLAVE" in its output.
The fix is to run mysql_fix_privilege_tables script which comes with mysql.
|Posted by Titi Alailima on July 14 2011 6:52pm
|[Delete] [Edit]
Under the section "If the I/O thread state says Connecting to master, check the following:" there should be a note regarding SSL-based replication that you should make sure the certificates have not expired. The "openssl x509" command can be use to find out the period of validity for the certificate files.
|Posted by Marcel Losekoot on August 13 2014 12:00am
|[Delete] [Edit]
Do not use a password that's more than 32 characters!
I could not get the replication slave to connect to the replication master, yet I could connect using the mysql client. The problem was that the password I had set was over 32 characters in length, which apparently gets truncated by the replication slave but not in the mysql server or in the mysql client, causing the connection to be refused to the replication slave but not to the mysql client. The clue I got was that inside the master.info file the password was truncated. Using a shorter password fixed it. This issue is described in the documentation for the change master command.


text:
- Home
- Hours
- Books & More
- Ebooks & More
- Programs
- Services
- About Us
- Support Us
Thank You For Your Donation!
Thank you from The Grand County Library District, we grateful for your support!
Your donation will insure Grand County Libraries continued growth into the future.
The is a receipt for a donation in which no benefit was received by the named donor.
Grand County Library District Tax Identification Number:
Local Links


text:
Indkvartering Ko Samui
With nearly 500 hotels and almost 60,000 rooms, including beach bungalows, condominiums, and private villas, finding a place to stay on Koh Samui is hardly a challenge. The trick is finding the right area of the island to suit your needs. Chaweng Beach offers the most variety of accommodation options as well as the most activities, while Mae Nam Beach is more suitable for those looking for quiet, sedentary relaxation. While Samui was once a haven for backpackers who were content with thatch roof, budget bungalows, these have generally all been replaced by mid-range, air conditioned, concrete bungalows and luxurious spa resorts. Regardless, there are still a few budget options to be found, and with so many choices it would be impossible not to find some accommodation that fits your budget and provides the ideal beach environment for your Koh Samui holiday. As one of the premier tourist destinations in Thailand, Koh Samui has innumerable attractions, ensuring that visitors with any interest will find something to keep them entertained on their Koh Samui holiday. The following are some of the most popular attractions on Koh Samui:
Highlight Accommodations
First Residence, the Four-Storey Great Value Modern Hotel, is designed for guests who search for a full-service accommodation with valuable prices. Modern contemporary facili... Flere detaljer
Guests can have a choice of 2 styles of ... Flere detaljer
Escape to your vil... Flere detaljer