| Bug #11140 | Instance Manager: IM Seg faults on "START" if instance is already running | ||
|---|---|---|---|
| Submitted: | 7 Jun 2005 15:42 | Modified: | 18 Feb 2006 0:30 |
| Reporter: | Jonathan Miller | Email Updates: | |
| Status: | Can't repeat | Impact on me: | |
| Category: | Instance Manager | Severity: | S3 (Non-critical) |
| Version: | 5.0 | OS: | Linux (Linux) |
| Assigned to: | Petr Chardin | CPU Architecture: | Any |
[18 Feb 2006 0:29]
Petr Chardin
can't repeat. I fail at the first step "setup cluster". However from the description looks like it is the bug which was fixed long ago.

Description: [ndbdev@ndb10 c1]$ /etc/init.d/mysql.server start Starting MySQL/etc/init.d/mysql.server: line 333: 30665 Segmentation fault $manager --user=$user --pid-file=$pid_file >/dev/null 2>&1 [ OK ] How to repeat: 1) Setup Cluster 2) setup for to mysqld pointing to cluster. 3) run IM start 4) run IM start again. Suggested fix: IM displays that IM is already running and exits the second IM process.