Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error 324 (net::ERR_EMPTY_RESPONSE) #2332

Closed
anonymous-matomo-user opened this issue Apr 18, 2011 · 8 comments
Closed

Error 324 (net::ERR_EMPTY_RESPONSE) #2332

anonymous-matomo-user opened this issue Apr 18, 2011 · 8 comments
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Milestone

Comments

@anonymous-matomo-user
Copy link

After updating to 1.3 (which completed successfully) this error returned. It did not happen straight away but possibly at the first cron job that builds reports after the update.

I now cant login

"Error 324 (net::ERR_EMPTY_RESPONSE: The server closed the connection without sending any data."

I can access the stats via the API but it isnt updating suggesting its something to do with report building?

NOTE: i had this error before which was fixed in the patch that is included with 1.3. See error #2288

thanks

@mattab
Copy link
Member

mattab commented Apr 18, 2011

It seems to be a google chrome issue? http://www.google.com/support/forum/p/Chrome/thread?tid=19043fff689eff09&hl=en

http://drupal.org/node/1048140

and MANY more. please have a look as this is probably not a piwik bug (if you find out this is a piwik bug please post a comment)

@robocoder
Copy link
Contributor

Sorry, I've never encountered this error message, and as far as I know the error message doesn't originate with Piwik, PHP, or MySQL.

@anonymous-matomo-user
Copy link
Author

Hi the problem is not with a browser (same problem in firefox and IE). But I have identified it.

The problem is due to permissions, restoring 777 to all files (such a high permission is required by my server) fixed it. I suspect something goes wrong with the cron job or another aspect of piwik which messes it up if permissions are incorrect.

I refer you to my original post where i said it worked fine at first, something must have happened to make it not work a few hours later. The problem is then the automatic update causes the new files to have incorrect (lower) permissions which need manually changing.

@robocoder
Copy link
Contributor

At minimum, I would have expected an error message.

For our reference, can you lower the permissions and use "curl" to capture the HTTP response (header and body)? And please see if there were any error messages in your web server log file that might identify where the issue occurred. Thanks.

@anonymous-matomo-user
Copy link
Author

Hi, sorry i cant replicate the error, changing permissions back gives the message that some files aren't writeable. I didnt check permissions before i changed them so i don't know which files had what.

The error log however shows these (lots of the same message with differing pid's up until i changed permissions)

Mon Apr 18 17:39:54 2011] [warn-phpd] mmap cache can't open /home/greensky/public_html/piwik/tmp/cache/tracker/1.php - Permission denied (pid 3520)

@robocoder
Copy link
Contributor

Interesting. I didn't know we used the mmap cache.

@anonymous-matomo-user anonymous-matomo-user added this to the 1.4 - Piwik 1.4 milestone Jul 8, 2014
@mattab mattab added the wontfix label Aug 3, 2014
@digjack
Copy link

digjack commented Nov 17, 2016

I have run into the same problem and after check the config for a while , I found the solution.
the question is nothing to do with the piwik, but the nginx config. From the offical nginx conf, I found a line like this

location ~* ^.+\.(?:jpg|png|css|gif|jpeg|js|swf)$ {
  # Defining the valid referers.
                  valid_referers none blocked *.piwik.com   othersite.com;   //change this line to deal question
                  if ($invalid_referer)  {
                          return 444;
                  }
                  expires max;
                  break;
         }

when we add tracker to the other site for tracking . the application will get the piwik.js from piwik application. and if this conf doesn't contain the refering url . the nginx will reject this request and return http code 444. my solution is add the valid url here . and the error disappear.

@mattab
Copy link
Member

mattab commented Dec 6, 2016

Hi @digjack in order for your comment to help everyone who could benefit, do you mind reporting it to the project directly here: https://github.com/perusio/piwik-nginx/issues

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug For errors / faults / flaws / inconsistencies etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. wontfix If you can reproduce this issue, please reopen the issue or create a new one describing it.
Projects
None yet
Development

No branches or pull requests

4 participants