This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Pages: [1]
1
CentOS 8 Problems / Re: mysql get 300% cpu
« on: May 03, 2024, 07:04:34 AM »
The software is invision board, I don't know about max_allowed_packet. Can I increase it for testing? Do I change this from php?
2
CentOS 8 Problems / Re: mysql get 300% cpu
« on: May 02, 2024, 10:26:12 AM »
It is a vps server from contabo. 4 cores and 8gb ram. On htop it shows the same. I have only one user. It shows when a forum loads. When I restart the server or in mysql it is fixed
3
CentOS 8 Problems / mysql get 300% cpu
« on: May 01, 2024, 07:02:52 AM »
Ηello. Please help. Why does mysql get 300% cpu usage?
This is what I get in my email.
Excessive resource usage: rpc (620 (Parent PID:620)
Time: Wed May 1 09:58:08 2024 +0300
Account: rpc
Resource: Process Time
Exceeded: 30668 > 1800 (seconds)
Executable: /usr/bin/rpcbind
Command Line: /usr/bin/rpcbind -w -f
PID: 620 (Parent PID:620)
Killed: No
This is what I get in my email.
Excessive resource usage: rpc (620 (Parent PID:620)
Time: Wed May 1 09:58:08 2024 +0300
Account: rpc
Resource: Process Time
Exceeded: 30668 > 1800 (seconds)
Executable: /usr/bin/rpcbind
Command Line: /usr/bin/rpcbind -w -f
PID: 620 (Parent PID:620)
Killed: No
5
CentOS 6 Problems / Re: Internal Server Error
« on: March 04, 2015, 08:22:29 PM »
Ηello...same problem here, installation vbulletin. Please help.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator, and inform them of the time the error occurred, and anything you might have done that may have caused the error.
More information about this error may be available in the server error log.
Pages: [1]