Bitwarden-mmsql keep restarting

good afternoon,

this morning I noticed that the Bitwarden server was not working, the web viewer shows the login page but it does not get access. I have tried with the Edge Plugin and I can’t save any data inside Bitwarden either.
I have checked the dockers with the command:

docker ps

and I have found the docker mssql service in restarting state…

Currently I have virtualized Ubuntu server 18.04.2 TLS VM and docker installed with docker as shown in:

I have had this docker with me for a year now and I have never had any problems, so I rule out that it is a security or connection issue, since it has failed just now without any change in the infrastructure or in the docker itself.

What do the mssql logs say?

docker logs bitwarden-mssql

There are also quite a few previous threads on this issue - here are a few to help you narrow down your issue, in case they are helpful:

The log say:

docker logs bitwarden-mssql

sqlservr: Unable to read instance id from /var/opt/mssql/.system/instance_id: No such device (19)
This program has encountered a fatal error and cannot continue running at Tue Aug 2 07:02:55 2022
The following diagnostic information is available:

     Reason: 0x00000003
     Status: 0x00000000
    Message: Unexpected call to legacy ABI.
      Stack:
             IP               Function
             ---------------- --------------------------------------
             0000564495883d7a malloc_usable_size+0xa876a
             000056449588386e malloc_usable_size+0xa825e
             00005644957b98ae <unknown>
             00005644958163e7 malloc_usable_size+0x3add7
    Process: 1 - sqlservr
     Thread: 33
Instance Id:
   Crash Id:
Build stamp: dcb1eac7fc5581ee21b21e5ba567c25535309d02a31d13737fe4e671d070afe5

Distribution: Ubuntu 16.04.6 LTS
Processors: 2
Total Memory: 4136525824 bytes
Timestamp: Tue Aug 2 07:02:55 2022

the docker-compose up command has shown me the following errors:

bitwarden-mssql | sqlservr: Unable to read instance id from /var/opt/mssql/.system/instance_id: No such device (19)
bitwarden-mssql | This program has encountered a fatal error and cannot continue running at Tue Aug 2 07:30:24 2022
bitwarden-mssql | The following diagnostic information is available:
bitwarden-mssql |
bitwarden-mssql | Reason: 0x00000003
bitwarden-mssql | Status: 0x00000000
bitwarden-mssql | Message: Unexpected call to legacy ABI.
bitwarden-mssql | Stack:
bitwarden-mssql | IP Function
bitwarden-mssql | ---------------- --------------------------------------
bitwarden-mssql | 0000555ed5813d7a malloc_usable_size+0xa876a
bitwarden-mssql | 0000555ed581386e malloc_usable_size+0xa825e
bitwarden-mssql | 0000555ed57498ae
bitwarden-mssql | 0000555ed57a63e7 malloc_usable_size+0x3add7
bitwarden-mssql | Process: 1 - sqlservr
bitwarden-mssql | Thread: 32
bitwarden-mssql | Instance Id:
bitwarden-mssql | Crash Id:
bitwarden-mssql | Build stamp: dcb1eac7fc5581ee21b21e5ba567c25535309d02a31d13737fe4e671d070afe5
bitwarden-mssql | Distribution: Ubuntu 16.04.6 LTS
bitwarden-mssql | Processors: 2
bitwarden-mssql | Total Memory: 4136525824 bytes
bitwarden-mssql | Timestamp: Tue Aug 2 07:30:24 2022

thanks for the links to the previous cases, I will read it and get back to you, I had searched a bit for previous cases but these I had not seen.
Thank you.

1 Like

Currently I have seen that the configuration folders in the /bwdata/docker/docker-compose.yml folder were defined as /var/opt/mssql did not exist on the machine.

I changed the path and left it like that:

11

I used sudo docker-compose up to launch the container and it launched it correctly showing me the following message at the end:

I have edited the http links by h/ttp that appear in the log since the forum does not allow to put more than two links and it did not allow me to post the log.

Blockquote [email protected]:~/bwdata/docker$ sudo docker-compose up
[sudo] password for administrador:
Starting bitwarden-api … done
Starting bitwarden-web … done
Starting bitwarden-mssql … done
Starting bitwarden-events … done
Starting bitwarden-identity … done
Starting bitwarden-icons … done
Starting bitwarden-notifications … done
Starting bitwarden-attachments … done
Starting bitwarden-sso … done
Starting bitwarden-portal … done
Starting bitwarden-admin … done
Starting bitwarden-nginx … done
Attaching to bitwarden-web, bitwarden-notifications, bitwarden-api, bitwarden-events, bitwarden-icons, bitwarden-attachments, bitwarden-identity, bitwarden-mssql, bitwarden-sso, bitwarden-admin, bitwarden-nginx, bitwarden-portal
bitwarden-api | info: Microsoft.Hosting.Lifetime[0]
bitwarden-api | Now listening on: http://[::]:5000
bitwarden-api | info: Microsoft.Hosting.Lifetime[0]
bitwarden-api | Application started. Press Ctrl+C to shut down.
bitwarden-api | info: Microsoft.Hosting.Lifetime[0]
bitwarden-api | Hosting environment: Production
bitwarden-api | info: Microsoft.Hosting.Lifetime[0]
bitwarden-api | Content root path: /app
bitwarden-attachments | Hosting environment: Production
bitwarden-attachments | Content root path: /etc/bitwarden/core/attachments
bitwarden-attachments | Now listening on: http://[::]:5000
bitwarden-attachments | Application started. Press Ctrl+C to shut down.
bitwarden-events | warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
bitwarden-events | Storing keys in a directory ‘/home/bitwarden/.aspnet/DataProtection-Keys’ that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
bitwarden-icons | warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
bitwarden-icons | Storing keys in a directory ‘/home/bitwarden/.aspnet/DataProtection-Keys’ that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
bitwarden-icons | info: Microsoft.Hosting.Lifetime[0]
bitwarden-icons | Now listening on: http://[::]:5000
bitwarden-icons | info: Microsoft.Hosting.Lifetime[0]
bitwarden-icons | Application started. Press Ctrl+C to shut down.
bitwarden-icons | info: Microsoft.Hosting.Lifetime[0]
bitwarden-icons | Hosting environment: Production
bitwarden-icons | info: Microsoft.Hosting.Lifetime[0]
bitwarden-icons | Content root path: /app
bitwarden-events | info: Microsoft.Hosting.Lifetime[0]
bitwarden-events | Now listening on: http://[::]:5000
bitwarden-events | info: Microsoft.Hosting.Lifetime[0]
bitwarden-events | Application started. Press Ctrl+C to shut down.
bitwarden-events | info: Microsoft.Hosting.Lifetime[0]
bitwarden-events | Hosting environment: Production
bitwarden-events | info: Microsoft.Hosting.Lifetime[0]
bitwarden-events | Content root path: /app
bitwarden-identity | info: Microsoft.Hosting.Lifetime[0]
bitwarden-identity | Now listening on: http://[::]:5000
bitwarden-identity | info: Microsoft.Hosting.Lifetime[0]
bitwarden-identity | Application started. Press Ctrl+C to shut down.
bitwarden-identity | info: Microsoft.Hosting.Lifetime[0]
bitwarden-identity | Hosting environment: Production
bitwarden-identity | info: Microsoft.Hosting.Lifetime[0]
bitwarden-identity | Content root path: /app
bitwarden-mssql | 2022-08-02 10:50:02.11 Server Microsoft SQL Server 2017 (RTM-CU18) (KB4527377) - 14.0.3257.3 (X64)
bitwardeNov 16 2019 01:14:50
bitwardeCopyright (C) 2017 Microsoft Corporation
bitwarden-notifications | warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
bitwarden-notifications | Storing keys in a directory ‘/home/bitwarden/.aspnet/DataProtection-Keys’ that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
bitwarden-notifications | info: Microsoft.Hosting.Lifetime[0]
bitwarden-notifications | Now listening on: http://[::]:5000
bitwarden-notifications | info: Microsoft.Hosting.Lifetime[0]
bitwarden-notifications | Application started. Press Ctrl+C to shut down.
bitwarden-notifications | info: Microsoft.Hosting.Lifetime[0]
bitwarden-notifications | Hosting environment: Production
bitwarden-notifications | info: Microsoft.Hosting.Lifetime[0]
bitwarden-notifications | Content root path: /app
bitwardeExpress Edition (64-bit) on Linux (Ubuntu 16.04.6 LTS)
2022-08-02 10:50:02.11 Server UTC adjustment: 0:00
2022-08-02 10:50:02.11 Server (c) Microsoft Corporation.
2022-08-02 10:50:02.11 Server All rights reserved.
2022-08-02 10:50:02.11 Server Server process ID is 28.
2022-08-02 10:50:02.11 Server Logging SQL Server messages in file ‘/var/opt/mssql/log/errorlog’.
2022-08-02 10:50:02.12 Server Registry startup parameters:
bitwarde -d /var/opt/mssql/data/master.mdf
bitwarde -l /var/opt/mssql/data/mastlog.ldf
bitwarde -e /var/opt/mssql/log/errorlog
2022-08-02 10:50:02.12 Server SQL Server detected 2 sockets with 1 cores per socket and 1 logical processors per socket, 2 total logical processors; using 1 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-08-02 10:50:02.12 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-08-02 10:50:02.12 Server Detected 3156 MB of RAM. This is an informational message; no user action is required.
2022-08-02 10:50:02.13 Server Using conventional memory in the memory manager.
2022-08-02 10:50:02.25 Server Buffer pool extension is already disabled. No action is necessary.
2022-08-02 10:50:02.34 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2022-08-02 10:50:02.34 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2022-08-02 10:50:02.35 Server Successfully initialized the TLS configuration. Allowed TLS protocol versions are [‘1.0 1.1 1.2’]. Allowed TLS ciphers are [‘ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:!DHE-RSA-AES256-GCM-SHA384:!DHE-RSA-AES128-GCM-SHA256:!DHE-RSA-AES256-SHA:!DHE-RSA-AES128-SHA’].
2022-08-02 10:50:02.37 Server Node configuration: node 0: CPU mask: 0x0000000000000001:0 Active CPU mask: 0x0000000000000001:0. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2022-08-02 10:50:02.38 Server The maximum number of dedicated administrator connections for this instance is ‘1’
2022-08-02 10:50:02.38 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2022-08-02 10:50:02.39 Server In-Memory OLTP initialized on lowend machine.
bitwarden-sso | info: IdentityServer4.Startup[0]
bitwarden-sso | Starting IdentityServer4 version 4.0.4+1b36d1b414f4e0f965af97ab2a7e9dd1b5167bca
bitwarden-sso | info: IdentityServer4.Startup[0]
bitwarden-sso | You are using the in-memory version of the persisted grant store. This will store consent decisions, authorization codes, refresh and reference tokens in memory only. If you are using any of those features in production, you want to switch to a different store implementation.
bitwarden-sso | info: IdentityServer4.Startup[0]
bitwarden-sso | Using the default authentication scheme idsrv for IdentityServer
bitwarden-sso | info: Bit.Sso.Startup[12482444]
bitwarden-sso | SSO started.
bitwarden-sso | info: Microsoft.Hosting.Lifetime[0]
bitwarden-sso | Now listening on: http://[::]:5000
bitwarden-sso | info: Microsoft.Hosting.Lifetime[0]
bitwarden-sso | Application started. Press Ctrl+C to shut down.
bitwarden-sso | info: Microsoft.Hosting.Lifetime[0]
bitwarden-sso | Hosting environment: Production
bitwarden-sso | info: Microsoft.Hosting.Lifetime[0]
bitwarden-sso | Content root path: /app
bitwarden-web | Hosting environment: Production
bitwarden-web | Content root path: /app
bitwarden-web | Now listening on: http://[::]:5000
bitwarden-web | Application started. Press Ctrl+C to shut down.
2022-08-02 10:50:02.45 Server Database Instant File Initialization: enabled. For security and performance considerations see the topic ‘Database Instant File Initialization’ in SQL Server Books Online. This is an informational message only. No user action is required.
ForceFlush is enabled for this instance.
2022-08-02 10:50:02.46 Server Query Store settings initialized with enabled = 1,
2022-08-02 10:50:02.48 spid6s Starting up database ‘master’.
2022-08-02 10:50:02.51 Server Software Usage Metrics is disabled.
ForceFlush feature is enabled for log durability.
2022-08-02 10:50:02.83 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2022-08-02 10:50:02.84 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
bitwarden-portal | info: Bit.Portal.Startup[12482444]
bitwarden-portal | Business Portal started.
2022-08-02 10:50:02.95 spid6s SQL Trace ID 1 was started by login “sa”.
bitwarden-portal | info: Microsoft.Hosting.Lifetime[0]
bitwarden-portal | Now listening on: http://[::]:5000
bitwarden-portal | info: Microsoft.Hosting.Lifetime[0]
bitwarden-portal | Application started. Press Ctrl+C to shut down.
bitwarden-portal | info: Microsoft.Hosting.Lifetime[0]
bitwarden-portal | Hosting environment: Production
bitwarden-portal | info: Microsoft.Hosting.Lifetime[0]
bitwarden-portal | Content root path: /app
2022-08-02 10:50:02.98 spid6s Server name is ‘4120714a7995’. This is an informational message only. No user action is required.
2022-08-02 10:50:03.01 spid21s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2022-08-02 10:50:03.03 spid21s Always On: The availability replica manager is waiting for the instance of SQL Server to allow client connections. This is an informational message only. No user action is required.
2022-08-02 10:50:03.04 spid6s Starting up database ‘msdb’.
2022-08-02 10:50:03.05 spid9s Starting up database ‘mssqlsystemresource’.
2022-08-02 10:50:03.06 spid9s The resource database build version is 14.00.3257. This is an informational message only. No user action is required.
2022-08-02 10:50:03.10 spid9s Starting up database ‘model’.
2022-08-02 10:50:03.44 spid18s A self-generated certificate was successfully loaded for encryption.
2022-08-02 10:50:03.44 spid9s Polybase feature disabled.
2022-08-02 10:50:03.45 spid9s Clearing tempdb database.
2022-08-02 10:50:03.47 spid18s Server is listening on [ ‘any’ 1433].
2022-08-02 10:50:03.48 spid18s Server is listening on [ ‘any’ 1433].
2022-08-02 10:50:03.51 spid18s Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag 7806. This is an informational message only. No user action is required.
2022-08-02 10:50:03.52 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2022-08-02 10:50:03.88 spid9s Starting up database ‘tempdb’.
2022-08-02 10:50:04.08 spid21s The Service Broker endpoint is in disabled or stopped state.
2022-08-02 10:50:04.09 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2022-08-02 10:50:04.15 spid21s Service Broker manager has started.
2022-08-02 10:50:04.19 spid6s Recovery is complete. This is an informational message only. No user action is required.
2022-08-02 10:50:21.43 spid52 Starting up database ‘vault’.
2022-08-02 10:50:21.51 spid52 Parallel redo is started for database ‘vault’ with worker pool size [1].
2022-08-02 10:50:21.58 spid52 Parallel redo is shutdown for database ‘vault’ with worker pool size [1].
bitwarden-admin | info: Microsoft.Hosting.Lifetime[0]
bitwarden-admin | Now listening on: http://[::]:5000
bitwarden-admin | info: Microsoft.Hosting.Lifetime[0]
bitwarden-admin | Application started. Press Ctrl+C to shut down.
bitwarden-admin | info: Microsoft.Hosting.Lifetime[0]
bitwarden-admin | Hosting environment: Production
bitwarden-admin | info: Microsoft.Hosting.Lifetime[0]
bitwarden-admin | Content root path: /app
bitwarden-web | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
bitwarden-web | Request starting HTTP/1.1 GET h/ttp://localhost:5000/ - -
bitwarden-web | info: Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware[2]
bitwarden-web | Sending file. Request path: ‘/index.html’. Physical path: ‘/app/index.html’
bitwarden-web | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
bitwarden-web | Request finished HTTP/1.1 GET h/ttp://localhost:5000/ - - - 200 1121 text/html 37.6861ms
bitwarden-attachments | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
bitwarden-attachments | Request starting HTTP/1.1 GET h/ttp://localhost:5000/alive - -
bitwarden-attachments | info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
bitwarden-attachments | Executing endpoint ‘/alive HTTP: GET’
bitwarden-attachments | info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
bitwarden-attachments | Executed endpoint ‘/alive HTTP: GET’
bitwarden-attachments | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
bitwarden-attachments | Request finished HTTP/1.1 GET http://localhost:5000/alive - - - 200 - - 35.8738ms
bitwarden-sso | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
bitwarden-sso | Request starting HTTP/1.1 GET h/ttp://localhost:5000/alive - -
bitwarden-sso | info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
bitwarden-sso | Executing endpoint ‘Bit.Sso.Controllers.HomeController.GetAlive (Sso)’
bitwarden-sso | info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
bitwarden-sso | Route matched with {action = “GetAlive”, controller = “Home”}. Executing controller action with signature System.DateTime GetAlive() on controller Bit.Sso.Controllers.HomeController (Sso).
bitwarden-sso | info: Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor[1]
bitwarden-sso | Executing ObjectResult, writing value of type ‘System.DateTime’.
bitwarden-sso | info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
bitwarden-sso | Executed action Bit.Sso.Controllers.HomeController.GetAlive (Sso) in 21.8756ms
bitwarden-sso | info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
bitwarden-sso | Executed endpoint ‘Bit.Sso.Controllers.HomeController.GetAlive (Sso)’
bitwarden-sso | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
bitwarden-sso | Request finished HTTP/1.1 GET h/ttp://localhost:5000/alive - - - 200 - application/json;+charset=utf-8 365.9993ms
bitwarden-portal | info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
bitwarden-portal | Request starting HTTP/1.1 GET /h/ttp://localhost:5000/alive - -
bitwarden-portal | info: Microsoft.AspNetCore.Routing.EndpointMiddleware[0]
bitwarden-portal | Executing endpoint ‘Bit.Portal.Controllers.HomeController.GetAlive (Portal)’
bitwarden-portal | info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[3]
bitwarden-portal | Route matched with {action = “GetAlive”, controller = “Home”}. Executing controller action with signature System.DateTime GetAlive() on controller Bit.Portal.Controllers.HomeController (Portal).
bitwarden-portal | info: Microsoft.AspNetCore.Mvc.Infrastructure.ObjectResultExecutor[1]
bitwarden-portal | Executing ObjectResult, writing value of type ‘System.DateTime’.
bitwarden-portal | info: Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker[2]
bitwarden-portal | Executed action Bit.Portal.Controllers.HomeController.GetAlive (Portal) in 28.868ms
bitwarden-portal | info: Microsoft.AspNetCore.Routing.EndpointMiddleware[1]
bitwarden-portal | Executed endpoint ‘Bit.Portal.Controllers.HomeController.GetAlive (Portal)’
bitwarden-portal | info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
bitwarden-portal | Request finished HTTP/1.1 GET XXX://localhost:5000/alive - - - 200 - application/json;+charset=utf-8 106.6237ms
bitwarden-identity | warn: Bit.Core.IdentityServer.ResourceOwnerPasswordValidator[12482444]
bitwarden-identity | => SpanId:3726959095b87f42, TraceId:d5b40527a22ad644b20e71a4a02ef191, ParentId:0000000000000000 => ConnectionId:0HMJKEJ8A1BRH => RequestPath:/identity/connect/token RequestId:0HMJKEJ8A1BRH:00000002
bitwarden-identity | Failed login attempt. 192.168.2.49

but the one I try to access continues to give me an error (this seems to be credentials).