为什么在手动关闭后不启动KeyClock和SQL的容器？

Question

重新启动后，当我尝试使用Portainer启动容器时，我会在KeyClock日志文件中看到以下错误。

{    
    "address" => [
        ("subsystem" => "undertow"),
        ("server" => "default-server"),
        ("host" => "default-host")
    ],
    "alias" => ["localhost"]
}, {
    "operation" => "add",
    "address" => [
        ("subsystem" => "undertow"),
        ("server" => "default-server"),
        ("host" => "default-host"),
        ("location" => "/")
    ],
    "handler" => "welcome-content"
}, {
    "operation" => "add",
    "address" => [
        ("subsystem" => "undertow"),
        ("server" => "default-server"),
        ("host" => "default-host"),
        ("setting" => "http-invoker")
    ],
    "security-realm" => "ApplicationRealm"
}, {
    "operation" => "add",
    "address" => [
        ("subsystem" => "undertow"),
        ("servlet-container" => "default")
    ]
}, {
    "operation" => "add",
    "address" => [
        ("subsystem" => "undertow"),
        ("servlet-container" => "default"),
        ("setting" => "jsp")
    ]
}, {
    "operation" => "add",
    "address" => [
        ("subsystem" => "undertow"),
        ("servlet-container" => "default"),
        ("setting" => "websockets")
    ]
}, {
    "operation" => "add",
    "address" => [
        ("subsystem" => "undertow"),
        ("configuration" => "handler"),
        ("file" => "welcome-content")
    ],
    "path" => expression "${jboss.home.dir}/welcome-content"
}, {
    "operation" => "add",
    "address" => [("subsystem" => "weld")]
}, {
    "operation" => "boottime-controller-initializer-step",
    "address" => []
}, {
    "operation" => "add-deployer-chains",
    "address" => []
}]: java.util.concurrent.RejectedExecutionException
    at [email protected]//org.jboss.threads.RejectingExecutor.execute(RejectingExecutor.java:37)
    at [email protected]//org.jboss.threads.EnhancedQueueExecutor.rejectShutdown(EnhancedQueueExecutor.java:2029)
    at [email protected]//org.jboss.threads.EnhancedQueueExecutor.execute(EnhancedQueueExecutor.java:757)
    at [email protected]//org.jboss.as.controller.notification.NotificationSupports$NonBlockingNotificationSupport.emit(NotificationSupports.java:95)
    at [email protected]//org.jboss.as.controller.OperationContextImpl.notifyModificationsComplete(OperationContextImpl.java:505)
    at [email protected]//org.jboss.as.controller.OperationContextImpl.releaseStepLocks(OperationContextImpl.java:1233)
    at [email protected]//org.jboss.as.controller.AbstractOperationContext$Step.finalizeInternal(AbstractOperationContext.java:1538)
    at [email protected]//org.jboss.as.controller.AbstractOperationContext$Step.finalizeStep(AbstractOperationContext.java:1496)
    at [email protected]//org.jboss.as.controller.AbstractOperationContext$Step.access$400(AbstractOperationContext.java:1360)
    at [email protected]//org.jboss.as.controller.AbstractOperationContext.executeResultHandlerPhase(AbstractOperationContext.java:912)
    at [email protected]//org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:792)
    at [email protected]//org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:468)
    at [email protected]//org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1415)
    at [email protected]//org.jboss.as.controller.ModelControllerImpl.boot(ModelControllerImpl.java:529)
    at [email protected]//org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:515)
    at [email protected]//org.jboss.as.controller.AbstractControllerService.boot(AbstractControllerService.java:477)
    at [email protected]//org.jboss.as.server.ServerService.boot(ServerService.java:459)
    at [email protected]//org.jboss.as.server.ServerService.boot(ServerService.java:412)
    at [email protected]//org.jboss.as.controller.AbstractControllerService$1.run(AbstractControllerService.java:416)
    at java.base/java.lang.Thread.run(Thread.java:829)
    Suppressed: java.util.concurrent.RejectedExecutionException: Executor is being shut down
        at [email protected]//org.jboss.threads.EnhancedQueueExecutor.rejectShutdown(EnhancedQueueExecutor.java:2031)
        ... 18 more
rUser with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'
User with username 'admin' already added to '/opt/jboss/keycloak/standalone/configuration/keycloak-add-user.json'

在研究此之后，我发现SQL Server已关闭，当我启动此问题时，我会看到以下错误。

Msg 1801, Level 16, State 3, Server 1f6e6d05683c, Line 1
Database 'Keycloak' already exists. Choose a different database name.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : Login timeout expired.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : TCP Provider: Error code 0x2749.
Sqlcmd: Error: Microsoft ODBC Driver 13 for SQL Server : A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online..
Msg 1801, Level 16, State 3, Server 1f6e6d05683c, Line 1
Database 'Keycloak' already exists. Choose a different database name.
Msg 1801, Level 16, State 3, Server 1f6e6d05683c, Line 1
Database 'Keycloak' already exists. Choose a different database name.
Msg 1801, Level 16, State 3, Server 1f6e6d05683c, Line 1
Database 'Keycloak' already exists. Choose a different database name.
Msg 1801, Level 16, State 3, Server 1f6e6d05683c, Line 1
Database 'Keycloak' already exists. Choose a different database name. 

我尝试通过Portainer以及Docker-Compose文件运行此错误。 任何建议都将非常有用。

Answer 1

我创建了一个新的容器数据库，链接到SQL容器。在现有数据库中，用户名：管理员已经从上一个安装创建。当我创建新的容器并与旧数据库链接时，它会显示错误，因为同名“ admin”已经存在。
解决方案：在我的YML文件中，我将用户名从“ admin”更改为“ admin1”。
容器正在启动并运行。