1.3 Beta Debug Errors

1.3 Beta Debug Errors

von Charil Ferrell -
Anzahl Antworten: 20

I updated to 1.3 Beta yesterday.  While looking for answers for a "no site logs" problem, I read where Martin said to turn on the debug so we can see what files in which the errors may be occuring.  I thought I would give that a try......OOPS!!!

This is the result of turning the debug on:

Table 'lwbinet_mdle1.mdl_event' doesn't exist

SELECT * FROM mdl_event WHERE timestart + timeduration >= 1084320000 AND timestart <= 1085529599 AND ( userid = 1 AND courseid = 0 AND groupid = 0 OR groupid = 0 AND courseid IN (1,1)) AND visible = 1 ORDER BY timestart

Table 'lwbinet_mdle1.mdl_cache_text' doesn't exist

SELECT * FROM mdl_cache_text WHERE md5key = 'ee9732f1be69f3d370107c911fd3720c' AND timemodified > '1084375196'

Table 'lwbinet_mdle1.mdl_event' doesn't exist

SELECT * FROM mdl_event WHERE timestart + timeduration >= 1083391200 AND timestart <= 1086069599 AND ( userid = 1 AND courseid = 0 AND groupid = 0 OR groupid = 0 AND courseid IN (1,1)) AND visible = 1


Notice: Undefined property: groupmode in /home/lwbinet/public_html/moodle1/blocks/online_users/block_online_users.php on line 45

Unknown column 's.timeaccess' in 'field list'

SELECT u.id, u.username, u.firstname, u.lastname, u.picture, s.timeaccess FROM mdl_user u, mdl_user_students s WHERE u.id = s.userid and s.course = 1 and s.timeaccess > 1084374956 ORDER BY s.timeaccess DESC

Unknown column 's.timeaccess' in 'field list'

SELECT u.id, u.username, u.firstname, u.lastname, u.picture, s.timeaccess FROM mdl_user u, mdl_user_teachers s WHERE u.id = s.userid and s.course = 1 and s.timeaccess > 1084374956 ORDER BY s.timeaccess DESC


Notice: Undefined property: groupmode in /home/lwbinet/public_html/moodle1/blocks/participants/block_participants.php on line 29

Notice: Undefined property: groupmodeforce in /home/lwbinet/public_html/moodle1/blocks/participants/block_participants.php on line 29

Notice: Undefined property: groupmode in /home/lwbinet/public_html/moodle1/blocks/participants/block_participants.php on line 30

Notice: Undefined property: groupmode in /home/lwbinet/public_html/moodle1/blocks/social_activities/block_social_activities.php on line 33

Notice: Undefined property: groupmodeforce in /home/lwbinet/public_html/moodle1/blocks/social_activities/block_social_activities.php on line 34

This error:

(Block db: /home/lwbinet/public_html/moodle1/blocks/db/block_db.php was not readable) there is no file in my new moodle in blocks/db named "block_db.php".

WOW, needless to say, I am not a php specialist.  I have gone to the files specified (when there was one) and found no typos or any thing that even remotely looked suspicious.  I am now at a loss.  This was a clean install all new folders/files. 

After almost 2 years (working as admin at another moodle site) and then having my own, I am wondering if I should just give up and move on perhaps to Claroline or a purchased software?  Anyway....my suggestion is DO NOT TURN ON DEBUG UNLESS YOU ARE A DEVELOPER AND VERY PROFFICIENT AT PHP.   I give up! (and that is very hard for a retired Marine).

Well good luck Martin in your endeavor.

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Gustav W Delius -
It seems that your database was not updated after you installed the new beta. Usually this happens automatically as soon as you visit the admin page. Did you visit the admin page? Did you get any error messages during that update?
Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Daryl Hawes -
"After almost 2 years (working as admin at another moodle site) and then having my own, I am wondering if I should just give up and move on perhaps to Claroline or a purchased software?  Anyway....my suggestion is DO NOT TURN ON DEBUG UNLESS YOU ARE A DEVELOPER AND VERY PROFFICIENT AT PHP.   I give up! (and that is very hard for a retired Marine).


Well good luck Martin in your endeavor."

Was this posted after hours of frustration? In reading this I get the sense that it's a rather extreme response. After all, you were attempting to install a beta version of the program, correct? Beta meaning that problems may occur, please contact the programmers if problems are found. Beta meaning do not use in a production environment. Beta meaning use at ones own risk.

The very first line points out the problem:
Table 'lwbinet_mdle1.mdl_event' doesn't exist. The new calendar code uses a new table "mdl_event". This table was not created on your server for some reason. Did you visit the admin page and run through the sql updates before trying to access your site?
Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Martin Dougiamas -
Nutzerbild von Core developers Nutzerbild von Documentation writers Nutzerbild von Moodle HQ Nutzerbild von Particularly helpful Moodlers Nutzerbild von Plugin developers Nutzerbild von Testers
This is all very unusual, Charil ... I agree with Gustav that you might not have visited the admin page somewhere along the way (the install and upgrade instructions explain this) ...
Mittelwert: -
Als Antwort auf Martin Dougiamas

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

Guys,

1.  This was posted after 20 hours of "debugging".  Yes I visited the admin page, there was only one error as explained in the post "1.3 BLOCK problem". 

Block db: /home/lwbinet/public_html/moodle1/blocks/db/block_db.php was not readable    (NOTE:  this file does not exist).

2.  When I originally installed this 1.3 version I was unable to log into my site.....see "1.3 beta error" postings and what I had to do to finally get that fixed.  (Martin you received an email from me about not being able to log in.)

3.  This was a clean install, I made a folder "new moodle" FTP'd everything over, so the problem does not lie in the mixing of old and new versions.

4.  I was looking for answers on "no site logs" as I have not had any since upgrading to 1.2 nor have I been able to grade any assignments as I keep getting the message "no students enrolled in this course" although there definately are students and I have had to get the students to email me the assignments now.

5.  This is my 3rd upgrade, I have a copy of the installtion instructions for each on my computer so that I can do each step as I install...which I have followed EXACTLY.

Frustration?  I would say so.  I have ended up spending most of my time searching for answers to these problems and fixing lots of typos in php instead of spending time working with my students or working on courses still to be posted.  This may seem a bit extreme to some, but please understand it was not hasty.

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Martin Dougiamas -
Nutzerbild von Core developers Nutzerbild von Documentation writers Nutzerbild von Moodle HQ Nutzerbild von Particularly helpful Moodlers Nutzerbild von Plugin developers Nutzerbild von Testers
Hi, Charil.

I understand your frustration, I really do, having been there before with other systems in the past. System administration of all kinds is often a long thankless slog through details, not helped when you aren't familiar with the territory.

I'm pretty sure, though, that the sort of things you're seeing are not Moodle bugs and typos (otherwise everyone else would be reporting them too) ... as you can see there are no such problems on this site, for example.

The problem here is deeper. Your database seems to be missing quite a few columns, and possibly tables.

My first guess was an incorrect upgrade (since the upgrade process is responsible for changing tables).  The timeaccess field was added to user_students on 27th October, 2003, and the event table was added on 17th January 2004.  A normal upgrade from 1.1.1 to 1.2 would have created these.  Perhaps you could tell us your complete upgrade path for this site ... when have you upgraded it?

It could also be a MySQL problem, such as corrupt databases.  Have you tried viewing and repairing the MySQL tables? You can do this using phpmyadmin (including the Moodle MySQL module available from the download page).

Finally, you can try this ... go into your "config" table (with phpmyadmin), find the entry for "version" and edit the number in there to be 2004011600 - save it and then immediately visit the admin page.  You should see lots of once-off errors as Moodle tries to redo lots of the upgrade, but I think once it's finished you should be back on track.
Mittelwert: -
Als Antwort auf Martin Dougiamas

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

Martin,

I did the upgrade to 1.3 beta day before yesterday.  I downloaded from moodle/download then click the Reston, VA.  on the redirect for the download.  Then I created a folder named "new moodle" and ftp'd everything there.  Then I did a data dump so not to lose all my classes and copied the config.php from "moodle1" to "new moodle" and then uploaded my data dump. Then renamed moodle1 to "old moodle" and renamed "new moodle" to "moodle1".

My page came up fine, but I was unable to log in....after 13 hours of debugging and then trying to remove blank lines in config.php (with 5 different word processors) unsuccessfully, I ended up having to do a moodle db from fantastico in an empty db for a new copy of config.php, after editing for the "new moodle" and then deleting the extra db, I was able to log in. When I went to admin I only received the 1 error (blocks). 

Yes I did the mysql db repair yesterday afternoon.  The messages for all modules listed OK, but again this morning, I have no logs and no assignments, and "no students enrolled in course."

I did the go into your "config" table (with phpmyadmin), find the entry for "version" and edit the number in there to be 2004011600 - save it and then immediately visit the admin page. 

WARNING!!! The code you are using is OLDER than the version that made these databases!

Block db: /home/lwbinet/public_html/moodle1/blocks/db/block_db.php was not readable

I will just start from scratch again...perhaps this time it will work. 

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

I found out why there was the block error, thanks to a very helpful gentleman.

Ref:  http://moodle.org/mod/forum/discuss.php?d=7866#37598

But I still have this error: 

WARNING!!! The code you are using is OLDER than the version that made these databases!

I am doing a fresh install at this very moment...perhaps this time the db will update properly.

Thank you everyone, and please forgive my frustration.

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Martin Dougiamas -
Nutzerbild von Core developers Nutzerbild von Documentation writers Nutzerbild von Moodle HQ Nutzerbild von Particularly helpful Moodlers Nutzerbild von Plugin developers Nutzerbild von Testers
Are you sure you typed 2004011600 ? One needs to exact about these things - did you add a digit accidentally (eg 20040116000 would cause a warning like you describe)

The fact that you have (or have had) some mixed up versions of Moodle files is almost certainly the reason for the upgrading problems you are having - but I think if you can get a clean set of files and reset this version number you should be OK.

I see you are using cpanel.  I would recommend uploading the latest .tgz version as one file and then unpacking it on the server using the Cpanel File Manager.
 
Mittelwert: -
Als Antwort auf Martin Dougiamas

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

Martin,

Yes I typed it exactly....I just got a fresh copy from CVS, and I am ftp-ing it now to a new folder on Cpanel.

Thank you...I will let you know how this turns out.

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

OK here goes.... I did a fresh download of 1.3 beta and used CVS Checkout.  I then ftp'd the whole thing to my Cpanel renamed moodle1 to "oldmoodle" and the new file to "moodle1".  I copied the config.php making sure I had the proper version as per Martin.  I then copied "mytheme" into moodle1.

I logged in, went to admin and this is the message I got:

Upgrading Moodle database from version 2004051100 to 2004051300...

Database was successfully upgraded

I thought great!!! it worked, woohoo! yippee!  Then I checked to see if the assignments, logs, and teachers  were working...this is the messages I received....

No logs found!

There are no assignments

No existing teachers

So, of course I turned on the debug  (uh oh) and round and round we go again...LOL.  This time, I think I will search until I found an answer for each one of these 20 debug errors until I drop.  I have decided that these errors are not going to defeat me, I will prevail and hopefully through this someone else may be helped as well.

I will give you guys an update as I fix each error, and exactly what I did to repair them.

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Martin Dougiamas -
Nutzerbild von Core developers Nutzerbild von Documentation writers Nutzerbild von Moodle HQ Nutzerbild von Particularly helpful Moodlers Nutzerbild von Plugin developers Nutzerbild von Testers
Charil, if you had done what I said with the version number in the database you would not have seen the message you reported:

Upgrading Moodle database from version 2004051100 to 2004051300...

you would have seen this instead:

Upgrading Moodle database from version 2004011600 to 2004051300...

(and then lots of once-off errors underneath, which are fine to ignore in this case)

Also, I suggested using the nightly download because your CVS might also be having problems, and this would eliminate that extra possibility.
Mittelwert: -
Als Antwort auf Martin Dougiamas

Re: 1.3 Beta Debug Errors

von W Page -
Hello All!

Two things.

THING 1 / PROBLEM

I am having a similar problem outlined at,
Problem with verion update (should have said "version")
http://moodle.org/mod/forum/discuss.php?d=7927

Module "forum" (2004031000) could not be installed. It requires a newer version of Moodle (currently you are using 2004022400, you need 2004031000).

I had been attempting an update fron v1.2b to 1.2.1stable.

I followed Martin's advice about changing the version in the config table.
2004022400 to 2004031000

Now I am getting this message,
WARNING!!! The code you are using is OLDER than the version that made these databases!

When I checked the version on the Admin page I saw this,
Moodle 1.2 Beta (2004031000)

Bewildering to me.

Can this be fixed without a complete reinstall??

THING 2 / MARTIN TAUGHT ME SOMETHING NEW AGAIN.

I did not know that I could upload a "TAR.GZ" file and decompress it using CPanel. This really made my day since I would prefer doing this than decompressing and then FTPing all the files of an entire site up to the server. Much less time consuming.

The site I refer to in "Thing 1" does not have SSH but it does provide CPanel. I have been looking in the file manager part of CPanel but I cannot see where and how I can decompress a file on the server.

Martin! can you give me a hint as to where to look so I can begin to use this feature.

Thanks in advance.

WP1
Mittelwert: -
Als Antwort auf W Page

Re: 1.3 Beta Debug Errors

von Charil Ferrell -
I just went to my Cpanel to search for the decompression issue....(we have an excellent how to's video for cpanel issues) all you have to do is click the file you want to decompress and on the far right at the top there are a list of commands just click "unzip" or "decompress".
Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von W Page -
Charil and Martin,

Thanks!

I FTPed the file to the server then went to CPanel and decompressed it vi the "File Manager".

Really neat and a great time saver.

Do either of you know if CPanel also has a kind of transloader abilty similar to SSH where I can call down a script directly to a server and, therefore, not have to download it to the pc first?

If not is there a script I can install which can do this for me?

Thanks again.

WP1
Mittelwert: -
Als Antwort auf Martin Dougiamas

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

Martin,

I did do the CVS nightly download , and I also did the 2004011600 version.php in moodle.

I also believe there is something wrong with my CVS as no matter how I do this I keep getting older version files.  I decided to delete my CVS Turtoise and reinstall.

I am certain that this is not a Moodle issue now...I installed a new moodle again through fantastico on a different db and everything works on it...this tells me that my 1.3 beta is corrupted through the CVS.

Thanks again

Mittelwert: -
Als Antwort auf Martin Dougiamas

Re: 1.3 Beta Debug Errors

von Charil Ferrell -

Martin,

1.  Just to make sure I did it exactly as you described...this morning I again got a copy of CVS nightly version  (moodle-latest) and downloaded it to my computer. 

2.  I ftp'd the zipped file to my Cpanel.

3.  Extracted the files on Cpanel.

4.  Copied  version.php (2004011600) and a copy of mytheme to the new moodle folder. 

5.  Edited config-dist.php renamed config.php

6.  Renamed the corresponding folders as necessary.

7.  Went to site, logged in, went to admin.

8.  Received this message: 

Backup version is now 2004051300

Database was successfully upgraded

OK, then I went to see if the previous problems still existed:

No logs found!

There are no assignments

So again I turned on debug and I have the exact same error messages.

Now I have upgraded this database 4 times in the last 3 days with the same results.

I think I will just delete everything except my data files and re-install via Fantastico then upload my data.  At least I know that 1.2.1 version in Fantastico works.

Mittelwert: -
Als Antwort auf Charil Ferrell

Re: 1.3 Beta Debug Errors

von Martin Dougiamas -
Nutzerbild von Core developers Nutzerbild von Documentation writers Nutzerbild von Moodle HQ Nutzerbild von Particularly helpful Moodlers Nutzerbild von Plugin developers Nutzerbild von Testers
The problem here is the step where you are editing version.php  ... that's not what you should be doing.

Here's how to update the version in the database:

  1. In Cpanel, click on MySQL databases.
  2. On that page click on "phpmyadmin" (down the bottom usually)
  3. Select the correct active Moodle database from the left
  4. Click on "config" to see that table
  5. Click on "Browse" to see all the records in that table
  6. Click on the little edit symbol next to the entry with "version" in the name column
  7. Change the number to 2004011600 and then hit "Go" to save it.
  8. NOW go to the admin page in Moodle.

Mittelwert: -
Als Antwort auf Charil Ferrell

1.3 Beta - Learning & Loving it!

von John Gone -
Glad to see you haven't given up, yet. This is a very helpful and supportive community and there aren't many "quitters" around here. Moodle users don't leave anyone behind and nobody drowns here unless they want to.

Your background in evangelism and the marines have taught you to persevere. This background has likely also taught you to step back and catch your breath and compose yourself before the next campaign as a clear head is critical if you're going to be effective.

Quote:
"After almost 2 years (working as admin at another moodle site) and then having my own, I am wondering if I should just give up" .

 Nah, relax, it'll work fine. Think of all the added experience you're gaining and the wonderful opportunity for documentation of the issues you've been faced with during this learning experience.

Good Luck, eh
Mittelwert: -
Als Antwort auf John Gone

Re: 1.3 Beta - Learning & Loving it!

von Charil Ferrell -

Thank you for the encouragement Captian John.

When get this worked out I know that this will eventually help another person with similar problems.

Mittelwert: -