Daily logs » Web Server http://blog.pnyet.web.id A Nobody trying to become a Somebody Wed, 25 Jan 2012 15:26:10 +0000 en hourly 1 http://wordpress.org/?v=3.3.1 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (/tmp) http://blog.pnyet.web.id/2011/12/04/php-warning-unknown-failed-write-session-data-files-verify-current-setting-session-save_path-correct-tmp.html http://blog.pnyet.web.id/2011/12/04/php-warning-unknown-failed-write-session-data-files-verify-current-setting-session-save_path-correct-tmp.html#comments Sun, 04 Dec 2011 02:21:50 +0000 David http://blog.pnyet.web.id/?p=731

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

]]> http://blog.pnyet.web.id/2011/12/04/php-warning-unknown-failed-write-session-data-files-verify-current-setting-session-save_path-correct-tmp.html/feed 0 nginx-1.0.0 stable version has been released http://blog.pnyet.web.id/2011/04/19/nginx-stable-version-has-bee-released.html http://blog.pnyet.web.id/2011/04/19/nginx-stable-version-has-bee-released.html#comments Mon, 18 Apr 2011 18:46:42 +0000 David http://blog.pnyet.web.id/?p=590

NGINX adalah aplikasi open source  web server, reverse proxy  dan e-mail (IMAP/POP3) proxy yang dirilis dibawah lisensi BSD. Proyek NGINX dijalankan sekitar 9 tahun yang lalu (2008) dengan rilis pertamanya versi 0.1.0. Saya belum lama ini telah memindahkan beberapa web server berbasis apache ke nginx dan telah menjalankan nginx sebagai reverse proxy untuk web service beberapa bulan terakhir. Saya cukup terkesan dengan performa yang ditawarkan oleh NGINX, sangat terasa bedanya dengan aplikasi web server lainnya.

Sesuai dengan judul artikel “nginx-1.0.0 stable version has been released” maka saya hanya akan memberikan informasi seputar NGINX terbaru yaitu nginx versi 1.0.0 yang dirilis pada 12 April 2011. Dibawah ini adalah change log nginx 1.0.0 dan sebelumnya:

Changes with nginx 1.0.0                                         12 Apr 2011

*) Bugfix: a cache manager might hog CPU after reload.
Thanks to Maxim Dounin.

*) Bugfix: an “image_filter crop” directive worked incorrectly coupled
with an “image_filter rotate 180″ directive.

*) Bugfix: a “satisfy any” directive disabled custom 401 error page.

Changes with nginx 0.9.7                                         04 Apr 2011

*) Feature: now keepalive connections may be closed premature, if there
are no free worker connections.
Thanks to Maxim Dounin.

*) Feature: the “rotate” parameter of the “image_filter” directive.
Thanks to Adam Bocim.

*) Bugfix: a case when a backend in “fastcgi_pass”, “scgi_pass”, or
“uwsgi_pass” directives is given by expression and refers to a
defined upstream.

Changes with nginx 0.9.6                                         21 Mar 2011

*) Feature: the “map” directive supports regular expressions as value
of the first parameter.

*) Feature: $time_iso8601 access_log variable.
Thanks to Michael Lustfield.

Oke, untuk informasi changelog selengkapnya Anda dapat mengunjungi http://nginx.org/en/CHANGES lalu untuk mendapatkan source code terbarunya dapat didownload melalui: http://nginx.org/download/nginx-1.0.0.tar.gz bisa juga update melalui svn: svn.nginx.org.

Review?

Silahkan install dan review sendiri :p

 

]]> http://blog.pnyet.web.id/2011/04/19/nginx-stable-version-has-bee-released.html/feed 0 Konfigurasi IPv6 di NGINX http://blog.pnyet.web.id/2011/02/27/konfigurasi-ipv6-di-nginx.html http://blog.pnyet.web.id/2011/02/27/konfigurasi-ipv6-di-nginx.html#comments Sat, 26 Feb 2011 20:32:18 +0000 David http://blog.pnyet.web.id/?p=551

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

]]> http://blog.pnyet.web.id/2011/02/27/konfigurasi-ipv6-di-nginx.html/feed 4 Migrating Web Server From Apache To Nginx http://blog.pnyet.web.id/2011/01/17/migrating-web-server-apache-nginx.html http://blog.pnyet.web.id/2011/01/17/migrating-web-server-apache-nginx.html#comments Sun, 16 Jan 2011 19:10:44 +0000 David http://blog.pnyet.web.id/?p=524

Since two years ago (2007) this blog is hosted by Apache web server, and today I changed out the sofware in web server. I never had a “serious” problem with apache but I heard if nginx is a lightweight, high-performance HTTP server and reverse proxy. Nginx pronounced of engine-x also can handle static HTML, and does very well with dynamic (PHP) content as well. But nginx isn’t ideal for every server, nginx can’t handle SVN or WebDav, I’m still using apache for some situation :D.

Nginx is very impressive for simple virtualhost and standalone web server configuration, migrating wordpress from apache to nginx isn’t difficult. After installing nginx and setting up the virtualhost for my domain (blog.pnyet.web.id) I just copying my old files into home directory of my website and then change the permission also import mysql databases. Voila…, my blog is running well in nginx. But actually nginx isn’t support .htaccess or .htpasswd so I’ve reconfigure url rewriting for this website. Below is my virtualhost for this blog:

server {
listen      blog.pnyet.web.id:80;
server_name  blog.pnyet.web.id;

#charset koi8-r;

access_log  logs/blogp.access.log  main;
error_log   logs/blogp.error.log  debug;

location / {
root   /home/myweb01/public_html;
index  index.php index.html index.htm;
try_files $uri $uri/ /index.php?q=$uri&$args;
}

error_page  404              /404.html;
error_page   500 502 503 504  /50x.html;
location = /50x.html {
root   html;
}

location ~ \.php$ {
root           /home/myweb01/public_html;
fastcgi_pass   127.0.0.1:9000;
fastcgi_index  index.php;
fastcgi_param  SCRIPT_FILENAME  /home/myweb01/public_html;$fastcgi_script_name;
include        conf.d/fastcgi_params;
}

location ~ /\.ht {
deny  all;
}
}

server {
listen       blog.pnyet.web.id:443;
server_name  blog.pnyet.web.id;

access_log  logs/blogp_ssl.access.log  main;
error_log   logs/blogp_ssl.error.log  debug;

ssl                  off;
ssl_certificate      ssl/2011.crt;
ssl_certificate_key  ssl/2011.key;
ssl_session_timeout  5m;
ssl_protocols  SSLv2 SSLv3 TLSv1;
ssl_ciphers  ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP;
ssl_prefer_server_ciphers   on;

location / {
root   /home/myweb01/public_html;
index  index.php index.html index.htm;
try_files $uri $uri/ /index.php?q=$uri&$args;
}

error_page  404              /404.html;
error_page   500 502 503 504  /50x.html;
location = /50x.html {
root   html;
}

location ~ \.php$ {
root           /home/myweb01/public_html;
fastcgi_pass   127.0.0.1:9000;
fastcgi_index  index.php;
fastcgi_param  SCRIPT_FILENAME   /home/myweb01/public_html$fastcgi_script_name;
include        conf.d/fastcgi_params;
}
}

To enable url rewriting in nginx for wordpress i just add “try_files $uri $uri/ /index.php?q=$uri&$args;” and my permalinks working without any problem.

Cheers…

]]> http://blog.pnyet.web.id/2011/01/17/migrating-web-server-apache-nginx.html/feed 0 pcfg_openfile: unable to check htaccess file, ensure it is readable http://blog.pnyet.web.id/2010/05/08/pcfg-openfile-unable-to-check-htaccess-file-ensure-it-is-readable.html http://blog.pnyet.web.id/2010/05/08/pcfg-openfile-unable-to-check-htaccess-file-ensure-it-is-readable.html#comments Sat, 08 May 2010 07:20:10 +0000 David http://blog.pnyet.web.id/?p=293

Sehari lalu saya memindahkan web server ke mesin yang lebih baik, processor double core dan ram serta harddisk yang lebih besar (sedikit). Setelah migrasi, saya tidak menggunakan konfigurasi web server sebelumnya, namun memang ada perubahan yang cukup signifikan dari web server tersebut dan salah satunya adalah user group. Jika di server sebelumnya, semua file website dimiliki oleh apache selaku owner service http di apache web server. Namun konfigurasi di server baru saya ingin membuat agar kepemilikan root directory virtual host tetap atas nama user. Setelah setup apache dan virtual host selesai, saya bingung sekali, mata udah ngantuk kepala agak pusing, mungkin perlu istirahat? Sebelum tidur saya menemukan error seperti dibawah ini, dan itu membuat saya tidak bisa tidur, oprek sana oprek sini ternyata tidak membuahkan hasil, karena anehnya masalah ini tidak terjadi pada website lainnya :(

[Sat May 08 12:14:09 2010] [crit] [client 118.97.186.242] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:14:11 2010] [crit] [client 118.97.186.242] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:19:48 2010] [crit] [client 202.47.75.2] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:19:52 2010] [crit] [client 202.47.75.2] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:21:23 2010] [crit] [client 202.47.75.2] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:22:59 2010] [crit] [client 66.249.69.245] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:24:21 2010] [crit] [client 202.47.75.2] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:28:54 2010] [crit] [client 125.161.196.15] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:28:56 2010] [crit] [client 125.161.196.15] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:28:58 2010] [crit] [client 125.161.196.15] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:29:01 2010] [crit] [client 125.161.196.15] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:33:24 2010] [crit] [client 110.138.22.31] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.google.co.id/url?sa=t&source=web&ct=res&cd=1&ved=0CC0QFjAA&url=http%3A%2F%2Fblog.pnyet.web.id%2F2010%2F02%2F24%2Fapache-error-500.html&rct=j&q=error+500+di+web&ei=LfLkS-7wKMexrAexuOHYAg&usg=AFQjCNEpsTFYWgnbhKVkCvq4c-3PeDMjwg
[Sat May 08 12:33:27 2010] [crit] [client 110.138.22.31] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:48:06 2010] [crit] [client 110.138.22.31] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable, referer: http://www.google.co.id/url?sa=t&source=web&ct=res&cd=1&ved=0CC0QFjAA&url=http%3A%2F%2Fblog.pnyet.web.id%2F2010%2F02%2F24%2Fapache-error-500.html&rct=j&q=error+500+di+web&ei=LfLkS-7wKMexrAexuOHYAg&usg=AFQjCNEpsTFYWgnbhKVkCvq4c-3PeDMjwg
[Sat May 08 12:53:33 2010] [crit] [client 66.249.69.245] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:53:34 2010] [crit] [client 66.249.69.245] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:56:51 2010] [crit] [client 66.249.69.245] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable
[Sat May 08 12:57:33 2010] [crit] [client 66.249.69.245] (13)Permission denied: /home/ngaknguk/public_html/.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable

Akhirnya usut punya usut si user belum saya masukan ke groupnya apache…., duh malu-maluin :((

Setelah saya jalankan:

# usermod -G ngaknguk,apache,ftp ngaknguk

# id ngaknguk

uid=501(ngaknguk) gid=48(apache) groups=48(apache),50(ftp),501(ngaknguk)

Setelah itu, blog bisa kembali online, cheers…

]]> http://blog.pnyet.web.id/2010/05/08/pcfg-openfile-unable-to-check-htaccess-file-ensure-it-is-readable.html/feed 1