My systems administrator is trying to set up our Apache server from scratch, and he has run into difficulties as outlined below. Can anyone give him a hand with some troublshooting? I am also going to give him instructions for getting onto the koha support irc channel, so he may be going online to seek further assistance that way. His name is Stan Blum and his email address is sblum@calacademy.org. Larry Currie I did all the setup stuff for apache, but can't get it to start. I'm trying to run it on the second network card, which is 198.31.79.74 and has the name informatics.calacademy.org. There should be no other applications using this address. The apache error_log gives the following : getpeername: Socket operation on non-socket getsockname: Socket operation on non-socket Error getting local address I think this might mean that the second card is not "registered" in the appropriate configuration file for the operating system (it hasn't been used before). However, it does appear to be functioning because I can ping the IP address successfully from another machine (although I haven't yet tried unplugging the network cable and seeing if that disables ping-ability -- something I should probably test to ensure this ping response is from the right source.) When I run netstat -tnlc, I don't get any listings for the 198.31.79.74 IP address; just ...73 and the localhost. I'm not sure that's the right thing to check, but I thought I'd try it. BTW, no one will be able to see ...74 from the outside, or ping anything else, because of the firewall. If you could pass this info on to someone with redhat - apache experience, I think we could sort it out pretty quickly -- or at least get to the next step, the apache configuration file, which confuses me because it has separate entries for Listen (IP address:port) BindAddress, and Port I'm also not sure about the inetd versus standalone setting and the owner and group settings. -Stan
Hi All, I tinkered with getting Koha (1.0/1.1) working on NT/2000 using IIS (instead of Apache) but using downloadable versions of Perl and MySQL for NT. I was making progress on the challenges of moving the html files to IIS from Apache style - major issues were: 1. Root relative referencing is different (ie what having a slash /url means) on NT/IIS it would be preferable to have it all (including OPAC) structured a little differently 2. Because the html's have insert statements, we either need to change the extensions to .htms and do some messing with IIS config to using the .include .DLL parser (fairly simple, but if missed nothing works). PERL & MySQL seemed to work fine, but I was hampered by some of the "bugginess" in 1.1 of Koha and a total lack of info on the database and how to populate it. I managed to get an ODBC connection going from NT to the MySQL database which meant I could use familiar Database tools to access the database but still no real clue how to populate. So, the project somewhat stopped. I'd like to have a go again now that I see a new version of Koha is out - and I understand it has a better install script and sample database? Some advise from folks on how smoothly new versions of Koha are running on Linux (and what versions please). Best Regards Andrew Hooper -----Original Message----- From: koha-admin@lists.katipo.co.nz [mailto:koha-admin@lists.katipo.co.nz] On Behalf Of Larry Currie Sent: Friday, 9 August 2002 3:43 a.m. To: koha@lists.katipo.co.nz Cc: Stan Blum Subject: [Koha] Koha status My systems administrator is trying to set up our Apache server from scratch, and he has run into difficulties as outlined below. Can anyone give him a hand with some troublshooting? I am also going to give him instructions for getting onto the koha support irc channel, so he may be going online to seek further assistance that way. His name is Stan Blum and his email address is sblum@calacademy.org. Larry Currie I did all the setup stuff for apache, but can't get it to start. I'm trying to run it on the second network card, which is 198.31.79.74 and has the name informatics.calacademy.org. There should be no other applications using this address. The apache error_log gives the following : getpeername: Socket operation on non-socket getsockname: Socket operation on non-socket Error getting local address I think this might mean that the second card is not "registered" in the appropriate configuration file for the operating system (it hasn't been used before). However, it does appear to be functioning because I can ping the IP address successfully from another machine (although I haven't yet tried unplugging the network cable and seeing if that disables ping-ability -- something I should probably test to ensure this ping response is from the right source.) When I run netstat -tnlc, I don't get any listings for the 198.31.79.74 IP address; just ...73 and the localhost. I'm not sure that's the right thing to check, but I thought I'd try it. BTW, no one will be able to see ...74 from the outside, or ping anything else, because of the firewall. If you could pass this info on to someone with redhat - apache experience, I think we could sort it out pretty quickly -- or at least get to the next step, the apache configuration file, which confuses me because it has separate entries for Listen (IP address:port) BindAddress, and Port I'm also not sure about the inetd versus standalone setting and the owner and group settings. -Stan _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
participants (2)
-
Andrew Hooper -
Larry Currie