I tried to run the application using docker compose since I want to play a bit with it before digging inside it and install development prerequisites. But i cannot open it in my browser.
I run the application using docker-compose up, I even tried with docker compose up.
Then I try to open the application from this URL:
I cloned the repository from master (36631d3e0e5a71954344c218e4c9f4a8aa066f97 at the time).
Windows 10
WSL2 (Ubuntu 20.04)
Docker for windows 4.5.1 (74721)
docker-compose version 1.25.0 (when run with docker-compose)
Docker Compose version v2.2.3 (when run with docker compose)
Docker Version
Client:
Version: 20.10.7
API version: 1.41
Go version: go1.13.8
Git commit: 20.10.7-0ubuntu5~20.04.2
Built: Mon Nov 1 00:34:17 2021
OS/Arch: linux/amd64
Context: default
Experimental: true
Server: Docker Engine - Community
Engine:
Version: 20.10.12
API version: 1.41 (minimum version 1.12)
Go version: go1.16.12
Git commit: 459d0df
Built: Mon Dec 13 11:43:56 2021
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.4.12
GitCommit: 7b11cfaabd73bb80907dd23182b9347b4245eb5d
runc:
Version: 1.0.2
GitCommit: v1.0.2-0-g52b36a2
docker-init:
Version: 0.19.0
GitCommit: de40ad0
## Logs
Log for `mymeetings_backend`
Waiting 60 seconds to start backend
Backend starting...
[16:15:01 INF] [API] [] Logger configured
[16:15:01 INF] [API] [] Connection string:Server=mymeetingsdb,1433;Database=MyMeetings;User=sa;Password=Test@12345
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0]
User profile is available. Using '/root/.aspnet/DataProtection-Keys' as key repository; keys will not be encrypted at rest.
info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[58]
Creating key {663ff309-4301-4a06-9f02-270ba6cfbb0e} with creation date 2022-02-24 16:15:01Z, activation date 2022-02-24 16:15:01Z, and expiration date 2022-05-25 16:15:01Z.
warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35]
No XML encryptor configured. Key {663ff309-4301-4a06-9f02-270ba6cfbb0e} may be persisted to storage in unencrypted form.
info: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[39]
Writing data to file '/root/.aspnet/DataProtection-Keys/key-663ff309-4301-4a06-9f02-270ba6cfbb0e.xml'.
[16:15:01 INF] [Meetings] [] Quartz starting...
[16:15:01 INF] [Meetings] [] Quartz started.
[16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.Administration.IntegrationEvents.MeetingGroupProposals.MeetingGroupProposalAcceptedIntegrationEvent
[16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.Payments.IntegrationEvents.SubscriptionExpirationDateChangedIntegrationEvent
[16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.UserAccess.IntegrationEvents.NewUserRegisteredIntegrationEvent
[16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.Payments.IntegrationEvents.MeetingFeePaidIntegrationEvent
[16:15:01 INF] [Administration] [] Quartz starting...
[16:15:01 INF] [Meetings] [] Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl
[16:15:01 INF] [Meetings] [] Quartz Scheduler v.3.0.7.0 created.
[16:15:01 INF] [Meetings] [] RAMJobStore initialized.
[16:15:01 INF] [Meetings] [] Scheduler meta-data: Quartz Scheduler (v3.0.7.0) 'Administration' with instanceId 'NONCLUSTERED'
Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 10 threads.
Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered.
[16:15:01 INF] [Meetings] [] Scheduler Administration$_NON_CLUSTERED started.
[16:15:01 INF] [Administration] [] Quartz started.
[16:15:01 INF] [Administration] [] Subscribe to CompanyName.MyMeetings.Modules.Meetings.IntegrationEvents.MeetingGroupProposedIntegrationEvent
[16:15:01 INF] [Administration] [] Subscribe to CompanyName.MyMeetings.Modules.UserAccess.IntegrationEvents.NewUserRegisteredIntegrationEvent
[16:15:01 INF] [UserAccess] [] Quartz starting...
[16:15:01 INF] [UserAccess] [] Quartz started.
[16:15:01 INF] [UserAccess] [] Subscribe to CompanyName.MyMeetings.Modules.Meetings.IntegrationEvents.MemberCreatedIntegrationEvent
[16:15:02 INF] [Payments] [] Quartz starting...
[16:15:02 INF] [Payments] [] Quartz started.
[16:15:02 INF] [Payments] [] Subscribe to CompanyName.MyMeetings.Modules.Administration.IntegrationEvents.MeetingGroupProposals.MeetingGroupProposalAcceptedIntegrationEvent
[16:15:02 INF] [Payments] [] Subscribe to CompanyName.MyMeetings.Modules.UserAccess.IntegrationEvents.NewUserRegisteredIntegrationEvent
[16:15:02 INF] [Payments] [] Subscribe to CompanyName.MyMeetings.Modules.Meetings.IntegrationEvents.MeetingAttendeeAddedIntegrationEvent
info: IdentityServer4.Startup[0]
Starting IdentityServer4 version 3.1.2.0
info: IdentityServer4.Startup[0]
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.
info: IdentityServer4.Startup[0]
Using the default authentication scheme Bearer for IdentityServer
info: IdentityServer4.Startup[0]
Authentication scheme Bearer is configured for IdentityServer, but it is not a scheme that supports signin (like cookies). If you support interactive logins via the browser, then a cookie-based scheme should be used.
dbug: IdentityServer4.Startup[0]
Using Bearer as default ASP.NET Core scheme for authentication
dbug: IdentityServer4.Startup[0]
Using Bearer as default ASP.NET Core scheme for sign-in
dbug: IdentityServer4.Startup[0]
Using Bearer as default ASP.NET Core scheme for sign-out
dbug: IdentityServer4.Startup[0]
Using Bearer as default ASP.NET Core scheme for challenge
dbug: IdentityServer4.Startup[0]
Using Bearer as default ASP.NET Core scheme for forbid
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://[::]:80
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /app
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Request starting HTTP/1.1 GET http://localhost:5000/
dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9]
AuthenticationScheme: Bearer was not authenticated.
dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9]
AuthenticationScheme: Bearer was not authenticated.
warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3]
Failed to determine the https port for redirect.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Request finished in 98.7663ms 404
info: Microsoft.AspNetCore.Hosting.Diagnostics[1]
Request starting HTTP/1.1 GET http://localhost:5000/
dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9]
AuthenticationScheme: Bearer was not authenticated.
dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9]
AuthenticationScheme: Bearer was not authenticated.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Request finished in 2.7497ms 404
Log for `modular-monolith-with-ddd_mymeetingsdb_1`
Starting sql server..
SQL server started.
2022-02-24 16:14:00.14 Server The licensing PID was successfully processed. The new edition is [Express Edition].
2022-02-24 16:14:00.45 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'.
2022-02-24 16:14:00.48 Server Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart.
2022-02-24 16:14:00.49 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'.
2022-02-24 16:14:00.50 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'.
2022-02-24 16:14:00.52 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'.
2022-02-24 16:14:00.53 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'.
2022-02-24 16:14:00.55 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'.
2022-02-24 16:14:00.65 Server Microsoft SQL Server 2017 (RTM-CU22-GDR) (KB4583457) - 14.0.3370.1 (X64)
Nov 6 2020 18:19:52
Copyright (C) 2017 Microsoft Corporation
Express Edition (64-bit) on Linux (Ubuntu 16.04.7 LTS)
2022-02-24 16:14:00.65 Server UTC adjustment: 0:00
2022-02-24 16:14:00.66 Server (c) Microsoft Corporation.
2022-02-24 16:14:00.66 Server All rights reserved.
2022-02-24 16:14:00.66 Server Server process ID is 40.
2022-02-24 16:14:00.66 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'.
2022-02-24 16:14:00.66 Server Registry startup parameters:
-d /var/opt/mssql/data/master.mdf
-l /var/opt/mssql/data/mastlog.ldf
-e /var/opt/mssql/log/errorlog
2022-02-24 16:14:00.67 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required.
2022-02-24 16:14:00.68 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2022-02-24 16:14:00.69 Server Detected 10188 MB of RAM. This is an informational message; no user action is required.
2022-02-24 16:14:00.69 Server Using conventional memory in the memory manager.
2022-02-24 16:14:00.69 Server Page exclusion bitmap is enabled.
2022-02-24 16:14:00.83 Server Buffer pool extension is already disabled. No action is necessary.
2022-02-24 16:14:00.99 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled.
2022-02-24 16:14:01.00 Server Implied authentication manager initialization failed. Implied authentication will be disabled.
2022-02-24 16:14:01.01 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-02-24 16:14:01.03 Server Query Store settings initialized with enabled = 1,
2022-02-24 16:14:01.05 Server The maximum number of dedicated administrator connections for this instance is '1'
2022-02-24 16:14:01.05 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff: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-02-24 16:14:01.07 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-02-24 16:14:01.08 Server In-Memory OLTP initialized on standard machine.
2022-02-24 16:14:01.12 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-02-24 16:14:01.14 Server Software Usage Metrics is disabled.
2022-02-24 16:14:01.14 spid6s Starting up database 'master'.
ForceFlush feature is enabled for log durability.
2022-02-24 16:14:01.24 spid6s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written.
2022-02-24 16:14:01.37 spid6s Converting database 'master' from version 862 to the current version 869.
2022-02-24 16:14:01.37 spid6s Database 'master' running the upgrade step from version 862 to version 863.
2022-02-24 16:14:01.41 spid6s Database 'master' running the upgrade step from version 863 to version 864.
2022-02-24 16:14:01.44 spid6s Database 'master' running the upgrade step from version 864 to version 865.
2022-02-24 16:14:01.47 spid6s Database 'master' running the upgrade step from version 865 to version 866.
2022-02-24 16:14:01.48 spid6s Database 'master' running the upgrade step from version 866 to version 867.
2022-02-24 16:14:01.50 spid6s Database 'master' running the upgrade step from version 867 to version 868.
2022-02-24 16:14:01.53 spid6s Database 'master' running the upgrade step from version 868 to version 869.
2022-02-24 16:14:01.83 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required.
2022-02-24 16:14:01.83 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required.
2022-02-24 16:14:01.89 spid6s SQL Trace ID 1 was started by login "sa".
2022-02-24 16:14:01.90 spid6s Server name is '44adf983a352'. This is an informational message only. No user action is required.
2022-02-24 16:14:01.91 spid18s Password policy update was successful.
2022-02-24 16:14:01.92 spid21s Always On: The availability replica manager is starting. This is an informational message only. No user action is required.
2022-02-24 16:14:01.93 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-02-24 16:14:01.93 spid6s Starting up database 'msdb'.
2022-02-24 16:14:01.93 spid11s Starting up database 'mssqlsystemresource'.
2022-02-24 16:14:01.94 spid11s The resource database build version is 14.00.3370. This is an informational message only. No user action is required.
2022-02-24 16:14:01.96 spid11s Starting up database 'model'.
2022-02-24 16:14:02.05 spid6s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written.
2022-02-24 16:14:02.07 spid11s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written.
2022-02-24 16:14:02.08 spid6s Converting database 'msdb' from version 862 to the current version 869.
2022-02-24 16:14:02.09 spid6s Database 'msdb' running the upgrade step from version 862 to version 863.
2022-02-24 16:14:02.12 spid11s Converting database 'model' from version 862 to the current version 869.
2022-02-24 16:14:02.13 spid11s Database 'model' running the upgrade step from version 862 to version 863.
2022-02-24 16:14:02.16 spid18s A self-generated certificate was successfully loaded for encryption.
2022-02-24 16:14:02.17 spid18s Server is listening on [ 'any' 1433].
2022-02-24 16:14:02.17 spid18s Server is listening on [ 'any' 1433].
2022-02-24 16:14:02.17 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-02-24 16:14:02.17 spid6s Database 'msdb' running the upgrade step from version 863 to version 864.
2022-02-24 16:14:02.19 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2022-02-24 16:14:02.20 spid11s Database 'model' running the upgrade step from version 863 to version 864.
2022-02-24 16:14:02.22 spid6s Database 'msdb' running the upgrade step from version 864 to version 865.
2022-02-24 16:14:02.24 spid11s Database 'model' running the upgrade step from version 864 to version 865.
2022-02-24 16:14:02.25 spid6s Database 'msdb' running the upgrade step from version 865 to version 866.
2022-02-24 16:14:02.27 spid11s Database 'model' running the upgrade step from version 865 to version 866.
2022-02-24 16:14:02.27 spid6s Database 'msdb' running the upgrade step from version 866 to version 867.
2022-02-24 16:14:02.29 spid11s Database 'model' running the upgrade step from version 866 to version 867.
2022-02-24 16:14:02.30 spid6s Database 'msdb' running the upgrade step from version 867 to version 868.
2022-02-24 16:14:02.31 spid11s Database 'model' running the upgrade step from version 867 to version 868.
2022-02-24 16:14:02.32 spid6s Database 'msdb' running the upgrade step from version 868 to version 869.
2022-02-24 16:14:02.34 spid11s Database 'model' running the upgrade step from version 868 to version 869.
2022-02-24 16:14:02.48 spid11s Polybase feature disabled.
2022-02-24 16:14:02.48 spid11s Clearing tempdb database.
2022-02-24 16:14:02.74 spid11s Starting up database 'tempdb'.
2022-02-24 16:14:02.90 spid21s The Service Broker endpoint is in disabled or stopped state.
2022-02-24 16:14:02.90 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2022-02-24 16:14:02.92 spid21s Service Broker manager has started.
2022-02-24 16:14:03.04 spid6s Recovery is complete. This is an informational message only. No user action is required.
2022-02-24 16:14:03.05 spid23s The default language (LCID 0) has been set for engine and full-text services.
Create database..
2022-02-24 16:14:27.51 spid51 Starting up database 'MyMeetings'.
2022-02-24 16:14:27.60 spid51 Parallel redo is started for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:14:27.62 spid51 Parallel redo is shutdown for database 'MyMeetings' with worker pool size [4].
Changed database context to 'MyMeetings'.
Database created
2022-02-24 16:14:32.69 spid51 Starting up database 'MyMeetings'.
2022-02-24 16:14:32.80 spid51 Parallel redo is started for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:14:32.82 spid51 Parallel redo is shutdown for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:15:02.13 spid51 Starting up database 'MyMeetings'.
2022-02-24 16:15:02.24 spid51 Parallel redo is started for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:15:02.25 spid51 Parallel redo is shutdown for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:24:28.42 Logon Error: 17836, Severity: 20, State: 17.
2022-02-24 16:24:28.42 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.18.0.1]
2022-02-24 16:24:31.20 Logon Error: 17836, Severity: 20, State: 17.
2022-02-24 16:24:31.20 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.18.0.1]
2022-02-24 16:24:36.25 Logon Error: 17836, Severity: 20, State: 17.
2022-02-24 16:24:36.25 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.18.0.1]
Issue
I tried to run the application using docker compose since I want to play a bit with it before digging inside it and install development prerequisites. But i cannot open it in my browser.
I run the application using
docker-compose up, I even tried withdocker compose up. Then I try to open the application from this URL:http://localhost:5000
But I get a 404 error
Are there some steps I am missing?
Context
I cloned the repository from master (36631d3e0e5a71954344c218e4c9f4a8aa066f97 at the time).
docker-compose)docker compose)Server: Docker Engine - Community Engine: Version: 20.10.12 API version: 1.41 (minimum version 1.12) Go version: go1.16.12 Git commit: 459d0df Built: Mon Dec 13 11:43:56 2021 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.12 GitCommit: 7b11cfaabd73bb80907dd23182b9347b4245eb5d runc: Version: 1.0.2 GitCommit: v1.0.2-0-g52b36a2 docker-init: Version: 0.19.0 GitCommit: de40ad0
Waiting 60 seconds to start backend Backend starting... [16:15:01 INF] [API] [] Logger configured [16:15:01 INF] [API] [] Connection string:Server=mymeetingsdb,1433;Database=MyMeetings;User=sa;Password=Test@12345 warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60] Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed. info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[0] User profile is available. Using '/root/.aspnet/DataProtection-Keys' as key repository; keys will not be encrypted at rest. info: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[58] Creating key {663ff309-4301-4a06-9f02-270ba6cfbb0e} with creation date 2022-02-24 16:15:01Z, activation date 2022-02-24 16:15:01Z, and expiration date 2022-05-25 16:15:01Z. warn: Microsoft.AspNetCore.DataProtection.KeyManagement.XmlKeyManager[35] No XML encryptor configured. Key {663ff309-4301-4a06-9f02-270ba6cfbb0e} may be persisted to storage in unencrypted form. info: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[39] Writing data to file '/root/.aspnet/DataProtection-Keys/key-663ff309-4301-4a06-9f02-270ba6cfbb0e.xml'. [16:15:01 INF] [Meetings] [] Quartz starting... [16:15:01 INF] [Meetings] [] Quartz started. [16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.Administration.IntegrationEvents.MeetingGroupProposals.MeetingGroupProposalAcceptedIntegrationEvent [16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.Payments.IntegrationEvents.SubscriptionExpirationDateChangedIntegrationEvent [16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.UserAccess.IntegrationEvents.NewUserRegisteredIntegrationEvent [16:15:01 INF] [Meetings] [] Subscribe to CompanyName.MyMeetings.Modules.Payments.IntegrationEvents.MeetingFeePaidIntegrationEvent [16:15:01 INF] [Administration] [] Quartz starting... [16:15:01 INF] [Meetings] [] Initialized Scheduler Signaller of type: Quartz.Core.SchedulerSignalerImpl [16:15:01 INF] [Meetings] [] Quartz Scheduler v.3.0.7.0 created. [16:15:01 INF] [Meetings] [] RAMJobStore initialized. [16:15:01 INF] [Meetings] [] Scheduler meta-data: Quartz Scheduler (v3.0.7.0) 'Administration' with instanceId 'NONCLUSTERED' Scheduler class: 'Quartz.Core.QuartzScheduler' - running locally. NOT STARTED. Currently in standby mode. Number of jobs executed: 0 Using thread pool 'Quartz.Simpl.DefaultThreadPool' - with 10 threads. Using job-store 'Quartz.Simpl.RAMJobStore' - which does not support persistence. and is not clustered. [16:15:01 INF] [Meetings] [] Scheduler Administration$_NON_CLUSTERED started. [16:15:01 INF] [Administration] [] Quartz started. [16:15:01 INF] [Administration] [] Subscribe to CompanyName.MyMeetings.Modules.Meetings.IntegrationEvents.MeetingGroupProposedIntegrationEvent [16:15:01 INF] [Administration] [] Subscribe to CompanyName.MyMeetings.Modules.UserAccess.IntegrationEvents.NewUserRegisteredIntegrationEvent [16:15:01 INF] [UserAccess] [] Quartz starting... [16:15:01 INF] [UserAccess] [] Quartz started. [16:15:01 INF] [UserAccess] [] Subscribe to CompanyName.MyMeetings.Modules.Meetings.IntegrationEvents.MemberCreatedIntegrationEvent [16:15:02 INF] [Payments] [] Quartz starting... [16:15:02 INF] [Payments] [] Quartz started. [16:15:02 INF] [Payments] [] Subscribe to CompanyName.MyMeetings.Modules.Administration.IntegrationEvents.MeetingGroupProposals.MeetingGroupProposalAcceptedIntegrationEvent [16:15:02 INF] [Payments] [] Subscribe to CompanyName.MyMeetings.Modules.UserAccess.IntegrationEvents.NewUserRegisteredIntegrationEvent [16:15:02 INF] [Payments] [] Subscribe to CompanyName.MyMeetings.Modules.Meetings.IntegrationEvents.MeetingAttendeeAddedIntegrationEvent info: IdentityServer4.Startup[0] Starting IdentityServer4 version 3.1.2.0 info: IdentityServer4.Startup[0] 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. info: IdentityServer4.Startup[0] Using the default authentication scheme Bearer for IdentityServer info: IdentityServer4.Startup[0] Authentication scheme Bearer is configured for IdentityServer, but it is not a scheme that supports signin (like cookies). If you support interactive logins via the browser, then a cookie-based scheme should be used. dbug: IdentityServer4.Startup[0] Using Bearer as default ASP.NET Core scheme for authentication dbug: IdentityServer4.Startup[0] Using Bearer as default ASP.NET Core scheme for sign-in dbug: IdentityServer4.Startup[0] Using Bearer as default ASP.NET Core scheme for sign-out dbug: IdentityServer4.Startup[0] Using Bearer as default ASP.NET Core scheme for challenge dbug: IdentityServer4.Startup[0] Using Bearer as default ASP.NET Core scheme for forbid info: Microsoft.Hosting.Lifetime[0] Now listening on: http://[::]:80 info: Microsoft.Hosting.Lifetime[0] Application started. Press Ctrl+C to shut down. info: Microsoft.Hosting.Lifetime[0] Hosting environment: Production info: Microsoft.Hosting.Lifetime[0] Content root path: /app info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Request starting HTTP/1.1 GET http://localhost:5000/
dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9] AuthenticationScheme: Bearer was not authenticated. dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9] AuthenticationScheme: Bearer was not authenticated. warn: Microsoft.AspNetCore.HttpsPolicy.HttpsRedirectionMiddleware[3] Failed to determine the https port for redirect. info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Request finished in 98.7663ms 404 info: Microsoft.AspNetCore.Hosting.Diagnostics[1] Request starting HTTP/1.1 GET http://localhost:5000/
dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9] AuthenticationScheme: Bearer was not authenticated. dbug: IdentityServer4.AccessTokenValidation.IdentityServerAuthenticationHandler[9] AuthenticationScheme: Bearer was not authenticated. info: Microsoft.AspNetCore.Hosting.Diagnostics[2] Request finished in 2.7497ms 404
Starting sql server.. SQL server started. 2022-02-24 16:14:00.14 Server The licensing PID was successfully processed. The new edition is [Express Edition]. 2022-02-24 16:14:00.45 Server Setup step is copying system data file 'C:\templatedata\master.mdf' to '/var/opt/mssql/data/master.mdf'. 2022-02-24 16:14:00.48 Server Did not find an existing master data file /var/opt/mssql/data/master.mdf, copying the missing default master and other system database files. If you have moved the database location, but not moved the database files, startup may fail. To repair: shutdown SQL Server, move the master database to configured location, and restart. 2022-02-24 16:14:00.49 Server Setup step is copying system data file 'C:\templatedata\mastlog.ldf' to '/var/opt/mssql/data/mastlog.ldf'. 2022-02-24 16:14:00.50 Server Setup step is copying system data file 'C:\templatedata\model.mdf' to '/var/opt/mssql/data/model.mdf'. 2022-02-24 16:14:00.52 Server Setup step is copying system data file 'C:\templatedata\modellog.ldf' to '/var/opt/mssql/data/modellog.ldf'. 2022-02-24 16:14:00.53 Server Setup step is copying system data file 'C:\templatedata\msdbdata.mdf' to '/var/opt/mssql/data/msdbdata.mdf'. 2022-02-24 16:14:00.55 Server Setup step is copying system data file 'C:\templatedata\msdblog.ldf' to '/var/opt/mssql/data/msdblog.ldf'. 2022-02-24 16:14:00.65 Server Microsoft SQL Server 2017 (RTM-CU22-GDR) (KB4583457) - 14.0.3370.1 (X64) Nov 6 2020 18:19:52 Copyright (C) 2017 Microsoft Corporation Express Edition (64-bit) on Linux (Ubuntu 16.04.7 LTS) 2022-02-24 16:14:00.65 Server UTC adjustment: 0:00 2022-02-24 16:14:00.66 Server (c) Microsoft Corporation. 2022-02-24 16:14:00.66 Server All rights reserved. 2022-02-24 16:14:00.66 Server Server process ID is 40. 2022-02-24 16:14:00.66 Server Logging SQL Server messages in file '/var/opt/mssql/log/errorlog'. 2022-02-24 16:14:00.66 Server Registry startup parameters: -d /var/opt/mssql/data/master.mdf -l /var/opt/mssql/data/mastlog.ldf -e /var/opt/mssql/log/errorlog 2022-02-24 16:14:00.67 Server SQL Server detected 1 sockets with 6 cores per socket and 12 logical processors per socket, 12 total logical processors; using 8 logical processors based on SQL Server licensing. This is an informational message; no user action is required. 2022-02-24 16:14:00.68 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required. 2022-02-24 16:14:00.69 Server Detected 10188 MB of RAM. This is an informational message; no user action is required. 2022-02-24 16:14:00.69 Server Using conventional memory in the memory manager. 2022-02-24 16:14:00.69 Server Page exclusion bitmap is enabled. 2022-02-24 16:14:00.83 Server Buffer pool extension is already disabled. No action is necessary. 2022-02-24 16:14:00.99 Server InitializeExternalUserGroupSid failed. Implied authentication will be disabled. 2022-02-24 16:14:01.00 Server Implied authentication manager initialization failed. Implied authentication will be disabled. 2022-02-24 16:14:01.01 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-02-24 16:14:01.03 Server Query Store settings initialized with enabled = 1, 2022-02-24 16:14:01.05 Server The maximum number of dedicated administrator connections for this instance is '1' 2022-02-24 16:14:01.05 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff: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-02-24 16:14:01.07 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-02-24 16:14:01.08 Server In-Memory OLTP initialized on standard machine. 2022-02-24 16:14:01.12 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-02-24 16:14:01.14 Server Software Usage Metrics is disabled. 2022-02-24 16:14:01.14 spid6s Starting up database 'master'. ForceFlush feature is enabled for log durability. 2022-02-24 16:14:01.24 spid6s The tail of the log for database master is being rewritten to match the new sector size of 4096 bytes. 3072 bytes at offset 418816 in file /var/opt/mssql/data/mastlog.ldf will be written. 2022-02-24 16:14:01.37 spid6s Converting database 'master' from version 862 to the current version 869. 2022-02-24 16:14:01.37 spid6s Database 'master' running the upgrade step from version 862 to version 863. 2022-02-24 16:14:01.41 spid6s Database 'master' running the upgrade step from version 863 to version 864. 2022-02-24 16:14:01.44 spid6s Database 'master' running the upgrade step from version 864 to version 865. 2022-02-24 16:14:01.47 spid6s Database 'master' running the upgrade step from version 865 to version 866. 2022-02-24 16:14:01.48 spid6s Database 'master' running the upgrade step from version 866 to version 867. 2022-02-24 16:14:01.50 spid6s Database 'master' running the upgrade step from version 867 to version 868. 2022-02-24 16:14:01.53 spid6s Database 'master' running the upgrade step from version 868 to version 869. 2022-02-24 16:14:01.83 spid6s SQL Server Audit is starting the audits. This is an informational message. No user action is required. 2022-02-24 16:14:01.83 spid6s SQL Server Audit has started the audits. This is an informational message. No user action is required. 2022-02-24 16:14:01.89 spid6s SQL Trace ID 1 was started by login "sa". 2022-02-24 16:14:01.90 spid6s Server name is '44adf983a352'. This is an informational message only. No user action is required. 2022-02-24 16:14:01.91 spid18s Password policy update was successful. 2022-02-24 16:14:01.92 spid21s Always On: The availability replica manager is starting. This is an informational message only. No user action is required. 2022-02-24 16:14:01.93 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-02-24 16:14:01.93 spid6s Starting up database 'msdb'. 2022-02-24 16:14:01.93 spid11s Starting up database 'mssqlsystemresource'. 2022-02-24 16:14:01.94 spid11s The resource database build version is 14.00.3370. This is an informational message only. No user action is required. 2022-02-24 16:14:01.96 spid11s Starting up database 'model'. 2022-02-24 16:14:02.05 spid6s The tail of the log for database msdb is being rewritten to match the new sector size of 4096 bytes. 512 bytes at offset 306688 in file /var/opt/mssql/data/MSDBLog.ldf will be written. 2022-02-24 16:14:02.07 spid11s The tail of the log for database model is being rewritten to match the new sector size of 4096 bytes. 2048 bytes at offset 75776 in file /var/opt/mssql/data/modellog.ldf will be written. 2022-02-24 16:14:02.08 spid6s Converting database 'msdb' from version 862 to the current version 869. 2022-02-24 16:14:02.09 spid6s Database 'msdb' running the upgrade step from version 862 to version 863. 2022-02-24 16:14:02.12 spid11s Converting database 'model' from version 862 to the current version 869. 2022-02-24 16:14:02.13 spid11s Database 'model' running the upgrade step from version 862 to version 863. 2022-02-24 16:14:02.16 spid18s A self-generated certificate was successfully loaded for encryption. 2022-02-24 16:14:02.17 spid18s Server is listening on [ 'any' 1433].
2022-02-24 16:14:02.17 spid18s Server is listening on [ 'any' 1433].
2022-02-24 16:14:02.17 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-02-24 16:14:02.17 spid6s Database 'msdb' running the upgrade step from version 863 to version 864.
2022-02-24 16:14:02.19 spid18s SQL Server is now ready for client connections. This is an informational message; no user action is required.
2022-02-24 16:14:02.20 spid11s Database 'model' running the upgrade step from version 863 to version 864.
2022-02-24 16:14:02.22 spid6s Database 'msdb' running the upgrade step from version 864 to version 865.
2022-02-24 16:14:02.24 spid11s Database 'model' running the upgrade step from version 864 to version 865.
2022-02-24 16:14:02.25 spid6s Database 'msdb' running the upgrade step from version 865 to version 866.
2022-02-24 16:14:02.27 spid11s Database 'model' running the upgrade step from version 865 to version 866.
2022-02-24 16:14:02.27 spid6s Database 'msdb' running the upgrade step from version 866 to version 867.
2022-02-24 16:14:02.29 spid11s Database 'model' running the upgrade step from version 866 to version 867.
2022-02-24 16:14:02.30 spid6s Database 'msdb' running the upgrade step from version 867 to version 868.
2022-02-24 16:14:02.31 spid11s Database 'model' running the upgrade step from version 867 to version 868.
2022-02-24 16:14:02.32 spid6s Database 'msdb' running the upgrade step from version 868 to version 869.
2022-02-24 16:14:02.34 spid11s Database 'model' running the upgrade step from version 868 to version 869.
2022-02-24 16:14:02.48 spid11s Polybase feature disabled.
2022-02-24 16:14:02.48 spid11s Clearing tempdb database.
2022-02-24 16:14:02.74 spid11s Starting up database 'tempdb'.
2022-02-24 16:14:02.90 spid21s The Service Broker endpoint is in disabled or stopped state.
2022-02-24 16:14:02.90 spid21s The Database Mirroring endpoint is in disabled or stopped state.
2022-02-24 16:14:02.92 spid21s Service Broker manager has started.
2022-02-24 16:14:03.04 spid6s Recovery is complete. This is an informational message only. No user action is required.
2022-02-24 16:14:03.05 spid23s The default language (LCID 0) has been set for engine and full-text services.
Create database..
2022-02-24 16:14:27.51 spid51 Starting up database 'MyMeetings'.
2022-02-24 16:14:27.60 spid51 Parallel redo is started for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:14:27.62 spid51 Parallel redo is shutdown for database 'MyMeetings' with worker pool size [4].
Changed database context to 'MyMeetings'.
Database created
2022-02-24 16:14:32.69 spid51 Starting up database 'MyMeetings'.
2022-02-24 16:14:32.80 spid51 Parallel redo is started for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:14:32.82 spid51 Parallel redo is shutdown for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:15:02.13 spid51 Starting up database 'MyMeetings'.
2022-02-24 16:15:02.24 spid51 Parallel redo is started for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:15:02.25 spid51 Parallel redo is shutdown for database 'MyMeetings' with worker pool size [4].
2022-02-24 16:24:28.42 Logon Error: 17836, Severity: 20, State: 17.
2022-02-24 16:24:28.42 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.18.0.1]
2022-02-24 16:24:31.20 Logon Error: 17836, Severity: 20, State: 17.
2022-02-24 16:24:31.20 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.18.0.1]
2022-02-24 16:24:36.25 Logon Error: 17836, Severity: 20, State: 17.
2022-02-24 16:24:36.25 Logon Length specified in network packet payload did not match number of bytes read; the connection has been closed. Please contact the vendor of the client library. [CLIENT: 172.18.0.1]