Skip to content

Commit

Permalink
2024-01-10 01:01:08 : readme
Browse files Browse the repository at this point in the history
  • Loading branch information
jamiesun committed Jan 9, 2024
1 parent 7d1079a commit 48ea29e
Show file tree
Hide file tree
Showing 3 changed files with 19 additions and 5 deletions.
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -21,6 +21,7 @@ TOUGHRADIUS uses advanced Golang technology to develop the system core, providin
## QABOT

ToughRadius provides an AI-based technical service bot that we hope can help you solve some technical problems.
<img width="1236" alt="image" src="https://github.com/talkincode/toughradius/assets/377938/b6dafb49-6850-4906-b69f-2c18196459c0">

[QABOT Link](https://qa.toughradius.net/)

Expand Down
10 changes: 5 additions & 5 deletions assets/buildinfo.txt
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
BuildVersion=latest v8.0.4 2024-01-02 02:00:12
BuildVersion=latest v8.0.4 2024-01-10 01:01:08
ReleaseVersion=v8.0.4
BuildTime=2024-01-02 02:00:12
BuildTime=2024-01-10 01:01:08
BuildName=toughradius
CommitID=375ca52501466fefb7007faa08b34611472d4e0a
CommitDate=Tue, 2 Jan 2024 02:00:07 +0800
CommitID=5564f4a00f2aa7d38e90a83f29a3a8f1fdab5b24
CommitDate=Tue, 2 Jan 2024 02:00:21 +0800
CommitUser=jamiesun.net@gmail.com
CommitSubject=aibot add
CommitSubject=2024-01-02 02:00:12 :
13 changes: 13 additions & 0 deletions docs/documents/issues.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,13 @@
## ToughRADIUS 常见问题

### 1. 为什么我安装好以后,输入用户名密码还是无法登录 ToughRADIUS 管理后台?

这确实是一个还没有完全解决的bug, toughradius 采用了自动初始化数据库的方法, 但是在某些情况下, 会导致初始化失败, 导致无法登录,
比如数据库首次启动晚于 toughradius 服务启动, 这种情况出现在 docker 模式部署,针对这个问题, toughradius 在最新的版本中加入了一个延时启动的功能,

但鉴于安装环境的差异,这种问题可能还会出现, 如果出现这种问题, 请尝试重启 toughradius 服务, 如果还是无法登录, 请尝试手动初始化数据库,具体方法如下:

进入容器内部, 执行如下命令:`toughradius -initdb`

同时,也可以借助观察数据库的日志,来判断数据库是否初始化成功, 如果数据库初始化成功, 会在日志中看到错误信息

0 comments on commit 48ea29e

Please sign in to comment.