Debian Buster: Kein Login nach Update auf Version 2.2 mehr möglich

Startseite › Foren › Installation › Debian Buster: Kein Login nach Update auf Version 2.2 mehr möglich

Verschlagwortet: , , , , ,

12 Beiträge anzeigen - 1 bis 12 (von insgesamt 12)
  • Autor
    Beiträge
  • 9. Januar 2023 um 12:16 #5234
    Veraendert
    Teilnehmer

    Die „Klassiker“ habe ich schon angesehen. Zugriff auf die Datenbanken habe ich, mariadb sollte also eigentlich nicht das Problem sein. Touch j-lawyer-server.ear habe ich auch versucht. Aufbau ist Debian-server und gemischte Windows/Linux-client-Architektur.

    Aber trotzden besteht beim Server die feste Überzeugung, dass die Verbindungsdaten falsch seien. Aus dem Fehler werde jedenfalls ich nicht wirklich schlau:

    [code]2023-01-09 12:09:07,126 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 82) exception caught: org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 2.1.0.12 (AddDefaultRoleToContact)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.doValidate(Flyway.java:1467)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.access$100(Flyway.java:82)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1349)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1341)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.execute(Flyway.java:1696)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.migrate(Flyway.java:1341)
    at deployment.j-lawyer-server.ear.j-lawyer-server-entities.jar//org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:732)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)

    2023-01-09 12:09:07,133 INFO [stdout] (ServerService Thread Pool — 81) Starting j-lawyer.org database migrations…
    2023-01-09 12:09:07,183 INFO [org.flywaydb.core.internal.database.DatabaseFactory] (ServerService Thread Pool — 81) Database: jdbc:mysql://localhost:3306/jlawyerdb (MySQL 5.5)
    2023-01-09 12:09:07,589 ERROR [org.jlawyer.persistence.DatabaseMigrator] (ServerService Thread Pool — 81) exception caught: org.flywaydb.core.api.FlywayException: Validate failed: Detected failed migration to version 2.1.0.12 (AddDefaultRoleToContact)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.doValidate(Flyway.java:1467)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.access$100(Flyway.java:82)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1349)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway$1.execute(Flyway.java:1341)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.execute(Flyway.java:1696)
    at deployment.j-lawyer-server.ear//org.flywaydb.core.Flyway.migrate(Flyway.java:1341)
    at deployment.j-lawyer-server.ear.j-lawyer-server-entities.jar//org.jlawyer.persistence.DatabaseMigrator.integrate(DatabaseMigrator.java:732)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:276)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)

    2023-01-09 12:09:12,100 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 81) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@7fe503a
    2023-01-09 12:09:12,102 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 81) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1016)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:942)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    … 9 more
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing column [delete_done] in table [calendar_setup]
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:136)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    … 11 more

    2023-01-09 12:09:12,100 INFO [org.hibernate.orm.beans] (ServerService Thread Pool — 82) HHH10005004: Stopping BeanContainer : org.hibernate.resource.beans.container.internal.CdiBeanContainerExtendedAccessImpl@3f36a129
    2023-01-09 12:09:12,104 ERROR [org.jboss.msc.service.fail] (ServerService Thread Pool — 82) MSC000001: Failed to start service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: org.jboss.msc.service.StartException in service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:198)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:128)
    at org.wildfly.security.elytron-private@1.8.0.Final//org.wildfly.security.manager.WildFlySecurityManager.doChecked(WildFlySecurityManager.java:649)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1.run(PersistenceUnitServiceImpl.java:212)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377)
    at java.base/java.lang.Thread.run(Thread.java:829)
    at org.jboss.threads@2.3.3.Final//org.jboss.threads.JBossThread.run(JBossThread.java:485)
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.persistenceException(EntityManagerFactoryBuilderImpl.java:1016)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:942)
    at org.hibernate.jipijapa-hibernate5-3@16.0.0.Final//org.jboss.as.jpa.hibernate5.TwoPhaseBootstrapImpl.build(TwoPhaseBootstrapImpl.java:44)
    at org.jboss.as.jpa@16.0.0.Final//org.jboss.as.jpa.service.PersistenceUnitServiceImpl$1$1.run(PersistenceUnitServiceImpl.java:170)
    … 9 more
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing column [delete_done] in table [calendar_setup]
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:136)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.GroupedSchemaValidatorImpl.validateTables(GroupedSchemaValidatorImpl.java:42)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.performValidation(AbstractSchemaValidator.java:89)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.internal.AbstractSchemaValidator.doValidation(AbstractSchemaValidator.java:68)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.performDatabaseAction(SchemaManagementToolCoordinator.java:191)
    at org.hibernate@5.3.9.Final//org.hibernate.tool.schema.spi.SchemaManagementToolCoordinator.process(SchemaManagementToolCoordinator.java:72)
    at org.hibernate@5.3.9.Final//org.hibernate.internal.SessionFactoryImpl.<init>(SessionFactoryImpl.java:310)
    at org.hibernate@5.3.9.Final//org.hibernate.boot.internal.SessionFactoryBuilderImpl.build(SessionFactoryBuilderImpl.java:467)
    at org.hibernate@5.3.9.Final//org.hibernate.jpa.boot.internal.EntityManagerFactoryBuilderImpl.build(EntityManagerFactoryBuilderImpl.java:939)
    … 11 more

    2023-01-09 12:09:12,141 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation („deploy“) failed – address: ([(„deployment“ => „j-lawyer-server.ear“)]) – failure description: {„WFLYCTL0080: Failed services“ => {
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing column [delete_done] in table [calendar_setup]“,
    „jboss.persistenceunit.\“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU\““ => „javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    Caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing column [delete_done] in table [calendar_setup]“
    }}
    2023-01-09 12:09:12,381 INFO [org.jboss.as.server] (ServerService Thread Pool — 43) WFLYSRV0010: Deployed „j-lawyer-server.ear“ (runtime-name : „j-lawyer-server.ear“)
    2023-01-09 12:09:12,390 INFO [org.jboss.as.controller] (Controller Boot Thread) WFLYCTL0183: Service status report
    WFLYCTL0186: Services which failed to start: service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-ejb.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    service jboss.persistenceunit.“j-lawyer-server.ear/j-lawyer-server-entities.jar#j-lawyer-server-ejbPU“: javax.persistence.PersistenceException: [PersistenceUnit: j-lawyer-server-ejbPU] Unable to build Hibernate SessionFactory
    WFLYCTL0448: 323 additional services are down due to their dependencies being missing or failed[/code]

    Hat jemand bitte, bitte eine Idee?

    • Dieses Thema wurde vor vor 1 Jahr, 3 Monaten von Veraendert bearbeitet.
    9. Januar 2023 um 12:26 #5236
    Veraendert
    Teilnehmer

    select version, success from flyway_schema_history hat die 2.2 gar nicht drin. Endet bei 2.1.0.12.

    9. Januar 2023 um 12:29 #5237
    j-lawyer.org
    Administrator

    Ein Datenbankupdate ist fehlgeschlagen, und zwar dieses hier:

    https://github.com/jlawyerorg/j-lawyer-org/blob/master/j-lawyer-server-entities/src/java/db/migration/V2_1_0_12__AddDefaultRoleToContact.sql

    Die Kommandos könnten nochmal manuell auf der Datenbank ausgeführt werden. Wenn erneut ein Fehler kommt, dann diesen Fehler hier posten. Wenn die Datenbank keinen Fehler meldet, dann einmal diese Migration als „erfolgreich“ markieren und den Serverdienst neu starten:

    update flyway_schema_history set success=1 where version='2.1.0.12';

    Wie alt ist die Debian-Installation und welche Datenbankversion wird eingesetzt? Der Treiber oben meldet eine MySQL 5.5, was mir sehr alt erscheint und auch nicht mehr im regulären Testprozedere enthalten ist.

    9. Januar 2023 um 12:34 #5238
    Veraendert
    Teilnehmer

    ERROR 1118 (42000) at line 2 in file: ‚/home/georg/bak/21.sql‘: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 8126. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs

    (datei in 21.sql von mir umbenannt)

    mariadb Ver 15.1 Distrib 10.3.36-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

    • Diese Antwort wurde vor vor 1 Jahr, 3 Monaten von Veraendert bearbeitet.
    • Diese Antwort wurde vor vor 1 Jahr, 3 Monaten von Veraendert bearbeitet.
    9. Januar 2023 um 13:21 #5242
    j-lawyer.org
    Administrator

    Die maximale Zeilenlänge dieser DB-Installation ist zu gering. Bitte folgende Statements ausführen, dann die jenigen der 2.1.0.12 und weiter verfahren wie oben beschrieben. 

    alter table contacts modify zipCode VARCHAR(50) BINARY;
alter table contacts modify country VARCHAR(150) BINARY;
alter table contacts modify phone VARCHAR(150) BINARY;
alter table contacts modify fax VARCHAR(150) BINARY;
alter table contacts modify bankCode VARCHAR(75) BINARY;
alter table contacts modify bankAccount  VARCHAR(75) BINARY;
alter table contacts modify email  VARCHAR(150) BINARY;
alter table contacts modify creator  VARCHAR(150) BINARY;
alter table contacts modify lastModifier  VARCHAR(150) BINARY;
alter table contacts modify mobile  VARCHAR(150) BINARY;
alter table contacts modify trafficInsuranceNumber  VARCHAR(150) BINARY;
alter table contacts modify motorInsuranceNumber  VARCHAR(150) BINARY;
alter table contacts modify titleInAddress  VARCHAR(100) BINARY;
alter table contacts modify profession  VARCHAR(150) BINARY;
alter table contacts modify degreePrefix  VARCHAR(100) BINARY;
alter table contacts modify degreeSuffix  VARCHAR(100) BINARY;
    9. Januar 2023 um 13:36 #5243
    Veraendert
    Teilnehmer

    2023-01-09 13:34:35,371 ERROR [com.jdimension.jlawyer.services.SingletonService] (Timer-7) observed directory returns null for #listFiles

    • Diese Antwort wurde vor vor 1 Jahr, 3 Monaten von Veraendert bearbeitet.
    • Diese Antwort wurde vor vor 1 Jahr, 3 Monaten von Veraendert bearbeitet.
    9. Januar 2023 um 13:37 #5244
    Veraendert
    Teilnehmer

    Aber anmelden geht. Yeah. Danke!

    9. Januar 2023 um 13:42 #5247
    j-lawyer.org
    Administrator

    > 2023-01-09 13:34:35,371 ERROR [com.jdimension.jlawyer.services.SingletonService] (Timer-7) observed directory returns null for #listFiles

    Das hat mit dem Update nichts zu tun, weist darauf hin dass das konfigurierte Scan-Verzeichnis inkorrekt ist oder nicht gelesen werden kann (bspw. keine Berechtigungen).

    Ggf. mal das Verzeichnis hier posten.

    > Aber anmelden geht. Yeah. Danke!

    Bitte im Client im Menü „?“ – „Über“ die Serverversion prüfen. Soll 2.2.0.4 sein, wenn alles erfolgreich war.

    9. Januar 2023 um 16:25 #5248
    Veraendert
    Teilnehmer

    Ja, ist 2.2.

    An die scans muss ich auch noch dran, stimmt. Der Zugriff erfolgt über sftp, nehme ich an. Das wird dann schwierig, weil der Server sich nicht auf dem Standard-Port meldet. Aber das bekomme ich hin. Ich bin nur bei Datenbanken schwach.

    9. Januar 2023 um 19:38 #5250
    j-lawyer.org
    Administrator

    Hallo,

    da Sie hier mit einer ungültigen Mailadresse registriert sind: lassen Sie mir bzgl. des heutigen GitHub-Sponsorings gern eine Adresse zukommen.

    Viele Grüße!

    10. Januar 2023 um 17:09 #5253
    Veraendert
    Teilnehmer

    Nein, kein sftp. Es war ein einfaches permission-Problem, nichts, was chmod nicht lösen könnte. Nur falls jemand über diesen Thread stolpert. Ich war ansonsten der Meinung gewesen, ich hätte schon dauerhaft eine Spende eingerichtet, dem war aber nicht so. Jetzt sollte das klappen. Und auch wenn eine j-lawyer-Tasse natürlich kultig ist: Das Geld für den Versand geht doch besser in die Entwicklung. Oder in Kaffee für Entwickler. Danke für alles!

    10. Januar 2023 um 17:25 #5254
    j-lawyer.org
    Administrator

    Ehrenmann / Ehrenfrau!

    Vielen Dank!

  • Autor
    Beiträge
12 Beiträge anzeigen - 1 bis 12 (von insgesamt 12)
  • Du musst angemeldet sein, um zu diesem Thema eine Antwort verfassen zu können.