Bug 12016 - After upgrading, APACHE is running but browser cannot connect
Summary: After upgrading, APACHE is running but browser cannot connect
Status: CLOSED FIXED
Alias: None
Product: Koha
Classification: Unclassified
Component: Installation and upgrade (command-line installer) (show other bugs)
Version: 3.14
Hardware: All All
: P5 - low trivial (vote)
Assignee: Galen Charlton
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-29 16:06 UTC by JB
Modified: 2014-12-07 20:02 UTC (History)
1 user (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description JB 2014-03-29 16:06:47 UTC
Since upgrading to this new release (3.14.5) on Thursday 28th March, 
(No changes were made to the config file - We only ran the upgrade, reindexed Zebra and restarted APACHE server)

a) we can ping the server, 
b) resolve the hostname, 
c) there are no errors output when starting the APACHE server, 
d) the config file for APACHE has no syntax errors, 
e) the virtual host for KOHA is set as active, 
f) the port is set to port 80, 

BUT even trying to navigate to the localhost from a local web browser it fails to connect to the http server.

Any ideas welcome -- Please help.
Comment 1 JB 2014-03-29 16:14:57 UTC
Sometimes it works for a minute or two and actually does manage to search the database, but within a couple minutes it's back to the same problem.
Comment 2 JB 2014-03-29 17:28:14 UTC
I have changed the importance to trivial, because I just do not have enough information about this, as it seems like sporadically things are starting to work. If I click on a shortcut to log into the staff client instead of "topsides". We use Koha on Firefox and Safari browsers and both are experiencing these errors. I'm not sure if this is a cache problem or an incompatible framework due to a framework change. I don't know how to delete a bug report, so I'm downgrading it until I have more information to make this easier to debug or if we determine that this is our fault and not a general Koha type bug we will try to delete it.

Sorry for the inconvenience.
Comment 3 Liz Rea 2014-04-24 03:01:59 UTC
If it comes to it, you can simply mark the bug as resolved. :)

This sounds pretty unlike anything I've heard of before - what version were you coming from?