#2339 closed task (worksforme)
Error from MySQL init script
Reported by: | Alexander Kahl | Owned by: | |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Bootscripts | Version: | SVN |
Severity: | normal | Keywords: | |
Cc: |
Description ¶
<sm0ker> i got a strange 'problem' always i start mysql bootscript. it start say ok and then "nohup: redirecting stderr to stdout" appears in the next line. what could that be?
<wolfpac> change /usr/bin/mysqld_safe --user=mysql 2>&1 >/dev/null & to /usr/bin/mysqld_safe --user=mysql >/dev/null 2>&1 &
Change History (3)
comment:1 by , 18 years ago
Resolution: | → worksforme |
---|---|
Status: | new → closed |
comment:2 by , 18 years ago
I've gotta ask: why redirect stderr at all? I haven't run mysqld in a while, so I don't know what they're pushing to stderr, but I'd think you'd want to see those messages in general if you have an error in you're configuration or something.
I've been going through the bootscripts quite a bit lately and see a lot of this redirecting of stderr to /dev/null. It bit me on the mountfs script when I was just getting silent FAIL. So, I don't know if it's applicable in this case, but what happens if you just don't redirect stderr at all?
I cannot duplicate this error. If there is an error, you want to see it so it can be fixed.