Installed new server can no longer access KOHA.
I have installed a new server with Ubuntu 14.04. Though I did the install of KOHA correctly. But now when I internet to the server I get the apache page and not the KOHA pages. Do need so help, but do not even know what to begin to ask the right questions. Thanks to those that respond. Jack Boulier LRC Director MTI College Sacramento, CA (916) 339.4370 Direct (916) 339.1500 ext. 270 (916) 339.0305 Fax
Boulier, Jack wrote:
I have installed a new server with Ubuntu 14.04. Though I did the install of KOHA correctly. But now when I internet to the server I get the apache page and not the KOHA pages. Do need so help, but do not even know what to begin to ask the right questions.
There is probably some other apache site configured with a higher priority than Koha. This is a choice you or Ubuntu made with your Apache configuration. It is not really a Koha problem, but http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.ubuntu;hb=... says 415 Disable Default Site 416 ================================================================= 417 418 These short instructions assume that the default site is 419 not needed. Talk with your system administrator, network 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING 421 the following command: 422 sudo a2dissite 000-default Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
MJ Ray schreef op wo 20-05-2015 om 12:11 [+0100]:
418 These short instructions assume that the default site is 419 not needed. Talk with your system administrator, network 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING 421 the following command: 422 sudo a2dissite 000-default
This is not really good advice (though at least it has caveats), except in the case of doing IP-based addressing. If you're doing virtual host-based addressing (which is normal), and you get the default "It works!" page, then you need to fix your configuration[0]. If removing the default site makes things work, then you're papering over a real issue and it's quite likely that relying on this will break when something changes in the future. So, don't disable the default site just to make Koha work: fix your apache configuration for Koha instead. And stop telling people to disable the default site to make it work. It's bad practice[1]. http://i.imgur.com/V3hUcpX.png Footnotes: [0] In particular, you don't have a ServerName or ServerAlias parameter that matches the hostname that you're trying to use specified in /etc/apache2/sites-enabled/library.conf [1] Unless you're doing IP-based addressing, but you should only do that if you really have no other choice as expecting people to memorise IP addresses sucks. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
Robin Sheat wrote:
MJ Ray schreef op wo 20-05-2015 om 12:11 [+0100]:
No, I didn't.
418 These short instructions assume that the default site is 419 not needed. Talk with your system administrator, network 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING 421 the following command: 422 sudo a2dissite 000-default
This is not really good advice (though at least it has caveats), except in the case of doing IP-based addressing.
Well, you know how to get INSTALL.ubuntu changed as well as I do. I'd replace that with a pointer to http://httpd.apache.org/docs/current/vhosts/ but someone thought it made sense for Ubuntu and I don't use Ubuntu much so I quoted it.
So you've got time to post snarky pictures but not patch the file? :-( Regards, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/
Hi Everyone, " And stop telling people to disable the default site to make it work. It's bad practice" Might I recommend that someone with experience in this area take a look at submitting an edit at http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages to include both Robin's concerns about disabling the default site, and expanding on the alternate way of solving the default "It Works!" page issue? I had no idea this issue could be fixed in the way suggested below. I rely on this Wiki page to get me through the installation process when I'm tinkering, as I'm sure may others do too. I think what's perhaps come out of this thread is that this Wiki install guide needs some attention by an expert. ;D FWIW. Best to all, Craig Butosi, MA, MLIS, B Mus (Hons.) LIBRARY SERVICES MANAGER THE ROYAL CONSERVATORY TELUS Centre for Performance and Learning 273 Bloor Street West Toronto, ON M5S 1W2 416.408.2824 x338 www.rcmusic.ca -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Robin Sheat Sent: May-20-15 7:00 PM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Installed new server can no longer access KOHA. MJ Ray schreef op wo 20-05-2015 om 12:11 [+0100]:
418 These short instructions assume that the default site is 419 not needed. Talk with your system administrator, network 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING 421 the following command: 422 sudo a2dissite 000-default
This is not really good advice (though at least it has caveats), except in the case of doing IP-based addressing. If you're doing virtual host-based addressing (which is normal), and you get the default "It works!" page, then you need to fix your configuration[0]. If removing the default site makes things work, then you're papering over a real issue and it's quite likely that relying on this will break when something changes in the future. So, don't disable the default site just to make Koha work: fix your apache configuration for Koha instead. And stop telling people to disable the default site to make it work. It's bad practice[1]. http://i.imgur.com/V3hUcpX.png Footnotes: [0] In particular, you don't have a ServerName or ServerAlias parameter that matches the hostname that you're trying to use specified in /etc/apache2/sites-enabled/library.conf [1] Unless you're doing IP-based addressing, but you should only do that if you really have no other choice as expecting people to memorise IP addresses sucks. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF Note: This email message and any attachments are intended only for the use of the individual to which it is addressed, and may contain information that is privileged, confidential and exempt from disclosure under applicable law. If the recipient of this email is not the intended recipient (or the employee or agent responsible for delivering the email to the intended recipient), you are hereby notified that any review, dissemination, distribution or copying or other use of this message is strictly prohibited. If you have received this communication in error, please notify the sender immediately by return email and delete this message and attachments from your system, thank you.
Craig Butosi schreef op vr 22-05-2015 om 18:43 [+0000]:
Might I recommend that someone with experience in this area take a look at submitting an edit at http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages to include both Robin's concerns about disabling the default site, and expanding on the alternate way of solving the default "It Works!" page issue? I had no idea this issue could be fixed in the way suggested below. I rely on this Wiki page to get me through the installation process when I'm tinkering, as I'm sure may others do too.
I think what's perhaps come out of this thread is that this Wiki install guide needs some attention by an expert. ;D
I tend to focus on these instructions: http://wiki.koha-community.org/wiki/Koha_on_Debian because I wrote them :) In theory, if you follow them correctly, things will work, however they are mostly written as a high-level guide for people who have a fair idea about how Linux works in the first place to avoid cluttering them up with things that aren't particularly Koha related. In this specific case, the vhost link that MJ Ray linked to is really the appropriate reference for learning how to fix it properly. Perhaps time I added a "common problems you might encounter and how to fix them" section. -- Robin Sheat Catalyst IT Ltd. ✆ +64 4 803 2204 GPG: 5FA7 4B49 1E4D CAA4 4C38 8505 77F5 B724 F871 3BDF
Greetings, This is why I much prefer looking at the Wiki, because the warning is more ominous and fear inducing. "Disable Default Site If you are running Drupal or any other web service on the same machine, do not disable the default site! If you are unsure, do not disable the default site! When in doubt, always talk with your system administrator, network administrator, or IT Department. The following is intentionally not boxed to prevent problems arising from improperly disabling the default site. If and only if Koha is the only thing on this server, then feel free to run this to disable the default site: sudo a2dissite 000-default" Additionally, given people's laziness leading to just cut and past the boxes in, this command is generally overlooked. This is written for the librarian with no linux experience trying an Ubuntu install. The problem is the Ubuntu pages give a little more detail than the Debian in terms of intermediate steps, but approach it from the "Oh shoot, this person knows nothing about networking or apache configuration". The Debian pages assume a higher level of networking and apache configuration understanding than that, last I checked. As for the INSTALL file, that update was way better than the previous version. :P GPML, Mark Tompsett -----Original Message----- From: MJ Ray Sent: Wednesday, May 20, 2015 7:11 AM To: koha@lists.katipo.co.nz Subject: Re: [Koha] Installed new server can no longer access KOHA. Boulier, Jack wrote:
I have installed a new server with Ubuntu 14.04. Though I did the install of KOHA correctly. But now when I internet to the server I get the apache page and not the KOHA pages. Do need so help, but do not even know what to begin to ask the right questions.
There is probably some other apache site configured with a higher priority than Koha. This is a choice you or Ubuntu made with your Apache configuration. It is not really a Koha problem, but http://git.koha-community.org/gitweb/?p=koha.git;a=blob;f=INSTALL.ubuntu;hb=... says 415 Disable Default Site 416 ================================================================= 417 418 These short instructions assume that the default site is 419 not needed. Talk with your system administrator, network 420 administrator, or IT Department to CONFIRM THIS BEFORE RUNNING 421 the following command: 422 sudo a2dissite 000-default Hope that informs, -- MJ Ray (slef), member of www.software.coop, a for-more-than-profit co-op http://koha-community.org supporter, web and library systems developer. In My Opinion Only: see http://mjr.towers.org.uk/email.html Available for hire (including development) at http://www.software.coop/ _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha
A couple of ideas: Is /etc/koha/koha-sites.conf pointing to the right OPACPORT? It should be 80. What's up with /etc/apache2/sites-available/000-default.conf? If you're only running Koha, you can disable it. Once I did that, I no longer got the apache page. See "Disable Default Site" in http://wiki.koha-community.org/wiki/Koha_on_ubuntu_-_packages I've been spending the past few days practicing setting up a new test site before I rebuild our production site, so these are the first things that came to mind. Fred King Medical Librarian, MedStar Washington Hospital Center fred.king@medstar.net 202-877-6221 ORCID 0000-0001-5266-0279 When you leave this ICU, you’ll go somewhere and say “This is sick? Not where I trained.” – ICU Attending Physician -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Boulier, Jack Sent: Tuesday, May 19, 2015 7:17 PM To: koha@lists.katipo.co.nz Subject: [Koha] Installed new server can no longer access KOHA. I have installed a new server with Ubuntu 14.04. Though I did the install of KOHA correctly. But now when I internet to the server I get the apache page and not the KOHA pages. Do need so help, but do not even know what to begin to ask the right questions. Thanks to those that respond. Jack Boulier LRC Director MTI College Sacramento, CA (916) 339.4370 Direct (916) 339.1500 ext. 270 (916) 339.0305 Fax _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected. Thank you. Help conserve valuable resources - only print this email if necessary.
As a slight tangent, if you want to run a web site on your server in addition to Koha, you can. Edit /etc/apache2/sites-available/000-default.conf to change VirtualHost to 81 (or whatever port you want) Then edit /etc/apache2/ports.conf to listen on port 81 (or whatever port you want) Then enable 000-default.conf, and edit the files in /var/www/html to produce a web page. No problem, lovely budgie. Fred King Medical Librarian, MedStar Washington Hospital Center fred.king@medstar.net 202-877-6221 ORCID 0000-0001-5266-0279 When you leave this ICU, you’ll go somewhere and say “This is sick? Not where I trained.” – ICU Attending Physician -----Original Message----- From: Koha [mailto:koha-bounces@lists.katipo.co.nz] On Behalf Of Boulier, Jack Sent: Tuesday, May 19, 2015 7:17 PM To: koha@lists.katipo.co.nz Subject: [Koha] Installed new server can no longer access KOHA. I have installed a new server with Ubuntu 14.04. Though I did the install of KOHA correctly. But now when I internet to the server I get the apache page and not the KOHA pages. Do need so help, but do not even know what to begin to ask the right questions. Thanks to those that respond. Jack Boulier LRC Director MTI College Sacramento, CA (916) 339.4370 Direct (916) 339.1500 ext. 270 (916) 339.0305 Fax _______________________________________________ Koha mailing list http://koha-community.org Koha@lists.katipo.co.nz https://lists.katipo.co.nz/mailman/listinfo/koha MedStar Health is a not-for-profit, integrated healthcare delivery system, the largest in Maryland and the Washington, D.C., region. Nationally recognized for clinical quality in heart, orthopaedics, cancer and GI. IMPORTANT: This e-mail (including any attachments) may contain information that is private, confidential, or protected by attorney-client or other privilege. If you received this e-mail in error, please delete it from your system without copying it and notify sender by reply e-mail, so that our records can be corrected. Thank you. Help conserve valuable resources - only print this email if necessary.
participants (6)
-
Boulier, Jack -
Craig Butosi -
King, Fred -
Mark Tompsett -
MJ Ray -
Robin Sheat