Solo 开发指南

您好,我在本地测试的时候第一次直接放在 tomcat 中是没法启动的,我启动了 Starter 里的 main 方法初始化之后才可以正常用 tomcat 打开.但是我把项目打包成 war 之后,部署在 centos 的云服务器的 tomcat 上之后,公网 ip+ 端口号/项目名却打不开,是因为没法初始化的缘故么? 还是需要什么别的操作才可以部署的?

lograr
29 分的是报错信息,31 分的是我把项目拿到之后单纯启动 tomcat 测试了一下

我还在初学阶段,麻烦您了

安装并启动了 mysql 后，接下来修改 root@localhost 密码为 12345

mysql 在安装后会创建一个 root@locahost 账户(这是 mysql 本地登录的账号。MySQL8.0 为远程连接 root@% 和本地连接 root@locahost 提供了不同的密码验证方式。)，并且把本地连接初始的密码放到了/var/log/mysqld.log 文件中；用 cat /var/log/mysqld.log | grep password 命令查看初始密码。

[root@VM_0_11_centos solo]# cat /var/log/mysqld.log | grep password


2019-06-23T03:35:57.941668Z 5 [Note] [MY-010454] [Server] A temporary password is generated for root@localhost: n=Ti,P4?J(uE

注：上面 n=Ti,P4?J(uE 就是初始密码。

使用初始密码登录 mysql

[root@VM_0_11_centos solo]# mysql -uroot -p


Enter password: 
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 12
Server version: 8.0.16 MySQL Community Server - GPL

Copyright (c) 2000, 2019, Oracle and/or its affiliates. All rights reserved.

Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

mysql 的 root 用户的验证方式变了。从下面命令结果可以看出 root 的用户的加密方式为 caching_sha2_passoword,而 navicat 连接所用的方式为 native_password。

mysql> use mysql

Reading table information for completion of table and column names

You can turn off this feature to get a quicker startup with -A

Database changed
mysql> select host, user, plugin from user;
+-----------+------------------+-----------------------+
| host      | user             | plugin                |
+-----------+------------------+-----------------------+
| %         | root             | mysql_native_password |
| localhost | mysql.infoschema | caching_sha2_password |
| localhost | mysql.session    | caching_sha2_password |
| localhost | mysql.sys        | caching_sha2_password |
| localhost | root             | caching_sha2_password |
+-----------+------------------+-----------------------+
5 rows in set (0.00 sec)

下面开始修改密码操作，但是直接用 alter 命令改还不行，因为 123456 密太简单，不满足密码策略，查看密码策略命令如下：

mysql> SHOW VARIABLES LIKE 'validate%';

+--------------------------------------+--------+

| Variable_name                        | Value  |
+--------------------------------------+--------+
| validate_password.check_user_name    | ON     |
| validate_password.dictionary_file    |        |
| validate_password.length             | 8      |
| validate_password.mixed_case_count   | 1      |
| validate_password.number_count       | 1      |
| validate_password.policy             | MEDIUM |
| validate_password.special_char_count | 1      |
+--------------------------------------+--------+
7 rows in set (0.01 sec)

需要把 validate_password.check_user_name 改为 OFF，validate_password.length 改为 1，validate_password.policy 改为 LOW。命令如下：

mysql> set global validate_password.check_user_name=0;
Query OK, 0 rows affected (0.00 sec)

mysql> set global validate_password.length=1;
Query OK, 0 rows affected (0.00 sec)

mysql> set global validate_password.policy=0;
Query OK, 0 rows affected (0.00 sec)

mysql> SHOW VARIABLES LIKE 'validate%';

+--------------------------------------+-------+
| Variable_name                        | Value |
+--------------------------------------+-------+
| validate_password.check_user_name    | OFF   |
| validate_password.dictionary_file    |       |
| validate_password.length             | 4     |
| validate_password.mixed_case_count   | 1     |
| validate_password.number_count       | 1     |
| validate_password.policy             | LOW   |
| validate_password.special_char_count | 1     |
+--------------------------------------+-------+
7 rows in set (0.00 sec)

然后才可以开始改密码了：（本地和远程的都改为 123456）

mysql> alter user'root'@'localhost' IDENTIFIED BY '123456';
Query OK, 0 rows affected (0.01 sec)

mysql> ALTER USER 'root'@'%' IDENTIFIED by '123456';
Query OK, 0 rows affected (0.01 sec)

mysql> ALTER USER 'root'@'%' IDENTIFIED WITH mysql_native_password BY '123456';
Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

org.b3log.latke.service.ServiceException: Initailize Solo error: A json object to persist to repository[name=vseu__option] does not contain a key[optionValue]
mysql 数据库初始化报了这个错误，这是什么问题？

刚刚重新拷了一次源码，只是下载了依赖，什么都没有改动。
Initailize Solo error: A json object to persist to repository[name=b3_solo_option] does not contain a key[optionValue]
环境 ubuntu+jdk8+idea+maven3.5（还没用到 mysql） 谢谢大佬
[INFO ]-[2018-09-02 01:17:46]-[org.b3log.solo.service.InitService:204]: YOUR DATA will be stored in directory [jdbc:h2:/home/lucky/solo_h2/db], please pay more attention to it~
[ERROR]-[2018-09-02 01:17:46]-[org.b3log.latke.Latkes:863]: Read skin configuration error[msg=null]
[WARN ]-[2018-09-02 01:17:46]-[org.b3log.solo.service.InitService:240]: Retrying to init Solo[retries=2]
[ERROR]-[2018-09-02 01:17:47]-[org.b3log.latke.Latkes:863]: Read skin configuration error[msg=null]
[WARN ]-[2018-09-02 01:17:47]-[org.b3log.solo.service.InitService:240]: Retrying to init Solo[retries=1]
[ERROR]-[2018-09-02 01:17:47]-[org.b3log.latke.Latkes:863]: Read skin configuration error[msg=null]
[WARN ]-[2018-09-02 01:17:47]-[org.b3log.solo.service.InitService:240]: Retrying to init Solo[retries=0]
[ERROR]-[2018-09-02 01:17:47]-[org.b3log.latke.Latkes:863]: Read skin configuration error[msg=null]
[ERROR]-[2018-09-02 01:17:47]-[org.b3log.solo.service.InitService:234]: Initialize Solo error
org.b3log.latke.repository.RepositoryException: A json object to persist to repository[name=b3_solo_option] does not contain a key[optionValue]
at org.b3log.latke.repository.Repositories.check(Repositories.java:193)
at org.b3log.latke.repository.AbstractRepository.add(AbstractRepository.java:107)
at org.b3log.solo.repository.impl.OptionRepositoryImpl_