On 07/01/14 22:35, Zbigniew Jędrzejewski-Szmek wrote:
That's what I'd guess too. Does is get fixed if you insert 'sleep 1' in
mysql-check.sh before it exits?
This seems likely because the output suggests that the script is short-lived.
Yes. It helps.
On 06/01/14 21:52, Zbigniew Jędrzejewski-Szmek wrote:
journalctl -o verbose for mysqld-check.sh
Zbyszku,
Here is output for 'journalctl SYSLOG_IDENTIFIER=mysqld-check.sh -o verbose'
Sat 2014-01-04 23:32:07.364159 CET
On Tue, Jan 7, 2014 at 11:19 PM, Warpme war...@o2.pl wrote:
On 06/01/14 21:52, Zbigniew Jędrzejewski-Szmek wrote:
journalctl -o verbose for mysqld-check.sh
Zbyszku,
Here is output for 'journalctl SYSLOG_IDENTIFIER=mysqld-check.sh -o verbose'
Sat 2014-01-04 23:32:07.364159 CET
On Tue, Jan 07, 2014 at 11:21:41PM +0200, Mantas Mikulėnas wrote:
On Tue, Jan 7, 2014 at 11:19 PM, Warpme war...@o2.pl wrote:
On 06/01/14 21:52, Zbigniew Jędrzejewski-Szmek wrote:
journalctl -o verbose for mysqld-check.sh
Zbyszku,
Here is output for 'journalctl
Hi *
I have question regarding logging with help of systemd journal.
I have mysql daemon unit which so some housekeeping after daemon start
(see below).
My question is: what is best method to query journal to see _ALL_
execution output of mysqld.service unit?
Kicking 'journalctl --unit
On Mon, Jan 06, 2014 at 09:09:56PM +0100, Warpme wrote:
Kicking 'journalctl --unit mysqld.service' gives output of
'/usr/bin/mysqld' but not '/usr/local/bin/mysqld-check.sh'
Can you show a record from journalctl -o verbose for mysqld-check.sh
(one of those not shown, just one is enough)?