1

This is the problem.

Live site blank in frontend or keep on loading and never load

impossible solution is we have to tell to customers that please clear your browser cache and than browse our site.

We need some Permanent solution for this.

please someone help us.

Improve this question
4
  • 1
    Why did you open a new question? Why is the bounty not on the original question? My guess is there might be something wrong with the core, did you try to update the store to a newer version so you are sure the Magento core is ok? After that you can look further when needed, but a core problem would be ruled out. Commented Feb 17, 2016 at 16:18
  • i tried to create bounty on new question, i should award minimum 300 points, so i created bounty and linked for that. we will try to upgrade to newer version. Commented Feb 17, 2016 at 16:51
  • @BabyinMagento instead of wasting days, take fresh copy of magento and install one by one module. if every thing get succeed import the customers, products and orders data. which takes time but its better when we don't have solution Commented Feb 19, 2016 at 14:02
  • @prasadmaganti thanks a lot for tips. but client want solution.to fix the issue. Commented Feb 20, 2016 at 14:33

4 Answers 4

Reset to default
5

As I can see in Chrome Cookies, Magento sets two cookies: one for domain ".sitename.com" and another for "sitename.com" with same name "frontend". After some time cookie with domain "sitename.com" will be expired because Magento does not use it anymore after creation. On all next pages Magento update the cookie with domain ".sitename.com". Probably after expiring you get conflict and it doesn't send any cookie to Magento. I would recommend you to set Cookie options for your domain like:

Cookie Path: / Cookie Domain: sitename.com

And check if it still creates two cookies. Also check with domain .sitename.com

Improve this answer
7
  • we will check it Commented Feb 17, 2016 at 5:09
  • how to test two cookies are created in browser? Commented Feb 18, 2016 at 5:58
  • I used Chrome, If you clean cookie and go to the website you will see only one 'frontend' cookie screencast.com/t/cOfFxjXXOrbi , further website usage will create one more cookie 'frontend' screencast.com/t/Z3Y8aldND0f . After that only second cookie will be used which you can see by non-changing of expired date. Commented Feb 18, 2016 at 16:17
  • i followed this : magento.stackexchange.com/questions/102283/… prntscr.com/a4x3ja you can see 2 frontend, means is this the issue, double cookies. Commented Feb 18, 2016 at 16:26
  • it didt worked for me Commented Feb 24, 2016 at 9:16
2
+50

Other than the suggestion I gave you in the other post (the hacked website possibility) you can also check your core_sessions MySQL table size.

Also check you are not using disk session with a huge session amount.

Make a test changing your local.xml:

<session_save><![CDATA[files]]></session_save>

Change to:

<session_save><![CDATA[db]]></session_save>

After this flush your cache and see if the problem persists.

Improve this answer
8
  • i will check that too. Commented Feb 16, 2016 at 21:05
  • it worked when i changed from file to db, again it started giving errors after some time Commented Feb 24, 2016 at 9:17
  • Check the number of entriesin core_session table Commented Feb 24, 2016 at 9:18
  • i will check that now..... Commented Feb 24, 2016 at 9:18
  • only 15 rows are there in table = prntscr.com/a79avv Commented Feb 24, 2016 at 9:29
1

Magento has in-built feature of setting the cookies lifetime to any number of seconds.

For turning this feature on go to Admin >> Session Cookie Management >> Lifetime and give a lower value(3600 or lower than that) and "Save" the system-config.

Hope this works for you

Improve this answer
2
  • we will check it Commented Feb 17, 2016 at 11:53
  • it didt worked for me Commented Feb 24, 2016 at 9:17
1

Several reasons why this could happen.

This happens when a module is trying to initialize a session, before sessions have started, so you may need to debug to find which module is doing that.

The other thing that can help is to set the cookie domain in your configuration as .sitename.com and set path to / This is because it mixes www.domain.com and domain.com cookies up.

Lastly, if it's a customer trying to login when the error happens, find that customer and delete the contents of their basket. You may want to think about cleaning out the sales quote tables in the database if this is the issue.

Improve this answer
2
  • sure, we will try your solution..... Commented Feb 22, 2016 at 16:51
  • i am trying removing one by one module and checking Commented Feb 24, 2016 at 9:18

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.