MRatWork Forum by Mustafa Ramadhan - KloxoMR tidak bisa diakses setelah update

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, 20:52:26

- MRatWork Forum by Mustafa Ramadhan »
- Language Specific Discussions »
- Indonesia Users »
- KloxoMR tidak bisa diakses setelah update

« previous next »

- Print

Pages: [1] 2 Go Down

### Author Topic: KloxoMR tidak bisa diakses setelah update (Read 2765 times)

0 Members and 1 Guest are viewing this topic.

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### KloxoMR tidak bisa diakses setelah update

« on: 2016-05-04, 08:46:15 »
baru saja saya update kloxomr ke versi 7.0.0.b-2016050402
setelah selesai update, halaman kloxomr tidak bisa dibuka, baik yg non-ssl (7778) maupun ssl (7777)
saya sudah coba 'sh /script/fix-all -y'; sh /script/restart-all -y' juga tidak bisa
coba restart service kloxo 'service kloxo restart'
buka http:<ip-address>:7778 malah muncul error 'Request Entity Too Large 413'
refresh lagi, tidak bisa dibuka (chrome : ERR_EMPTY_RESPONSE)
Logged

#### MRatWork

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

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #1 on: 2016-05-04, 12:34:26 »
Sehabis update, jalankan 'sh /script/cleanup'.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #2 on: 2016-05-04, 12:58:31 »
Quote from: MRatWork on 2016-05-04, 12:34:26

> Sehabis update, jalankan 'sh /script/cleanup'.

sudah pak
setiap ada update di kloxomr, di bagian bawah setelah yum update selesai dijalankan memang ada semacam 'notif' untuk menjalankan sh /script/cleanup
Code: [Select]

    Running Transaction
      Updating   : kernel-firmware-2.6.32-573.26.1.el6.noarch                  1/22
      Updating   : MariaDB-compat-10.0.25-1.el6.i686                           2/22
      Updating   : MariaDB-common-10.0.25-1.el6.i686                           3/22
      Updating   : MariaDB-client-10.0.25-1.el6.i686                           4/22
      Updating   : initscripts-9.03.49-1.el6.centos.5.i686                     5/22
      Installing : kernel-2.6.32-573.26.1.el6.i686                             6/22
    grubby fatal error: unable to find a suitable template
      Updating   : kernel-headers-2.6.32-573.26.1.el6.i686                     7/22
      Updating   : MariaDB-server-10.0.25-1.el6.i686                           8/22
      Updating   : MariaDB-shared-10.0.25-1.el6.i686                           9/22
      Updating   : kloxomr7-7.0.0.b-2016050402.mr.noarch                      10/22

     _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/
     _/                                                                          _/
     _/  ..:: Kloxo-MR Web Panel ::..                                            _/
     _/                                                                          _/
     _/  Attention:                                                              _/
     _/                                                                          _/
     _/  Run 'sh /script/cleanup' for to make sure running well                  _/
     _/  or 'sh /script/cleanup-simple' (cleanup without fix services configs)   _/
     _/                                                                          _/
     _/  Run 'sh /script/upcp -y' if update from Kloxo 6.1.x/Kloxo-MR 6.5.x      _/
     _/                                                                          _/
     _/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

sudah dijalankan tetapi tetap tidak bisa diakses
web yg di host tetap aktif normal (dengan nginxproxy) tapi kloxomr tidak jalan
seperti 'down'
sebelum update bisa dipakai normal
tapi setelah update kok malah jadi begini
« Last Edit: 2016-05-04, 13:01:08 by Wibowo »
Logged

#### MRatWork

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

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #3 on: 2016-05-04, 13:06:42 »
Coba reboot. Error 413 muncul karena terlalu banyak akses sehingga kena ban.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #4 on: 2016-05-04, 13:11:48 »
Quote from: MRatWork on 2016-05-04, 13:06:42

> Coba reboot. Error 413 muncul karena terlalu banyak akses sehingga kena ban.

sudah pak
jadi setiap kali perintah 'restart' untuk kloxo dikirim (reboot - 'sh /script/restart -y' - 'service kloxo restart' - sh /script/restart-all)
ketika pertama menghasilkan error 413, selanjutnya menghasilkan empty response di browser (tidak bisa diakses seperti web server mati total)
Logged

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #5 on: 2016-05-04, 13:20:44 »
Quote from: MRatWork on 2016-05-04, 13:06:42

> Coba reboot. Error 413 muncul karena terlalu banyak akses sehingga kena ban.

system.log hiawatha '/var/log/hiawatha/system.log'
Code: [Select]

    Wed 04 May 2016 03:16:07 -0400|Hiawatha v10.1 started.
    Wed 04 May 2016 03:16:17 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 03:16:50 -0400|Hiawatha v10.1 started.
    Wed 04 May 2016 03:19:17 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 03:19:17 -0400|Hiawatha v10.1 started.
    Wed 04 May 2016 07:10:27 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 07:10:27 -0400|Hiawatha v10.1 started.
    Wed 04 May 2016 07:10:40 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 07:10:40 -0400|Hiawatha v10.1 started.
    125.163.234.115|Wed 04 May 2016 07:12:04 -0400|Maximum request size reached
    125.163.234.115|Wed 04 May 2016 07:12:04 -0400|Client banned because of sending a too large request
    125.163.234.115|Wed 04 May 2016 07:12:05 -0400|Maximum request size reached
    125.163.234.115|Wed 04 May 2016 07:12:05 -0400|Client banned because of sending a too large request
    Wed 04 May 2016 07:13:09 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 07:13:09 -0400|Hiawatha v10.1 started.
    125.163.234.115|Wed 04 May 2016 07:14:06 -0400|Maximum request size reached
    125.163.234.115|Wed 04 May 2016 07:14:06 -0400|Client banned because of sending a too large request
    Wed 04 May 2016 07:18:06 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 07:18:06 -0400|Hiawatha v10.1 started.
    125.163.234.115|Wed 04 May 2016 07:18:10 -0400|Silent client disconnected
    125.163.234.115|Wed 04 May 2016 07:18:10 -0400|Maximum request size reached
    125.163.234.115|Wed 04 May 2016 07:18:10 -0400|Client banned because of sending a too large request
    36.80.245.177|Wed 04 May 2016 07:18:52 -0400|Maximum request size reached
    36.80.245.177|Wed 04 May 2016 07:18:52 -0400|Client banned because of sending a too large request
    Wed 04 May 2016 07:22:58 -0400|Hiawatha v10.1 stopped.
    Wed 04 May 2016 07:23:09 -0400|Hiawatha v10.1 started.
    139.59.252.253|Wed 04 May 2016 07:23:52 -0400|Maximum request size reached
    139.59.252.253|Wed 04 May 2016 07:23:52 -0400|Client banned because of sending a too large request
    207.244.83.208|Wed 04 May 2016 07:24:00 -0400|Maximum request size reached
    207.244.83.208|Wed 04 May 2016 07:24:00 -0400|Client banned because of sending a too large request
    139.59.252.253|Wed 04 May 2016 07:29:12 -0400|Unbanned (3 connect attempts during ban)
    207.244.83.208|Wed 04 May 2016 07:29:24 -0400|Unbanned (3 connect attempts during ban)
    125.163.234.115|Wed 04 May 2016 07:29:58 -0400|Maximum request size reached
    125.163.234.115|Wed 04 May 2016 07:29:58 -0400|Client banned because of sending a too large request

tiba2 ip di banned karena 'maximum request'
baru dibuka sudah 'maximum request' ?
nilai 'maximum request' ini bisa diganti lewat mana pak?
aneh ini
Logged

#### MRatWork

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

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #6 on: 2016-05-04, 13:34:55 »
Waktu ban adalah 300 detik (5 menit). Coba tunggu 10 menit dan kemudian coba login.
Jika gagal, ganti 'BanOnMaxReqSize = 300' ke 'BanOnMaxReqSize = 0' di '/usr/local/lxlabs/kloxo/init/hiawatha.conf.base'. Dan kemudian lakukan restart dengan 'sh /script/restart -y'.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #7 on: 2016-05-04, 14:20:47 »
Quote from: MRatWork on 2016-05-04, 13:34:55

> Waktu ban adalah 300 detik (5 menit). Coba tunggu 10 menit dan kemudian coba login.
> Jika gagal, ganti 'BanOnMaxReqSize = 300' ke 'BanOnMaxReqSize = 0' di '/usr/local/lxlabs/kloxo/init/hiawatha.conf.base'. Dan kemudian lakukan restart dengan 'sh /script/restart -y'.

tidak bisa pak
jadinya malah selalu seperti ini
ditunggu lama pun (lebih dari 300 detik) yang muncul selalu seperti ini pak
sudah pakai browser lain, coba lewat lain provider tetap sama pak
bahkan pake curl pun tetap 413
Code: [Select]

    [root@harihari]# curl -I -L hostmikro.id:7778
    HTTP/1.1 413 Request Entity Too Large
    Date: Wed, 04 May 2016 12:40:00 GMT
    Server: Hiawatha_for_Kloxo-MR
    Accept-Ranges: bytes
    Connection: close
    Content-Length: 887
    Content-Type: text/html

    [root@harihari]#

« Last Edit: 2016-05-04, 14:24:27 by Wibowo »
Logged

#### MRatWork

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

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #8 on: 2016-05-04, 14:32:54 »
Beri saya hak akses ke ssh dan Kloxo-MR panel. Kirim via PM.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #9 on: 2016-05-04, 15:24:05 »
Quote from: MRatWork on 2016-05-04, 14:32:54

> Beri saya hak akses ke ssh dan Kloxo-MR panel. Kirim via PM.

sudah pak
Logged

#### MRatWork

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

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #10 on: 2016-05-04, 15:33:44 »
Maksudnya sudah PM ke saya?.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #11 on: 2016-05-04, 16:31:24 »
Quote from: MRatWork on 2016-05-04, 15:33:44

> Maksudnya sudah PM ke saya?.

iya sudah saya pm pak
Logged

#### NginxHolic

- Valuable Member
- Posts: 84
- Karma: +1/-0

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #12 on: 2016-05-04, 16:48:48 »
Apakah update Kloxo MR aman?
Logged

#### MRatWork

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

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #13 on: 2016-05-04, 17:04:17 »
Kok PM saya kosong?.
Logged
..:: MRatWork (Mustafa Ramadhan Projects) ::..
-- Server/Web-integrator - Web Hosting (Kloxo-MR READY!) --

#### Wibowo

- Master
- Posts: 391
- Karma: +0/-0
- Gender:

##### Re: KloxoMR tidak bisa diakses setelah update

« Reply #14 on: 2016-05-04, 17:19:05 »
Quote from: MRatWork on 2016-05-04, 17:04:17

> Kok PM saya kosong?.

tadi saya kirim sekitar jam 20:30 (GMT +7) pak
saya kirim ulang pak
Logged

- Print

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

- MRatWork Forum by Mustafa Ramadhan »
- Language Specific Discussions »
- Indonesia Users »
- KloxoMR tidak bisa diakses setelah update

Top 4 Global Search Engines: Google Bing Baidu Yahoo

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

Page created in 0.05 seconds with 18 queries.

Mirror created by MasterkinG32.CoM