Document Type | Troubleshooting
Category | Installation
Applicable Product Versions | 6FS06, 6FS07, 6FS07PS, 7FS01, 7FS02, 7FS02PS
Document Number | TINTS016
Issue
During installation and service startup in a redundant environment, if the file owner and group (uid/gid/groups) of the shared storage area differ, the service may fail to start properly.
Note
Assuming the OS account Tibero used to install Tibero is created with UID 1001 on node A and 2002 on node B.
[node A]
$ id tibero uid=1001(tibero) gid=1001(tibero) groups=1001(tibero)
[node B]
$ id tibero uid=2001(tibero) gid=2001(tibero) groups=2001(tibero)
After installing and starting Tibero on node A for the shared storage area, when checking the same shared storage area on node B, the user and group of the files may appear only as numbers like 1001, or be recognized as a different user with uid/gid 1001.
$ ls -ld /tibero_engine /tibero_archive /tibero_data drwxr-xr-x 3 1001 1001 4096 May 2 13:40 /tibero_engine drwxr-xr-x 5 1001 1001 4096 May 2 13:40 /tibero_archive drwxr-xr-x 7 1001 1001 4096 May 2 13:40 /tibero_data
Cause
This issue occurs when the UID/GID and group information of the Tibero OS accounts on each node do not match, causing the ownership of files stored on the shared volume to be incorrectly recognized by the other node.
Solutions
[node A]
$ id tibero uid=1001(tibero) gid=1001(tibero) groups=1001(tibero)
[node B]
$ id tibero uid=1001(tibero) gid=1001(tibero) groups=1001(tibero)
Note
Initially, set the tibero accounts on both nodes identically.# Create group first $ groupadd -g 1001 tibero # Create user $ useradd -u 1001 -g 1001 -m tibero
Modify an already created tibero account.
# Change group first groupmod -g 1001 tibero # Change user UID usermod -u 1001 -g 1001 tibero