Difference between revisions of "Known issues"

From TempusServa wiki
Jump to navigation Jump to search
Line 62: Line 62:
   sudo killall -KILL mysqld_safe mysqld
   sudo killall -KILL mysqld_safe mysqld
   
   
If you cannot start MySQL again try cleaning up the logfiles
If you cannot start MySQL again try removing the logfiles


   sudo rm /mnt/sda/mysql/ib_logfile0
   sudo mv /mnt/sda/mysql/ib_logfile0 /mnt/sda/backup/
   sudo rm /mnt/sda/mysql/ib_logfile1
   sudo mv /mnt/sda/mysql/ib_logfile1 /mnt/sda/backup/


===== Warning during server stop =====
===== Warning during server stop =====

Revision as of 14:03, 21 April 2024

The following list describes wellknown issues in Tempus Serva.

Frontend

Certain texts result in error when saving

When saving you get an error that looks like this

 Incorrect string value: '\xC2\x94s\xC3

Your database is in legacy format and needs updating

 main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8
Special characters are not displayed correctly

You might be using an older version of the database that is not using UTF8. This can bo corrected by running this codeunit:

 main?command=dk.p2e.blanket.codeunit.common.PageConvertDatabaseToUTF8
Media files sometimes dont display after a boot

Media files are stored temporaryly within the web application when requested. Depending of the speed of the underlying filesystem, they will not allways be available for the server right away.

  • Workaround: Reload the page (F5)
  • Resolution: Tweak the configuration parameter mediaFilterDelayMS
Upload of files fails after server restart

Sometimes tempoarray folders are not reestablished after the server boots

  • Frontend: Personal menu > Services > Rebuild folders
  • Backend: Modules > Admin services
An error has occured

Sometimes lowlevel tampering with field configuration, or force changing field types will result in this error.

  • Workaround: Deploy solution
  • Resolution
    1. Check which field fails: Modules > Event viewer
    2. Delete field and create again

Designer

References not fixed during restore where components need renaming (solution/bundles)

Workaround: Correct all parent/child references manually and redeploy solution

Solution configurations cannot be set to an empty value

Workaround: Set value to single whitespace " ".

Old backups from other solutions found in list of backups

When deleting solutions the Designer does not delete corresponding backups (saftety reasons).

In the future a list will be implemented to browse older backups, but untill hen you should just ignore this issue.

Engine

No unfixed issues

Conatainer specific

Tomcat

Unable to restart services

Kille the underlying processes for both webserver and database

 sudo killall -KILL tomcat
 sudo killall -KILL mysqld_safe mysqld

If you cannot start MySQL again try removing the logfiles

 sudo mv /mnt/sda/mysql/ib_logfile0 /mnt/sda/backup/
 sudo mv /mnt/sda/mysql/ib_logfile1 /mnt/sda/backup/
Warning during server stop

Example

SEVERE: The web application [/sandbox] registered the JDBC driver [com.mysql.jdbc.Driver] but failed to unregister it when the web application was stopped. To prevent a memory leak, the JDBC Driver has been forcibly unregistered.

The warning is of no importance because the shutdown automatically kills all objects in memory, and no memory leaks are there possible.

JBoss

WARN errors during boot

Example

17:56:40,337 WARN [org.jboss.as.server.deployment] (MSC service thread 1-12) Class Path entry ...

The warnings are due to jar taht have their version number appended to their name. Possible fixes include stripping the names of all jar files in the /WEB-INF/lib/, but recommended solution is ignoring the warnings.