Re: Corrupted relay log
On 10/28/2004 8:07 AM, gerald_clark [EMAIL PROTECTED] wrote: Paul Fierro wrote: One of my slaves stopped running due to a corrupted relay log. The error file shows: Error writing file 'dbs2.log' (errno: 28) Error in Log_event::read_log_event(): 'read error', data_len: 160, event_type: 2 $ perror 28 Error code 28: No space left on device You are out of disk space. At the time of the error this may have been the case, but I have plenty of disk space now. Is there a way to bypass/skip the corrupted relay log file? Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Corrupted relay log
One of my slaves stopped running due to a corrupted relay log. The error file shows: Error writing file 'dbs2.log' (errno: 28) Error in Log_event::read_log_event(): 'read error', data_len: 160, event_type: 2 Error reading relay log event: slave SQL thread aborted because of I/O error Slave: Could not parse relay log event entry. The possible reasons are: the master's binary log is corrupted (you can check this by running 'mysqlbinlog' on the binary log), the slave's relay log is corrupted (you can check this by running 'mysqlbinlog' on the relay log), a network problem, or a bug in the master's or slave's MySQL code. If you want to check the master's binary log or slave's relay log, you will be able to know their names by issuing 'SHOW SLAVE STATUS' on this slave. Error_code: 0 Error running query, slave SQL thread aborted. Fix the problem, and restart the slave SQL thread with SLAVE START. We stopped at log 'dbm-bin.004' position 22254778 I ran mysqlbinlog on the relay log file as suggested in the error message, and when it stopped running it displayed: ERROR: Error in Log_event::read_log_event(): 'Event too big', data_len: 1696607332, event_type: 105 Could not read entry at offset 9068607:Error in log format or read error None of the other slaves had this problem, so I ruled out a corrupted master binary log. What are my options, if any? I tried SQL_SLAVE_SKIP_COUNTER but the slave still wouldn't start. Can I instruct the slave to skip this particular relay log file? Thanks, Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Show databases shows all even if no rights;
On 10/17/2004 7:12 AM, Michael J. Pawlowsky [EMAIL PROTECTED] wrote: All priviliges for that user in mysql.user are set to N. I know this is hard to read but here are the outputs from user and db. [snip] Paul DuBois wrote: At 10:02 -0400 10/16/04, Michael J. Pawlowsky wrote: I just noticed that a restricted user to only one database can still run show databases; and see all the names of the databases in MySQL. You would think that it would only return the databases that that user is allowed to connect to. Is there a way I can show only those databases that he has rights to without giving him rights to the mysql database to use the db table? Make sure that the user doesn't have any global privileges that apply to databases. If the user has such a privilege, SHOW DATABASES will display all databases. (To check this, look at the privilege columns in the mysql.user table for the user's account record.) Your grant tables suggest that you are not running MySQL 4.0. As of 4.0.2, the behavior you describe disappears: http://dev.mysql.com/doc/mysql/en/Show_database_info.html Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Replication problem with a cross database query
On 10/06/2004 6:23 PM, Bill Thomason [EMAIL PROTECTED] wrote: I originally posted a query about a problem entitled Table doesn't exist on query replication problem... The original title might be a little misleading. The slave replication is halting on a transaction that contains a query that spans two databases - one that is being replicated and the other is not. Could anyone provide me with some general rules of thumb about breaking down such a query? This may sound like a vague or possibly stupid question since this predicament is probably very specific to the situation. I didn't write the original query but I am establishing the master/slave relationships and uncovered the bug in doing so. Other than altering your database schema or replicating the reporting database, your options appear to be very limited. You can't use 'SQL_SLAVE_SKIP_COUNTER = 1' unless your slave is not running, and bookending the troublesome query with 'SQL_LOG_BIN = 0' and 'SQL_LOG_BIN = 1' only works from within the mysql client. Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: PHP reports 3.23.49, command line reports 4.0.1
On 09/23/2004 9:37 AM, Stembridge, Michael [EMAIL PROTECTED] wrote: I installed PHP 4.3.1 via source and used the following option when configuring: ./configure --with-mysql The database has worked great for a couple of years, however I noticed a problem today. Phpinfo() returns MySQL Version 3.23 from a php script. Client API version 3.23.49 MYSQL_MODULE_TYPE builtin MYSQL_SOCKET /var/lib/mysql/mysql.sock MYSQL_INCLUDE no value MYSQL_LIBS no value However, issuing 'mysql -V' at the command line returns version 4.0.1. So I assume the version of MySQL bundled with PHP 4.3.1 is in fact 3.23.49 and this is overriding my standalone installation. It's not overriding anything, it's doing what you asked: in your configure you told PHP to use its built-in (MYSQL_MODULE_TYPE) MySQL support. Without recompiling, is there a way to upgrade the bundled client? No - I believe you need to recompile PHP (this path assumes an RPM installation of MySQL): ./configure --with-mysql=/usr You also need to recompile when you upgrade MySQL, for example from 4.0.20 to 4.0.21. Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: PHP reports 3.23.49, command line reports 4.0.1
On 09/23/2004 11:11 AM, Stembridge, Michael [EMAIL PROTECTED] wrote: Without recompiling, is there a way to upgrade the bundled client? No - I believe you need to recompile PHP (this path assumes an RPM installation of MySQL): Yes, MySQL is installed via RPM. So, when I recompile PHP I should leave -off- the '--with-mysql' configuration option altogether? No, leave it and include a path to MySQL (see below). If you specify '--with-mysql' you will use PHP's built-in MySQL support, and if you leave it off you will compile PHP without MySQL support. If yes, how does PHP know MySQL exists on the system, or is this handled automatically behind the scenes? The '/usr' part of '--with-mysql=/usr' tells PHP where to look: ./configure --with-mysql=/usr Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Fatal error 1236 (replication)
Our master suffered a power failure. When fixed we brought up its only slave and found that it wouldn't replicate. The error log revealed that the slave was requesting replication from an impossible position: Slave SQL thread initialized, starting replication in log 'dbm-bin.041' at position 117415283, relay log './dbs1-relay-bin.016' position: 117415850 Slave I/O thread: connected to master '[EMAIL PROTECTED]:3306', replication started in log 'dbm-bin.041' at position 117415283 Error reading packet from server: Client requested master to start replication from impossible position (server_errno=1236) Got fatal error 1236: 'Client requested master to start replication from impossible position' from master when reading data from binary log Slave I/O thread exiting, read up to log 'dbm-bin.041', position 117415283 Master status: mysql show master status; +-+--+--+--+ | File| Position | Binlog_do_db | Binlog_ignore_db | +-+--+--+--+ | dbm-bin.043 | 89536436 | | | +-+--+--+--+ I'm guessing the slave is out of sync because the master wasn't able to flush its data to disk before failing. Is it possible to recover from this situation -- perhaps by modifying master.info and relay-log.info? Or should I start over with a new snapshot of the master? Thanks, Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: OS X 10.3.3 and byte ordering update
On 03/17/2004 9:46 AM, Paul DuBois [EMAIL PROTECTED] wrote: At 9:39 -0600 3/17/04, David Bourne wrote: I saw this too in an Apple tech note. It would have been nice if they had included version numbers. Was this change made with a version of MySQL that are publicly available? I seem to remember seeing a dump/reload requirement a few versions ago. MySQL was updated to 4.0.18. Can someone post a URL for this tech note, please? I haven't noticed any particular problems with MySQL after updating my iBook, but I'd like to know what this is about. Thanks. http://docs.info.apple.com/article.html?artnum=107851 Paul -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
