osTicket Basic Installation Error

shenulal

Hi,
I’m new to osTicket, and while trying to configure it, I encountered the following error:
"core: Unknown or invalid schema signature (5fb92bef17f3b603659e024c01cc7a59 .. 76eb6d920994eae1ddfb8e2cae868d0b)"
I’m using MySQL version 8.0.43—could this version be causing the issue? Could you please help me identify and resolve the problem?

Thanks,
Shenulal

KevinTheJedi

shenulal

No, it's saying you are using a schema signature that's not a real osTicket signature - probably a custom version or a mod was applied, etc. You will need to track down where 76eb6d920994eae1ddfb8e2cae868d0b is coming from.

Cheers.

dustinsymes

I am getting this error too. I am using the latest develop code base. I did make some of my own custom modifications to the PHP code (added a bunch of API endpoints) but I did not change the schema signatures anywhere that I can recall. Plus the bad signature matches shenulal's, so highly unlikely that its something I added.

KevinTheJedi

dustinsymes

Do an exact search on Google (wrap the hash with double quotes) and the only place you’ll find the hash is this post. You can also do a search for that hash in the codebase on GitHub and you won’t find it there either (same as the shortened version). So it’s definitely not a core hash.

Now, the hash 5fb92bef17f3b603659e024c01cc7a59 does exist and this is 1.18.x so if your hash is this currently then there is no upgrading needed.

Cheers.

dustinsymes

It is weird for sure. I thought it was odd that two people would get the same, incorrect hash in isolation. In my case my environment is not super clean, that is on me. My database was started with a docker container on a 1.17.2 version. Then I dropped the database and started again before installing with the latest code from the develop branch on github. I have a theory that the docker container may have affected the database somewhere along the way. I managed to update my core.sig file and added a patch file to my code base to get rolling which has allowed me to get past the problem. I can do more investigating if it would help but since I am running probably not worth digging much deeper unless more people start having issues.