In either /etc/httpd/conf.d/111.111.1.1.conf or /etc/apache2/conf.d/111.111.1.1.confNameVirtualHost 111.111.1.1:8443
Listen 111.111.1.1:8443
Thanks, did you commented these lines?jarland wrote:It's just because you don't have any sites with SSL on them, but Apache is configured to listen on port 8443 for SSL traffic. It's just a warning. You can ignore it, or if you have no plans for SSL you can comment out these two lines:
In either /etc/httpd/conf.d/111.111.1.1.conf or /etc/apache2/conf.d/111.111.1.1.confNameVirtualHost 111.111.1.1:8443
Listen 111.111.1.1:8443
Code: Select all
2014/01/18 14:48:45 [error] 10650#0: *109 upstream prematurely closed connection while reading response header from upstream, client: 2.133.122.19, server: domain.kz, request: "GET / HTTP/1.1", upstream: "http://145.85.26.134:8080/", host: "domain.kz", referrer: "http://domain.kz/admin/reports"Domain error log says what i have typed before and httpd/error_log:jarland wrote:That error means that Apache closed the connection before nginx got what it needed. This can happen if Apache is restarted at the same time the request is made. However, it sounds like that isn't what is happening exactly.
Check the error log in /home/user/web/domain.tld/logs and in /var/log/httpd/error_log. Look and see if there are any other errors with identical time stamps. What we're seeing is nginx passing on it's problem, but not saying why Apache severed the connection. Hopefully the Apache logs will present the actual cause of the error.
Code: Select all
[Sat Jan 18 01:53:39 2014] [notice] child pid 4169 exit signal Segmentation fault (11)
[Sat Jan 18 01:53:53 2014] [notice] child pid 4172 exit signal Segmentation fault (11)
[Sat Jan 18 01:53:53 2014] [notice] child pid 4175 exit signal Segmentation fault (11)
[Sat Jan 18 01:53:55 2014] [notice] child pid 4176 exit signal Segmentation fault (11)
[Sat Jan 18 01:53:55 2014] [notice] child pid 4178 exit signal Segmentation fault (11)Code: Select all
[Sun Jan 19 01:36:57 2014] [notice] child pid 20739 exit signal Segmentation fault (11)
[Sun Jan 19 01:36:57 2014] [notice] child pid 20740 exit signal Segmentation fault (11)
[Sun Jan 19 01:39:39 2014] [notice] child pid 20742 exit signal Segmentation fault (11)
[Sun Jan 19 01:39:40 2014] [notice] child pid 20743 exit signal Segmentation fault (11)
[Sun Jan 19 01:39:48 2014] [notice] child pid 20744 exit signal Segmentation fault (11)I already have memory_limit 256M. Your drupal worked because you restarted vesta and apache. Try to drop all tables in DB and delete all drupal files including .htaccess and .gitignore. Then install it again from scratch without any reboots and you will see 500 internal server error.jarland wrote:Installed drupal at http://jarland.org , fresh CentOS 6.5 with VestaCP.
So I edited /etc/php.ini and changed memory_limit to 256M. I enabled error logging for PHP. Ran "service vesta restart" and "service httpd restart" and I haven't been able to check PHP error logging because there has been no error since. Clicking all around, unable to reproduce the error thus far.Code: Select all
[Sun Jan 19 01:36:57 2014] [notice] child pid 20739 exit signal Segmentation fault (11) [Sun Jan 19 01:36:57 2014] [notice] child pid 20740 exit signal Segmentation fault (11) [Sun Jan 19 01:39:39 2014] [notice] child pid 20742 exit signal Segmentation fault (11) [Sun Jan 19 01:39:40 2014] [notice] child pid 20743 exit signal Segmentation fault (11) [Sun Jan 19 01:39:48 2014] [notice] child pid 20744 exit signal Segmentation fault (11)
My guess is Drupal needs the memory_limit for PHP a bit higher than default.