MRatWork Forum by Mustafa Ramadhan - Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

Sponsor:
Server and Web Integrator
Link:
6.5.0 or 7.0.0
Click for "How to install"
Donation/Sponsorship:
Kloxo-MR is open-source.
Donate and or Sponsorship always welcome.
Click to:

MRatWork Forum | Please login or register. | 2017-11-07, 15:32:21

- MRatWork Forum by Mustafa Ramadhan »
- Language Specific Discussions »
- Indonesia Users »
- Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« previous next »

- Print

Pages: [1] 2 Go Down

### Author Topic: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ? (Read 4842 times)

0 Members and 1 Guest are viewing this topic.

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« on: 2015-08-13, 09:40:51 »
bagaimana Cara Mengetahui Penyebab Tingginya Penggunaan Ram ? Sejak pagi vps saya error dan HIGH CPU Usage, saya buka Putty saja lemot & koneksi gagal, buka CP kloxo-mr nya pun sama saja lemot banget, saya tanyakan via ticket Digital Ocean katanya berdasarkan graph nya CPU nya high usage, saya cek berdasarkan free -m melalui console accesss nya Digital Ocean (web) ram 1 Gb terpakai semuannya. saya coba reboot, power off, sh restart-all, fix-all, cleanup, dll masih sama saja setiap reboot pun ram jadi besar, padahal sebelumnya tidak seperti itu..
apa yang harus saya lakukan yah ?
ini sysinfo kloxo-mr yg saya gunakan berdasarkan screenshot sebelum vps saya bermasalah
Quote

> [root@vps ~]# sh /script/sysinfo
> A. Kloxo-MR: 7.0.0.b-2015070802
> - Web: hiawatha-9.13.0-f.6.mr.el6.i386
> - PHP: php53s-5.3.29-1.ius.el6 (fpm mode)
> B. Plateform:
> - OS: CentOS release 6.6 (Final) i686
> - Hostname: vps.acmi1899.com
> C. Services:
> 1. MySQL: mysql55-5.5.44-2.ius.el6.i686
> 2. PHP:
> - Branch: php53u-cli-5.3.29-1.ius.el6.i686
> - Multiple:
> * php55m-5.5.26-1.ius.el6
> - Used: php55m
> 3. Httpd: httpd-2.2.29-2.mr.el6.i386
> - PHP Type: php-fpm_event
> 4. Lighttpd: --uninstalled--
> 5. Hiawatha: hiawatha-9.13.0-f.6.mr.el6.i386
> 6. Nginx: --uninstalled--
> 7. Cache: --uninstalled--
> 8. Dns: --uninstalled--
> 9. Qmail: qmail-toaster-1.03-1.3.55.mr.el6.i386
> - with: courier-imap-toaster-4.1.2-1.3.18.mr.el6.i386
> D. Memory:
> total used free shared buffers cached
> Mem: 1006 752 253 0 59 455
> -/+ buffers/cache: 237 769
> Swap: 1023 0 1023
> E. Disk Space:
> Filesystem Size Used Avail Use% Mounted on
> /dev/vda1 20G 5.2G 14G 28% /

Logged

#### zenkul

- Global Moderator
- Master
- Posts: 383
- Karma: +3/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #1 on: 2015-08-13, 12:54:18 »
sambil menunggu pencerahan coba periksa
- lewat perintah ssh "top" tanpa tanda petik lalu enter, amati apakah ada yang mencurigakan
- juga selanjutnya bisa periksa kloxo-mr panel server>>log manager untuk httpd, hiawatha, php-fpm dan mysql
#kalau lemot banget sampai nggak bisa buka kloxo-mr, service-nya bisa di stop dulu ; "service php-fpm stop; service httpd stop; service hiawatha stop"
#bisa testing juga kalau misalnya "hanya hiawatha"
« Last Edit: 2015-08-13, 13:10:30 by zenkul »
Logged
easy, secure and speed up web panel ===> Kloxo-MR

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #2 on: 2015-08-13, 13:21:55 »
Di Kloxo-MR 7.0 terakhir, bisa digunakan 'mem-usage' dan 'cpu-usage' per-user.
Ini contoh:
Code: [Select]

    login as: root
    Server refused our key
    root@62.210.181.21's password:
    Last login: Thu Aug 13 04:09:47 2015 from 180.246.171.170
    [root@oln3 ~]# sh /script/mem-usage
    User     Count     Swap      USS      PSS      RSS
    qmailq       1        0    84.0K    89.0K   408.0K
    qmailr       1        0   112.0K   117.0K   412.0K
    dbus         1   128.0K   144.0K   163.0K   472.0K
    qmails       1        0   168.0K   185.0K   548.0K
    memcached     1        0   500.0K   521.0K   872.0K
    haldaemon     2   464.0K   628.0K   769.0K     2.0M
    qmaill       9        0   768.0K   858.0K     5.0M
    lxlabs       1        0   784.0K   917.0K     1.4M
    qmaild       6        0     1.4M     1.9M     4.9M
    devel        2        0    32.9M    40.1M    54.1M
    root        76    22.9M   119.5M   154.5M   273.6M
    mysql        1        0   270.1M   270.3M   271.6M
    apache       8        0     1.4G     1.5G     1.9G
    ---------------------------------------------------
               110    23.5M     1.9G     2.0G     2.5G
    [root@oln3 ~]# sh /script/cpu-usage
    apache 1.9
    root 0
    [root@oln3 ~]#

Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### zenkul

- Global Moderator
- Master
- Posts: 383
- Karma: +3/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #3 on: 2015-08-13, 13:33:31 »
iya bisa "sh /script/mem-usage"
Logged
easy, secure and speed up web panel ===> Kloxo-MR

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #4 on: 2015-08-13, 13:34:57 »
Quote from: zenkul on 2015-08-13, 13:33:31

> iya bisa "sh /script/mem-usage"

Catatan: webserver (seperti httpd, hiawatha dan lain-lain) menggunakan 'apache' sebagai user.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #5 on: 2015-08-13, 19:27:36 »
terima kasih banyak, ini saya test hasil mem-usage nya :
Quote

> [root@vps ~]# sh /script/mem-usage
> Loaded plugins: fastestmirror, priorities, protectbase, replace
> Setting up Install Process
> Loading mirror speeds from cached hostfile
> * base: centos.usonyx.net
> * extras: mirror.nus.edu.sg
> * mratwork-epel: mirror.smartmedia.net.id
> * mratwork-ius-stable: hkg.mirror.rackspace.com
> * updates: mirror.nus.edu.sg
> 0 packages excluded due to repository protections
> Resolving Dependencies
> There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
> --> Running transaction check
> ---> Package smem.noarch 0:1.4-1.el6 will be installed
> --> Finished Dependency Resolution
> Dependencies Resolved
> ================================================================================
> Package Arch Version Repository Size
> ================================================================================
> Installing:
> smem noarch 1.4-1.el6 mratwork-epel 21 k
> Transaction Summary
> ================================================================================
> Install 1 Package(s)
> Total download size: 21 k
> Installed size: 41 k
> Downloading Packages:
> smem-1.4-1.el6.noarch.rpm | 21 kB 00:00
> Running rpm_check_debug
> Running Transaction Test
> Transaction Test Succeeded
> Running Transaction
> Installing : smem-1.4-1.el6.noarch 1/1
> Verifying : smem-1.4-1.el6.noarch 1/1
> Installed:
> smem.noarch 0:1.4-1.el6
> Complete!
> User Count Swap USS PSS RSS
> dbus 1 248.0K 4.0K 4.0K 8.0K
> qmailq 1 52.0K 4.0K 4.0K 8.0K
> qmailr 1 72.0K 4.0K 4.0K 8.0K
> qmails 1 96.0K 4.0K 4.0K 8.0K
> tinydns 1 56.0K 4.0K 4.0K 8.0K
> qmaild 3 104.0K 40.0K 54.0K 112.0K
> lxlabs 1 452.0K 64.0K 77.0K 128.0K
> qmaill 10 548.0K 96.0K 113.0K 308.0K
> vpopmail 2 58.0M 828.0K 948.0K 1.2M
> mysql 1 57.1M 10.7M 10.7M 10.9M
> agustian_irmawan 6 27.7M 45.0M 61.9M 145.8M
> root 74 69.1M 68.4M 77.2M 108.1M
> apache 3 113.0M 400.9M 401.3M 402.7M
> ---------------------------------------------------
> 105 326.4M 526.0M 552.3M 669.4M

setelah ini apa yang harus saya lakukan pak ?
Logged

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #6 on: 2015-08-13, 19:51:01 »
ini adalah hasil lainnya yang isi nya malah berbeda =
[qoute][root@vps ~]# sh /script/mem-usage
User Count Swap USS PSS RSS
dbus 1 248.0K 4.0K 4.0K 8.0K
tinydns 1 0 52.0K 52.0K 64.0K
qmailq 1 0 68.0K 72.0K 204.0K
qmailr 1 0 72.0K 72.0K 112.0K
qmails 1 0 144.0K 151.0K 312.0K
qmaild 3 0 152.0K 168.0K 324.0K
qmaill 10 28.0K 624.0K 668.0K 1.7M
lxlabs 1 0 592.0K 767.0K 1.3M
mysql 1 20.7M 21.0M 21.1M 21.5M
vpopmail 2 16.0K 3.0M 21.9M 61.0M
root 128 45.5M 51.2M 65.7M 116.8M
apache 3 9.6M 491.4M 492.5M 495.2M
---------------------------------------------------
153 76.0M 568.3M 603.2M 698.5M
[root@vps ~]#
[/quote]
Quote from: agustianirmawan on 2015-08-13, 19:27:36

> terima kasih banyak, ini saya test hasil mem-usage nya :
> Quote

> > [root@vps ~]# sh /script/mem-usage
> > Loaded plugins: fastestmirror, priorities, protectbase, replace
> > Setting up Install Process
> > Loading mirror speeds from cached hostfile
> > * base: centos.usonyx.net
> > * extras: mirror.nus.edu.sg
> > * mratwork-epel: mirror.smartmedia.net.id
> > * mratwork-ius-stable: hkg.mirror.rackspace.com
> > * updates: mirror.nus.edu.sg
> > 0 packages excluded due to repository protections
> > Resolving Dependencies
> > There are unfinished transactions remaining. You might consider running yum-complete-transaction first to finish them.
> > --> Running transaction check
> > ---> Package smem.noarch 0:1.4-1.el6 will be installed
> > --> Finished Dependency Resolution
> > Dependencies Resolved
> > ================================================================================
> > Package Arch Version Repository Size
> > ================================================================================
> > Installing:
> > smem noarch 1.4-1.el6 mratwork-epel 21 k
> > Transaction Summary
> > ================================================================================
> > Install 1 Package(s)
> > Total download size: 21 k
> > Installed size: 41 k
> > Downloading Packages:
> > smem-1.4-1.el6.noarch.rpm | 21 kB 00:00
> > Running rpm_check_debug
> > Running Transaction Test
> > Transaction Test Succeeded
> > Running Transaction
> > Installing : smem-1.4-1.el6.noarch 1/1
> > Verifying : smem-1.4-1.el6.noarch 1/1
> > Installed:
> > smem.noarch 0:1.4-1.el6
> > Complete!
> > User Count Swap USS PSS RSS
> > dbus 1 248.0K 4.0K 4.0K 8.0K
> > qmailq 1 52.0K 4.0K 4.0K 8.0K
> > qmailr 1 72.0K 4.0K 4.0K 8.0K
> > qmails 1 96.0K 4.0K 4.0K 8.0K
> > tinydns 1 56.0K 4.0K 4.0K 8.0K
> > qmaild 3 104.0K 40.0K 54.0K 112.0K
> > lxlabs 1 452.0K 64.0K 77.0K 128.0K
> > qmaill 10 548.0K 96.0K 113.0K 308.0K
> > vpopmail 2 58.0M 828.0K 948.0K 1.2M
> > mysql 1 57.1M 10.7M 10.7M 10.9M
> > agustian_irmawan 6 27.7M 45.0M 61.9M 145.8M
> > root 74 69.1M 68.4M 77.2M 108.1M
> > apache 3 113.0M 400.9M 401.3M 402.7M
> > ---------------------------------------------------
> > 105 326.4M 526.0M 552.3M 669.4M

> setelah ini apa yang harus saya lakukan pak ?

Logged

#### zenkul

- Global Moderator
- Master
- Posts: 383
- Karma: +3/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #7 on: 2015-08-13, 19:58:42 »
# sekedar merespon
itu apache kok gede banget
apa kloxo-mr nya msih standar ?
apa sudah apache optimize (pilih yg kecil) lewat panel ?
----
to : Pak MR, kalau hiawatha proxy seperti itu berarti user apache = apache + hiawatha + php (fpm)
« Last Edit: 2015-08-13, 20:05:51 by zenkul »
Logged
easy, secure and speed up web panel ===> Kloxo-MR

#### MRatWork

- Administrator
- The Elite
- Posts: 15,381
- Karma: +112/-9
- Gender:

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #8 on: 2015-08-14, 01:45:23 »
Quote from: zenkul on 2015-08-13, 19:58:42

> # sekedar merespon
> itu apache kok gede banget
> apa kloxo-mr nya msih standar ?
> apa sudah apache optimize (pilih yg kecil) lewat panel ?
> ----
> to : Pak MR, kalau hiawatha proxy seperti itu berarti user apache = apache + hiawatha + php (fpm)

Coba jalankan 'smem|grep -i apache|grep -v grep'. Anda akan tahu aplikasi apa saja yang 'jalan' dibawah 'apache' user.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #9 on: 2015-08-14, 02:10:35 »
Quote

> [root@vps ~]# smem|grep -i apache|grep -v grep
> 32044 apache /usr/sbin/fcgi-pm 5128 32 207 628
> 31903 apache /usr/sbin/hiawatha -c /etc/ 2544 6200 6267 6580
> 8195 apache /usr/sbin/httpd.event 4464 505000 505285 506036
> [root@vps ~]#

ini pak hasil nya... gimana tuh pak ?
Quote from: MRatWork on 2015-08-14, 01:45:23

> Quote from: zenkul on 2015-08-13, 19:58:42

> > # sekedar merespon
> > itu apache kok gede banget
> > apa kloxo-mr nya msih standar ?
> > apa sudah apache optimize (pilih yg kecil) lewat panel ?
> > ----
> > to : Pak MR, kalau hiawatha proxy seperti itu berarti user apache = apache + hiawatha + php (fpm)

> Coba jalankan 'smem|grep -i apache|grep -v grep'. Anda akan tahu aplikasi apa saja yang 'jalan' dibawah 'apache' user.

Logged

#### zenkul

- Global Moderator
- Master
- Posts: 383
- Karma: +3/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #10 on: 2015-08-14, 04:48:36 »
iya memang apache (httpd) yg paling gede
saran saya itu
opsi 1
- apache optimize lewat panel (atau cekik secara manual pada file httpd.conf)
opsi 2
- pilih hanya hiawatha
## max child untuk php-fpm bisa juga dicekik, misalnya jadi 3
jangan lupa periksa log manager terutama hiawatha garbage, barangkali aja kena flooding, itu kok swap bisa sampai habis
) atau mungkin normal karena lonjakan trafik, kalau iya, berarti memang perlu "dicekik" atau naikkan spek vps
- untuk optimasi (penyesuaian/tuning) ternyata sudah banyak contoh, search aja di sini
« Last Edit: 2015-08-14, 04:53:33 by zenkul »
Logged
easy, secure and speed up web panel ===> Kloxo-MR

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #11 on: 2015-08-14, 05:14:26 »
pak kalau pilihannya hanya hiawatha berarti pilihannya hiawatha saja yah bukan hiawatha-proxy ?
saya tidak bisa akses panel, loading terus sangat lemot... buka via putty juga lemot..
max child untuk php-fpm itu merubah nya dibagian mana pak ?
periksa log manager terutama hiawatha garbage itu bagaimana cara nya pak ?
sepertinya bukan karena lonjakan traffic pak soalnya masih sama saja per hari nya 3000-7000 pengunjung nya..
Quote from: zenkul on 2015-08-14, 04:48:36

> iya memang apache (httpd) yg paling gede
> saran saya itu
> opsi 1
> - apache optimize lewat panel (atau cekik secara manual pada file httpd.conf)
> opsi 2
> - pilih hanya hiawatha
> ## max child untuk php-fpm bisa juga dicekik, misalnya jadi 3
> jangan lupa periksa log manager terutama hiawatha garbage, barangkali aja kena flooding, itu kok swap bisa sampai habis
> ) atau mungkin normal karena lonjakan trafik, kalau iya, berarti memang perlu "dicekik" atau naikkan spek vps
> - untuk optimasi (penyesuaian/tuning) ternyata sudah banyak contoh, search aja di sini

Logged

#### zenkul

- Global Moderator
- Master
- Posts: 383
- Karma: +3/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #12 on: 2015-08-14, 05:41:40 »
reboot lewat vps panel >> login via ssh >> stop beberapa servis (lihat komen kedua di atas)
>> lalu masuk (login) ke kloxo-mr >> server >> log manager >> lihat terutama yg bagian hiawatha
dan bisa dicoba "hanya" hiawatha (nggak pake proxy)
BTW kloxo-mr nya juga perlu diupdate
« Last Edit: 2015-08-14, 05:48:49 by zenkul »
Logged
easy, secure and speed up web panel ===> Kloxo-MR

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #13 on: 2015-08-14, 08:42:42 »
sudah berhasil dapatkan log nya pak.. ini isi nya
Contents for /hiawatha/garbage.log
Quote

> 222.186.129.5|Sun 09 Aug 2015 11:17:30 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Sun 09 Aug 2015 11:33:21 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 04:34:25 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Wed 12 Aug 2015 04:40:25 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 04:54:32 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 05:08:35 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Wed 12 Aug 2015 05:08:40 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 07:14:22 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 08:18:50 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Wed 12 Aug 2015 08:37:09 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 10:38:20 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Wed 12 Aug 2015 10:39:00 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 11:32:18 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 20:21:53 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 20:50:39 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 146.185.239.100|Wed 12 Aug 2015 20:57:00 -0400|GET http://24x7-allrequestsallowed.com/?PHPSESSID=a45ad32b00143PP%5BJW_HYCB%5DJOT HTTP/1.1
> Host: 24x7-allrequestsallowed.com
> Accept: */*
> Proxy-Connection: Keep-Alive
> 222.186.129.5|Wed 12 Aug 2015 21:18:12 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Wed 12 Aug 2015 21:18:18 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Wed 12 Aug 2015 21:24:16 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 21:24:43 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.129.5|Wed 12 Aug 2015 23:18:15 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.1
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80
> 222.186.30.211|Thu 13 Aug 2015 02:50:54 -0400|POST http://123.249.24.233/POST_ip_port.php HTTP/1.0
> Referer: http://123.249.24.233/POST_ip_port.phpAccept: */*
> Accept-Language: zh-cn
> Content-Type: application/x-www-form-urlencoded
> User-Agent: Mozilla/4.0 (compatible; MSIE 9.0; Windows NT 6.1; 125LA; .NET CLR 2.0.50727; .NET CLR 3.0.04506.648; .NET CLR 3.5.21022)
> Host: 123.249.24.233
> Content-Length: 38
> Pragma: no-cache
> &verifycode=&ip_port=128.199.165.86:80

di dalam log nya ada IP yang saya tidak kenal pak..
dan baru saja saya rubah menjadi hiawatha saja pak...
saya juga sudah update kloxo-mr nya kok kemarin
Quote from: zenkul on 2015-08-14, 05:41:40

> reboot lewat vps panel >> login via ssh >> stop beberapa servis (lihat komen kedua di atas)
> >> lalu masuk (login) ke kloxo-mr >> server >> log manager >> lihat terutama yg bagian hiawatha
> dan bisa dicoba "hanya" hiawatha (nggak pake proxy)
> BTW kloxo-mr nya juga perlu diupdate

Logged

#### agustianirmawan

- Valuable Member
- Posts: 99
- Karma: +0/-0

##### Re: Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

« Reply #14 on: 2015-08-14, 11:22:41 »
Setelah saya mengganti Hiawatha-proxy menjadi hiawatha saja, website nya tidak bisa diakses, buka di opera tulisannya This webpage has a redirect loop gak ada logo kloxo-mr kalaupun emang muncul kode error..
bagaimana penyelesaiannya yah pak ?
Quote

> [root@vps ~]# sh /script/sysinfo
> A. Kloxo-MR: 7.0.0.b-2015081101
> - Web: hiawatha-9.14.0-f.6.mr.el6.i386
> - PHP: php53s-5.3.29-1.ius.el6 (fpm mode)
> B. Plateform:
> - OS: CentOS release 6.7 (Final) i686
> - Hostname: vps.acmi1899.com
> C. Services:
> 1. MySQL: mysql55-5.5.45-1.ius.el6.i686
> 2. PHP:
> - Branch: php53u-cli-5.3.29-1.ius.el6.i686
> - Multiple:
> * php55m-5.5.26-1.ius.el6
> - Used: --Use PHP Branch--
> 3. Httpd: httpd-2.2.31-1.mr.el6.i386
> - PHP Type: php-fpm_event
> 4. Lighttpd: --uninstalled--
> 5. Hiawatha: --used--
> 6. Nginx: --uninstalled--
> 7. Cache: --uninstalled--
> 8. Dns: --uninstalled--
> 9. Qmail: qmail-toaster-1.03-1.3.55.mr.el6.i386
> - with: courier-imap-toaster-4.1.2-1.3.18.mr.el6.i386
> D. Memory:
> total used free shared buffers cached
> Mem: 1006 795 211 0 13 135
> -/+ buffers/cache: 646 359
> Swap: 1023 11 1012
> E. Disk Space:
> Filesystem Size Used Avail Use% Mounted on
> /dev/vda1 20G 6.9G 12G 37% /

Logged

- Print

Pages: [1] 2 Go Up
« previous next »

- MRatWork Forum by Mustafa Ramadhan »
- Language Specific Discussions »
- Indonesia Users »
- Cara Mengetahui Penyebab Tingginya Penggunaan Ram ?

Top 10 Social Networking: Facebook Twitter LinkedIn Pinterest Google Plus Tumblr Instagram VK Flickr Vine

..:: Monetize Your Website with ylliXmedia ::.. ..:: Online Advertising that Sale Anything with ylliXmedia ::..

- Design By SMFSimple.com
- SMF 2.0.14 | SMF © 2017, Simple Machines

Page created in 0.049 seconds with 17 queries.

Mirror created by MasterkinG32.CoM