mysql@t2-bitsx-db304:~$ lscpu
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
CPU(s): 4
On-line CPU(s) list: 0-3
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 4
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 42
Model name: Intel Xeon E312xx (Sandy Bridge)
Stepping: 1
CPU MHz: 2299.996
BogoMIPS: 4599.99
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 32K
L1i cache: 32K
L2 cache: 4096K
L3 cache: 16384K
NUMA node0 CPU(s): 0-3
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx rdtscp lm constant_tsc rep_good nopl xtopology eagerfpu pni pclmulqdq ssse3 cx16 sse4_1 sse4_2 x2apic popcnt tsc_deadline_timer aes xsave avx hypervisor lahf_lm xsaveopt arat
mysql@t2-bitsx-db304:~$ lsb_release -a
LSB Version: :core-4.1-amd64:core-4.1-noarch
Distributor ID: CentOS
Description: CentOS Linux release 7.4.1708 (Core)
Release: 7.4.1708
Codename: Core

For starters, could you please attach the MariaDB error log and specify what exactly it means, "can not login [to] the database"? What error are you getting?

Uploaded the error log.

Judging by the log, your upgrade went well and the server re-started fine after it in the matter of seconds.
So, repeating the question,
> what exactly it means, "can not login [to] the database"? What error are you getting?

Q> "can not login [to] the database"
I mean mariadb can not create socket to listen the port that it'll provide external service.
Before I killed the process, there's no any error to the error log and std output.

It can be reproduced by the datafiles that I want to upload.

> I mean mariadb can not create socket to listen the port that it'll provide external service.
Right, sorry, I missed it.

There was the bug MDEV-19918 in earlier 10.4 versions which would have the same effect. It was fixed in 10.4.14, but since you're upgrading to 10.4.12, you can be affected.
You are using the audit plugin and you have plugin-load=server_audit=server_audit.so, so all that it would take is also having the plugin in mysql.plugin table (or having there something that couldn't be loaded, but I suppose it is less likely).
Could you try to disable plugin-load=server_audit=server_audit.so in the config file, restart, and if it starts, inspect the contents of mysql.plugin?

Let me try, and feedback later.

It's really caused by the audit plugin, after disabled it, mariadb can create socket and listen the port now.
Thank you very much.