Bug #43627 Forcing shutdown of 1 plugins

• Submitted: 13 Mar 2009 9:50
• Modified: 19 Jan 2010 4:42
• Reporter: Andrew 007
• Status: Closed
• Category: MySQL Server
• Severity: S3 (Non-critical)
• Version: 5.1.32
• OS: Windows
• CPU Architecture: Any
• Tags: plugins, shutdown

[13 Mar 2009 9:50] Andrew 007

Description:
After a fresh installation of MySQL 5.1.32 on Win 2003 I have the following on every restart of the server:

[Warning] Forcing shutdown of 1 plugins

Any Idea?

How to repeat:
Shutdown the server 5.1.32 on WIN2003

[13 Mar 2009 10:04] Sveta Smirnova

Thank you for the report.

This can be duplicate of bug #42820. Does mysqld run after installation or it is stopped? Please provide full error log file.

[17 Mar 2009 5:15] Meiji KIMURA

MySQL 5.1.32 output unnessary message in error.log when shutdown.

090317 10:57:12 [Warning] Forcing shutdown of 1 plugins

I looked into this problem in detail, so I found it is caused by DISABLED FEDERATED plugin, 
but there is no operation for this.

[Workaround]

There is no workaround. Ignore it.

[Suggested fix]

Add PLUGIN_IS_DISABLED after PLUGIN_IS_UNINITIALIZED at Line.1525 in sql_plugin.cc.

        case PLUGIN_IS_FREED:
        case PLUGIN_IS_UNINITIALIZED:
        case PLUGIN_IS_DISABLED: // Added.
          free_slots++;
          break;
        }

This error message is displayed by Line.1541 in sql_plugin.cc.

    if (count > free_slots)
      sql_print_warning("Forcing shutdown of %d plugins", count - free_slots);

'count' means a number of plugin elements (plugin_array.elements), and 
'free_slots' is count up when element status is PLUGIN_IS_FREED or PLUGIN_IS_UNINITIALIZED.

But  plugin_deinitialize operation is ommitted when state is PLUGIN_IS_DISABLED, like this.

      if (!(plugins[i]->state & (PLUGIN_IS_UNINITIALIZED | PLUGIN_IS_FREED |
                                 PLUGIN_IS_DISABLED)))

So I supposed that we have to add PLUGIN_IS_DISABLED to be suggested.

[12 Jan 2010 9:08] Meiji KIMURA

MySQL 5.1.40 or later, this message don't appear.

I supposed that it was fixed with some modification of sources.