SystemLog | Spring AOP 实现记录系统操作日志 | Aspect Oriented library

According this line

The NLog Database-Target doesn't have a Layout-property, that can be assigned. Instead use input parameter-collection.

WindowsIdentity-nuget-package is required for ${windows-identity} on NetCore, and must be included:

Because you added only the --dbpath option in the command line the rest of settings are ignored ( defaults are used). Best is to add all configuration settings in the mongodb.conf file and start the mongodb service with the config file as follow:

This line say it all:

The answer is for other people who encountered this.

So basically service mongod start didn't run using root user.

And I don't know when it have been changed.

However you need to lookup the user in /lib/systemd/system/mongod.service

In my case is mongodb

Then run

sudo chown -R mongodb:mongodb {your_log_path} {your_db_path}

You have this problem:

I've changed the Form's BackColor and TransparencyKey to Fuchsia, and the Label.ForeColor to Gray. Note how the TransparencyKey outlines the text. Here is a good explanation.

The suggested fix - commented above - is to draw the string yourself, Gdi+ way to have a control over the string rendering quality through the TextRenderingHint.SingleBitPerPixelGridFit hinting which provides a better antialiasing for this problem.

This is because of how await works. When await acts on a Task that is incomplete, it returns. So your program is working like this:

1. Main runs, and calls Initializer.Start()
2. Initializer.Start() runs and calls ChromiumInfo.InitializeAsync()
3. ChromiumInfo.InitializeAsync() runs until it calls await Task.WhenAll(settingInit, browserSettingInit)
4. Because Task.WhenAll returns an incomplete Task, ChromiumInfo.InitializeAsync() returns its own incomplete Task and execution returns to Initializer.Start().
5. The await in Initializer.Start() sees the incomplete Task and returns its own incomplete Task and execution returns to Main().
6. Because Main() doesn't act on the Task returned by Initializer.Start(), execution continues to the next line, which is the end of the program.

The solution is fairly simple: Change your Main method to async and use await.

• Check the registry ‘HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTFRS\Parameters\SysVol\DomainName’ on the domain controller. This key should not exist if SYSVOL replication is happening correctly on the domain controller and if the sysvol directory is published correctly. Also, if this key doesn’t exist means all potential source domain controllers in the domain should themselves have shared the NETLOGON and SYSVOL shares and applied default domain and domain controllers policy.

• Please check for event 1704s in the application log of the domain controller as the ‘Enterprise Domain Controllers’ group should have the ‘Access this computer from the network’ right assigned in default domain controllers policy.

• Also, please check the SYSVOL replica set under advanced features in ‘Active Directory Users and Computers’ under CN=’domain system volume’,CN=file replication service,CN=system,CN= as well as run the command ‘NTFRSUTL DS [DCNAME]’ on the domain controller. Output shows that the mentioned domain controller object is appearing in ‘CN=Domain System Volume(SYSVOL share),CN=NTFRS Subscriptions,CN=%DCNAME%,OU=Domain Controllers,DC=’. This will mostly resolve the issue of SYSVOL share not publishing and communicating with the client network.

• Check the DFS replication state in the DCs in your domain by running the following command: -

"Detected unclean shutdown" means the server was not stopped gracefully. Depending on the nature of the shutdown, there may be inconsistency or corruption present in the data files.

So now it is checking the data files and rolling them back to a self-consistent state.

The "has been running for" messages show it is making progress. Let it finish and it will hopefully be able to return the data to a usable state.