Since last week my virtual airline can not receive flights reports because the PIREPS function stopped working by surprise (manually or through smartCARS).
I tried reinstalling the PIREPS module, the classes files and the whole site using the last version of phpVMS available but it does not work either.
I contacted my hosting provider and after some tests they told me it could be a problem compatibility with MariaDB. Last Wednesday they updated their servers, including MariaDB, since then I have this issue.
Hi , it’s set to 5.6 but it does not work either. Acoording what my hosting provider said, this could be an imcopatibily problem with MariaDB. I tested phpVMS with 000webhost (With php 7.0 and a previews version of mariaDB) and it works perfectely.
It looks like this has hit our airline now. It all started after pilots were not able to file PIREPs with error “There was an error adding your PIREP : Schedule does not exist. Please update this manually.”. As the error made no sence, I googeled for hrs., tried different steps, but nothing has worked so far. I have been contact with our hosting company and they sayd that they performed an update from MariaDB 10.1.38 to 10.3.14. rollback not possible. So it looks like it might be related. I am running phpvms 5.5.x @ http://efb.flying.ee/ with highly customized systems, not really ready to move to phpvms 7 yet. Rest of the site works perfectly, sending PIREPs is impossible.
Is there anyone who can advise what to do further besides rollback or get another hosting company? There has to be a solution from our side as I can imagine that this problem will spread as MariaDB 10.3 is out since 2017?
It looks like this has hit our airline now. It all started after pilots were not able to file PIREPs with error “There was an error adding your PIREP : Schedule does not exist. Please update this manually.”. As the error made no sence, I googeled for hrs., tried different steps, but nothing has worked so far. I have been contact with our hosting company and they sayd that they performed an update from MariaDB 10.1.38 to 10.3.14. rollback not possible. So it looks like it might be related. I am running phpvms 5.5.x @ http://efb.flying.ee/ with highly customized systems, not really ready to move to phpvms 7 yet. Rest of the site works perfectly, sending PIREPs is impossible.
Is there anyone who can advise what to do further besides rollback or get another hosting company? There has to be a solution from our side as I can imagine that this problem will spread as MariaDB 10.3 is out since 2017?
Waiting for a soonest reply.
Is there an error log or possible to get the error from SQL? I was gonna ask what the sql error, etc, might be above this line:
Hi, could you please advise where to get/access the SQL error log? Did not find anything related from cPanel. There was nothing specific on error_log created by phpVMS itself.
Hi, could you please advise where to get/access the SQL error log? Did not find anything related from cPanel. There was nothing specific on error_log created by phpVMS itself.
Unfortunately, you’ll have to edit the code where I pointed out so that you can output the exact message there. Unfortunately, it could just be that the code is just too “old” to support maria properly. As pointed out, though they’re supposed to be compatible, there could still be issues in compat
This is due to strict mode being implemented, I had found a work around by putting INSERT IGNORE for all insert requests. Basically it comes down to the way phpvms stores the date and time of a pirep being filed. Using the INSERT IGNORE will allow the data to be submitted to the db as it ignores any error that is thrown up. It is not the best but for what i can see the only way to work around this problem if you do not have a VPS or dedicated server. As most hosts are reluctant to turn strict mode off.