Probléme d'initialisation de la base de données

waarpr66
Tags: #<Tag:0x0000775b942fe600>

(hicham khalil) #1

Je souhaite installer waarp R66 sous Windows, j'ai donc téléchargé le paquet waarp-r66-3.0.8-1.windows et j'ai procédé à la configuration et la création de l'instance.
lors de l'initialisation de la base je rencontre le message d'erreur suivant (extrait du fichier server.log)

04/01/2018/15:34:17.663 ERROR [org.waarp.common.database.DbRequest] [main] org.waarp.common.database.DbRequest.select(DbRequest.java:124) : SQL Exception Request:SELECT * FROM CONFIGURATION ERREUR: la relation « configuration » n'existe pas
Position : 16
04/01/2018/15:34:17.667 ERROR [org.waarp.common.database.DbSession] [main] org.waarp.common.database.DbSession.error(DbSession.java:251) : SQLException: ERREUR: la relation « configuration » n'existe pas
Position : 16 SQLState: 42P01VendorError: 0
04/01/2018/15:34:17.671 WARN [org.waarp.openr66.configuration.FileBasedConfiguration] [main] org.waarp.openr66.configuration.FileBasedConfiguration.loadDatabase(FileBasedConfiguration.java:1858) : Database is not yet initiated: run ServerInitDatabase -initdb first
org.waarp.common.database.exception.WaarpDatabaseSqlException: SQL Exception Request:SELECT * FROM CONFIGURATION
at org.waarp.common.database.DbRequest.select(DbRequest.java:128)
at org.waarp.openr66.configuration.FileBasedConfiguration.loadDatabase(FileBasedConfiguration.java:1856)
at org.waarp.openr66.configuration.FileBasedConfiguration.setConfigurationInitDatabase(FileBasedConfiguration.java:2130)
at org.waarp.openr66.server.ServerInitDatabase.main(ServerInitDatabase.java:120)
Caused by: org.postgresql.util.PSQLException: ERREUR: la relation « configuration » n'existe pas
Position : 16
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2455)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:2155)
at org.postgresql.core.v3.QueryExecutorImpl.execute(QueryExecutorImpl.java:288)
at org.postgresql.jdbc.PgStatement.executeInternal(PgStatement.java:430)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:356)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:303)
at org.postgresql.jdbc.PgStatement.executeCachedSql(PgStatement.java:289)
at org.postgresql.jdbc.PgStatement.executeWithFlags(PgStatement.java:266)
at org.postgresql.jdbc.PgStatement.execute(PgStatement.java:262)
at org.waarp.common.database.DbRequest.select(DbRequest.java:120)
... 3 common frames omitted

Pourriez-vous SVP me donner une piste pour résoudre ce problème ?


(Maxime Robert) #2

Bonjour,

Ceci n'est pas une erreur à proprement parler. Au lancement du serveur WaaprR66 vérifie si la base est bien initialisée.
Cependant cette vérification est aussi faite à l'initialisation de la base.

Votre base est normalement correctement initialisée malgré le message d'erreur.

Cette erreur va être corrigée rapidement et le patch sera disponible bientôt.


(hicham khalil) #3

Bonjour,

Je vous merci pour votre retour.

Malgré les tests que j’ai effectués je n’arrive toujours pas réussi à démarrer mon instance.
J’ai viens de refaire une création d’une nouvelle base vierge et j’ai suivi la documentation de l’installation sur (https://doc.waarp.org/waarp-r66/latest/fr/installation/instance-creation.html)
J’ai donc lancé l’initialisation de la base via la commande «bin\waarp-r66server.bat EAI initdb » puis j’ai essayé de démarrer mon instance comme décrit sur le document.

Malheureusement cela n’a pas fonctionné, je me demande s’il y a des étapes qui ont été loupées !

C:\waarp-r66-3.0.8-1>bin\waarp-r66server.bat EAI initdb
09:07:47,867 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [C:\waarp-r66-3.0.8-1\etc\conf.d\EAI\logback
-server.xml] at [file:/C:/waarp-r66-3.0.8-1/etc/conf.d/EAI/logback-server.xml]
09:07:48,295 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
09:07:48,320 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.cor
e.rolling.RollingFileAppender]
09:07:48,333 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
09:07:48,407 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1459794865 - Will use zip compression
09:07:48,410 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1459794865 - Will use the pattern data/EAI/log/server.log.%d{yyyy
-MM-dd}.%i.log for the active file
09:07:48,415 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@69ea3742 - The date pattern is 'yyyy-MM-dd' from file nam
e pattern 'data/EAI/log/server.log.%d{yyyy-MM-dd}.%i.log.zip'.
09:07:48,415 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@69ea3742 - Roll-over at midnight.
09:07:48,422 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@69ea3742 - Setting initial period to Wed Jan 10 09:07:48
GMT 2018
09:07:48,423 |-WARN in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@69ea3742 - SizeAndTimeBasedFNATP is deprecated. Use SizeA
ndTimeBasedRollingPolicy instead
09:07:48,447 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: data\EAI\log\server.log
09:07:48,447 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [data\EAI\log\server.log]
09:07:48,452 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.cor
e.ConsoleAppender]
09:07:48,454 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
09:07:48,456 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.cla
ssic.net.SyslogAppender]
09:07:48,463 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [SYSLOG]
09:07:48,470 |-INFO in ch.qos.logback.classic.net.SyslogAppender[SYSLOG] - Defaulting maxMessageSize to [65000]
09:07:48,477 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - ROOT level set to WARN
09:07:48,477 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT]
09:07:48,478 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
09:07:48,479 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@4b952a2d - Registering current configuration as safe fallbac
k point

CREATE TABLE MULTIPLEMONITOR (COUNTCONFIG INTEGER NOT NULL , COUNTHOST INTEGER NOT NULL , COUNTRULE INTEGER NOT NULL , HOSTID
VARCHAR(8096) PRIMARY KEY )
CREATE TABLE CONFIGURATION (READGLOBALLIMIT BIGINT NOT NULL , WRITEGLOBALLIMIT BIGINT NOT NULL , READSESSIONLIMIT BIGINT NOT N
ULL , WRITESESSIONLIMIT BIGINT NOT NULL , DELAYLIMIT BIGINT NOT NULL , UPDATEDINFO INTEGER NOT NULL , HOSTID VARCHAR(8096) PRI
MARY KEY )
CREATE TABLE HOSTCONFIG (BUSINESS TEXT NOT NULL , ROLES TEXT NOT NULL , ALIASES TEXT NOT NULL , OTHERS TEXT NOT NULL , UPDATE
DINFO INTEGER NOT NULL , HOSTID VARCHAR(8096) PRIMARY KEY )
CREATE TABLE HOSTS (ADDRESS VARCHAR(8096) NOT NULL , PORT INTEGER NOT NULL , ISSSL BOOLEAN NOT NULL , HOSTKEY BYTEA NOT NULL
, ADMINROLE BOOLEAN NOT NULL , ISCLIENT BOOLEAN NOT NULL , ISACTIVE BOOLEAN NOT NULL , ISPROXIFIED BOOLEAN NOT NULL , UPDATEDI
NFO INTEGER NOT NULL , HOSTID VARCHAR(8096) PRIMARY KEY )
CREATE TABLE RULES (HOSTIDS TEXT , MODETRANS INTEGER , RECVPATH VARCHAR(8096) , SENDPATH VARCHAR(8096) , ARCHIVEPATH VARCHAR(8096
) , WORKPATH VARCHAR(8096) , RPRETASKS TEXT , RPOSTTASKS TEXT , RERRORTASKS TEXT , SPRETASKS TEXT , SPOSTTASKS TEXT , SERRORTASKS
TEXT , UPDATEDINFO INTEGER , IDRULE VARCHAR(8096) PRIMARY KEY )
CREATE TABLE RUNNER (GLOBALSTEP INTEGER NOT NULL , GLOBALLASTSTEP INTEGER NOT NULL , STEP INTEGER NOT NULL , RANK INTEGER NOT
NULL , STEPSTATUS CHAR(3) NOT NULL , RETRIEVEMODE BOOLEAN NOT NULL , FILENAME VARCHAR(8096) NOT NULL , ISMOVED BOOLEAN NOT NU
LL , IDRULE VARCHAR(8096) NOT NULL , BLOCKSZ INTEGER NOT NULL , ORIGINALNAME VARCHAR(8096) NOT NULL , FILEINFO TEXT NOT NULL ,
TRANSFERINFO TEXT NOT NULL , MODETRANS INTEGER NOT NULL , STARTTRANS TIMESTAMP NOT NULL , STOPTRANS TIMESTAMP NOT NULL , INFO
STATUS CHAR(3) NOT NULL , UPDATEDINFO INTEGER NOT NULL , OWNERREQ VARCHAR(8096) NOT NULL , REQUESTER VARCHAR(8096) NOT NULL ,
REQUESTED VARCHAR(8096) NOT NULL , SPECIALID BIGINT NOT NULL , CONSTRAINT runner_pk PRIMARY KEY (OWNERREQ,REQUESTER,REQUESTED,
SPECIALID))
CREATE INDEX IDX_RUNNER ON RUNNER (STARTTRANS, OWNERREQ, STEPSTATUS, UPDATEDINFO, GLOBALSTEP, INFOSTATUS, SPECIALID)
CREATE SEQUENCE RUNSEQ MINVALUE -9223372036854775807 START WITH -9223372036854775807
End creation
End upgrade
Load done

C:\waarp-r66-3.0.8-1>bin\waarp-r66server.bat EAI start
"Starting Waarp R66 Server... "
09:08:22,920 |-INFO in ch.qos.logback.classic.LoggerContext[default] - Found resource [C:\waarp-r66-3.0.8-1\etc\conf.d\EAI\logback
-server.xml] at [file:/C:/waarp-r66-3.0.8-1/etc/conf.d/EAI/logback-server.xml]
09:08:23,381 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - debug attribute not set
09:08:23,403 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.cor
e.rolling.RollingFileAppender]
09:08:23,419 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [FILE]
09:08:23,537 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1225439493 - Will use zip compression
09:08:23,539 |-INFO in c.q.l.core.rolling.TimeBasedRollingPolicy@1225439493 - Will use the pattern data/EAI/log/server.log.%d{yyyy
-MM-dd}.%i.log for the active file
09:08:23,546 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@56ac3a89 - The date pattern is 'yyyy-MM-dd' from file nam
e pattern 'data/EAI/log/server.log.%d{yyyy-MM-dd}.%i.log.zip'.
09:08:23,546 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@56ac3a89 - Roll-over at midnight.
09:08:23,553 |-INFO in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@56ac3a89 - Setting initial period to Wed Jan 10 09:07:49
GMT 2018
09:08:23,554 |-WARN in ch.qos.logback.core.rolling.SizeAndTimeBasedFNATP@56ac3a89 - SizeAndTimeBasedFNATP is deprecated. Use SizeA
ndTimeBasedRollingPolicy instead
09:08:23,592 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - Active log file name: data\EAI\log\server.log
09:08:23,592 |-INFO in ch.qos.logback.core.rolling.RollingFileAppender[FILE] - File property is set to [data\EAI\log\server.log]
09:08:23,594 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.cor
e.ConsoleAppender]
09:08:23,597 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [STDOUT]
09:08:23,600 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - About to instantiate appender of type [ch.qos.logback.cla
ssic.net.SyslogAppender]
09:08:23,603 |-INFO in ch.qos.logback.core.joran.action.AppenderAction - Naming appender as [SYSLOG]
09:08:23,612 |-INFO in ch.qos.logback.classic.net.SyslogAppender[SYSLOG] - Defaulting maxMessageSize to [65000]
09:08:23,620 |-INFO in ch.qos.logback.classic.joran.action.LevelAction - ROOT level set to WARN
09:08:23,620 |-INFO in ch.qos.logback.core.joran.action.AppenderRefAction - Attaching appender named [FILE] to Logger[ROOT]
09:08:23,622 |-INFO in ch.qos.logback.classic.joran.action.ConfigurationAction - End of configuration.
09:08:23,623 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@27c20538 - Registering current configuration as safe fallbac
k point

Cannot start Server OpenR66 for EAI
"done"

C:\waarp-r66-3.0.8-1>


(Maxime Robert) #4

Je n'ai pas tout le détails sans les logs.
Cependant il me semble que vous n'avez pas chargé la base avec les données d'authentification de l'instance locale.
Il faut que vous créez un fichier authent.xml et que vous le chargez en base via la commande C:\waarp-r66-3.0.8-1>bin\waarp-r66server.bat EAI loadauth (ou loadconf qui charge l'authentification et les règles de transfert))

A noter que pour utiliser WaarpR66 il vous faut 2 instances connaissant leur authentification respective ce qui se traduit par un fichier authent.xml avec 2 entrées (l'authent de l'instance local et celle de l'instance distante). Ainsi qu'une règle de transfert en commun via le fichier rule.xml. Ces 2 fichiers doivent être chargé en base de données via la commande C:\waarp-r66-3.0.8-1>bin\waarp-r66server.bat EAI loadconf.

La documentation va être mise à jour.