-
-
Notifications
You must be signed in to change notification settings - Fork 404
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
Error after re-running setup: "Your database schema is not up-to-date!" #916
Comments
I have the same issue on a clean install on CentOS 7 |
Well I have no idea where the issue comes from. You might wish to see if the GIT version of PartKeepr works and report back |
@JelleDijkhuizen can you check what Also which database system are you using? MySQL or PostgreSQL? |
ALTER TABLE TempUploadedFile CHANGE originalname originalname VARCHAR(255) DEFAULT NULL, CHANGE extension extension VARCHAR(255) DEFAULT NULL; and i'm running 10.2.10-MariaDB-log MariaDB Server |
@JelleDijkhuizen it seems that setup did not, for some reason, update the tables. Make a database backup and you run If you re-run
If it still lists lots of fields, I think I have to report an upstream issue against doctrine. |
Mmm wierd. I executed the command it tels me: Database schema updated successfully! "34" queries were executed but then when I recheck still the same output. |
@andreaslink-de the message is completely different, can you create a separate issue for that? @JelleDijkhuizen it seems like doctrine decides that the database schema doesn't match the configuration, as such that might be the root cause. I will try to reproduce the issue and create an upstream bug report |
Yes, of course, but this was just an info-add-on. The main issue is still the same as I was just following your suggestion to update the table. |
@andreaslink-de no, I believe that these particular events are not logged. You could try to restart your webserver, sometimes APC caches metadata and restarting the webserver helps. |
@FELICITUS Yes, that fixed it! I restarted MySQL and Apache2, now the issue is fixed for me. I can login without database schema pop-up! |
I'm getting similar results to @JelleDijkhuizen. If I run
Then if I run
I've restarted my server and run the commands again, but I still have the 'schema not up-to-date' error (PartKeepr version in my original post.) Chris |
I did some digging in the database but the changes are written to the database. So my quastion at thius point is: this warning does it come from a database check or a check with the command php app/console doctrine:schema:update --dump-sql ? |
I ran into the same problem trying to run partkeepr 1.3.0 attached to a mariadb 10.3 image. It turns out that there is a compatibility problem between mariadb 10.3 and doctrine 2.5. See also this bug report: |
It looks like the bug you @phuebner mentioned is fixed in doctrine. |
@mindsolve as far as I can tell there's no backport to the doctrine 2.5 series, so no, an update is not possible without upgrading the whole Symfony2 environment, which is a huge effort right now. As I'm the only PartKeepr developer, this will most likely take quite a long time. |
I have the same problem by running partkeepr on my Synology NAS. Everything works Ok on installation but I have this message every time I enter into the system. My default PHP is 5.6 running under Apache 2.2. If I run "php app/console doctrine:schema:update --force" I get the message: PHP Fatal error: Call to undefined function Zend\Code\Reflection\token_get_all() in /volume1/web/test/vendor/zendframework/zend-code/src/Reflection/MethodReflection.php on line 230 Fatal error: Call to undefined function Zend\Code\Reflection\token_get_all() in /volume1/web/test/vendor/zendframework/zend-code/src/Reflection/MethodReflection.php on line 230 If I run "php56 app/console doctrine:schema:update --force" I get this one: [Exception] I don't know at all How to install php-ldap (that on php.ini is active) for this php56 version on Synology... or, in any case, how to install/activate Tokenizer for php The problem is that there is two different compilations of php on the system, one of them in the usual folder of a linux system, and another one in the @appstore folder.... My MYSQL distribution is MariaDB 10.3 Any one has any idea about how to solve this??? Thanks a lot in advance |
I run it with php 7.0 on a Synology nas. Maybe that will solve your issue? |
I tried with php 7.0 also, with the same problem... No ldap-mod...
El mar., 6 nov. 2018 23:09, HendriXML <notifications@github.com> escribió:
… I run it with php 7.0 on a Synology nas. Maybe that will solve your issue?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#916 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ40MJ25zVQe961-xFfchsfp9KN4WMj3ks5usgingaJpZM4P9xxi>
.
|
Are you shure the right ini is used. There is a way to let php report it. Did you also run the commandline “php70” instead of just “php”? I remember to have issues there. I made a ini myself because I couldn’t find the ini files, the webserver uses. Those determine which modules are loaded. |
From my notes on how to run cron-job:
Add to ini:
Command to run the cronjob
|
Thanks a lot HendriXML, it worked for me so now I can run the app/console
doctrine:schema:update --force with the result:
Updating database schema...
Database schema updated successfully! "34" queries were executed
But still, when I log-in onto partkeepr I have the message:
Your database schema is not up-to-date! Please re-run setup immediately!
So I don't know if I have to restart all services (Apache, WebStation,
MariaDB...). I will try..
Many thanks for your comments, now I have a much better idea about how the
system is working..
Manuel
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Libre
de virus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
El mar., 6 nov. 2018 a las 23:30, HendriXML (<notifications@github.com>)
escribió:
… From my notes on how to run cron-job:
cp /usr/syno/etc/packages/WebStation/php70/php.ini
/usr/local/bin/PartKeeprCli.ini vi /usr/local/bin/PartKeeprCli.ini
Add to ini:
``
extension_dir = ***@***.***/PHP7.0/usr/local/lib/php70/modules
extension = ldap.so
extension = pdo_mysql.so
[pdo_mysql]
pdo_mysql.default_socket = /run/mysqld/mysqld10.sock
``
/usr/local/bin/php70 -c /usr/local/bin/PartKeeprCli.ini
/volume1/web/Partkeepr/app/console partkeepr:cron:run
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#916 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQ40MCxXSxl8iWVS6LsPIMJLzwVL__BJks5usg2jgaJpZM4P9xxi>
.
|
Great! Have you tried rerunning the setup? I too get the message of the database schema not beeing up to date, but that was -I think- after I deleted al the standard Footprints. I ran setup afterwards and they where inserted again, but I guess the check also checks wether the auto increment id’s are as to be expected from a “fresh table”. They are however the second time higher. The moral of the story is: some checks may be to sensitive. Like not every criteria can be checked by running it’s fixer. Maybe I will fix my issue by hand, maybe I will leave it as it is. Maybe I will search for the check and disable it. I haven’t made up my mind about it. |
PartKeepr is not fully compatible with 10.3 partkeepr/PartKeepr#916 (comment).
I think this is a duplucate of #1050 and similar threads originating in the too old symphony framework. Thus closing. |
System Information
I've had PartKeepr working on an Ubuntu 16.04 server for a few days and I've started adding parts to it without any issues. Today I added an Octopart API key to parameters.php, and then re-run setup which proceeded without any errors or warnings. I then restarted the server.
Now when I log in to PartKeepr I get the error "Your database schema is not up-to-date! Please re-run setup immediately!"
I re-run setup again, and the setup page 2/2 was all green ("Database successfully install/updated", "Database schema successfully migrated", etc), but after completing setup I still get the warning that my database schema is not up-to-date.
Here's my system information:
Please let me know if there's any other information you require.
Thanks for your continued work on PartKeepr.
Chris
The text was updated successfully, but these errors were encountered: