The only things I can think of are: that the server that koha runs on may have to be on a privileged port (<1024) I doubt that this is the case. It is the easiest to test, though. Maybe trying to run koha on port 880? that there is something listening on on port 198 (what?) " netstat | grep 198 " might give an answer, but it doesn't say why Koha is trying to bind to port98. port 198 could be hard coded somewhere? " grep -d recurse 198 /etc/* " might give a pointer. I don't understand why apache is trying to use port 198. Is There something unusual in /etc/apache/httpd.conf ? Micheas On Fri, 2002-07-19 at 09:07, Larry Currie wrote:
Good morning. I have been trying to get version 1.2.1 of Koha up and working, but I'm having trouble getting the Apache server to run successfully. In particular, I keep getting a critical "error (13) permission denied: make_sock: could not bind to port 198" when I attempt to follow a borrower card number link from the URL http://198.31.79.73:8081/cgi-bin/koha/member.pl after performing a member search or when I go to look at the details of an item record. Would someone with expertise in this area be able to join me on the #koha-support channel sometime today or tomorrow to help me get to the bottom of this problem? I'm on Pacific Coast Standard time. Micheas on the list suggested that I execute these two commands to begin to see what is happening:
$ netstat | grep ESTABLISHED tcp 0 20 bcsl:ssh user-73-89.calacad:2060 ESTABLISHED tcp 0 0 localhost:34622 localhost:34623 ESTABLISHED tcp 0 0 localhost:34623 localhost:34622 ESTABLISHED
uname -a Linux bcsl 2.4.2-2smp #1 SMP Sun Apr 8 20:21:34 EDT 2001 i686 unknown
Larry Currie -- Lawrence W. Currie User Services Librarian California Academy of Sciences Golden Gate Park San Francisco, CA 94118 lcurrie@calacademy.org (415) 750-7108 (415) 750-7106 fax http://www.calacademy.org/research/library/
_______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha