This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
docpublic:systemes:esup:esup_socle_4_c6 [2014/07/22 22:14] procacci@tem-tsp.eu [import group] |
docpublic:systemes:esup:esup_socle_4_c6 [2015/05/20 16:10] (current) procacci@tem-tsp.eu [build & config properties] |
||
---|---|---|---|
Line 123: | Line 123: | ||
ensuite, faut-il appliquer ce patch : https:// | ensuite, faut-il appliquer ce patch : https:// | ||
+ | |||
+ | ==== pb LC_COLLATE ==== | ||
+ | |||
+ | suite a une mise a jour a chaud sur le container openvz, apres un redemrrage des services (tomcat, postgres ...) le portail ne marchait plus ! | ||
+ | |||
+ | uPortal.log: | ||
+ | |||
+ | < | ||
+ | [esup4] WARN [main] Jan/09 09: | ||
+ | org.postgresql.util.PSQLException: | ||
+ | Detail: The database was initialized with LC_COLLATE " | ||
+ | Hint: Recreate the database with another locale or install the missing locale. | ||
+ | </ | ||
+ | |||
+ | cette erreure est expliquée sur http:// | ||
+ | |||
+ | où la conclusion est : | ||
+ | |||
+ | < | ||
+ | If PostgreSQL hasn't been restarted after the new locale has been created, that would be the reason. service postgresql restart should suffice. | ||
+ | This is presumably due to how locales are implemented in Linux libc. The new locales don't get seamlessly imported into the environment of already running processes. | ||
+ | </ | ||
+ | |||
+ | donc simplement en redemarrant la VM , tout repart sans soucis ! | ||
+ | |||
+ | ==== acces BD ==== | ||
ouverture acces BD en mode trust (ident par defaut n' | ouverture acces BD en mode trust (ident par defaut n' | ||
Line 816: | Line 842: | ||
+environment.build.ldap.baseDn=dc=int-evry, | +environment.build.ldap.baseDn=dc=int-evry, | ||
+environment.build.ldap.userName=cn=mcibind, | +environment.build.ldap.userName=cn=mcibind, | ||
- | +environment.build.ldap.password=mcianony | + | +environment.build.ldap.password=secret |
| | ||
| |