Subtle issues with CMS can arise from old versions of libraries or supporting software. Please ensure you are running the minimum versions of each dependency (described in Dependencies).
In the next sections we list some known symptoms and their possible causes.
Symptom. Error message “Cannot determine OID of function lo_create”
Possible cause. Your database must be at least PostgreSQL 8.x to support large objects used by CMS.
Symptom. Exceptions regarding missing database fields or with the wrong type.
Possible cause. The version of CMS that created the schema in your database is different from the one you are using now. If the schema is older than the current version, you can update the schema as in Updating CMS. If this fails, and you do not care about the content of the database, the following commands will erase all content, clear the schema and rebuild it.
python cms/db/SQLAlchemyAll.py redrop
python cms/db/SQLAlchemyAll.py
Symptom. Message from ContestWebServer such as: WARNING:root:Invalid cookie signature KFZzdW5kdWRlCnAwCkkxMzI5MzQzNzIwCnRw...
Possible cause. The contest secret key (defined in cms.conf) may have been changed and users’ browsers are still attempting to use cookies signed with the old key. If this is the case, the problem should correct itself and won’t be seen by users.
Symptom. Ranking Web Server displays wrong data, or too much data.
Possible cause. RWS is designed to handle groups of contests. If you want to delete the previous data, run it with the `-d` option. See RankingWebServer for more details
Symptom. Ranking Web Server misbehaving
Possible cause. Ensure you are running Tornado 2.0 or higher. (see issue #2)
Symptom. The freopen test fails.
Possible cause. Add the dup3 syscall to the allowed list.
Symptom. Importing a contest with ContestImporter fails.
Possible cause. The contest was imported with a previous version of CMS. Wait for us to provide update scripts for exports, or contact us for the fast solution.
Symptom. ResourceService keeps restarting its services.
Possible cause. As stated in the README, a reason for this could be that the “process_cmdline” in the configuration isn’t suited to your system. To find the one that suits you, you can run a service by hand (for example cmsLogService), then run ps aux and search for a process that looks like /usr/bin/python2 /usr/local/bin/cmsLogService. The “process_cmdline” corresponding to this would be ["/usr/bin/python2", "/usr/local/bin/cms%s", "%d"]. This value is the default one and should work well on most Ubuntu systems, but for example on some Gentoo systems you may need to use ["/usr/bin/python2.7", "/usr/bin/cms%s", "%d"].