SST donor logs an error (Invalid argument) even if SST was successful

Bug #415956 reported by Alex Yurchenko
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MySQL patches by Codership
Fix Released
Medium
Alex Yurchenko

Bug Description

Log message:
090819 16:08:57 [Note] [DEBUG] WSREP: wsrep_sst_mysqldump complete: 22 (Invalid argument)

Offending code:
    if (proc.error()) {
        sql_print_error ("WSREP: '%s' failed: %d (%s)",
                         proc.str, proc.error(), strerror(proc.error()));
        return -proc.error();
    }

    sql_print_information (
        "[DEBUG] WSREP: wsrep_sst_mysqldump complete: %d (%s)",
        errno, strerror(errno));

Apparently it reports a stray errno and it is moot.

Related branches

Changed in codership-mysql:
assignee: nobody → Alex Yurchenko (ayurchen)
importance: Undecided → Medium
milestone: none → 0.7
status: New → In Progress
Revision history for this message
Alex Yurchenko (ayurchen) wrote :

According to "The Open Group Base Specifications Issue 6 IEEE Std 1003.1, 2004 Edition":

"The value of errno should only be examined when it is indicated to be valid by a function's return value."

So using errno in the above code is wrong.

Changed in codership-mysql:
status: In Progress → Fix Committed
Changed in codership-mysql:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.