No announcement yet.

Fedora 12 Apache and SQLite problems

  • Filter
  • Time
  • Show
Clear All
new posts

  • Fedora 12 Apache and SQLite problems

    I had a few problems running PTS 2.2 and 2.4 alpha 3 (those were the versions I tried) on Fedora 12, but I managed to solve them. If anybody else has the same problem this could be usefull.

    After a fresh install of fedora 12 on a somewhat old computer I wanted to test its performance so I installed PTS 2.2 via the included "install-sh" file. When it came to the apache benchmark it threw a few errors:

    - pts run as regular user, apache error (13) something about make_sock failed;
    - pts run as root, apache error (98) something about the pid file;

    After a lot of poking around I finally discovered the error. Apache was not listening on the correct port. Somehow the patch file included in pts that was supposed to change the listening port on httpd_/conf/httpd.conf to 8088 was not being applied, so the pts' apache server was trying to listen on port 80 that was already in use. The way to solve this is to manually edit the file ~/.phoronix-test-suite/installed-tests/apache/httpd_/conf/httpd.conf and change Listen 80 to Listen 8088.

    Another problem surfaced when trying to run the SQLite test. It always returned 0,00 seconds but no error was reported. I then discovered that the test was not successfully installed but no error was thrown at install time. In fact PTS reported SQLite as successfully installed although it wasn't. First I had to install some tcl devel packages that were not installed on my system. Until I did this PTS did throw an error when trying to install the SQLite test. After this dependency was taken care of I thought everything was fine, but the test always returned 0,00 seconds as I've said in the beggining. It turns out that in order to properly install the SQLite test the installer needs to add some files to /usr/share/tcl8.5/sqlite3/ which obviously can only be done by root. Solution is simples, run "phoronix-test-suite install sqlite" with "sudo".

    I may have done something wrong since no one else complained about these problems, but if I did, someone else might do the same and I hope my little experience in this helps.