Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.

MySQL pomoc - EOPNOTSUPP Operation not supported

[es] :: MySQL :: MySQL pomoc - EOPNOTSUPP Operation not supported

Strane: 1 2

[ Pregleda: 3889 | Odgovora: 21 ] > FB > Twit

Postavi temu Odgovori

Autor

Pretraga teme: Traži
Markiranje Štampanje RSS

Zizi007
BiH

Član broj: 134354
Poruke: 24
81.93.69.*



Profil

icon Re: MySQL pomoc - EOPNOTSUPP Operation not supported03.08.2009. u 14:32 - pre 179 meseci
Evo sta sam dobio do Cpanel podrske, poslao sam im prije toga jedan email i nista posebno nisu odgovorili niti rijesili, pa sam ponovo pisao da je problem jos uvijek tu i evo odgovora ... Napominjem problem opet nije rijesen, sto je jos gore sada pise da je CPU oko 50% za taj proces komandu ...


Hi,

At the time Ken logged in, it wasn't doing much of anything. There were idle connections, but not much else. When I logged in, it took over 2 minutes to get to the shell. Load was > 10, and httpd was busy.

User/database 'medio633_m6e3d3' has the most connections to the db, although user 'bespl237_bes1mb' looks like they're doing the most right now.


The major load on your server appears to be Apache and waiting for connections to drop (keepalive), eventually filling up all available children and causing system load to spike - not MySQL. I've tuned this in /usr/local/apache/conf/includes/pre_virtualhost_global.conf for you. An example of the problem:


root@server [/usr/src]# /etc/init.d/httpd status

Apache Server Status for localhost

Server Version: Apache/2.2.11 (Unix) mod_ssl/2.2.11
OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4
FrontPage/5.0.2.2635 PHP/5.2.10

Server Built: Jul 30 2009 10:58:46
_________________________________________________________________

Current Time: Monday, 03-Aug-2009 14:46:19 CEST
Restart Time: Thursday, 30-Jul-2009 11:27:51 CEST
Parent Server Generation: 1
Server uptime: 4 days 3 hours 18 minutes 28 seconds
Total accesses: 11024623 - Total Traffic: 71.3 GB
CPU Usage: u288.74 s118.1 cu37.84 cs0 - .124% CPU load
30.8 requests/sec - 209.0 kB/second - 6.8 kB/request
167 requests currently being processed, 12 idle workers

KWWWKKWWWWKWKWWKKWWWKKKKWWKKW.KKKKKKKKKKW.WKK.KWWK.KWKW_K.WWKKWW
WKKWWWKKW._KW._W.WWWKW.W.K_KW_W.WKKK.WKW.KW..WKC.RKWKK_K_W.KW.K.
.K.WKK...KWWK.KKWW.WWK.W...KWW.KWW.WW.KWK.K.WW.W...._.W....K.._K
W.K..WKKWW.K...KKK.KR..._CWK....KK.W.._.W_..KK..KW.KK.WK.KK.W...

Scoreboard Key:
"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process


After tuning, you have more children available for service, and your load is dropping to a managable level. So although I do see MySQL occasionally use some CPU, I think the core problem here was Apache and insufficient waiting children.

root@server [/usr/local/apache/conf/includes]# /etc/init.d/httpd status

Apache Server Status for localhost

Server Version: Apache/2.2.11 (Unix) mod_ssl/2.2.11
OpenSSL/0.9.8e-fips-rhel5 mod_auth_passthrough/2.1 mod_bwlimited/1.4
FrontPage/5.0.2.2635 PHP/5.2.10

Server Built: Jul 30 2009 10:58:46
_________________________________________________________________

Current Time: Monday, 03-Aug-2009 14:49:37 CEST
Restart Time: Monday, 03-Aug-2009 14:47:29 CEST
Parent Server Generation: 2
Server uptime: 2 minutes 8 seconds
Total accesses: 7598 - Total Traffic: 40.4 MB
CPU Usage: u69.55 s14.47 cu0 cs0 - 65.6% CPU load
59.4 requests/sec - 323.5 kB/second - 5.4 kB/request
153 requests currently being processed, 79 idle workers

KWWWW_KW_WW_WWWWK__K__W_WWK__K_W.__KC_WWWW_WKWKWW_KKC__K___KW_WW
K_WKKWWW__W_______WKWKWCWK___WWKWWW_K_W_CWWKWWWWK__WKKKWW_KC_WWK
____W__K_KW_W_WWW_WKW_W_W_W_WW_KKKWKK_CKKWWW_W_C__KC._KKWWKW_WK_
KWKW___WWWWK_K_CWWWW_W__WWW_WWKW_C_W_KC_W_......................

Scoreboard Key:
"_" Waiting for Connection, "S" Starting up, "R" Reading Request,
"W" Sending Reply, "K" Keepalive (read), "D" DNS Lookup,
"C" Closing connection, "L" Logging, "G" Gracefully finishing,
"I" Idle cleanup of worker, "." Open slot with no current process

root@server [/usr/local/apache/conf/includes]# uptime
14:49:55 up 4 days, 14:45, 1 user, load average: 2.84, 6.90, 10.15



--
Jamyn Shanley, Analyst
cPanel of Texas, Inc.

cPanel Conference 2009!
October 5th, 6th, & 7th
Houston, TX
Unlimited Learning!

http://conference.cpanel.net
 
Odgovor na temu

bogdan.kecman
Bogdan Kecman
"specialist"
Oracle
srbistan

Član broj: 201406
Poruke: 15887
*.31.24.217.adsl2.beograd.com.

Sajt: mysql.rs


+2377 Profil

icon Re: MySQL pomoc - EOPNOTSUPP Operation not supported03.08.2009. u 19:29 - pre 179 meseci
nisam video server, ali info koji si ti ovde prosledio (da je mysql radio - nista, a uzimao xyz% cpu-a ) nema veze sa ovim sto su ti oni poslali ... dakle ok je da je apache pri velikom opterecenju uzme puno cpu-a ali ako ti pri "nikakvoj" poseti (dakle nijedan query na mysql-u) imas mysql sa visokim cpu usage-om - tu nesto nije ok

samo je pitanje da li EOPNOTSUPP pravi stvarno problem ili ne ... ja na centosu sa 5.4 imam EOPNOTSUPP koliko oces u strace izlazu ..

Code:

getsockname(372, {sa_family=AF_FILE, path="/tmp/mysql.soc\1"}, [7596489827298574354]) = 0
fcntl(372, F_SETFL, O_RDONLY)           = 0
fcntl(372, F_GETFL)                     = 0x2 (flags O_RDWR)
fcntl(372, F_SETFL, O_RDWR|O_NONBLOCK)  = 0
setsockopt(372, SOL_IP, IP_TOS, [8], 4) = -1 EOPNOTSUPP (Operation not supported)
futex(0xce2a44, FUTEX_WAKE_OP_PRIVATE, 1, 1, 0xce2a40, {FUTEX_OP_SET, 0, FUTEX_OP_CMP_GT, 1}) = 1
futex(0xce1e80, FUTEX_WAKE_PRIVATE, 1)  = 1
select(15, [14], NULL, NULL, NULL


a doticni mysql radi 1/1 bez ikakvih problema - uzima 0% cpu-a kada ne radi nista, radi extra brzo ... etc etc .. tako da EOPNOTSUPP realno ne znaci nista / nije de fakto problem na verzijama posle 5.0.44.

dakle - kresni ti njemu lepo onaj "log-slow-queries" .. pa vidi el ima tu nekih upita koji ne valjaju ... to koliko ja vidim nije "test" masina vec neki production tako da nije zgoreg da to svejedno imas upaljeno - takodje, spomenuh ti onaj url za optimizaciju - prazan my.cnf nikako ne valja, svi defaulti na mysql-u su dovoljno mali da moze mysql da se starta na svakoj masini - ali to je daleko od optimalnog za normalan rad!

tek kada imas mysql koji je iole iskonfigurisan mozes dalje da gledas da li jos nesto fali ..
 
Odgovor na temu

[es] :: MySQL :: MySQL pomoc - EOPNOTSUPP Operation not supported

Strane: 1 2

[ Pregleda: 3889 | Odgovora: 21 ] > FB > Twit

Postavi temu Odgovori

Navigacija
Lista poslednjih: 16, 32, 64, 128 poruka.