This article referring to another article that not published yet, I had some issue with session.save_path in php-fpm setup. For security improvements  I want to make PHP execute under individual user accounts insted of a system user like nginx (default www user and group). In apache environments I can use suPHP or suExec and in Nginx I can use php-fpm with custom “pool” each web server and that makes PHP scripts executed by owner and groups that describe in each pool.
But I got the following error message when try to installing some cms, and how to solve?

2011/12/03 23:49:34 [error] 1330#0: *126 FastCGI sent in stderr: “PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0″ while reading upstream, client: 192.168.0.13, server: localhost, request: “GET /lgz/src/index.php HTTP/1.1″, upstream: “fastcgi://127.0.0.1:9000″, host: “172.16.0.1″, referrer: “http://172.16.0.1/lgz/src/login.php”
2011/12/03 23:54:34 [error] 1333#0: *208 FastCGI sent in stderr: “PHP Warning:  Unknown: open(/tmp/sess_ig3mpbuc2fuhjt1p4ibpe3maa4, O_RDWR) failed: Permission denied (13) in Unknown on line 0″ while reading upstream, client: 192.168.0.13, server: localhost, request: “GET /lgz/src/index.php HTTP/1.1″, upstream: “fastcgi://127.0.0.1:9000″, host: “172.16.0.1″, referrer: “http://172.16.0.1/lgz/src/login.php?referer=%2Flgz%2Fsrc%2Findex.php”
2011/12/03 23:54:34 [error] 1333#0: *208 FastCGI sent in stderr: “PHP Warning:  Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) in Unknown on line 0″ while reading upstream, client: 192.168.0.13, server: localhost, request: “GET /lgz/src/index.php HTTP/1.1″, upstream: “fastcgi://127.0.0.1:9000″, host: “172.16.0.1″, referrer: “http://172.16.0.1/lgz/src/login.php?referer=%2Flgz%2Fsrc%2Findex.php”

I’m sure that the /tmp permission are correct, but in fact I can’t use cookies to process authentication method. The problem is in my pool configuration and I need to add custom php rules here:

php_admin_value[session.save_handler] = files
php_admin_value[session.save_path] = “/tmp”
php_admin_value[session.use_cookies] = 1
php_admin_value[session.name] = PHPSESSID

After uncommented the lines in above, php scripts was success to execute and allowed use cookies in /tmp. This is stupid mind because I haven’t read the manpage before start using pool even my another websites running well, it’s habit (trying before RTFM, and RTFM after see an error). Below is an example of my php-fpm pool configuration:

[site1]
listen = 127.0.0.1:9000
listen.backlog = -1
listen.allowed_clients = 127.0.0.1
;listen.owner = nginx
;listen.group = nginx
;listen.mode = 0666
user = site1
group = site1
pm = dynamic
pm.max_children = 50
pm.start_servers = 20
pm.min_spare_servers = 5
pm.max_spare_servers = 35
pm.max_requests = 200
access.log = log/$pool.access.log
access.format = %R – %u %t “%m %r%Q%q” %s %f %{mili}d %{kilo}M %C%%
;request_terminate_timeout = 0
request_slowlog_timeout = 20
slowlog = log/$pool.log.slow
env[HOSTNAME] = $HOSTNAME
env[PATH] = /usr/local/bin:/usr/bin:/bin
env[TMP] = /tmp
env[TMPDIR] = /tmp
env[TEMP] = /tmp

#add your custom php.ini
php_admin_value[sendmail_path] = /usr/sbin/sendmail -t -i -f webmaster@site1.pnyet.web.id
php_admin_value[memory_limit] = 256M
php_admin_value[session.save_handler] = files
php_admin_value[session.save_path] = “/tmp”
php_admin_value[session.use_cookies] = 1
php_admin_value[session.name] = PHPSESSID

Don’t forget to restart php-fpm after change the configuration :)

reference: http://http://php-fpm.org/wiki

Actually this article was posted in here and I’ll repost this article because some times my old blog is unavailable. By the way, how important to setting or configure date and time in your linux machine?Date and time is very important in every operating system, because without time that configured properly it’s hard to read log files.

In other case, server doesn’t work properly without a valid time if in there running some services that required valid date and time (example, hourly access list, monitoring system, log server, internet portal). So what?

How to setting date and time on linux machine? Configure date and time on linux machine is very simple and easy, just one step like below:

# date -s ‘MM/DD/YYYY HH:MM:SS’ <– change with actual date and time eg: ‘08/18/2011 23:32:00′
# date -s 081823322011
# hwclock –utc –systohc

That’s all, and your date?

# date
Thu Aug 18 23:34:23 WIT 2011

Just few steps and safe your life :)

Tonight I have a plan to maintenance two servers in my office, but my laptop seems not good, sometimes desktop is freeze and can’t click anything, so I have to restart for several times. Ok, let’s change back from Unity to Gnome classic, and after changed to Gnome classic my desktop seems good. Something stupid make me broken, I’ve enable some effect in Compiz config manager and make some menus disappeared!. Where is “close, minimize, maximize” window menu?

Well, my plan has changed from maintenance servers to recovering my laptop, it’s so tiring me, because last time I got same problem my stupid solutions is replace my profile with a new profile finally I got my window menu back, but I’m missing my email settings, wine config, and other utilities setting :mrgreen: . Ok, I’m triying to restore the compiz setting to default but can’t solve the problem. So what happen with my window decoration? Hm…, window decoration, yeay “Window Decoration” in Compiz config may be related to this problem…

I’ve checked Window Decoration in compiz config and found that this menu was disabled, what I’m done? Ok, let’s try to enable Window Decoration like this (see picture):

After enabled Window Decoration in Compiz Config – Effects my desktop working smoothly :)

Thank you Sleppy…….

Beberapa hari lalu saya melakukan installasi MySQL Community Server (Open Source) menggunakan source di CentOS 5.5 x86_64bit dan akan digunakan sebagai backend dari MySQL Load Balancing. MySQL yang saya gunakan adalah versi 5.1.56 (Community) karena beberapa kali saya menggunakan MySQL versi 5.5.11 mengalami masalah kompatibiltas dengan beberapa aplikasi yang sudah running :mrgreen: .

Beberapa hal yang saya lakukan sebelum meng-compile dan menginstal MySQL adalah mempersiapkan mesin agar sesuai dengan kebutuhan, metode yang saya gunakan untuk installasi operating system adalah mode minimal dan setelah itu menentukan struktur direktori yang akan digunakan untuk penyimpanan data, rencananya data MySQL akan saya simpan di /home/mysql kemudian file instalasi sendiri akan saya taruh di /usr/local/mysql.  See below:

Install dependencies yang akan digunakan oleh MySQL maupun development tools:

# yum -y install gcc make automake glibc ncurses ncurses-devel

Kemudian download source MySQL dari http://mysql.com/downloads/mysql/5.1.html (pilih source code), ekstrak, compile dan install:

# wget ftp://ftp.jaist.ac.jp/pub/mysql/Downloads/MySQL-5.1/mysql-5.1.56.tar.gz
# tar -zxvf mysql-5.1.56.tar.gz
# cd mysql-5.1.56
# ./configure –prefix=/usr/local/mysql –datadir=/home/mysql –with-unix-socket-path=/usr/local/mysql/tmp/mysql.sock –localstatedir=/home/mysql/data
# make
# make install

Selanjutnya buat symbolik link dari /usr/local/mysql/bin ke /usr/bin/

# ln -s /usr/local/mysql/bin/* /usr/bin/

Next, copy file init MySQL agar dapat dilakukan start melalui /etc/init.d atau service dan ubah permissionnya supaya executable:

# cp /home/mysql/mysql/mysql.server /etc/init.d/mysql
# chmod +x /etc/init.d/mysql

Selanjutnya copy file konfigurasi mysql dan sesuaikan dengan kebutuhan, karena terdapat beberapa file konfigurasi untuk level yang berbeda-beda (small – medium – large), beberapa pilihannya adalah berikut:

my-huge.cnf
my-innodb-heavy-4G.cnf
my-large.cnf
my-medium.cnf
my-small.cnf

Untuk penjelasan detail mengenai file-file konfigurasi diatas dapat dibaca didalam file-file tersebut, saya sendiri menggunakan large :d

# cp /home/mysql/mysql/my-large.cnf /etc/my.cnf

Next, buat MySQL privileges yang didalamnya termasuk host, user,tables_priv, columns_priv, dan func tables dengan menjalankan script:

# /usr/local/mysql/bin/mysql_install_db

Sampai proses ini, intalasi MySQL dari source telah selesai dan MySQL server siap digunakan, jangan lupa start servicenya  dan buat agar service MySQL running di run level 3 5 :p

# chkconfig –level 35 mysql on
# /etc/init.d/mysql start

Dari command diatas akan terdapat notifikasi “Starting MySQL. SUCCESS!”, proses MySQL yang sedang berjalan juga dapat dilihat melalui:

# ps aux |grep mysql
root     19716  0.0  0.0  63816  1332 pts/0    S    13:45   0:00 /bin/sh /usr/local/mysql/bin/mysqld_safe –datadir=/home/mysql –pid-file=/home/mysql/srv15.varnion.com.pid
mysql    19804  0.0  0.1 310996  5044 pts/0    Sl   13:45   0:00 /usr/local/mysql/libexec/mysqld –basedir=/usr/local/mysql –datadir=/home/mysql –user=mysql –log-error=/home/mysql/srv15.varnion.com.err –pid-file=/home/mysql/srv15.varnion.com.pid –socket=/usr/local/mysql/tmp/mysql.sock –port=3306

Nah, sampai disini diharapkan tidak ada masalah dikemudian hari dari project mysql cluster load balancing dapat dilanjutkan..

Hope this useful :d

referensi: http://dev.mysql.com/doc/refman/5.1/en/source-installation.html

Sehubungan dengan ditambahkannya IPv6 di server saya, hal yang harus segera saya lakukan adalah dengan meng-enable IPv6 di webserver (NGINX) agar semua domain lebih cihui dengan menggunakan IPv6. Saat ini banyak organisasi telekomunikasi, teknologi informasi yang telah mengaplikasikan IPv6 untuk keperluan sehari-hari mereka, begitu juga dengan corporate tempat saya bekerja yang sedang melakukan improvisasi IPv6 kedalam infrastrukturnya.

NGINX merupakan alternatif web server dari apache yang sudah membumi, namun semenjak saya menggunakan nginx saya cukup terkesan dengan performa NGINX karena memang jauh lebih keren daripada apache, meski untuk urusan modul apache jauh lebih lengkap. NGINX sudah mendukup IPv6 namun secara default module ini harus disertakan pada saat melakukan compile package. Berikut ini adalah step by step bagaimana mengkonfigurasi NGINX dengan dukungan IPv6 dan juga virtualhost dengan menggunakan IPv6…

Langkah pertama adalah memastikan apakah NGINX yang diinstall sudah mendukung IPv6?

$ /usr/sbin/nginx -V
nginx version: nginx/0.8.54
built by gcc 4.1.2 20080704 (Red Hat 4.1.2-48)
TLS SNI support disabled
configure arguments: –prefix=/usr/local/nginx……….  –with-ipv6

Jika terdapat “–with-ipv6″ maka nginx telah mendukung IPv6 dan jika tidak ditemukan maka kita dapat melakukan compile ulang dengan menambahkan –with-ipv6 pada saat configure. Selanjutnya adalah mencoba melakukan setting virtualhost agar menggunakan ipv6, langkahnya adalah dengan mengedit konfigurasi virtualhost dengan menambahkan binding port agar listen ke ipv6.

$ sudo vi /usr/local/nginx/conf/vhost/default

server {
listen  80;
listen [::]:80 default ipv6only=on;
listen [::]:443 default ipv6only=on;
server_name _;

“default ipv6only=on” adalah agar port tesebut hanya listen pada ipv6 sehingga tidak bentrok dengan port 80 yang digunakan ipv4, jika default upv4only=on dihilangkan maka akan muncul pesan error seperti dibawah ini:

Starting nginx: [emerg]: bind() to [::]:80 failed (98: Address already in use)
[emerg]: bind() to 0.0.0.0:443 failed (98: Address already in use)
[emerg]: bind() to [::]:80 failed (98: Address already in use)
[emerg]: bind() to 0.0.0.0:443 failed (98: Address already in use)
[emerg]: bind() to [::]:80 failed (98: Address already in use)
[emerg]: bind() to 0.0.0.0:443 failed (98: Address already in use)

Oke, next adalah konfigurasi virtualhost untuk spesifik domain agar listen ke ipv6 dan konfigurasinya seperti dibawah ini:

server {
listen      blog.pnyet.web.id:80;
listen [2406:2400:dc7f::d4e7:130]:80;
server_name  blog.pnyet.web.id;

server {
listen      blog.pnyet.web.id:443;
listen [2406:2400:dc7f::d4e7:130]:443;
server_name  blog.pnyet.web.id;

Simpan konfigurasi tersebut diatas dan lihat apakah binding http port dan https port sudah listen ke IPv6, jika sudah maka hasilnya akan seperti ini:

tcp        0      0 0.0.0.0:80                  0.0.0.0:*                   LISTEN      32580/nginx.conf
tcp        0      0 0.0.0.0:443                 0.0.0.0:*                   LISTEN      32580/nginx.conf
tcp        0      0 :::80                       :::*                        LISTEN      32580/nginx.conf
tcp        0      0 :::443                      :::*                        LISTEN      32580/nginx.conf

Nah, dari tulisan ini saya harapkan agar IPv6 lebih dikenali dan diminati karena semakin menipisnya Ipv4 seperti ozon dibumi :p