Skip to main content

[OpenWRT] Apache Not Running

Bagi anda pengguna Apache pada OpenWRT mungkin pernah mengalami masalah ini, ketika sukses menginstall Apache tidak ada error apapun, begitu juga ketika menjalankan service apachectl start tidak memunculkan error, namun halaman index.html tidak dapat diakses dari web browser. Konfigurasi Apache pada openWRT bisa anda simak lengkap disini [..]. Jika anda mengalami masalah yang sama dengan saya, coba lihat log pada /var/log/error_log
cat /var/log/error_log
[Sat Dec 07 06:45:52 2013] [info] server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers), spawning 8 children, there are 1 idle, and 1 total children
[Sat Dec 07 06:45:52 2013] [notice] child pid 5268 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5272 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5273 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5274 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5275 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5276 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5277 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5278 exit signal Segmentation fault (11)
[Sat Dec 07 06:45:53 2013] [notice] child pid 5279 exit signal Segmentation fault (11)
Jika anda mengalami log yang sama, maka benar adanya sebuah bug pada Apache. Apache yang saya gunakan adalah versi 2.2.15.

Solusi
Bug ini sudah dianggap fixed [lihat disini], caranya cukup mudah, buka file httpd.conf anda pada folder /etc/apache.
vi /etc/apache/httpd.conf
Cari line yang berisi LogLevel debug, diganti dengan LogLevel notice. Semoga hal ini bisa memperbaiki bug yang ada. Setelah itu silahkan coba cek pada browser anda http://[ip address]:[port]

Good Luck

Comments

Popular posts from this blog

HackRF Mayhem Failed to Update - M0 Guru Meditation Hard

I was on Mayhem Portapack v2.0.1 and want to upgrade to the latest stable release v2.1.0. The update went okay using the web upgrade https://hackrf.app/. But then I saw the latest nightly update and want to try it, since it has many new tools that are not yet included in the stable release. But then the update failed :( Disclaimer: I didn't take any photos of the errors, since I was focused on googling the solution. So the error was " Bad Firmware or Failed W/R error" during the upgrade process, and it was stuck. So I had to restart the device, and it was booting to the Mayhem menu, but on the bottom left, which should show the current firmware version, it was showing a  "FLASH ERR"  message. I think I should go back to the stable release, but I can't. Every time I want to flash the stable release version, the portapack will shows an error M0 Guru Meditation - Hard Fault.  There's an issue that was closed on the Mayhem GIT repo that has the same issue a...

Macintosh Classic II Brightness Issue

The Problem My Macintosh Classic II suffers from an issue where the display CRT goes dim after a few minutes on a cold boot. Every time it happens, I need to crank up the cut-off and brightness  pot behind the machine to show the image. The Analyze At first, I thought it must be the brightness issue, so I searched for the Macintosh Classic analog board schematic to check the brightness line. I found the schematic from Bomarc, and the schematic is suitable with my board, since there are two analog board versions.  I started to suspect the resistors and potentiometer on the brightness line. This Macintosh version has software-controlled brightness, so the analog board will get a 22.25 kHz square wave PBM signal from the logic board to control the brightness. I checked and replaced some resistors and cleaned the potentiometer, but nothing seems to work. The signal is there, and no sign of degradation that makes the screen dim after a few minutes.  Brightness Line So I suspec...

Fiberhome HG6145D2 Superadmin Login

Maybe some of you are using In**ehome ISP as your home internet and found out that using the provided login has minimal options to configure the router: user  user1234 I know it’s not the admin login, and that must be a full-control user account that can be used to control this router fully. So I searched and found some posts on the net and most of them are telling me to use: admin %0|F?H@f!berhO3e I tested it and it doesn’t work! But there’s more to it, you need to reset the router first by pressing the reset button on the side of the router. Then after resetting, you can log in using the admin superaccount! But keep in mind, never use the user log in again, because it will lock the super admin login until you reset the router again. Cheers 🍺