Opengauss simple version installation error

[[email protected] simpleInstall]$ sh install.sh -w "[email protected]" &&source ~/.bashrc
[step 1]: check parameter
[step 2]: check install env and os setting
[step 3]: change_gausshome_owner
[step 4]: set environment variables

/home/omm/.bashrc: line 16: ulimit: open files: cannot modify limit: Operation not permitted
[step 6]: init datanode
The files belonging to this database system will be owned by user "omm".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.UTF-8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

could not create directory /var/log/omm: Permission denied
creating directory /opt/opengauss/software/data/single_node ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers ... 32MB
creating configuration files ... ok
Begin init undo subsystem meta.
[INIT UNDO] Init undo subsystem meta successfully.
creating template1 database in /opt/opengauss/software/data/single_node/base/1 ... The core dump path is an invalid directory
2022-07-19 13:58:00.740 [unknown] [unknown] localhost 140169086360640 0[0:0#0] [BACKEND] WARNING: macAddr is 21076/13163551, sysidentifier is 1381236936/3693047771, randomNum is 3961352155
ok
initializing pg_authid ... ok
setting password ... ok
initializing dependencies ... ok
loading PL/pgSQL server-side language ... ok
creating system views ... ok
creating performance views ... ok
loading system objects' descriptions ... ok
creating collations ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
initialize global configure for bucketmap length ... ok
creating information schema ... ok
loading foreign-data wrapper for distfs access ... ok
loading foreign-data wrapper for hdfs access ... ok
loading foreign-data wrapper for log access ... ok
loading hstore extension ... ok
loading foreign-data wrapper for MOT access ... ok
loading security plugin ... ok
update system tables ... ok
creating snapshots catalog ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok
freezing database template0 ... ok
freezing database template1 ... ok
freezing database postgres ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run gs_initdb.

Success. You can now start the database server of single node using:

gaussdb -D /opt/opengauss/software/data/single_node --single_node
or
gs_ctl start -D /opt/opengauss/software/data/single_node -Z single_node -l logfile

[step 7]: start datanode
could not create directory /var/log/omm: Permission denied
[2022-07-19 13:58:43.914][4252][][gs_ctl]: gs_ctl started,datadir is /opt/opengauss/software/data/single_node
[2022-07-19 13:58:44.034][4252][][gs_ctl]: waiting for server to start...
.0 LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.

0 LOG: [Alarm Module]Host Name: host134

0 LOG: [Alarm Module]Host IP: 192.168.1.134

0 LOG: [Alarm Module]Cluster Name: dbCluster

0 LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57

0 WARNING: failed to open feature control file, please check whether it exists: FileName=gaussdb.version, Errno=2, Errmessage=No such file or directory.
0 WARNING: failed to parse feature control file: gaussdb.version.
0 WARNING: Failed to load the product control file, so gaussdb cannot distinguish product version.
The core dump path is an invalid directory
2022-07-19 13:58:44.297 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: when starting as multi_standby mode, we couldn't support data replicaton.
gaussdb.state does not exist, and skipt setting since it is optional.2022-07-19 13:58:44.304 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]can not read GAUSS_WARNING_TYPE env.

2022-07-19 13:58:44.305 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host Name: host134

2022-07-19 13:58:44.307 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Host IP: 192.168.1.134

2022-07-19 13:58:44.307 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Cluster Name: dbCluster

2022-07-19 13:58:44.308 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: [Alarm Module]Invalid data in AlarmItem file! Read alarm English name failed! line: 57

2022-07-19 13:58:44.405 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] LOG: loaded library "security_plugin"
2022-07-19 13:58:44.406 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2022-07-19 13:58:44.407 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] WARNING: could not create any HA TCP/IP sockets
2022-07-19 13:58:44.407 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] FATAL: could not create lock file "/opt/huawei/tmp/.s.PGSQL.5432.lock": No such file or directory
[2022-07-19 13:58:45.035][4252][][gs_ctl]: waitpid 4255 failed, exitstatus is 256, ret is 2

[2022-07-19 13:58:45.035][4252][][gs_ctl]: stopped waiting
[2022-07-19 13:58:45.035][4252][][gs_ctl]: could not start server
Examine the log output.
import sql file
Would you like to create a demo database (yes/no)? no
Input no, operation skip.

---

Other answers 1：

2022-07-19 13:58:44.407 [unknown] [unknown] localhost 140587269000256 0[0:0#0] 0 [BACKEND] FATAL: could not create lock file "/opt/huawei/tmp/.s.PGSQL.5432.lock": No such file or directory

Other answers 2：

https://www.modb.pro/doc/25441

Look at this document

Other answers 3：

Your document adopts OM Way to deploy , The simple version I use here is installed , Follow the steps in the official documentation to install .

Other answers 4：

https://opengauss.org/zh/docs/3.0.0/docs/installation/%E5%8D%95%E8%8A%82%E7%82%B9%E5%AE%89%E8%A3%85.html

Follow the installation steps here to prompt the above error .

Other answers 5：

Permission problems ,

Ordinary users must have a database package decompression path 、 Read of installation path 、 Write and execute operation permissions , And the installation path must be empty .

Other answers 6：

1 groupadd dbgrp2 useradd -g dbgrp -d /home/omm  -m -s /bin/bash omm3 echo "omm" | passwd  -‐stdin omm4 mkdir -p /opt/software/openGauss5 chmod 755 -R /opt/software6 chown -R omm:dbgrp  /opt/software/openGauss 
 Have you executed all the authorization orders , For directories and users you create locally , Authorize and change membership 

Other answers 7：

[[email protected] opengauss]$ id omm
uid=1007(omm) gid=1010(dbgrp) groups=1010(dbgrp)

[[email protected] opengauss]$ ls -al
total 4
drwxrwxr-x 5 omm dbgrp 48 Jul 19 10:39 .
drwxr-xr-x. 21 root root 4096 Jul 19 10:27 ..
drwx------ 2 omm dbgrp 6 Jul 19 13:36 data
drwx------ 2 omm dbgrp 6 Jul 19 13:36 pg_log
drwx------ 11 omm dbgrp 142 Jul 19 13:42 software
[[email protected] opengauss]$ pwd
/opt/opengauss

All the orders you said were carried out , I wonder why I reported these two catalogues , The installation does not involve these two directories .

/var/log/omm

/opt/huawei/tmp

Other answers 8：

Under the instructions I used this machine before OM Has been installed on a stand-alone , Then I uninstalled Now use the simple version to install

These two directories seem to be related to OM Installation related , It's strange why the simple version is related to these two directories .

Other answers 9：

.bashrc Take a look at the screenshot

Other answers 10：

Problem solved , I put the operating system omm Users can delete and recreate

Other answers 11：

OK