Messages

106

Indonesia Users / Re: MYSQL Bengkak

« on: 2014-01-09, 22:06:35 »

Coba lihat saja directory (artinya itu sekaligus name domain) mana saja yang menghabiskan ruang.

Menjalankan 'sh /script/mysql-optimize --select=optimize' akan 'merapikan' (semacam defrag) database sehingga akan memperkecil pemakaian ruang.

lama banget selesainya egk sabaran di ctrl+cencel :
( note : Table does not support optimize, doing recreate + analyze instead )
hampir semua begitu..

akhirnya ketemu yang bikin lama saat melakukan optimize:

Code: [Select]

There is a common issue whereby a sites 'cache_form' table gets really big. It basically doesn't clear on Cron runs and just keeps growing, often getting to a couple GB in size.

There are various posts about possible causes and cures, but if you find that you aren't able to log into your site to clear your caches due to your DB size limit being breached, then you can use this MySQL query to clear the 'cache_form' table manually. This will just clear the table - it won't break your site and you won't lose any data.
dan saya juga sudah melakukan 'sh /script/mysql-convert --engine=MyISAM' lanjut dengan 'sh /script/mysql-optimize --select=optimize'
sedikit lega.. walau belum ke tahap penyelesaian bengkaknya pada:

Code: [Select]

mysql 404525940736 Jan 10 03:58 ibdata1
nunggu kode dari master yang akan saya paste di ssh master

Terima kasih master..

107

Indonesia Users / Re: MYSQL Bengkak

« on: 2014-01-09, 20:45:05 »

pusing master.. 

108

Indonesia Users / Re: MYSQL Bengkak

« on: 2014-01-09, 19:40:43 »

The paths to individual InnoDB data files and their sizes. The full directory path to each data file is formed by concatenating innodb_data_home_dir to each path specified here. The file sizes are specified KB, MB or GB (1024MB) by appending K, M or G to the size value. If specifying data file size in kilobytes (KB), do so in multiples of 1024. Otherwise, KB values are rounded off to nearest megabyte (MB) boundary. The sum of the sizes of the files must be at least slightly larger than 10MB. If you do not specify innodb_data_file_path, the default behavior is to create a single auto-extending data file, slightly larger than 10MB, named ibdata1. The size limit of individual files is determined by your operating system. You can set the file size to more than 4GB on those operating systems that support big files. You can also use raw disk partitions as data files. For detailed information on configuring InnoDB tablespace files, see Section 14.3.6, “InnoDB Configuration”.

Code: [Select]

http://dev.mysql.com/doc/refman/5.5/en/innodb-configuration.html
semakin hari semakin bengkak:

Code: [Select]

375.088G ibdata1

Code: [Select]

[mysqld]
innodb_file_per_table=on
;###123###;###123###;###123###;###123###;###123###;###123###skip-innodb
default-storage-engine=myisam

## General
datadir                         = /var/lib/mysql
tmpdir                          = /var/lib/mysqltmp
socket                          = /var/lib/mysql/mysql.sock
;###123###;###123###;###123###;###123###;###123###;###123###skip-name-resolve
sql-mode                        = NO_ENGINE_SUBSTITUTION
#event-scheduler                = 1

## Cache
thread-cache-size               = 16
table-open-cache                = 4096
table-definition-cache          = 2048
query-cache-size                = 32M
query-cache-limit               = 1M

## Per-thread Buffers
sort-buffer-size                = 1M
read-buffer-size                = 1M
read-rnd-buffer-size            = 1M
join-buffer-size                = 1M

## Temp Tables
tmp-table-size                  = 32M
max-heap-table-size             = 64M

## Networking
back-log                        = 100
#max-connections                = 200
max-connect-errors              = 10000
max-allowed-packet              = 100M
interactive-timeout             = 3600
wait-timeout                    = 600

### Storage Engines
innodb                          = FORCE

## MyISAM
key-buffer-size                 = 64M
myisam-sort-buffer-size         = 128M

## InnoDB
#innodb-buffer-pool-size        = 128M
#innodb-log-file-size           = 100M
#innodb-log-buffer-size         = 8M
#innodb-file-per-table          = 1
#innodb-open-files              = 300

## Replication
server-id                       = 1
#log-bin                        = /var/log/mysql/bin-log
#relay-log                      = /var/log/mysql/relay-log
relay-log-space-limit           = 16G
expire-logs-days                = 3
#read-only                      = 1
#sync-binlog                    = 1
#log-slave-updates              = 1
#binlog-format                  = STATEMENT
#auto-increment-offset          = 1
#auto-increment-increment       = 2

## Logging
#log-output                      = FILE
#slow-query-log                  = 1
#slow-query-log-file             = /var/log/mysql/slow-log
#log-slow-slave-statements
#long-query-time                 = 2

[mysqld_safe]
log-error                       = /var/log/mysqld.log
open-files-limit                = 65535

[mysql]
no-auto-rehash

109

Indonesia Users / Re: MYSQL Bengkak

« on: 2014-01-09, 01:48:38 »

dir -l /var/lib/mysql
total 388430616
mysql mysql         4096 Jan  3 02:26 admin
mysql mysql         4096 Jan  7 12:47 afterlogic
mysql mysql 397353680896 Jan  9 07:41 ibdata1
mysql mysql      5242880 Jan  9 07:41 ib_logfile0
mysql mysql      5242880 Jan  9 07:41 ib_logfile1

Bolehkah yang diberi warna merah dihapus? ada efek samping nya egk?

Thx

110

Indonesia Users / Re: No valid SOA record came back!

« on: 2014-01-09, 00:20:50 »

Selamat pagi  sambil ngopi dan merokok ya..

langsung aja  masih tersesat dengan permasalahan pada judul ini' hasil googling ditemukan artikel mengenai bind 'http://www.unixmen.com/dns-server-installation-step-by-step-using-centos-6-3/' apakah pada artikel tsb dapat di gunakan pada kloxo-mr yang saya gunakan?

A. Kloxo-MR: 6.5.0.f-2014010101

B. OS: CentOS release 5.10 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.35-1.ius.el5
   2. PHP: php54-5.4.23-3.ius.el5
   3. Httpd: httpd-2.2.26-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: --uninstalled-- ( karena menggunakan nginx-special dan nginx-proxy)
   6. Qmail: qmail-toaster-1.03-1.3.29.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.14.mr.el5
   7. Dns: bind-9.9.4-1.P1.el5

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          2469       2428         41          0        382        992
   -/+ buffers/cache:       1053       1416
   Swap:        11999          0      11999

Terima kasih.

111

Indonesia Users / Re: folder user email muncul di folder /localhost/ pada versi 6.5.0.f-2014010101

« on: 2014-01-07, 14:13:04 »

  bukan itu maksudku kakanda.. tapi yang ku maksudkan bagaimana jika downgrade ke versi MR yang sebelumnya.. saat in iyang digunakan kan 'versi 6.5.0.f-2014010101' bagaimana jika ku downgrade ke sebelumnya?

atau sebaiknya aku tunggu releas yang berikutnya saja.. 

thx.

112

Indonesia Users / Re: folder user email muncul di folder /localhost/ pada versi 6.5.0.f-2014010101

« on: 2014-01-07, 04:50:41 »

Code: [Select]

A. Kloxo-MR: 6.5.0.f-2014010101

B. OS: CentOS release 5.10 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.35-1.ius.el5
   2. PHP: php54-5.4.23-3.ius.el5
   3. Httpd: httpd-2.2.26-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: nginx-1.5.8-1.el5
   6. Qmail: qmail-toaster-1.03-1.3.29.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.14.mr.el5
   7. Dns: bind-9.9.4-1.P1.el5

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          2469       2340        129          0        216       1221
   -/+ buffers/cache:        902       1567
   Swap:        11999          0      11999
Jika downgrade apakah permasalahan pada akun email yang terbentuk folder pada localhost akan teratasi?

Mohon arahannya master.

Thx

113

Indonesia Users / Re: [ASK] Web Tiba2 Menjadi Lemot

« on: 2014-01-07, 04:25:56 »

setelah saya upgrade ke kloxo versi paling akhir belum saya cek performa web saya, tapi setelah saya cek tiba2 kok lemot, loadingnya lama, padahal menurut saya membuka halaman yang sangat ringan.... sudah saya switch php type dll tetap sama... saya cek speedtest server masih kenceng, saya tanya ke CS katanya gk ada masalah... kira2 masalahnya apa ya?
ngeload html static aja lama hXXp://mp3days.com/coba.html

*) pakek openvz ramnode, selama ini tidak pernah mengalami masalah gangguan serve...

Code: [Select]

A. Kloxo-MR: 6.5.0.f-2014010301

B. OS: CentOS release 5.10 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.35-1.ius.el5
   2. PHP: php53u-5.3.28-1.ius.el5
   3. Httpd: httpd-2.2.26-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: nginx-1.5.8-1.el5
   6. Qmail: qmail-toaster-1.03-1.3.29.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.14.mr.el5
   7. Dns: bind-9.9.4-1.P1.el5

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          1024        597        426          0          0        195
   -/+ buffers/cache:        402        621


Script Webnya pake apa?
coba widged share this nya di non aktifkan dulu..

114

Indonesia Users / Re: folder user email muncul di folder /localhost/ pada versi 6.5.0.f-2014010101

« on: 2014-01-04, 01:46:28 »

Hi, mau pakai nginx apa saja (termasuk nantinya jika tengine sudah tersedia) maka nginx akan terlihat aktif.

Jangan pakai nginx-special karena akan diganti dengan tengine.

Dalam standard Kloxo (juga Kloxo-MR tentunya) tidak akan ada directory localhost. Coba saja hapus directory tersebut dan jalankan lagi 'sh /script/fixmail-all'.

nginx-special gantinya apa?
yum remove nginx-special; yum install ?

115

Indonesia Users / Re: folder user email muncul di folder /localhost/ pada versi 6.5.0.f-2014010101

« on: 2014-01-04, 00:50:29 »

saya sudah pilih satu-satu hingga semua terpilih dan siap untuk di remove alhasil gagal semua kembali lagi menjadi ada lagi.. 

ada cara lain?

thx

116

Indonesia Users / Re: No valid SOA record came back!

« on: 2014-01-03, 15:03:41 »

versi 6.5.1.f kapan saya bisa cicipin 

117

Indonesia Users / Re: folder user email muncul di folder /localhost/ pada versi 6.5.0.f-2014010101

« on: 2014-01-03, 15:00:14 »

saya sudah pilih satu-satu hingga semua terpilih dan siap untuk di remove alhasil gagal semua kembali lagi menjadi ada lagi.. 

118

Indonesia Users / folder user email muncul di folder /localhost/ pada versi 6.5.0.f-2014010101

« on: 2014-01-03, 13:49:58 »

seluruh user email muncul namanya berupa folder di folder /localhost/ pada versi 6.5.0.f-2014010101
contoh freedoom@domain.tld maka user email tersebut muncul berupa folder dengan nama 'freedoom' di '/localhost/'

A. Kloxo-MR: 6.5.0.f-2014010101

B. OS: CentOS release 5.10 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.35-1.ius.el5
   2. PHP: php54-5.4.23-3.ius.el5
   3. Httpd: httpd-2.2.26-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: --uninstalled-- ( karena menggunakan nginx-special dan nginx-proxy)
   6. Qmail: qmail-toaster-1.03-1.3.29.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.14.mr.el5
   7. Dns: bind-9.9.4-1.P1.el5

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          2469       2428         41          0        382        992
   -/+ buffers/cache:       1053       1416
   Swap:        11999          0      11999

solusinya dipersilahkan.. thx

119

Indonesia Users / Re: No valid SOA record came back!

« on: 2014-01-03, 13:27:46 »

  ini berdasarkan refernsi dari versi bind yang didapat dari '/usr/share/doc/bind-9.9.4/sample/etc/named.conf'.. apakah versi MR x ini sudah sesuai? atau di saya nya yang belum pas configurasinya..!! 

Code: [Select]

/*
 Sample named.conf BIND DNS server 'named' configuration file
 for the Red Hat BIND distribution.

 See the BIND Administrator's Reference Manual (ARM) for details, in:
   file:///usr/share/doc/bind-{version}/arm/Bv9ARM.html
 Also see the BIND Configuration GUI : /usr/bin/system-config-bind and
 its manual.
*/

options
{
// Put files that named is allowed to write in the data/ directory:
directory "/var/named"; // "Working" directory
dump-file "data/cache_dump.db";
        statistics-file "data/named_stats.txt";
        memstatistics-file "data/named_mem_stats.txt";


/*
  Specify listenning interfaces. You can use list of addresses (';' is
  delimiter) or keywords "any"/"none"
*/
//listen-on port 53 { any; };
listen-on port 53 { 127.0.0.1; };

//listen-on-v6 port 53 { any; };
listen-on-v6 port 53 { ::1; };

/*
  Access restrictions

  There are two important options:
    allow-query { argument; };
      - allow queries for authoritative data

    allow-query-cache { argument; };
      - allow queries for non-authoritative data (mostly cached data)

  You can use address, network address or keywords "any"/"localhost"/"none" as argument
  Examples:
    allow-query { localhost; 10.0.0.1; 192.168.1.0/8; };
    allow-query-cache { ::1; fe80::5c63:a8ff:fe2f:4526; 10.0.0.1; };
*/

allow-query { localhost; };
allow-query-cache { localhost; };

// Enable/disable recursion - recursion yes/no;
recursion yes;

/* DNSSEC related options. See information about keys ("Trusted keys", bellow) */

/* Enable serving of DNSSEC related data - enable on both authoritative
     and recursive servers DNSSEC aware servers */
dnssec-enable yes;

/* Enable DNSSEC validation on recursive servers */
dnssec-validation yes;

/* Enable DLV by default, use built-in ISC DLV key. */
dnssec-lookaside auto;
};

logging
{
/*      If you want to enable debugging, eg. using the 'rndc trace' command,
 *      named will try to write the 'named.run' file in the $directory (/var/named).
 *      By default, SELinux policy does not allow named to modify the /var/named directory,
 *      so put the default debug log file in data/ :
 */
        channel default_debug {
                file "data/named.run";
                severity dynamic;
        };
};

/*
 Views let a name server answer a DNS query differently depending on who is asking.

 By default, if named.conf contains no "view" clauses, all zones are in the
 "default" view, which matches all clients.

 Views are processed sequentially. The first match is used so the last view should
 match "any" - it's fallback and the most restricted view.

 If named.conf contains any "view" clause, then all zones MUST be in a view.
*/

view "localhost_resolver"
{
/* This view sets up named to be a localhost resolver ( caching only nameserver ).
 * If all you want is a caching-only nameserver, then you need only define this view:
 */
match-clients { localhost; };
recursion yes;

# all views must contain the root hints zone:
zone "." IN {
        type hint;
        file "/var/named/named.ca";
};

        /* these are zones that contain definitions for all the localhost
         * names and addresses, as recommended in RFC1912 - these names should
* not leak to the other nameservers:
*/
include "/etc/named.rfc1912.zones";
};
view "internal"
{
/* This view will contain zones you want to serve only to "internal" clients
   that connect via your directly attached LAN interfaces - "localnets" .
 */
match-clients { localnets; };
recursion yes;

zone "." IN {
        type hint;
        file "/var/named/named.ca";
};

        /* these are zones that contain definitions for all the localhost
         * names and addresses, as recommended in RFC1912 - these names should
* not leak to the other nameservers:
*/
include "/etc/named.rfc1912.zones";
 
// These are your "authoritative" internal zones, and would probably
// also be included in the "localhost_resolver" view above :

/*
  NOTE for dynamic DNS zones and secondary zones:

  DO NOT USE SAME FILES IN MULTIPLE VIEWS!

  If you are using views and DDNS/secondary zones it is strongly
  recommended to read FAQ on ISC site (www.isc.org), section
  "Configuration and Setup Questions", questions
  "How do I share a dynamic zone between multiple views?" and
  "How can I make a server a slave for both an internal and an external
   view at the same time?"
*/

zone "my.internal.zone" {
type master;
file "my.internal.zone.db";
};
zone "my.slave.internal.zone" {
type slave;
file "slaves/my.slave.internal.zone.db";
masters { /* put master nameserver IPs here */ 127.0.0.1; } ;
// put slave zones in the slaves/ directory so named can update them
};
zone "my.ddns.internal.zone" {
type master;
allow-update { key ddns_key; };
file "dynamic/my.ddns.internal.zone.db";
// put dynamically updateable zones in the slaves/ directory so named can update them
};
};

key ddns_key
{
algorithm hmac-md5;
secret "use /usr/sbin/dnssec-keygen to generate TSIG keys";
};

view "external"
{
/* This view will contain zones you want to serve only to "external" clients
 * that have addresses that are not match any above view:
 */
match-clients { any; };

zone "." IN {
        type hint;
        file "/var/named/named.ca";
};

recursion no;
// you'd probably want to deny recursion to external clients, so you don't
        // end up providing free DNS service to all takers

// These are your "authoritative" external zones, and would probably
        // contain entries for just your web and mail servers:

zone "my.external.zone" {
type master;
file "my.external.zone.db";
};
};

/* Trusted keys

  This statement contains DNSSEC keys. If you want DNSSEC aware resolver you
  have to configure at least one trusted key.

  Note that no key written below is valid. Especially root key because root zone
  is not signed yet.
*/
/*
trusted-keys {
// Root Key
"." 257 3 3 "BNY4wrWM1nCfJ+CXd0rVXyYmobt7sEEfK3clRbGaTwSJxrGkxJWoZu6I7PzJu/
             E9gx4UC1zGAHlXKdE4zYIpRhaBKnvcC2U9mZhkdUpd1Vso/HAdjNe8LmMlnzY3
             zy2Xy4klWOADTPzSv9eamj8V18PHGjBLaVtYvk/ln5ZApjYghf+6fElrmLkdaz
             MQ2OCnACR817DF4BBa7UR/beDHyp5iWTXWSi6XmoJLbG9Scqc7l70KDqlvXR3M
             /lUUVRbkeg1IPJSidmK3ZyCllh4XSKbje/45SKucHgnwU5jefMtq66gKodQj+M
             iA21AfUVe7u99WzTLzY3qlxDhxYQQ20FQ97S+LKUTpQcq27R7AT3/V5hRQxScI
             Nqwcz4jYqZD2fQdgxbcDTClU0CRBdiieyLMNzXG3";

// Key for forward zone
example.com. 257 3 5 "AwEAAaxPMcR2x0HbQV4WeZB6oEDX+r0QM65KbhTjrW1ZaARmPhEZZe
                      3Y9ifgEuq7vZ/zGZUdEGNWy+JZzus0lUptwgjGwhUS1558Hb4JKUbb
                      OTcM8pwXlj0EiX3oDFVmjHO444gLkBO UKUf/mC7HvfwYH/Be22GnC
                      lrinKJp1Og4ywzO9WglMk7jbfW33gUKvirTHr25GL7STQUzBb5Usxt
                      8lgnyTUHs1t3JwCY5hKZ6CqFxmAVZP20igTixin/1LcrgX/KMEGd/b
                      iuvF4qJCyduieHukuY3H4XMAcR+xia2 nIUPvm/oyWR8BW/hWdzOvn
                      SCThlHf3xiYleDbt/o1OTQ09A0=";

// Key for reverse zone.
2.0.192.IN-ADDRPA.NET. 257 3 5 "AQOnS4xn/IgOUpBPJ3bogzwcxOdNax071L18QqZnQQQA
                                VVr+iLhGTnNGp3HoWQLUIzKrJVZ3zggy3WwNT6kZo6c0
                                tszYqbtvchmgQC8CzKojM/W16i6MG/ea fGU3siaOdS0
                                yOI6BgPsw+YZdzlYMaIJGf4M4dyoKIhzdZyQ2bYQrjyQ
                                4LB0lC7aOnsMyYKHHYeRv PxjIQXmdqgOJGq+vsevG06
                                zW+1xgYJh9rCIfnm1GX/KMgxLPG2vXTD/RnLX+D3T3UL
                                7HJYHJhAZD5L59VvjSPsZJHeDCUyWYrvPZesZDIRvhDD
                                52SKvbheeTJUm6EhkzytNN2SN96QRk8j/iI8ib";
};
*/

A. Kloxo-MR: 6.5.0.f-2014010101

B. OS: CentOS release 5.10 (Final) i686

C. Apps:
   1. MySQL: mysql55-5.5.35-1.ius.el5
   2. PHP: php54-5.4.23-3.ius.el5
   3. Httpd: httpd-2.2.26-1.el5
   4. Lighttpd: --uninstalled--
   5. Nginx: --uninstalled-- ( karena menggunakan nginx-special dan nginx-proxy)
   6. Qmail: qmail-toaster-1.03-1.3.29.mr.el5
      - with: courier-imap-toaster-4.1.2-1.3.14.mr.el5
   7. Dns: bind-9.9.4-1.P1.el5

D. Php-type (for Httpd/proxy): php-fpm_event

E. Memory:
                total       used       free     shared    buffers     cached
   Mem:          2469       2428         41          0        382        992
   -/+ buffers/cache:       1053       1416
   Swap:        11999          0      11999

120

Indonesia Users / Re: No valid SOA record came back!

« on: 2014-01-02, 17:44:22 »

setelah kembali mencoba cleanup ada yang berubah tapi sekarang kesulitan

sh /script/resetpassword master {newpassword}
Notice : The resource you have requested doesn't exist. The server returned the error message: <br>  not_admin_cannot_modify_general   <br>

Thx.