Skip to main content
Delphix

Protected Usernames May Lead to Issues When Accessing the CLI (KBA1849)

 

KBA

KBA#1849

Applicable Delphix Versions

This article applies to the following versions of the Delphix Engine:

Major Release

All Sub Releases

5.3 5.3.0.0
5.2 5.2.2.0, 5.2.2.1, 5.2.3.0, 5.2.4.0, 5.2.5.0, 5.2.5.1, 5.2.6.0, 5.2.6.1

5.1

5.1.0.0, 5.1.1.0, 5.1.2.0, 5.1.3.0, 5.1.4.0, 5.1.5.0, 5.1.5.1, 5.1.6.0, 5.1.7.0, 5.1.8.0, 5.1.8.1, 5.1.9.0, 5.1.10.0

5.0

5.0.1.0, 5.0.1.1, 5.0.2.0, 5.0.2.1, 5.0.2.2, 5.0.2.3, 5.0.3.0, 5.0.3.1, 5.0.4.0, 5.0.4.1 ,5.0.5.0, 5.0.5.1, 5.0.5.2, 5.0.5.3, 5.0.5.4

Troubleshooting using Protected Usernames

The OS that the Delphix application runs on has a number of internal usernames for internal processes. These processes usually start at boot time to perform some system-wide tasks.

There can be a conflict if a username is created in the Delphix Application that matches any of the usernames listed below.

  • root
  • daemon
  • bin
  • sys
  • adm
  • lp
  • uucp
  • nuucp
  • smmsp
  • listen
  • gdm
  • webservd
  • postgres
  • unknown
  • svctag
  • nobody
  • noaccess
  • nobody4

Difficulties logging in to the CLI will be the manifestation of this conflict.

Resolution

There are two possible solutions to this issue.

1. Don't use any of the usernames listed above.

2. Always specify the intended login. @DOMAIN for Delphix administration (delphix_admin) or @SYSTEM for server setup (sysadmin)

Example:
$ ssh -l sys@DOMAIN delphixengine
Password: 
delphixengine>
$ ssh -l webservd@SYSTEM delphixengine
Password: 
delphixengine>