Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

core: Unknown or invalid schema signature #511

Closed
StaNov opened this issue Feb 1, 2014 · 15 comments
Closed

core: Unknown or invalid schema signature #511

StaNov opened this issue Feb 1, 2014 · 15 comments
Labels

Comments

@StaNov
Copy link

StaNov commented Feb 1, 2014

I just downloaded latest version (1.8.0.2) and uploaded it to my webhosting.

The installation keeps telling me this:

core: Unknown or invalid schema signature (6de40a4d5bad7a2923e769a4db1ff3b9 .. 833a0f36e10d073fb9e7fb3c8db4e8ef)

snmek obrazovky pozen 2014-02-01 13 20 24

Running:  
PHP 5.3
MySQL 5.6.14

I have googled solution for osticket 1.7, but it was not suitable for me.

Thanks for help.

@greezybacon
Copy link
Contributor

This generally happens when you upload osTicket to a Windoze server via FTP in ASCII mode. If that's the case for you, re-upload the files in binary mode

@StaNov
Copy link
Author

StaNov commented Feb 1, 2014

That worked. Thanks a lot 👍

@angelleye
Copy link

Hmmm...I'm getting this on Windows, but I used git clone. Any idea why that wouldn't work for me?

Seems to have worked fine when I downloaded the zip and extracted manually.

@greezybacon
Copy link
Contributor

Re-upload the files with your FTP client set to BINARY mode

@angelleye
Copy link

I didn't upload or use FTP. I used Git clone.

@greezybacon
Copy link
Contributor

It's a newline issue with the files. Perhaps you git is configured strangely where it isn't honoring the file formats in the upstream repo

@vikas-DabKick
Copy link

I downloaded it as zip and installed as per procedure no problem has occured.. but when I tried to install using a cloned copy I faced this problem

download the code as a zip file and unzip and try to install.

@ntozier
Copy link
Contributor

ntozier commented May 26, 2016

@vikas-DabKick cross posting. Naughty.
I'm quite sure that you did not download 1.8.0.2 since it has not been available for download at osticket.com/download for around 2 years now. Please download current from http://osticket.com/download and try again.

@amitarunabh
Copy link

Just change the second part of signatures in the file-
include\upgrader\streams\core.sig

@stamminator
Copy link

Just change the second part of signatures in the file-
include\upgrader\streams\core.sig

This worked for me. I pasted in the second signature that it was failing to match against. I truly have no clue what I'm doing, but hey, "it worked"!
¯\_(ツ)_/¯

@JediKev JediKev closed this as completed Jan 6, 2020
@andriitukai
Copy link

Just change the second part of signatures in the file-
include\upgrader\streams\core.sig

This worked for me. I pasted in the second signature that it was failing to match against. I truly have no clue what I'm doing, but hey, "it worked"!
¯_(ツ)_/¯

that worked, thanks

@ghost
Copy link

ghost commented Feb 22, 2022

I downloaded it as zip and installed as per procedure no problem has occured.. but when I tried to install using a cloned copy I faced this problem

download the code as a zip file and unzip and try to install.

same for me.

@JediKev
Copy link
Contributor

JediKev commented Feb 22, 2022

@augustineashal

I assume that when you cloned the repo you did not switch to the appropriate branch. In this case you'd clone it and use the 1.16.x branch as this contains the latest release v1.16.1.

Cheers.

@JediKev
Copy link
Contributor

JediKev commented Mar 1, 2023

@sbocel

The Schema Signature is an MD5 hash of the setup/inc/streams/core/install-mysql.sql file. As new database tables and columns are added/modified/removed the aforementioned file changes so that new installs have the new, updated schema (structure). Naturally, when the file changes the MD5 hash changes. So you can think of it as like a serial number for a specific database schema. Now, with this in mind, we use the Schema Signature to check what your schema is and when you go to upgrade we can see what database patches/tasks need to be ran.

Cheers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

9 participants