volgens sandeep gupta.
i have tried insalling moodle several times but its not completing .a url http://localhost/moodle/user/editadvanced.php?id=2 comes up always and nothing happens after it.. please tell all posible reasons.. i have uninstalled skype in case of port overlapping but didnt work. also i tried it to install with bitnami module but thts also not working
volgens Paul Smith.
Hi Everyone
I have just started using Moodle, everything is working correctly apart from when I'm updating my courses when I click the save button I get the following error:
Coding error detected, it must be fixed by a programmer: The data source class does not exist.
If I click the continue button the changes take place so I'm not sure if it's something I need to worry about.
I'm running Moodle 2.7 and using the Snap theme, I really hope someone can point me in the right direction.
Thank you in advance
Paul
volgens Annie Price.
Hi Ken,
Thank you so much for the response - much appreciated.
Unfortunately, I have no idea how to use tar - wouldn't even know where to put in those commands!
So I am going to try simply backing up /filedir and see if that works.
Fingers crossed.
Annie
volgens George Rayner.
So I've got a Moodle server running on the internal network that is accessible by just using the internal IP address, but I would now like to make it accessible from outside the network by using the public IP. Unfortunately, i'm not very good at this sort of stuff and I could really use some help with this. Any help at all is greatly appreciated.
volgens Иван Харитонов.
OK, I tried this and I think here's the reason I couldn't get through:
"Moodle 3.2 or later requires at least PHP 5.6.5 (currently using version 5.3.28).
Some servers may have multiple PHP versions installed, are you using the correct executable?"
That's what the command line says. Which is strange for I had manually changed server php version to 7.0 beforehand and during the installation the built-in checking confirmed the newest php version.. I don't have a printscreen but recall that for sure.
Does this mean I should simply choose an older version of Moodle? Or would you recommend to get into contact with the server staff and clarify the php version issue? Or maybe there's another option?
volgens Daniel meanock.
Thanks Ken,
Right so i have ditched the cache folders mentioned above. (didnt do anything )
All seems fine with permissions (checked) and cpanel is behaving as it should
If i enter the url example i get :
The requested URL /xxx was not found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.
volgens morola oyedele.
hello good people,
I installed moodle on a Linux server, i need to access it from outside the machine, i located the config.php and changed localhost/moodle to IP address/Moodle but i am not able to access it, kindly help
thank you
volgens Gary Marsh.
MOODLE Version: 2.9.4+ (Build: 20160225)
For a year, a very competent Moodle Partner provided excellent hosting and advice while I structured and was developing free marine education website courses for Canadian mariners preparing to sit Transport Canada Marine Certificates of Competency Examinations.
Alas, when the hosting contract renewal time came around, I determined that I could not afford the annual hosting cost and instead, decided to purchase a Lenovo ThinkServer TS140 with Linux Ubuntu 16.04 LTS OS, to continue developing the website.
I am located in Penticton, British Columbia, Canada and thought that it wouldn't be too difficult to find someone to setup the server with the MOODLE website backup file that the Moodle Partner provided. I was wrong!
I know nothing about servers and so, for the past month, while researching how to migrate the website backup file to a server, I have spent most of my time trying to learn Linux Terminal commands to setup the server. If there is even a dim light at the end of this dark tunnel, then I've yet to find the switch to, at least, establish direction.
Here are a couple of questions:
Any help or advice that gets me to the point when I can just focus on developing courses again, I'm sure it will be like escaping a sinking ship, in an inflated liferaft, on a vacant sea . . . very much appreciated.
Gary Marsh
volgens Иван Харитонов.
14.04.1-Ubuntu, Apache 2.4.7 with nginx 1.4.6 and PHP versions 5.2, 5.3, 5.4,5.5.,5.6, 7.0
No additory caching.
by Oliver Bay.
Ken,by leslie tindale.
Hi Adrian,
I am facing the same issue after updating to 3.2 today. Any progress ???
I'm going to try Ken's suggestions shortly and will get back.
Thanks everyone for the posts and suggestions.
Leslie
by Иван Харитонов.
OK, I changed the php version of ssh and here's what I got
by Ken Task.
Well, let's review just how you got 3.2 code to the server, please.
Describe.
'spirit of sharing', Ken
by Ken Task.
There are serveral linux versions ... they do behave slightly differently ... so what flavor of distro do you have? Ubuntu, CentOS, Other?
Is the web server accessible by itself ... config for apache has sto be setup and functioning first before moodle code. Is the web service running?
ps aux |grep httpd (CentOS/RH family)
or
ps -aux |grep apache2 (Ubutnu/Debian family)
'spirit of sharing', Ken
by Emma Richardson.
What you need to figure out is what exactly is included in the file backup from Moodle Partner. In order to restore, you need three things. 1. Moodle code (either downloaded from moodle or perhaps in the backup). I actually doubt it is in the backup and you would probably be better to download it. I would check what version of Moodle you are coming from and mirror that version to get started. You can upgrade later. 2. Moodledata folder. This is the folder with all of your content in it and should be part of the backup that you received. 3. Database backup. This will need to be restored to your new server.
Once you have figured out what is in your backup file, you should be able to follow the migration instructions and get up and running. You will also need to deal with DNS issues to tell the world and moodle software where your site is located now.
by Ken Task.
Ok then, that does make sense, doesn't it?
So drop the database. Then re-create it via mysql client.
mysql -u superuser -p
at the mysql> prompt ... show databases;
The ';' at the end are important.
Then drop database [nameofdatabaseformoodle];
Then recreate still at mysql prompt:
create database moodle character set utf8 collate utf8_general_ci;
Quit the mysql client: \q or exit [ENTER]
Then run the php install.php script again.
You're gaining on it! ;)
'spirit of sharing', Ken
by Garren Shannon.
Randy... sorry for my lack of knowledge in this but is this something that is part of a theme? In other words, if I try a different theme, they may be there?
by morola oyedele.
hello Ken,
thank you for the response, its a redhat installation, i am new to Linux but my environment is a large enterprise with about 6000 users so the windows installation is not going to be stable. i will check the web service
by Daniel meanock.
Hi Ken
ok so,
1 - i installed a fresh 2.7 on a new domain on the dedicated server
2 - copied over my existing moodle data from shared server to new install on dedi
3 - I imported the db from existing shared to dedi
4 - i then updated the new install to 3.2 by deleting entire moodle folder - then uploading the latest moodle version freshly downloaded from moodle site, then i copied back in the config file, then when i loaded the site it did some updating to the db and once complete all was fine apart from these errors
I think that covers it, i didnt take any other steps and assumed as it said in the upgrading notes :
Note: You can only upgrade to Moodle 3.2 from Moodle 2.7 or later. If upgrading from earlier versions, you must upgrade to 2.7 as a first step.
That it was ok to jump straight to this ?
Thanks Ken
by Ken Task.
The 'devil' is in the details ... I have helped entities (at least 2) restore a site to a local server coming off a MP.
Detail 1: I'd be surprised if the MP has given you a code backup. Most MP's offer an extra bell and whistle that they offer but ONLY if you host with them. So your move to your server must now deai with a minor update to the version of Moodle as close to what you had when hosted with the MP. 2.9.4+ to the highest 2.9.x available.
One could get the exact version of Moodle code, but it would mean using git and that is a level of expertise beyond OP right now. This is gonna be a problem solving project for anyone - even to those who have a lot of experience with Moodle. It can be done ... it's just not a quick and easy 1,2,3 kinda thing.
So bottom line there ... you should get the moodle 2.9.highest code downloaded to your server from:
References:
https://docs.moodle.org/dev/Releases#Moodle_2.9
https://docs.moodle.org/29/en/Upgrading
Detail 2:
The sql dump you have has to be imported into a new DB for Moodle. That requires getting MySQL running first ... with a proper superuser login and password to begin. Then another DB user that has access to the Moodle DB you re-created for it.
Detail 3: is the eaiest ...
The un-archving of what probably is a tar.gz of moodledata to the proper location on the new server. If I re-call Ubuntu 14.04 server calls the web service apache2 and it's document root is /var/www/html/
The un-archiving of the data directory should go into /var/www/
And ithe data directory ownerships/permissions need to be changed to the apache2 web service user - which is www-data on that flavor of linux, I think.
Detail 3:
Almost done ... the creation of a config.php file from config-dist.php file.
cp config-dist.php config.php
nano config.php
then add the data to the values for the DB, the wwwroot, the datadirectory location.
You do NOT need to set all that's in config.php .... just the minimums right now.
Having done all that ... time to test ... go to another workstation and attempt to access the server first by it's static IP address then by it's fully qualfied domain name ... which is yet another devil detail depending upon home network IF that's where the server physically resides now ... or if co-located on a service providers network.
The FQDN is the fullly qualfied domain name of the server ... it was hosted before with an MP and all the data in the DB refer to that domain ... to which you no longer have access.
Two options ... but there is yin/yang cause it's hosted on a home network .. ie, at the house as opposed to another provider which is already on the internet ... a home network is not, traditionally accessible by anyone on internet.
For local access on home network to begin ... just test it ...
edit the /etc/host file on your local system.
Add a line:
Static_IP_address_of_server then next to that the FQDN as it existed on the MP site.
Example:
192.168.1.22 www.tons.online www
Got the domain name from your profile in Moodle.
Then, in a work station you will use to access the new internal private IP'd moodle server, do the same with the workstation's host file.
Your workstation will then not try DNS to find www.tons.online but the host file ... which is pointed to your internal private network only right now Moodle server by an FQDN.
Uhhhh ... think you can see this will require a lot of work ... and when you finish, there's the 'last mile' to go yet ... how to get the public internet to be able to see your server by that domain name ... assuming you own that domain name.
Ok, I've left out many, many, many details ... above are only the 'devils' in such a project just to get it up and running in your private network.
'spirit of sharing', Ken
