[SOLVED] MySQL boot syntax error ')'??

DJRcomputing · 05-23-2011, 11:26 PM

Mental note: ignore start-up process scroll.

Okay, now MySQL is just being (even more) difficult. Prior to boot's starting MySQL, I notice the line

Code:

/etc/rc2.d/S19mysql: line 132: syntax error near unexpected token ')'

Near?? Line 132 consists of

Code:

'stop')

Which is proper, and identical to all the other /etc/rc#.d/S19mysql scripts that don't result in errors. C'mon...!

Though it seems like a non-issue, any ideas as to a solution?

Wim Sturkenboom · 05-23-2011, 11:35 PM

Did you run a diff on the scripts to make sure they are the same; a space or <tab> that you don't see can already be a pain.

And the problem is probably just before line 132; maybe a missing semicolon?

DJRcomputing · 05-24-2011, 12:48 AM

Quote:

Originally Posted by Wim Sturkenboom

Did you run a diff on the scripts to make sure they are the same...

diff didn't output anything, so I'm guessing they're the same:

Code:

# diff /etc/rc2.d/S19mysql /etc/rc3.d/S19mysql
#

Quote:

Originally Posted by Wim Sturkenboom

...a space or <tab> that you don't see can already be a pain.

Which is why I'm not a coder. Kudos to those who are. The extent of my hacking: Off The Mark cartoon.

Quote:

Originally Posted by Wim Sturkenboom

And the problem is probably just before line 132; maybe a missing semicolon?

Since I'm not proficient in coding (scripts), I just attached the script file so those who know can check it. If someone patches it, just attached the fixed S19mysql to your reply, please. Thanks.

Wim Sturkenboom · 05-24-2011, 01:14 AM

Code:

case "${1:-''}" in
  'start')
	sanity_checks;
	# Start daemon
	log_daemon_msg "Starting MySQL database server" "mysqld"
	if mysqld_status check_alive nowarn; then
	   log_progress_msg "already running"
	   log_end_msg 0
	else
  	    /usr/local/mysql/bin/mysqld_safe > /dev/null 2>&1 &
	    # 6s was reported in #352070 to be too few when using ndbcluster
	    for i in 1 2 3 4 5 6 7 8 9 10 11 12 13 14; do
                sleep 1
	        if mysqld_status check_alive nowarn ; then break; fi
		log_progress_msg "."
	    done
	    if mysqld_status check_alive warn; then
                log_end_msg 0
	        # Now start mysqlcheck or whatever the admin wants.
	        output=$(/var/mysql/mysql-start)
		[ -n "$output" ] && log_action_msg "$output"
	    else
	        log_end_msg 1
		log_failure_msg "Please take a look at the syslog"
	    fi
	fi

	# Some warnings
        # if $MYADMIN variables | egrep -q have_bdb.*YES; then
        #    echo "BerkeleyDB is obsolete, see /usr/share/doc/mysql-server-5.0/README.Debian.gz" | $ERR_LOGGER -p daemon.info
        # fi
        # if [ -f /etc/mysql/debian-log-rotate.conf ]; then
        #    echo "/etc/mysql/debian-log-rotate.conf is obsolete, see /usr/share/doc/mysql-server-5.0/NEWS.Debian.gz" | $ERR_LOGGER -p daemon.info
        # fi
	# ;;

  'stop')

I think you're problem will be solved by removing the # in the line that I marked in bold red

If you look at all the other options (stop, restart, ...), they are terminated by a double semicolon before the next option. But for the start one that double semicolon is commented out.

Keeps the question why the other runlevels don't complain (unless you have not actually tried them)

DJRcomputing · 05-24-2011, 07:10 AM

Quote:

Originally Posted by Wim Sturkenboom

I think you're problem will be solved by removing the # in the line that I marked in bold red

Thaaaat didn't work. The resulting error(s) made me laugh, as it reminded me of my website's 404 page.

Code:

/etc/rc2.d/S19mysql: WARNING: /etc/init/my.cnf cannot be read. Blame LOLcat (warning).
Starting MySQL database server: mysqld . . . . . failed!

Quote:

Originally Posted by Wim Sturkenboom

If you look at all the other options (stop, restart, ...), they are terminated by a double semicolon before the next option. But for the start one that double semicolon is commented out.

I actually put the ;; below the 2nd fi at the end of the 'start') section. Same result, but seemed like better form. Interestingly, the 'stop') section ends in a double fi without the ;; too, yet no complaints. *shrug*

Quote:

Originally Posted by Wim Sturkenboom

Keeps the question why the other runlevels don't complain (unless you have not actually tried them)

Shhh...I'm just glad my server runs, regardless of whichever runlevel it choses, since it's my first foray into Linux. FWIW, I just noticed that during shutdown, it gives the same error regarding /etc/rc0.d/K21mysql, which is identical to S19mysql.

Wim Sturkenboom · 05-24-2011, 07:43 AM

Quote:

Originally Posted by DJRcomputing

I actually put the ;; below the 2nd fi at the end of the 'start') section. Same result, but seemed like better form. Interestingly, the 'stop') section ends in a double fi without the ;; too, yet no complaints. *shrug*

All sections end with ';;' except the start one.

Code:

case "${1:-''}" in
  'start')
...
	# ;;

  'stop')
...
	;;

  'restart')
...
	;;

  'reload'|'force-reload')
...
	;;

  'status')
...
  	;;

  *)
...
	;;
esac

I've stripped all the stuff out so you can see the frame work of the case and the difference between the start section and the others.

Don't care about number of fi's unless you start counting the if's as well

DJRcomputing · 05-27-2011, 11:17 PM

Quote:

Originally Posted by Wim Sturkenboom

All sections end with ';;' except the start one.

*sigh* Thank you for carefully reading my previous reply:

Quote:

Originally Posted by DJRcomputing

Thaaaat didn't work. The resulting error(s) made me laugh, as it reminded me of my website's 404 page.

However,

Quote:

Originally Posted by Wim Sturkenboom

I've stripped all the stuff out so you can see the frame work of the case and the difference between the start section and the others.

Don't care about number of fi's unless you start counting the if's as well

I appreciate you pointing out my oversight. I thought the 'stop') case ended @ line 154, and not 163, as if a new case invisibly started at 156. Whoops. LOL!

I've also learned that /etc/rc#.d/###mysql are just symlinks to /etc/init.d/mysql for the different runlevels, so of course they're all the same. Duh...

Finally, I asked my father, who's a proficient coder, and he recommended the same thing you did. I guess I'll just live with the benign "splinter" (ie: annoying) syntax error, which beats failed! any day.

In the end, I consider this resolved, unless anyone has the "solution", but not [SOLVED]. However, it's not worth any more of my time. I'm still going to report the bug, so their devs look into their own coding.

DJRcomputing · 05-29-2011, 08:22 AM

Quote:

Originally Posted by DJRcomputing

MySQL is just being (even more) difficult.

Oooookay?! The problem just...fixed itself? The error went away...on it's own? Just...disappeared? Even the runlevel symlinks are gone. *boggles* I didn't delete it/them. mysql.server is there, but...

http://dev.mysql.com/doc/refman/5.0/...tic-start.html

The MySQL daemon loads like it always has, which I thought was tied into /etc/init.d/mysql, as an executable copy of mysql.server...so how was /etc/init.d/mysql different, and where'd IT come from?? I'm so confused. I could rename mysql.server to mysql & the ###mysql.server symlinks to ###mysql, but I'm leaving this $h!+ alone & marking this b!+ch [SOLVED] while I can. I get that my server is "possessed" by daemons & all, but...???

Then again, it could be my cats. *shrug* (Malicious li'l hackers.) Maybe they were trying to help me out for a change (doubtful). They do, after all, like playing with mice...