Simple Machines Community Forum

SMF Support => Server Performance and Configuration => Topic started by: ozbob on May 30, 2019, 03:44:54 PM

Title: Broken SMF forum on Linux upgrade
Post by: ozbob on May 30, 2019, 03:44:54 PM
Hello,

My forum at https://railbotforum.org/mbs/  has been upgraded to a new Linux 7 server.

This has broken the forum.

I am getting this error.

(https://ozrecover.net/images/misc/dberror.jpg)

Can you advise how to proceed please?

Thanks.

Bob

Title: Re: Broken SMF forum on Linux upgrade
Post by: vbgamer45 on May 30, 2019, 03:50:50 PM
Open /etc/my.cnf
Change sql_mode
To
sql_mode = ""


Then restart mysql
Title: Re: Broken SMF forum on Linux upgrade
Post by: ozbob on May 30, 2019, 03:56:52 PM
Thanks.  I am not sure how to do that.
Title: Re: Broken SMF forum on Linux upgrade
Post by: Illori on May 30, 2019, 04:05:10 PM
did you upgrade the server? do you manage the server, if the answer is no, contact your host.
Title: Re: Broken SMF forum on Linux upgrade
Post by: ozbob on May 30, 2019, 04:08:25 PM
Thanks.  No I did not do the upgrade.  Will go back to my host.
Title: Re: Broken SMF forum on Linux upgrade
Post by: ozbob on May 30, 2019, 05:50:06 PM
Thanks host effected the change suggested above.

All fine now.

Thank you for the help in resolving the issue.

:)
Title: Re: Broken SMF forum on Linux upgrade
Post by: vbgamer45 on May 30, 2019, 05:50:31 PM
Glad all is working!
Title: Re: Broken SMF forum on Linux upgrade
Post by: LiroyvH on May 31, 2019, 08:51:14 PM
Actually that looks like it may be a bug. If it is: one we should probably address if reasonably possible. Encountered it before but forgot about it.
Disabling such mySQL modes is reasonable for a short-term solution, but I don't think it ought to be long-term. Not a huge problem/major concern, but all the same. Would save some trouble too.
Title: Re: Broken SMF forum on Linux upgrade
Post by: albertlast on June 01, 2019, 12:42:34 AM
Well the base issue is here that the query are "broken",
this broken queries got fixed in smf 2.1 to get work.

this took some time...

but the funny thing is,
the most of the quries got already fixed in 2.0.x but only for postgres