I've tried everything with Apache2 on Deb and I can't figure out how to get koha to load. koha-httpd and apache2.conf enclosed. http://www.nabble.com/file/p12065240/apache2.conf apache2.conf http://www.nabble.com/file/p12065240/koha-httpd.conf koha-httpd.conf I've tried everything I can think of. Apache refuses to do anything with 8080 or 8000 Matt -- View this message in context: http://www.nabble.com/Apache2-Fu-tf4240211.html#a12065240 Sent from the Koha - Discuss mailing list archive at Nabble.com.
exaurdon <mstockfleth@hotmail.com> wrote:
http://www.nabble.com/file/p12065240/apache2.conf apache2.conf http://www.nabble.com/file/p12065240/koha-httpd.conf koha-httpd.conf
I've tried everything I can think of. Apache refuses to do anything with 8080 or 8000
Explain "refuses to do anything with" please. Does netstat -pn --listen --tcp | grep apache # show apache listening on those ports? If not, did you try /etc/init.d/apache2 force-reload # ? Is dragonetworks.net a NameVirtualHost? Your VirtualHost bits should use the IP address if possible: using the fully qualified domain name for the IP address of the virtual host is explicitly not recommended in http://httpd.apache.org/docs/2.2/mod/core.html#virtualhost Hope that helps, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
I changed it to wyrm:80, 8000, 8080, etc. However now I get 404's on everything, but apache is listening to the ports. It is possible that editing the files on 2 machines has caused some line feeds, but not sure how to fix that off hand. http://www.nabble.com/file/p12069607/koha-httpd.conf koha-httpd.conf -- View this message in context: http://www.nabble.com/Apache2-Fu-tf4240211.html#a12069607 Sent from the Koha - Discuss mailing list archive at Nabble.com.
I tried dos2unix...that's not it. No clue why even 80 is giving me 404 now. exaurdon wrote:
I changed it to wyrm:80, 8000, 8080, etc. However now I get 404's on everything, but apache is listening to the ports.
It is possible that editing the files on 2 machines has caused some line feeds, but not sure how to fix that off hand.
http://www.nabble.com/file/p12069607/koha-httpd.conf koha-httpd.conf -- View this message in context: http://www.nabble.com/Apache2-Fu-tf4240211.html#a12079040 Sent from the Koha - Discuss mailing list archive at Nabble.com.
exaurdon <mstockfleth@hotmail.com> wrote:
I tried dos2unix...that's not it. No clue why even 80 is giving me 404 now.
You may find some clues in your system /var/log/apache2/error.log or your koha opac-error_log file, like "some/thing: file not found" Hope that helps, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
what I did was added back the include /etc/apache2/sites-enabled and inclue /etc/koha-httpd.conf which then when I put in dragonetworks.net:8080 or 8000 sends me to apache-default (It Works!...no, actually it doesn't. Foul Apache trickery!) MJ Ray-2 wrote:
exaurdon <mstockfleth@hotmail.com> wrote:
I tried dos2unix...that's not it. No clue why even 80 is giving me 404 now.
You may find some clues in your system /var/log/apache2/error.log or your koha opac-error_log file, like "some/thing: file not found"
Hope that helps, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/ _______________________________________________ Koha mailing list Koha@lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha
-- View this message in context: http://www.nabble.com/Apache2-Fu-tf4240211.html#a12079433 Sent from the Koha - Discuss mailing list archive at Nabble.com.
exaurdon <mstockfleth@hotmail.com> wrote:
what I did was added back the include /etc/apache2/sites-enabled and inclue /etc/koha-httpd.conf which then when I put in dragonetworks.net:8080 or 8000 sends me to apache-default (It Works!...no, actually it doesn't. Foul Apache trickery!)
It sounds like apache is using the settings that are in /etc/apache2/sites-availabled/default from the debian package. This may be because the last koha-httpd.conf that I saw had something like ServerName wyrm:8080, not ServerName dragonetworks.net:8080 (or ServerAlias of that). Either way, it sounds like a general apache configuration problem, not a Koha problem, so you might find the Apache Virtual Hosting guide at http://httpd.apache.org/docs/2.0/vhosts/name-based.html useful, or you could try asking in an Apache forum. My current usual solution is to symlink koha-httpd.conf from /etc/apache2/sites-enabled/ and not add any Include to the default file. Sooner or later there will be a debian package. Some of the building continues at http://serene.ttllp.co.uk/~mjr/ Hope that helps, -- MJ Ray - see/vidu http://mjr.towers.org.uk/email.html Experienced webmaster-developers for hire http://www.ttllp.co.uk/ Also: statistician, sysadmin, online shop builder, workers co-op. Writing on koha, debian, sat TV, Kewstoke http://mjr.towers.org.uk/
participants (2)
-
exaurdon -
MJ Ray