Solved Kunena Internal Error

I recently moved over to a dedicated server. Today, I switched on the forum and was met with an error as you can see below by the screenshot. The silly thing is, I was today going to upgrade to 2 after moving all my websites across to the dedicated server, but I don't want to do this until I find out how to fix this error

So can you please now turn on Debug mode in Kunena, and post the error report along with your Kunena Configuration report. As this is a support question, I will move it to the Support Category.

500 - JDatabaseMySQL::query: 145 - Table './penn1969_ofish/jos_kunena_whoisonline' is marked as crashed and should be repaired SQL=SELECT COUNT(*) FROM jos_kunena_whoisonline WHERE userip='109.145.143.147' AND userid='62'

I'm not sure what you mean by the kunena configuration report, I've never had to do this before, this is the first time I've encountered one of these messages

Unless of course you mean this

Database collation check:

Legacy mode: Enabled | Joomla! SEF: Enabled | Joomla! SEF rewrite: Enabled | FTP layer: Disabled |

This message contains confidential information

htaccess: Exists | PHP environment: Max execution time: 30 seconds | Max execution memory: 128M | Max file upload: 2M

Kunena menu details:

Joomla default template details : rt_catalyst_j15 | author: RocketTheme | version: 1.5.3 | creationdate: 04/29/08

Kunena default template details : Blue Eagle (default) | author: Kunena Team | version: 1.7.2 | creationdate: 2012-01-31

Kunena version detailled: Installed version: 1.7.2 | Build: 5215 | Version name: Omega | Kunena detailled configuration:

Warning: Spoiler!

[th]Kunena config settings:[/th]

board_offline	0
board_ofset	0
enablerss	1
enablepdf	1
threads_per_page	20
messages_per_page	12
messages_per_page_search	15
showhistory	1
historylimit	6
shownew	1
jmambot	0
disemoticons	0
template	default
showannouncement	1
avataroncat	1
catimagepath	category_images/
showchildcaticon	1
annmodid	62
rtewidth	450
rteheight	300
enableforumjump	1
reportmsg	1
username	1
askemail	0
showemail	0
showuserstats	1
showkarma	0
useredit	1
useredittime	0
useredittimegrace	600
editmarkup	1
allowsubscriptions	1
subscriptionschecked	0
allowfavorites	1
maxsubject	50
maxsig	300
regonly	0
changename	1
pubwrite	0
floodprotection	0
mailmod	0
mailadmin	0
captcha	0
mailfull	0
allowavatar	1
allowavatarupload	1
allowavatargallery	1
avatarquality	65
avatarsize	3500
allowimageupload	0
allowimageregupload	0
imageheight	400
imagewidth	600
imagesize	200
allowfileupload	0
allowfileregupload	0
filetypes	zip,txt,doc,gz,tgz
filesize	120
showranking	1
rankimages	0
avatar_src
fb_profile
pm_component
userlist_rows	30
userlist_online	1
userlist_avatar	1
userlist_name	1
userlist_username	1
userlist_posts	1
userlist_karma	1
userlist_email	0
userlist_usertype	1
userlist_joindate	1
userlist_lastvisitdate	1
userlist_userhits	1
latestcategory	0
showstats	1
showwhoisonline	1
showgenstats	1
showpopuserstats	1
popusercount	5
showpopsubjectstats	1
popsubjectcount	5
usernamechange	0
rules_infb	1
rules_cid	104
help_infb	0
help_cid	1
showspoilertag	1
showvideotag	1
showebaytag	1
trimlongurls	1
trimlongurlsfront	40
trimlongurlsback	20
autoembedyoutube	1
autoembedebay	1
ebaylanguagecode	en-us
fbsessiontimeout	1800
highlightcode	0
rss_type	topic
rss_timelimit	month
rss_limit	100
rss_included_categories
rss_excluded_categories
rss_specification	rss2.0
rss_allow_html	1
rss_author_format	name
rss_author_in_title	1
rss_word_count	0
rss_old_titles	1
rss_cache	900
fbdefaultpage	categories
default_sort	asc
alphauserpointsnumchars	0
sef	1
sefcats	0
sefutf8	0
showimgforguest	1
showfileforguest	0
pollnboptions	10
pollallowvoteone	1
pollenabled	1
poppollscount	5
showpoppollstats	1
polltimebtvotes	00:15:00
pollnbvotesbyuser	100
pollresultsuserslist	1
maxpersotext	50
ordering_system	mesid
post_dateformat	ago
post_dateformat_hover	datetime
hide_ip	0
js_actstr_integration	0
imagetypes	jpg,jpeg,gif,png
checkmimetypes	1
imagemimetypes	image/jpeg,image/jpg,image/gif,image/png
imagequality	50
thumbheight	32
thumbwidth	32
hideuserprofileinfo	put_empty
integration_access	jomsocial
integration_login	jomsocial
integration_avatar	jomsocial
integration_profile	jomsocial
integration_private	jomsocial
integration_activity	jomsocial
boxghostmessage	1
userdeletetmessage	0
latestcategory_in	1
topicicons	1
onlineusers	1
debug	0
catsautosubscribed	0
showbannedreason	1
version_check	1
showthankyou	1
showpopthankyoustats	1
popthankscount	5
mod_see_deleted	1
bbcode_img_secure	text
listcat_show_moderators	1
lightbox	1
activity_limit	0
show_list_time	720
show_session_type	0
show_session_starttime	0
userlist_allowed	1
userlist_count_users	1
enable_threaded_layouts	0
category_subscriptions	post
topic_subscriptions	every
pubprofile	0
thankyou_max	10
email_recipient_count	0
email_recipient_privacy	bcc
email_visible_address
captcha_post_limit	0

Third-party components: Jomsocial 2.2.4 | UddeIm 2.0

Third-party SEF components: None

Plugins: System - Mootools Upgrade: Enabled | System - Mootools12: Disabled | My Kunena Forum Menu 1.6.0-RC1 | My Kunena Forum Posts 1.6.0-RC1

Modules: Kunena Latest 1.6.0-RC2 | Kunena Login 1.6.0-RC2

Look at the K 1.7 Support header. You can find your configuration report in the Kunena admin backend. Copy and past the un-edited report in your reply so that the mods and devs can pinpoint the error. Thanks.

EDIT: Crossed-posts

Jiminimonka wrote: Look at the K 1.7 Support header. You can find your configuration report in the Kunena admin backend. Copy and past the un-edited report in your reply so that the mods and devs can pinpoint the error. Thanks.

EDIT: Crossed-posts

have I posted the relevant information?

Yes, thanks.

oscarfishlover: G'day, mate. Great news to hear that you've move your site operations to a dedicated server but not so great news to hear that part of your database has somehow gotten into a tangle.

The first thing to attend to is the crashed table. Although the kunena_whoisonline table is not of terribly significant importance - well, it's not important unless knowing who is online is more important than people being able to actually use the forum is concerned - you should be able to repair or restore table to a "more-or-less" stable state. There's a table repair feature in phpMyAdmin that may do the trick. Obviously, before rolling up your sleeves and delving into places - in other words, MySQL - where the slightest wrongdoing can blast one's website into the great void, I would make sure that I had a very good backup first.

I hope that phpMyAdmin provides you with the solution you need. However, there are a few other matters that require your immediate attention:

(1) You're using several very old (and ill-suited to the current version of Kunena that you're running). You should upgrade immediately:

• My Kunena Forum Menu plugin;
• My Kunena Forum Posts plugin;
• Kunena Latest module;
• Kunena Login module (although, I can't actually see where you're using this on your website ... so you can probably uninstall this module if it's no longer required).

(2) You should seriously consider updating uddeIM and JomSocial

(3) I'm sure you've read it all before but please read the article about Legacy mode . The Kunena project abandoned testing Kunena on J! 1.5 running legacy mode about 2-3 years ago and, for that reason, people who have problems running Kunena on J! 1.5 with legacy mode are pretty much on their own.

(4) For your information, K 1.7.2 was pronounced at end-of-life at the time it was released in January this year. K 1.7.2 continues to be support but all support for K 1.7 will cease as of 31 August this year. K 2.0 has been available for public download for the past couple of months and all our efforts are now directed at this version. We recommend that all members of the Kunena community use whatever opportunities they can to develop and implement their plans to upgrade to K 2.0.

I hope my suggestions (in respect of repairing the database table(s) and upgrading those very old "release candidate" versions of Kunena add-ons) help.

Hey, thanks very much for the reply. I think I'll try the repair feature first. I'm just backing my database up as I type this. Sorry, but what exactly is a feature called, is it called "table repair" or something similar?

Well, that was a lot easier than I was expecting. sorry, before asking the obvious,I should have just gone on the Internet before asking the obvious. But thanks very much, you have saved my day

php.about.com/od/mysqladministration/qt/repair_mysql.htm