I've installed Moodle v3.8 on Docker (php7.2-apache), but it's stucked at "System" screen when installing -error is attached
Stuck screen photo here
Plz help me to solve this, thank a lot
I had the same problem when installing moodle 3.10 (PHP 7.2). Reloading the page got me further to plugin installation.
How do you know it is stuck? It takes a while for the 'success' messages to start to appear - especially for the 'System'.
Same thing happened to me, I thought it was hanging, but it turns out I just had to leave it alone and it worked.
These are few points you can take care of:
it'll take few minutes to get installed, until then don't refresh the page
if it doesn't show anything after few minutes delete files and folders of moodledata and restart moodle installation
open phpMyAdmin and refresh your database
Hope that'll help, thank you.
Same issue with Moodle 4.0.1 so I understood the issue was version independent.
Nginx error log recorded a line of
upstream timed out (110: Connection timed out) while reading upstream
So I added to my /etc/nginx/sites-available/default config the following timeout related lines
location ~ [^/]\.php(/|$) {
...
fastcgi_read_timeout 300;
fastcgi_send_timeout 300;
fastcgi_connect_timeout 300;
}
as per this accepted answer Nginx + Php-fpm fastcgi upstream timed out
I used 300 instead of 600 because the former is same as max_execution_time and max_input_time in my php.ini
Related
I'm trying to install Grafana on a server, and installation goes through properly. However, when I try to start the service (using sudo service grafana start) it fails with the cryptic message:
2016/02/11 18:45:38 [web.go:93 StartServer()] [E] Fail to start server: open : no such file or directory
I have been unable to find an answer to this.
I assume that I'm simply missing an apt-get package or something really simple, but there's no more information than this.
Anyone have an idea?
Thanks for your time.
EDIT:
While unable to solve the actual problem, I realized that though I configured the server to run over HTTPS, the actual SSL is handled through the proxy by my host, and the server should run internally on HTTP. When changing this, the server started properly. It's not a solution to this specific problem, but as it may point others with this problem in the right direction;
the problem had to do with running over HTTPS.
Good luck!
when configuring Grafana to use HTTPs you need to specify cert & key paths, looks likely that Grafana could not find one of them.
i am using using activator project which has play 2.4.2 . just for testing i deployed raw project which only listen on port 80 0r 9000 and returning Ok("abc").
but when i check the output of
$ sudo lsof -i | wc -l
the number increasing gradually with time, and after some time let say 24-48 hours. the server crashes with exception too many file open.
i tested with apache benchmark also, after completion of benchmarking, there is still some connections open and never close.
please someone help.
There seems to be some debate around this issue, when sometime back I was working with playframework.
First verify that if your client is asking for connection to be kept alive. In this case playframework would honor the client and keep the connection open. See this disscussion . The takeaway from discussion was play can handle a lot of request, which is questionable if you think about DoS attacks.
The other thing there seems to be options to kill the connection from the action with the header, but I have never tried with those. See this. I am not able to pull any documentation around this option at this moment.
Edit : Seems to be mentioned in 2.2. hightlight.
One of my Drupal websites homepage (just the homepage) is constantly redirecting when the site is visited. Tends to happen randomly. Which I don't understand why it would do this. I talked a bit on the Drupal community and it is said to be a server issue. Not Drupal.
Error 310 (net::ERR_TOO_MANY_REDIRECTS): There were too many redirects.
I don't currently have CPanel access to check the server logs though. I am somewhat fluent in terminal and I have root SSH access to the server.
Where and what commands would I have to run to find and access the logs that could possible help me figure where to start with fixing this? Would they just be located in /var/? What would I be looking for once I get access to the logs, just a steady stream of the duplicated IP address that it keeps being redirected too?
Found out this IS a Drupal Commerce Kickstart core issue.
Found follow errors in php logs:
PHP Warning: Unknown: Input variables exceeded 1000. To increase the limit change max_input_vars in php.ini
PHP Fatal error: Unsupported operand types in public_html/dev/profiles/commerce_kickstart/modules/contrib/search_api_db/service.inc on line 970
Got the redirect loop to stop after increasing the max_input_vars to 9000. I feel it's more of a bandaid fix though. So I'm taking this further into the Commerice Kickstart community.
I am unable to get a Login page after Moodle 2.5 installation got over. it throws following error
The page isn't redirecting properly
Firefox has detected that the server is redirecting the request for this address in a way that will never complete.
This problem can sometimes be caused by disabling or refusing to accept cookies.
I will be more helpful if anybody gives me an answer.
Assuming this is a fresh install?
I would first check this setting is correct in config.php - something like
$CFG->wwwroot = 'http://localhost/yourwebname';
or
$CFG->wwwroot = 'http://www.yourdomainname.com';
If those are correct then clear the cookies in the browser for the specific domain.
And maybe clear the Moodle cache. From a terminal, go to your web directory
cd /var/www/moodle
Then run
php admin/cli/purge_caches.php
http://docs.moodle.org/25/en/Administration_via_command_line#Purge_caches_via_CLI
I had this same issue (except with XAMMP, and Moodle 2.7, but my guess is the same issues are at play). The solution at https://moodle.org/mod/forum/discuss.php?d=239793#p1115879 worked for me.
Basically, delete the contents of moodledata\cache (just use explorer, no need for any CLI stuff), and increase max memory in php.ini (should be wamp\php\php.ini) from 128M to 1024M, then try loading the page again.
I've had Nginx & Thin playing nicely on Ubuntu 10.04 for a couple of years. I have a script in /etc/init.d that starts Thin, using some .yml files in /etc/thin.
All of a sudden restarting Thin for any reason causes a permission denied error in Nginx.
Thin is running on a couple of sockets in /tmp, owned by root. I don't know if that was always the case...but if I change the owner of the socket to www-data (used by Nginx) everything works fine. So I wrote another script to handle it.
Thin is running v1.2.7, and Nginx is 0.7.65. Neither has changed. I did upgrade to Ruby 1.9.3p194 from 1.9.2p290.
Does anybody else have this issue, and have you found a more reasonable fix than "manually" updating permissions?
Upgrading Thin to 1.3.1 solved it. I should've tried that right away, but I had issues with a staging server.
Anyway. Maybe this will help someone else.