Cannot shutdown a shutdown connection MySQL Enterprise Monitor
We are facing below errors on MySQL Enterprise Monitor.. While deleting a connection from MySQL Instances it is displaying following error messages.
Also it is not deleted event it displays success message.
Cannot shutdown a shutdown connection
Connection refused: connect
Any way of doing this? Any table in DB storing information in MySQL databases.
MySQL 5.6.21
Windows Platform
mysql windows shutdown
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
We are facing below errors on MySQL Enterprise Monitor.. While deleting a connection from MySQL Instances it is displaying following error messages.
Also it is not deleted event it displays success message.
Cannot shutdown a shutdown connection
Connection refused: connect
Any way of doing this? Any table in DB storing information in MySQL databases.
MySQL 5.6.21
Windows Platform
mysql windows shutdown
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is this ongoing? What are you trying to kill?
– eroomydna
Jan 16 '15 at 13:26
I am trying to remove a mysql connection from MySQL Enterprise Monitor
– Nawaz Sohail
Jan 16 '15 at 14:11
To be honest, this is nothing I ran into in my brief spell with Ent Mon. Seeing as though you need a support agreement to use Enterprise Monitor you should raise a ticket with Oracle for further debugging.
– eroomydna
Jan 16 '15 at 22:47
add a comment |
We are facing below errors on MySQL Enterprise Monitor.. While deleting a connection from MySQL Instances it is displaying following error messages.
Also it is not deleted event it displays success message.
Cannot shutdown a shutdown connection
Connection refused: connect
Any way of doing this? Any table in DB storing information in MySQL databases.
MySQL 5.6.21
Windows Platform
mysql windows shutdown
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
We are facing below errors on MySQL Enterprise Monitor.. While deleting a connection from MySQL Instances it is displaying following error messages.
Also it is not deleted event it displays success message.
Cannot shutdown a shutdown connection
Connection refused: connect
Any way of doing this? Any table in DB storing information in MySQL databases.
MySQL 5.6.21
Windows Platform
mysql windows shutdown
mysql windows shutdown
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
edited Jan 17 '15 at 2:44
RolandoMySQLDBA
142k24223379
142k24223379
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
asked Jan 16 '15 at 11:22
Nawaz SohailNawaz Sohail
9171718
9171718
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 12 mins ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
Is this ongoing? What are you trying to kill?
– eroomydna
Jan 16 '15 at 13:26
I am trying to remove a mysql connection from MySQL Enterprise Monitor
– Nawaz Sohail
Jan 16 '15 at 14:11
To be honest, this is nothing I ran into in my brief spell with Ent Mon. Seeing as though you need a support agreement to use Enterprise Monitor you should raise a ticket with Oracle for further debugging.
– eroomydna
Jan 16 '15 at 22:47
add a comment |
Is this ongoing? What are you trying to kill?
– eroomydna
Jan 16 '15 at 13:26
I am trying to remove a mysql connection from MySQL Enterprise Monitor
– Nawaz Sohail
Jan 16 '15 at 14:11
To be honest, this is nothing I ran into in my brief spell with Ent Mon. Seeing as though you need a support agreement to use Enterprise Monitor you should raise a ticket with Oracle for further debugging.
– eroomydna
Jan 16 '15 at 22:47
Is this ongoing? What are you trying to kill?
– eroomydna
Jan 16 '15 at 13:26
Is this ongoing? What are you trying to kill?
– eroomydna
Jan 16 '15 at 13:26
I am trying to remove a mysql connection from MySQL Enterprise Monitor
– Nawaz Sohail
Jan 16 '15 at 14:11
I am trying to remove a mysql connection from MySQL Enterprise Monitor
– Nawaz Sohail
Jan 16 '15 at 14:11
To be honest, this is nothing I ran into in my brief spell with Ent Mon. Seeing as though you need a support agreement to use Enterprise Monitor you should raise a ticket with Oracle for further debugging.
– eroomydna
Jan 16 '15 at 22:47
To be honest, this is nothing I ran into in my brief spell with Ent Mon. Seeing as though you need a support agreement to use Enterprise Monitor you should raise a ticket with Oracle for further debugging.
– eroomydna
Jan 16 '15 at 22:47
add a comment |
1 Answer
1
active
oldest
votes
There is really nothing you can do once a shutdown starts. Why ?
According to the MySQL Documentation on the Shutdown Process
2 The server creates a shutdown thread if necessary.
Depending on how shutdown was initiated, the server might create a
thread to handle the shutdown process. If shutdown was requested by a
client, a shutdown thread is created. If shutdown is the result of
receiving a SIGTERM signal, the signal thread might handle shutdown
itself, or it might create a separate thread to do so. If the server
tries to create a shutdown thread and cannot (for example, if memory
is exhausted), it issues a diagnostic message that appears in the
error log:
Error: Can't create thread to kill server
3 The server stops accepting new connections.
To prevent new activity from being initiated during shutdown, the
server stops accepting new client connections by closing the handlers
for the network interfaces to which it normally listens for
connections: the TCP/IP port, the Unix socket file, the Windows named
pipe, and shared memory on Windows.
It sounds like you are past Stage 3 because you got Connection refused: connect
In addition, note what may have triggered Stage 2:
If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so.
What could be that trigger ? Stage 1 says regarding Windows
A server running as a service on Windows shuts down when the services manager tells it to.
At this point, you have most likely reached Stage 4, which would go on to terminate currently active connections.
CONCLUSION
Maybe a Bug Report or Trouble Ticket would be in order. Just make sure you have done your due diligence in terms of finding out if the Service Manager died or that human error or lack of memory on the Windows box was ruled out.
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "182"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f89450%2fcannot-shutdown-a-shutdown-connection-mysql-enterprise-monitor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is really nothing you can do once a shutdown starts. Why ?
According to the MySQL Documentation on the Shutdown Process
2 The server creates a shutdown thread if necessary.
Depending on how shutdown was initiated, the server might create a
thread to handle the shutdown process. If shutdown was requested by a
client, a shutdown thread is created. If shutdown is the result of
receiving a SIGTERM signal, the signal thread might handle shutdown
itself, or it might create a separate thread to do so. If the server
tries to create a shutdown thread and cannot (for example, if memory
is exhausted), it issues a diagnostic message that appears in the
error log:
Error: Can't create thread to kill server
3 The server stops accepting new connections.
To prevent new activity from being initiated during shutdown, the
server stops accepting new client connections by closing the handlers
for the network interfaces to which it normally listens for
connections: the TCP/IP port, the Unix socket file, the Windows named
pipe, and shared memory on Windows.
It sounds like you are past Stage 3 because you got Connection refused: connect
In addition, note what may have triggered Stage 2:
If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so.
What could be that trigger ? Stage 1 says regarding Windows
A server running as a service on Windows shuts down when the services manager tells it to.
At this point, you have most likely reached Stage 4, which would go on to terminate currently active connections.
CONCLUSION
Maybe a Bug Report or Trouble Ticket would be in order. Just make sure you have done your due diligence in terms of finding out if the Service Manager died or that human error or lack of memory on the Windows box was ruled out.
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
add a comment |
There is really nothing you can do once a shutdown starts. Why ?
According to the MySQL Documentation on the Shutdown Process
2 The server creates a shutdown thread if necessary.
Depending on how shutdown was initiated, the server might create a
thread to handle the shutdown process. If shutdown was requested by a
client, a shutdown thread is created. If shutdown is the result of
receiving a SIGTERM signal, the signal thread might handle shutdown
itself, or it might create a separate thread to do so. If the server
tries to create a shutdown thread and cannot (for example, if memory
is exhausted), it issues a diagnostic message that appears in the
error log:
Error: Can't create thread to kill server
3 The server stops accepting new connections.
To prevent new activity from being initiated during shutdown, the
server stops accepting new client connections by closing the handlers
for the network interfaces to which it normally listens for
connections: the TCP/IP port, the Unix socket file, the Windows named
pipe, and shared memory on Windows.
It sounds like you are past Stage 3 because you got Connection refused: connect
In addition, note what may have triggered Stage 2:
If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so.
What could be that trigger ? Stage 1 says regarding Windows
A server running as a service on Windows shuts down when the services manager tells it to.
At this point, you have most likely reached Stage 4, which would go on to terminate currently active connections.
CONCLUSION
Maybe a Bug Report or Trouble Ticket would be in order. Just make sure you have done your due diligence in terms of finding out if the Service Manager died or that human error or lack of memory on the Windows box was ruled out.
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
add a comment |
There is really nothing you can do once a shutdown starts. Why ?
According to the MySQL Documentation on the Shutdown Process
2 The server creates a shutdown thread if necessary.
Depending on how shutdown was initiated, the server might create a
thread to handle the shutdown process. If shutdown was requested by a
client, a shutdown thread is created. If shutdown is the result of
receiving a SIGTERM signal, the signal thread might handle shutdown
itself, or it might create a separate thread to do so. If the server
tries to create a shutdown thread and cannot (for example, if memory
is exhausted), it issues a diagnostic message that appears in the
error log:
Error: Can't create thread to kill server
3 The server stops accepting new connections.
To prevent new activity from being initiated during shutdown, the
server stops accepting new client connections by closing the handlers
for the network interfaces to which it normally listens for
connections: the TCP/IP port, the Unix socket file, the Windows named
pipe, and shared memory on Windows.
It sounds like you are past Stage 3 because you got Connection refused: connect
In addition, note what may have triggered Stage 2:
If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so.
What could be that trigger ? Stage 1 says regarding Windows
A server running as a service on Windows shuts down when the services manager tells it to.
At this point, you have most likely reached Stage 4, which would go on to terminate currently active connections.
CONCLUSION
Maybe a Bug Report or Trouble Ticket would be in order. Just make sure you have done your due diligence in terms of finding out if the Service Manager died or that human error or lack of memory on the Windows box was ruled out.
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
There is really nothing you can do once a shutdown starts. Why ?
According to the MySQL Documentation on the Shutdown Process
2 The server creates a shutdown thread if necessary.
Depending on how shutdown was initiated, the server might create a
thread to handle the shutdown process. If shutdown was requested by a
client, a shutdown thread is created. If shutdown is the result of
receiving a SIGTERM signal, the signal thread might handle shutdown
itself, or it might create a separate thread to do so. If the server
tries to create a shutdown thread and cannot (for example, if memory
is exhausted), it issues a diagnostic message that appears in the
error log:
Error: Can't create thread to kill server
3 The server stops accepting new connections.
To prevent new activity from being initiated during shutdown, the
server stops accepting new client connections by closing the handlers
for the network interfaces to which it normally listens for
connections: the TCP/IP port, the Unix socket file, the Windows named
pipe, and shared memory on Windows.
It sounds like you are past Stage 3 because you got Connection refused: connect
In addition, note what may have triggered Stage 2:
If shutdown is the result of receiving a SIGTERM signal, the signal thread might handle shutdown itself, or it might create a separate thread to do so.
What could be that trigger ? Stage 1 says regarding Windows
A server running as a service on Windows shuts down when the services manager tells it to.
At this point, you have most likely reached Stage 4, which would go on to terminate currently active connections.
CONCLUSION
Maybe a Bug Report or Trouble Ticket would be in order. Just make sure you have done your due diligence in terms of finding out if the Service Manager died or that human error or lack of memory on the Windows box was ruled out.
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
edited Jan 17 '15 at 2:47
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
answered Jan 17 '15 at 2:42
RolandoMySQLDBARolandoMySQLDBA
142k24223379
142k24223379
add a comment |
add a comment |
Thanks for contributing an answer to Database Administrators Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fdba.stackexchange.com%2fquestions%2f89450%2fcannot-shutdown-a-shutdown-connection-mysql-enterprise-monitor%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Is this ongoing? What are you trying to kill?
– eroomydna
Jan 16 '15 at 13:26
I am trying to remove a mysql connection from MySQL Enterprise Monitor
– Nawaz Sohail
Jan 16 '15 at 14:11
To be honest, this is nothing I ran into in my brief spell with Ent Mon. Seeing as though you need a support agreement to use Enterprise Monitor you should raise a ticket with Oracle for further debugging.
– eroomydna
Jan 16 '15 at 22:47