看内容是皮肤插件为 null, 导致 Tomcat 也无法启动, 请问如何解决 是按照开发手册下载过皮肤过模块的, 但是还是这问题 Git clone --recurse-submodules [链接] [root@db11 test]# git clone --recurse-submodules https://g ..

Solo tomcat 启动报错 Read skin [Pinghsu]'s configuration failed: null

看内容是皮肤插件为 null, 导致 Tomcat 也无法启动, 请问如何解决
是按照开发手册下载过皮肤过模块的, 但是还是这问题
Git clone --recurse-submodules https://github.com/b3log/solo.git

[root@db11 test]# git clone --recurse-submodules https://github.com/b3log/solo.git

正克隆到 'solo'...
remote: Enumerating objects: 28, done.
remote: Counting objects: 100% (28/28), done.
remote: Compressing objects: 100% (16/16), done.
remote: Total 43921 (delta 9), reused 23 (delta 9), pack-reused 43893
接收对象中: 100% (43921/43921), 92.06 MiB | 14.87 MiB/s, done.
处理 delta 中: 100% (24309/24309), done.
子模组 'src/main/webapp/skins' (https://github.com/b3log/solo-skins) 已为路径 'src/main/webapp/skins' 注册
正克隆到 'src/main/webapp/skins'...
remote: Enumerating objects: 1110, done.
remote: Counting objects: 100% (1110/1110), done.
remote: Compressing objects: 100% (684/684), done.
remote: Total 11660 (delta 785), reused 709 (delta 425), pack-reused 10550
接收对象中: 100% (11660/11660), 23.56 MiB | 5.19 MiB/s, done.
处理 delta 中: 100% (8743/8743), done.

皮肤模块是存在的

[root@db11 solo2]# ls src/main/webapp/skins/

9IPHP   Bruce   Community  Finding  Jane    metro-hot  next     owmx-3.0  README.md  tree-house
Andrea  Casper  favourite  i-nove   Medium  NeoEase    nijigen  Pinghsu   timeline   yilia
[root@db11 solo2]# 
29-May-2019 13:13:42.352 信息 [localhost-startStop-1] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
[WARN ]-[2019-05-29 13:13:42]-[org.b3log.latke.Latkes:609]: !!!!Runtime mode is [DEVELOPMENT], please make sure configured it with [PRODUCTION] in latke.properties if deployed on production environment!!!!
[INFO ]-[2019-05-29 13:13:43]-[org.b3log.solo.util.Markdowns:129]: [markdown-http] is not available, uses built-in [flexmark] for markdown processing. Please read FAQ section in user guide (https://hacpai.com/article/1492881378588) for more details.
[INFO ]-[2019-05-29 13:13:43]-[org.b3log.solo.SoloServletListener:99]: Solo is booting [ver=3.6.1, servletContainer=Apache Tomcat/8.5.31, os=Linux, isDocker=false, markdownHttpAvailable=false, pid=87665, runtimeDatabase=MYSQL, runtimeMode=DEVELOPMENT, jdbc.username=root, jdbc.URL=jdbc:mysql://localhost:3306/solo?useUnicode=yes&characterEncoding=UTF-8&useSSL=false&serverTimezone=UTC]
[ERROR]-[2019-05-29 13:13:43]-[org.b3log.latke.Latkes:829]: Read skin [Pinghsu]'s  configuration failed: null
[ERROR]-[2019-05-29 13:13:43]-[org.b3log.solo.SoloServletListener:315]: Can't load the default skins, please make sure skin [Pinghsu] is under skins directory and structure correctly

  • Solo

    Solo 是一款小而美的开源博客系统,专为程序员设计。

    Solo 有着非常活跃的社区,可将文章作为帖子推送到社区,来自社区的回帖将作为博客评论进行联动。

    这是一种全新的网络社区体验,让热爱记录和分享的你不再感到孤单!
    具体细节请浏览 B3log 构思

    792 引用 • 5893 回帖 • 685 关注
2 操作
fz8770 在 2019-05-29 14:04:10 更新了该帖
fz8770 在 2019-05-29 14:15:11 更新了该帖
16 回帖   
请输入回帖内容...
  • 88250

    请参考开发手册克隆皮肤子模块。

    1 回复
  • fz8770        

    我是下载了皮肤模块的
    Git clone --recurse-submodules https://github.com/b3log/solo.git

    1 回复
    1 操作
    fz8770 在 2019-05-29 14:01:29 更新了该回帖
  • 88250      

    看下 src/main/webapp/skins 下面是否有皮肤文件。

    1 回复
  • fz8770        

    有的

    [root@db11 solo2]# ls src/main/webapp/skins/
    
    9IPHP   Bruce   Community  Finding  Jane    metro-hot  next     owmx-3.0  README.md  tree-house
    Andrea  Casper  favourite  i-nove   Medium  NeoEase    nijigen  Pinghsu   timeline   yilia
    [root@db11 solo2]# 
    
    1 回复
  • 88250      

    JDK 版本是多少?

    1 回复
  • fz8770        

    [root@db12 ~]# java -version
    
    java version "1.8.0_45"
    Java(TM) SE Runtime Environment (build 1.8.0_45-b14)
    Java HotSpot(TM) 64-Bit Server VM (build 25.45-b02, mixed mode)
    

  • 88250

    编译构建没有问题么?你可以用内置的 Jetty 启动看看。

    mvn jetty:run
    
    1 回复
  • fz8770        

    我是用 /usr/local/maven3.5/bin/mvn clean package -Dmaven.test.skip=true 构建, 没出错,
    直接 /usr/local/maven3.5/bin/mvn jetty:run

    [INFO] Started o.e.j.m.p.JettyWebAppContext@2256f14{/,file:///root/test/solo2/src/main/webapp/,AVAILABLE}{file:///root/test/solo2/src/main/webapp/}
    
    [INFO] Jetty server exiting.
    [INFO] ------------------------------------------------------------------------
    [INFO] BUILD FAILURE
    [INFO] ------------------------------------------------------------------------
    [INFO] Total time: 20.342 s
    [INFO] Finished at: 2019-05-29T15:12:24+08:00
    [INFO] ------------------------------------------------------------------------
    [ERROR] Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.4.12.v20180830:run (default-cli) on project solo: Failure: 地址已在使用 -> [Help 1]
    [ERROR] 
    [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
    [ERROR] Re-run Maven using the -X switch to enable full debug logging.
    [ERROR] 
    [ERROR] For more information about the errors and possible solutions, please read the following articles:
    [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
    [root@db11 solo2]# vim src/main/resources/latke.properties 
    [root@db11 solo2]# 
    

    即使我修改了 VIM src/main/resources/latke.properties 的端口为 8066 (默认 8080 已经被占用了)

    1 回复
  • 88250      

    latke.props 里面那个端口是访问的端口,不是监听端口。改监听端口在 pom.xml 里面。

    1 回复
  • fz8770        

    修改 pom.xml 端口后 run 可以, 浏览器访问可以看到欢迎使用  Solo

    
    [INFO ]-[2019-05-29 15:20:57]-[com.zaxxer.hikari.HikariDataSource:123]: HikariPool-1 - Start completed.
    [WARN ]-[2019-05-29 15:20:57]-[org.b3log.solo.service.InitService:161]: Solo has not been initialized, please open your browser to init Solo
    [INFO] Started o.e.j.m.p.JettyWebAppContext@2256f14{/,file:///root/test/solo2/src/main/webapp/,AVAILABLE}{file:///root/test/solo2/src/main/webapp/}
    [INFO] Started ServerConnector@79611d2c{HTTP/1.1,[http/1.1]}{0.0.0.0:8066}
    [INFO] Started @24455ms
    [INFO] Started Jetty Server
    
  • 88250

    部署到 Tomcat 中为啥不行这个问题我暂时回答不了 😂
    建议用 Docker 部署,以后也方便无痛升级。

    1 回复
  • fz8770        

    好的 感谢

  • zorkelvll  

    A 再把 skins 那个工程 clone 下来,放到 Solo 工程的 skins 目录下,然后再打包

  • henrywendy  

    我在用 Docker 启动 挂载皮肤 也是 出现了这个问题,Docker 挂载 如图:image.png
    查看 Docker 日志 如图:image.png

    请问 这是什么原因导致的 @88250 @88250

    1 回复
  • 88250      

    你好,如果不需要挂载本地 skins 的话请勿加上该参数。如果需要挂载的话,请确认其子目录结构是否正确,并确保默认皮肤(Pinghsu)位于该目录下。

    1 回复
  • henrywendy        

    感谢 @88250 已经解决 ,初衷是想用第三放的皮肤,然后 在网上查资料 Docker 挂载 本地目录就可以了,其他 这里面少了一个步骤 就是 挂载之前 把本地的目录 Git clone 一下 官方的皮肤目录。我是整个目录全部 clone 下来了,可以不全部下也可以只下载 Pingsu 这个默认皮肤 就可以了,然后 在把第三方的 皮肤 clone 到 同一个目录中。Solo 管理后台就会加载 到 你 clone 的皮肤,再次感谢 @88250

请输入回帖内容 ...