comment on

I don't know what platform you are running MySQL on, but I know on Red Hat Linux that MySQL logging was *NOT* turned on by default. In order to turn on logging I had to modify the /etc/rc.d/init.d/mysql start/stop/status script - where it invokes safe_mysqld, I add '--log=/var/log/mysqld.log' and so changed the line

   from this:
       /usr/bin/safe_mysqld  --defaults-file=/etc/my.cnf >/dev/null 2>
+&1 &

   to this:
       /usr/bin/safe_mysqld  --defaults-file=/etc/my.cnf --log=/var/lo
+g/mysqld.log >/dev/null 2>&1 &
[download]

and remember to restart the mysqld server('service mysqld restart' on Red Hat Linux) to make the changes take effect. If you can get MySQL to log messages it might help you figure out what the problem is.

HTH.

In reply to Re: mysql service and dbd::mysql by hmerrill
in thread mysql service and dbd::mysql by rhoadesjn

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Perl: the Markov chain saw
	PerlMonks