1,126
edits
Difference between revisions of "Unable to determine the database engine"
Jump to navigation
Jump to search
m
Unable to determine the database engine (view source)
Revision as of 04:14, 24 May 2020
, 04:14, 24 May 2020Added section about CMOD directory permissions.
(Added section on using the instance name in arsdb -uv command.) |
m (Added section about CMOD directory permissions.) |
||
| Line 19: | Line 19: | ||
== Troubleshooting == | == Troubleshooting == | ||
If you're not installing CMOD as the server's 'root' or 'admin' account, ensure that you have the proper permissions to access the configuration files, and any intermediate directories. You may need to change the ownership and permissions of the CMOD installation directory or configuration files to match the ID that you intend to run the Content Manager OnDemand daemon [[arssockd]] as. | |||
$ ls -l | |||
drwxr-xr-x. 3 archive archive 4096 May 11 21:41 bin | |||
drw-r--r--. 2 archive archive 4096 May 23 23:59 config | |||
drwxr-xr-x. 2 archive archive 25 May 11 21:41 dd | |||
drwxr-xr-x. 7 archive archive 70 May 11 21:41 exits | |||
The archive user can't traverse into the 'config' directory -- it's missing the execute privilege! | |||
$ chmod 755 config | |||
$ ls -l | |||
drwxr-xr-x. 3 archive archive 4096 May 11 21:41 bin | |||
drwxr-xr-x. 2 archive archive 4096 May 23 23:59 config | |||
drwxr-xr-x. 2 archive archive 25 May 11 21:41 dd | |||
drwxr-xr-x. 7 archive archive 70 May 11 21:41 exits | |||
Permissions now allow the 'archive' user to access the contents of the 'config' directory. | |||
Check to see that your [[ars.ini]] configuration parameters are correct and up to date. On some platforms, the values (especially User ID's) are case-sensitive, so you may need to use "archive" instead of "ARCHIVE". | Check to see that your [[ars.ini]] configuration parameters are correct and up to date. On some platforms, the values (especially User ID's) are case-sensitive, so you may need to use "archive" instead of "ARCHIVE". | ||