blog documentation FAQ followers forum marketplace services youtube

solved core update crashes

The Jamroom Network » Forum » Installation and Configuration » Page » core update crashes
alt=
DannyA
@dannya
9 years ago
584 posts
I have to say, EVERY time i do a core update, my system crashes and I get 500 errors. We end up having to go through all kinds of steps and usually manually clearing the cache to get things to work again. I don't know if this is common, but extremely annoying. It makes it very difficult to update on a regular basis.
updated by @dannya: 02/14/16 03:36:02PM
brian
@brian
9 years ago
10,148 posts
If you get 500 internal server errors, you have a server issue.

I have 15+ domains I run with Jamroom and never see this, so I would suspect you have larger server issues going on.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
douglas
@douglas
9 years ago
2,791 posts
Are you using our hosting or another hosting company?

I update a lot of sites and have never had an issue. Most of the sites are not on shared hosting plans except one, which is kind of slow when updating, but I've never gotten a 500 server error message on any of them.


--

Douglas Hackney
Jamroom Team - Designer/Developer/Support
FAQ-Docs-Help Videos
alt=
DannyA
@dannya
9 years ago
584 posts
I'm not suggesting it's a native jr issue. I'm sure a plain vanilla system works fine. And although I have a lot of custom modules, I think it's related to something in the server configuration. However, I will say that my server is configured according to your requirements. So there must be something else in the configuration. I suspect it has something to do with the symlinks, but have not been able to pin down the issue.
alt=
DannyA
@dannya
9 years ago
584 posts
Been down for 2 hours. Good thing it's not my production server.
brian
@brian
9 years ago
10,148 posts
No reason to be down for 2 hours - your sys admin should be able to identify the issue in 2 minutes:

/var/log/apache2/error_log


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
(snipped)

[Sun Nov 08 19:06:54.708788 2015] [core:error] [pid 13931] [client 122.161.49.207:64688] AH00124: Request exceeded the limit of 10 internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
[Sun Nov 08 19:08:46.273487 2015] [autoindex:error] [pid 13309] [client 66.249.64.136:53036] AH01276: Cannot serve directory /home/dev/public_html/: No matching DirectoryIndex (index.html,index.php,sitemap.xml,modules/jrCore/router.php) found, and server-generated directory index forbidden by Options directive
alt=
DannyA
@dannya
9 years ago
584 posts
After 4 hours, we are giving up. Going to have to re-install the whole thing.
brian
@brian
9 years ago
10,148 posts
None of the "PHP Notices" are issues. Here is your problem:

No matching DirectoryIndex (index.html,index.php,sitemap.xml,modules/jrCore/router.php) found, and server-generated directory index forbidden by Options directive

You are missing this file:

modules/jrCore/router.php

OR your apache2 config is configured for the wrong web directory.

I apologize that you're having issues - I would highly recommend that before you "go live" you find a system administrator that knows what they are doing and can fix these types of issues. There's no reason this should be more than a 4 minute event - certainly NOT a 4 hour event.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
The file wasn't missing. It's something to do with the symlinks.
brian
@brian
9 years ago
10,148 posts
Make sure FollowSymLinks is enabled in the Options directive for the domain (it is enabled by default):

https://httpd.apache.org/docs/2.4/mod/core.html#options


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
brian
@brian
9 years ago
10,148 posts
The other one to watch out for is "SymLinksIfOwnerMatch" - if you have that enabled, then it means symlinks are followed only if the destination is owned by the same user that owners the symlink. This means if you are running Apache has the "httpd" or "www" user, and you upload the files as root (or another user) and you do NOT chown them to www/httpd, then symlinks are not followed:

https://httpd.apache.org/docs/2.4/sections.html


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
In this case I used the ACP marketplace to do the update, so I don't think that's it.

Been 8 hours now. Even after fresh install, restoring db causing 500 error.All manner of files not found. I'm annoyed beyond words, but grateful it didn't happen in production with many active users. Probably would have to shut the company down by now.

Going to try to revert everything back.
brian
@brian
9 years ago
10,148 posts
If you're getting 500 errors on your system, and it's all related to files not found, then there is a reason that is happening: Either the files do not exist, or they exist in a different location than your website is configured to look.

Again - in either situation a competent system administrator would figure it out very quickly. I understand you're annoyed and want this to be a Jamroom issue, but it's not.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
updated by @brian: 11/10/15 10:58:24AM
alt=
DannyA
@dannya
9 years ago
584 posts
DannyA:
I'm not suggesting it's a native jr issue. I'm sure a plain vanilla system works fine. And although I have a lot of custom modules, I think it's related to something in the server configuration. However, I will say that my server is configured according to your requirements. So there must be something else in the configuration. I suspect it has something to do with the symlinks, but have not been able to pin down the issue.
brian
@brian
9 years ago
10,148 posts
Sorry about that - should have read the full thread again before responding - I assumed you are "annoyed beyond words" at us - sorry for the misunderstanding :)


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
Nope. I prefer to take full responsibility. This has been something that has never worked right for me. Sometimes it went away if we cleared the cache. Sometimes we had to go into code and debug. But unfortunately, it's made it very difficult to upgrade regularly. We should have done a fresh install but it was never a priority as it would take to much time. Now we have no choice. Again, my fault for not backing up the db. Lesson learned. At least it wasn't in production.
Ken Rich
Ken Rich
@ken-rich
9 years ago
926 posts
Not sure if this helps but I'm in Jamroom hosting, just tried an update and now I can't access my network at all.

I get 500 server error with blank page.

I'm certain that Jamroom hosting provides a properly configured server, so the problem appears to be in the updates themselves ( not that I'm any kind of authority on these things).


--

Ken Rich
indiegospel.net
brian
@brian
9 years ago
10,148 posts
I'm not seeing an issue here Ken:

http://indiegospel.net/

Is it a different domain?

Thanks!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
Ken Rich
Ken Rich
@ken-rich
9 years ago
926 posts
Hi Brian,

If you guys didn't do anything then it apparently resolved itself.

It was that domain http://indiegospel.net and I was seeing 500 server error, even after clearing cache and restarting browser.

I think it was definitely a "REAL" problem but I don't know how it fixed itself.

Also, I have noticed this error a few times now on updates but didn't think much of it because it cleared itself within seconds. I chalked it up to some temporary difficulty due to the core being overwritten/altered.

This time was different, the network was gone for several minutes and I couldn't find a way to get it back. Then poof it magically appeared again. ?????


--

Ken Rich
indiegospel.net
Ken Rich
Ken Rich
@ken-rich
9 years ago
926 posts
I just checked the error logs and nothing shows up - sorry I can't be more helpful - this stuff is way out of my league.


--

Ken Rich
indiegospel.net
brian
@brian
9 years ago
10,148 posts
Ken Rich:
I just checked the error logs and nothing shows up - sorry I can't be more helpful - this stuff is way out of my league.

Hi Ken -

Already followed up on the ticket a bit ago, but will post here just in case you did not get my response:

Quote:
It was likely a bad cache item that could have been causing it (PHP xcache) - I actually saw the same thing on one of my dev sites I updated to, and it was due to a change in the router.php file that references $_SERVER instead of __FILE__ (php variables). It reset usually pretty quickly, but if you ever see this again just restart the web server.

You can restart your Web Server, MySQL and entire server from your "Server Tools" section in your hosting.

Hope this helps!


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net
alt=
DannyA
@dannya
9 years ago
584 posts
Something that might be helpful, if it's not doing so already, if have the cache automatically cleared before an update is made. a big part of the problem is, when you have a problem, you can no longer access the acp to do integrity check, clear cache, etc...
brian
@brian
9 years ago
10,148 posts
The marketplace module already does this via it's jrMarket_reset_opcode_caches() function - which probably works 99% of the time. There's just no way to guarantee that every update is going to work 100% of the time, all the time, every time.

There are a lot of variables in play on servers that are outside of Jamroom's control, and any of these could play a part in keeping something from working as it should (firewalls, extra server caches, file system caching, 3rd party "optimizers", MySQL database quotas and "security" add ons, etc.)

The best defense against this is to have a good understanding of how your server works, and what to do (and where to look) when problems occur, because at some point problems WILL occur with any server, and your downtime is going to depend on how ready you are for that.


--
Brian Johnson
Founder and Lead Developer - Jamroom
https://www.jamroom.net

Tags