铛铛启动报错，index.w页面可以打开，但组织树为空

cj120435462

铛铛启动报错，index.w页面可以打开，但组织树为空，也创建不了群组和讨论组。启动日志如下：
[INFO] [12/18/2017 22:27:43.583] [main] [DatadogExtension(akka://kamon)] Starting the Kamon(Datadog) extension
INFO  akka.event.slf4j.Slf4jLogger    Slf4jLogger started
14:27:44.663UTC INFO  akka.remote.Remoting akka.remote.Remoting   Starting remoting
14:27:44.951UTC INFO  akka.remote.Remoting akka.remote.Remoting   Remoting started; listening on addresses :[akka.tcp://actor-server@127.0.0.1:63781]
14:27:44.954UTC INFO  akka.remote.Remoting akka.remote.Remoting   Remoting now listens on addresses: [akka.tcp://actor-server@127.0.0.1:63781]
14:27:44.982UTC INFO  a.c.Cluster(akka://actor-server) akka.cluster.Cluster(akka://actor-server)   Cluster Node [akka.tcp://actor-server@127.0.0.1:63781] - Starting up...
14:27:45.163UTC INFO  a.c.Cluster(akka://actor-server) akka.cluster.Cluster(akka://actor-server)   Cluster Node [akka.tcp://actor-server@127.0.0.1:63781] - Registered cluster JMX MBean [akka:type=Cluster]
14:27:45.163UTC INFO  a.c.Cluster(akka://actor-server) akka.cluster.Cluster(akka://actor-server)   Cluster Node [akka.tcp://actor-server@127.0.0.1:63781] - Started up successfully
14:27:45.193UTC INFO  a.c.Cluster(akka://actor-server) akka.cluster.Cluster(akka://actor-server)   Cluster Node [akka.tcp://actor-server@127.0.0.1:63781] - Metrics will be retreived from MBeans, and may be incorrect on some platforms. To increase metric accuracy add the 'sigar.jar' to the classpath and the appropriate platform-specific native libary to 'java.library.path'. Reason: java.lang.ClassNotFoundException: org.hyperic.sigar.Sigar
14:27:45.206UTC INFO  a.c.Cluster(akka://actor-server) akka.cluster.Cluster(akka://actor-server)   Cluster Node [akka.tcp://actor-server@127.0.0.1:63781] - Metrics collection has started successfully
14:27:45.207UTC INFO  a.c.Cluster(akka://actor-server) akka.cluster.Cluster(akka://actor-server)   Cluster Node [akka.tcp://actor-server@127.0.0.1:63781] - No seed-nodes configured, manual cluster join required
DEBUG com.zaxxer.hikari.HikariConfig     - configuration:
DEBUG com.zaxxer.hikari.HikariConfig    allowPoolSuspension.............false
DEBUG com.zaxxer.hikari.HikariConfig    autoCommit......................true
DEBUG com.zaxxer.hikari.HikariConfig    catalog.........................null
DEBUG com.zaxxer.hikari.HikariConfig    connectionInitSql...............null
DEBUG com.zaxxer.hikari.HikariConfig    connectionTestQuery.............null
DEBUG com.zaxxer.hikari.HikariConfig    connectionTimeout...............1000
DEBUG com.zaxxer.hikari.HikariConfig    dataSource......................null
DEBUG com.zaxxer.hikari.HikariConfig    dataSourceClassName.............null
DEBUG com.zaxxer.hikari.HikariConfig    dataSourceJNDI..................null
DEBUG com.zaxxer.hikari.HikariConfig    dataSourceProperties............{password=<masked>}
DEBUG com.zaxxer.hikari.HikariConfig    driverClassName................."org.postgresql.Driver"
DEBUG com.zaxxer.hikari.HikariConfig    healthCheckProperties...........{}
DEBUG com.zaxxer.hikari.HikariConfig    healthCheckRegistry.............null
DEBUG com.zaxxer.hikari.HikariConfig    idleTimeout.....................600000
DEBUG com.zaxxer.hikari.HikariConfig    initializationFailFast..........false
DEBUG com.zaxxer.hikari.HikariConfig    isolateInternalQueries..........false
DEBUG com.zaxxer.hikari.HikariConfig    jdbc4ConnectionTest.............false
DEBUG com.zaxxer.hikari.HikariConfig    jdbcUrl........................."jdbc:postgresql://localhost:5432/im"
DEBUG com.zaxxer.hikari.HikariConfig    leakDetectionThreshold..........0
DEBUG com.zaxxer.hikari.HikariConfig    maxLifetime.....................1800000
DEBUG com.zaxxer.hikari.HikariConfig    maximumPoolSize.................100
DEBUG com.zaxxer.hikari.HikariConfig    metricRegistry..................null
DEBUG com.zaxxer.hikari.HikariConfig    metricsTrackerFactory...........null
DEBUG com.zaxxer.hikari.HikariConfig    minimumIdle.....................20
DEBUG com.zaxxer.hikari.HikariConfig    password........................<masked>
DEBUG com.zaxxer.hikari.HikariConfig    poolName........................""
DEBUG com.zaxxer.hikari.HikariConfig    readOnly........................false
DEBUG com.zaxxer.hikari.HikariConfig    registerMbeans..................false
DEBUG com.zaxxer.hikari.HikariConfig    scheduledExecutorService........null
DEBUG com.zaxxer.hikari.HikariConfig    threadFactory...................null
DEBUG com.zaxxer.hikari.HikariConfig    transactionIsolation............null
DEBUG com.zaxxer.hikari.HikariConfig    username........................"admin"
DEBUG com.zaxxer.hikari.HikariConfig    validationTimeout...............1000
INFO  com.zaxxer.hikari.HikariDataSource     - Started.
DEBUG com.zaxxer.hikari.pool.HikariPool     - Pool stats (total=0, active=0, idle=0, waiting=1)
INFO  com.zaxxer.hikari.pool.PoolBase     - Driver does not support get/set network timeout for connections. (杩欎釜 org.postgresql.jdbc.PgConnection.getNetworkTimeout() 鏂规硶灏氭湭琚疄浣溿€?
DEBUG com.zaxxer.hikari.pool.HikariPool     - Added connection org.postgresql.jdbc.PgConnection@83ee9be
DEBUG com.zaxxer.hikari.pool.HikariPool     - Added connection org.postgresql.jdbc.PgConnection@4c2fe441
INFO  o.f.c.i.dbsupport.DbSupportFactory    Database: jdbc:postgresql://localhost:5432/im (PostgreSQL 9.5)
DEBUG org.flywaydb.core.Flyway    DDL Transactions Supported: true
DEBUG org.flywaydb.core.Flyway    Schema: public

cj120435462

详细日志见附件

cj120435462

详细日志见附件

cj120435462

只使用即时通讯功能

cj120435462

上面的问题解决了，把数据库用户设为超级用户即可。
现在有个新的问题：Cannot read property 'getContext' of undefined

jishuang

铛铛的问题请到铛铛的论坛发帖

cj120435462

jishuang 发表于 2017-12-19 09:03
铛铛的问题请到铛铛的论坛发帖

铛铛每人回复呢

cj120435462

jishuang 发表于 2017-12-19 09:03
铛铛的问题请到铛铛的论坛发帖

发布的帖子好几天每人理呢 系统急着上线呢

jishuang

已经通知相关人员处理，急需解决的可以联系起步相关的商务人员跟进