MySQL and Syslog
Hi All, Anyone had tried to push all MySQL logs to the centralized syslog server? Can you share with me how did you do it? I have centralized syslog (rsyslog-3.22.1-3.el5) server who resides separately and a remote MySQL server (mysql-server-5.0.77-4.el5_4.2) on other node. How to accomplish this to work smoothly that all logs of MySQL will be forwarded to the syslog? Cheers. James
To get Processlist and Status of MySQL ?
Hi All, What is the other way to get the *processlist* and *status* of mysql server on event that the mysql server cannot be able to reach due to hung or crashed? Cheers, James
Re: To get Processlist and Status of MySQL ?
I found some tools to capture the MySQL processlist, log errors, etc. MySQLReport <http://hackmysql.com/mysqlreport> and mytop<http://jeremy.zawodny.com/mysql/mytop/>apps. My goal is to grab the logs of mysql including the processlist to help me assist in diagnosis of faults. What tool/apps do you use? Thanks. James On Tue, May 18, 2010 at 5:06 AM, Raj Shekhar wrote: > In infinite wisdom James Corteciano wrote: > > > [1 ] > > Hi All, > > > > What is the other way to get the *processlist* and *status* of mysql > server > > on event that the mysql server cannot be able to reach due to hung or > > crashed? > > GDB <http://poormansprofiler.org/> > > -- > Raj Shekhar > - > If there's anything more important than my ego around, I want it > caught and shot now. > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: > http://lists.mysql.com/mysql?unsub=ja...@linux-source.org > >
Got error 139 from storage engine (InnoDB)
Hi All, I have received error message "ERROR 1030 (HY000) at line 167: Got error 139 from storage engine" when importing dump database to MySQL server. The MySQL server is using InnoDB. I have google it and it's something problem on exceeding a row-length limit in the InnoDB table. Any have idea how to fix this? Thanks. Regards, James
Re: Got error 139 from storage engine (InnoDB)
Hi Joerg,
Thanks for your reply.
I found out that this error was limitation row length of 8000 bytes on
InnoDB. I have check the dump sql file and one particular table is causing
error 139.
What I did is just to use MyISAM engine rather than InnoDB for a specific
table only.
BTW, the machine has 24GB memory and Quad-Core CPU. The platform is RHEL 5.5
x64 and mysql-server-5.0.77-4.el5_4.2.
*Rob Wultsch *and Prabhat Kumar, thanks for your response.
Regards,
James
On Tue, Jul 6, 2010 at 5:19 PM, Joerg Bruehe wrote:
> James, all,
>
>
> James Corteciano wrote:
> > Hi All,
> >
> > I have received error message "ERROR 1030 (HY000) at line 167: Got error
> 139
> > from storage engine" when importing dump database to MySQL server. The
> MySQL
> > server is using InnoDB. I have google it and it's something problem on
> > exceeding
> > a row-length limit in the InnoDB table.
>
> you are putting overload on our crystal balls - why don't you tell us
> (at least!) the MySQL version and the platform?
>
>
> "error 139" looks like it is some Unix/Linux.
> On all these platforms, the exit code "139" means the process died
> because of signal 11 ("segmentation violation", "SIGSEGV"),
> and then a core dump was taken (indicated by the value 128).
> 139 == 11 + 128.
>
> You should use your debugger of choice to get a stack backtrace, unless
> this was already done automatically during crash analysis / recovery.
>
>
> >
> > Any have idea how to fix this?
>
> Only when the backtrace is known, there may be some educated guesses
> about the cause of the problem.
> But all such effort is wasted unless you tell the versions.
>
>
> Jörg
>
> --
> Joerg Bruehe, MySQL Build Team, joerg.bru...@sun.com
> ORACLE Deutschland B.V. & Co. KG, Komturstrasse 18a, D-12099 Berlin
> Geschaeftsfuehrer: Juergen Kunz, Marcel v.d. Molen, Alexander v.d. Ven
> Amtsgericht Muenchen: HRA 95603
>
>
MySQL Workbench - libmdcanvasgtk.so.0: undefined symbol: pixman_image_unref
Hi All, I have downloaded mysql-workbench-oss-5.2.14-1rhel5.i386.rpm to test the MySQL GUI tools. I've installed it with no errors. When I run the 'mysql-workbench' command, it gives me error message: # mysql-workbench /usr/bin/mysql-workbench-bin: symbol lookup error: /usr/lib/mysql-workbench/libmdcanvasgtk.so.0: undefined symbol: pixman_image_unref Any have idea how to fix this? Thanks. Regards, James
How to dump MySQL data on remote server using mysqldump
Hi, I have mysql server separated from web server. My problem is, when I dump the data from database using the command "mysqldump -uuser -p -h mysql_server -t -T /tmp/dbname database_name" on web server, all data were dumped to the /tmp/dbname of mysql server and not inside of web server. [web]$ mysqldump -uuser -p -h mysql_server -t -T /tmp/dbname database_name [web]$ ll /tmp/dbname total 0 [mysql]$ ll /tmp/dbname total 2 -rw-rw-rw- 1 mysql mysql table_name.txt How could I put the dump data on web server and not the local disk on mysql server? Thanks. Regards, James
