ydbinstall script checks for Supported or known Supportable platform and issues a warning otherwise
Created by: whitten
Final Release Note
The ydbinstall
script checks for existence and contents of /etc/os-release
, and aborts the install of YottaDB if it detects an unsupported platform. Rerunning it with --force-install
overrides this behavior and goes ahead with the install even if it is an unsupported platform.
Description
I installed yottdb 1.22 into a Linux account named "ydb", and ran the command "gtm" below, and got errors. I'm not quite sure what to tell you, and realize after I ran this, that perhaps I should have run some other command than "gtm" i.e. "ydb" but as you can see, it made the same errors.
I don't know what information you need to have for a bug-report like this,
[ydb@here ~]$ /usr/local/lib/yottadb/r122/gtm
YDB>w 1 1 YDB>h [ydb@here ~]$ /usr/local/lib/yottadb/r122/gtm /tmp/ydb_env_30864_ZFOxtN/out: line 1: fg: no job control dirname: missing operand Try `dirname --help' for more information. /usr/local/lib/yottadb/r122/gtm: line 20: /ydb_20180516210018UTC_mupip_recover: Permission denied
YDB>h
dirname: missing operand
Try dirname --help' for more information. /usr/local/lib/yottadb/r122/gtm: line 32: /ydb_20180516210018UTC-20180516210026UTC_mupip_rundown: Permission denied find: invalid argument
-exec' to -mtime' [ydb@here ~]$ dirname dirname: missing operand Try
dirname --help' for more information.
[ydb@here ~]$ /usr/local/lib/yottadb/r122/ydb /tmp/ydb_env_30901_4GyfVL/out: line 1: fg: no job control dirname: missing operand Try `dirname --help' for more information. /usr/local/lib/yottadb/r122/ydb: line 20: /ydb_20180516210653UTC_mupip_recover: Permission denied
YDB>h
dirname: missing operand
Try dirname --help' for more information. /usr/local/lib/yottadb/r122/ydb: line 32: /ydb_20180516210653UTC-20180516210736UTC_mupip_rundown: Permission denied find: invalid argument
-exec' to `-mtime'
Issues identified by the above report
-
If "realpath" executable does not exist, then "ydb" script errors out with a %YDBENV-F-YDBGTMMISMATCH error. It needs to check if "readlink" is available in case "realpath" is not. And if so use that instead. On all linux systems, one of the two will most likely exist.
-
If $HOME/.fis-gtm directory exists, the "ydb" script errors out with a %YDBENV-F-YDBGTMMISMATCH error. The issue is that the ydb script assumes $HOME/.fis-gtm is a softlink to $HOME/.yottadb which is not guaranteed. It needs to continue even if .fis-gtm is not a softlink to .yottadb.
-
The ydb script errors out with a "${USER}_20180518192042UTC_mupip_recover: Permission denied" in case it is run by multiple users on the same box and those users are not in the same group. This is because the first user would create /tmp/yottadb/r1.22_x86_64 directory usually with no write permissions for the world and that would cause errors for the second user invocation of ydb. The script should prevent such errors from happening by using different temporary directories for different users.
Draft Release Note
The ydbinstall script checks for existence and contents of /etc/os-release
, and aborts the install of YottaDB if it detects an unsupported platform. Rerunning it with --force-install overrides this behavior and goes ahead with the install even if it is an unsupported platform.