Diagnostic Messages 8001 - 8809

Number Diagnostic Text Meaning Action

8001

Could not authenticate <principal> for <service>. Please check your ticket -- it may be expired

Kerberos initialization problem.

Check your Kerberos configuration.

8006

Could not construct local service principal name for

<client principal> @ <client host>

Kerberos could not construct a principal for the listed service on the listed server.

Check the Kerberos settings in your Privilege Management settings file and the Kerberos configuration (typically in /etc/krb5.conf).

8007

Could not determine service name from principal name for

<client principal> @ <client host>

Kerberos could not construct a principal for the listed service on the listed server.

Check the Kerberos settings in your Privilege Management settings file and the Kerberos configuration (typically in /etc/krb5.conf).

8008

Could not build a tgt principal for <client principal name> code <Kerberos code number>

Kerberos could not construct a TGT principal for the listed principal.

Check the Kerberos settings in your Privilege Management settings file and the Kerberos configuration (typically in /etc/krb5.conf).

8010

<code> while getting time of day

 

Contact BeyondTrust Support.

8011

<code> reading keytab entry

<client name>

There was a problem reading the keytab entry.

Contact BeyondTrust Support.

8012

<code> while getting initial credentials for <Policy Server>

Tje ticket could not be removed from Kerberos.

Contact BeyondTrust Support.

8013.1

Could not send token length

A server ceased functioning while processing the request.

Contact BeyondTrust Support.

8013.2

sending token length: ## of ## bytes written

A server ceased functioning while processing the request.

Contact BeyondTrust Support.

8014.1

Could not send token

A server ceased functioning while processing the request.

Contact BeyondTrust Support.

8014.2

sending token data: ## of ## bytes written

A server ceased functioning while processing the request.

Contact BeyondTrust Support.

8015.1

recv_token could not read token length

Encountered an internal Kerberos problem.

Contact BeyondTrust Support.

8015.2

recv_token length: ## of ## bytes read

Encountered an internal Kerberos problem.

Contact BeyondTrust Support.

8016

<service>: recv_token could not allocate memory for token data

<length>

Encountered an internal Kerberos problem.

Contact BeyondTrust Support.

8017.1

recv_token could not read token data

Encountered an internal Kerberos problem.

Contact BeyondTrust Support.

8017.2

recv_token sending token data:

## of ## bytes written

Encountered an internal Kerberos problem.

Contact BeyondTrust Support.

8019

Error initializing kerberos library

The designated Kerberos library could not be started.

Check that the library defined in the settings file, and verify it is correct.

8020

<service name>: GSS-API error

###: <description>

The named Kerberos service has a problem with the GSS interface.

Check the KDC logs to ensure the user's principal is added.

Contact BeyondTrust Support.

8021

client failed to establish context to <service>/<host>

A GSS context could not be established to the listed server.

 

8022

acquiring server credentials for <service>

A server could not acquire the client credentials for the listed service.

 

8023

establishing server context for

<service>/<host>

A GSS context could not be established for the listed client.

 

8024

initKerberosKey socket is not open

The Kerberos socket was not open when the connection was attempted.

 

8025

Kerberos key initialization error connecting to log server

<log host>

A Kerberos connection failed while contacting a log server.

 

8026

Kerberos key initialization error during initial startup

A Kerberos connection failure occurred from pblocald.

 

8027

Kerberos principal initialization error during log server reconnect

A Kerberos connection failure occurred while trying to reconnect the log server to pblocald.

 

8028

Kerberos keytab error during log server reconnect

A Kerberos connection failure occurred while trying to reconnect the log server to pblocald.

 

8029

Kerberos key initialization error during log server reconnect

A Kerberos connection failure occurred while trying to reconnect the log server to pblocald.

 

8030

Kerberos key initialization error during reconnect

A Kerberos connection failure occurred while trying to reconnect the log server to pblocald.

 

8031

Kerberos key initialization error

A Kerberos connection failure occurred from the log server.

 

8032

Kerberos key initialization error during log server reconnect

A Kerberos connection failure from the log server while trying to reconnect to pblocald.

 

8033

Kerberos key initialization error

A Kerberos connection failure occurred from the policy server while trying to connect to pblocald.

 

8034

Kerberos key initialization error during reconnect

A Kerberos connection failure occurred from pbrun while trying to reconnect to pblocald.

 

8035

Kerberos key initialization error

A Kerberos connection failure occurred from pbrun while trying to connect to a policy server.

 

8036

Kerberos key initialization error

A Kerberos connection failure occurred from pbguid while trying to connect to a policy server.

 

8037

Kerberos key initialization error

A Kerberos connection failure occurred from pbbench while trying to connect.

 

8038

Can not initialize Kerberos settings

pbguid could not initialize its Kerberos settings.

 

8039

code <Kerberos internal code> when parsing name %s

The principal name could not be obtained.

Check the principal name in the settings and keytab files. Also, check to make sure the principal exists.

8040

code <Kerberos internal code> could not get credentials for

<user name>

No credentials were found for the user.

Verify the user credentials actually exist.

8041

code <Kerberos internal code> initializing cache for update

The credentials cache could not be initialized.

Check that the cache is on a writable file system.

8042

code <Kerberos internal code> while storing credentials

The credentials cache could not be updated.

Check that the cache is on a writable file system.

8043

could not look up user <user id number>

Could not find the expected user while trying to obtain credentials.

Check that the user id number is valid.

8044

code <Kerberos internal code> while initializing Kerberos context

The Kerberos security context could not be established.

Check that the principals are correct in the settings and keytab files.

8045

could not find entry for user

<user id number>

Could not find the expected user while trying to obtain credentials.

Check that the user ID number is valid.

8046

code <Kerberos internal code> could not parse name from principal

Could not determine the principal name from the user credentials.

Check the principal name in the settings and keytab files. Check that the principal exists.

8047

could not find entry for user

<user id number>

Could not find the expected user while attempting to validate credentials.

Check that the user ID number is valid.

8048

undiagnosed return opening and setting default cache -

<Kerberos result code>

An unexpected result was obtained while trying to open and set the default cache.

Contact BeyondTrust Support.

8049

invalid keytab '<keytab file name>'

The expected keytab file is invalid or does not exist. This is followed by a system-specific reason.

Check that the keytab file exists and that the path name and permissions are correct.

8050

keytab file keytab '<keytab file name>' is empty

The specified keytab file exists, but has no content.

Determine why the keytab file is empty and populate it, or use another keytab file.

8051

code <Kerberos internal code> could not resolve keytab

Could not resolve the contents of the keytab file

Determine why the keytab file is invalid and correct it or use another keytab file.

8052

Could not retrieve user information.

Could not find the user's identity

Make sure the user exists on the host machine.

8053

No password supplied for Kerberos Authentication

The user did not type a password for Kerberos authentication when requested.

Enter the correct password when requested.

8054

Could not construct remote service principal name for

<service name> @ <server host>

Kerberos could not construct a principal for the listed service on the listed server.

Check the Kerberos settings in your Privilege Management settings file and the Kerberos configuration (typically in /etc/krb5.conf).

8055

Could not determine remote service name from principal name for <service name> @

<server host>

Kerberos could not determine the principal name for the listed service on the listed host.

Check the Kerberos settings in your Privilege Management settings file and the Kerberos configuration (typically in /etc/krb5.conf).

8056

code <Kerberos internal code> while getting default cache

Could not find the default cache

Check that the cache is on a writable file system.

8057

PAM SESSION Error: <string>

A problem (indicated by <string>) was encountered attempting to open a PAM session. Often times, <string> is meaningless (for example, "PAM session start failure"). <string> is returned by the PAM framework and cannot be more specific.

Investigate reasons why the PAM session might be failing. Sometimes, PAM debugging techniques must be employed. Other times, the PB logs or system logs on the runhost might indicate the problem (for example, user is not a member of the specified Solaris Project).

8058

project <Solaris project name> does not exist

The requesting user or policy has specified a Solaris Project for which the task should run as. The project does not exist on the runhost.

Determine if the correct project has been specified. Add the project to the runhost if necessary.

8059

user <username> not a member of project <projectname>

The indicated runuser is not a member of the specified Solaris project.

Specify the correct runuser and project.

8060

solaris projects error:

<message>.

The Solaris PAM subsystem may not provide enough information to readily determine the cause of the problem.

Look at the runhost system logs and Privilege Management logs for an indication why the Solaris Project may not have been set correctly.

8061

Error assigning Solaris Project

The Solaris PAM subsystem may not provide enough information to readily determine the cause fo the problem.

Look at the runhost system logs and Privilege Management logs for an indication why the Solaris Project may not have been set correctly.

8062

pam_setcred failed-<error number>: <error msg>

The PAM framework failed to perform the pam_setcred() function. The <error msg> indicates the failure. This message may not provide enough details as to the real cause of the problem.

Examine the system logs on the runhost to determine the cause of the problem.

8063

username required for Solaris project

The username was not set when attempting to assign the task to a solaris project.

Contact BeyondTrust Support.

8064

Project set on Solaris 8

Solaris 8 does not support Solaris projects; however, the request user or the policy set a project name.

Do not specify a Solaris Project.

8065

Project set on unplanned platform

The internal code to verify that a platform supports Solaris Projects needs to be updated with a new platform.

Contact BeyondTrust Support.

8066

Project <projectname> set on non-Solaris platform

Only Solaris 9+ platforms support Solaris Projects.

Ensure that the Solaris project is only specified for Solaris 9+ runhosts.

8067

missing username

The username was not set when attempting to assign the task to a solaris project.

Contact BeyondTrust Support.

8068

missing msgptr

Internal error.

Contact BeyondTrust Support.

8069

Solaris Projects are not enabled

Solaris Projects are not enabled.

Enable Solaris projects using the enablesolarisprojects keyword or using PAM in pb.settings. Or, do not specify a Solaris Project.

8070

unknown solaris project error

An unknown problem occurred when setting the Solaris Project.

Contact BeyondTrust Support.

8071

No default project

The getdefaultproj() library function failed to retun a default project for the runuser.

Examine system logs and Solaris Project configuration on the runhost for possible causes.

8072

project <project name> resource control limit has been reached

The Solaris project has resource limits configured. A resource limit has been reached.

Wait until the resource is not near peak utilization or increase the resource limit.

8073

user <username> could not join project <project name>. errno:<number>

The setproject() library call encountered an error.

Investigate the system logs on the runhost. Investigate the errno value for <number>.

8074

errno:<number> binding to project <project name> resource pool

The setproject() library call encountered an error regarding the project’s resource limits.

Investigate the system logs on the runhost. Investigate the errno value for <number>.

8075

unknown error:<number> errno:<number> binding to project <project name>.

The setproject() library call returned an error and errno.

Investigate the system logs on the runhost. Investigate the errno value for <number>.

8076

LOCAL MODE and project is set, however enablesolarisprojects keyword is not enabled.

LOCAL MODE and project is set; however, the enablesolarisprojects keyword is not enabled.

Enable the enablesolarisprojects keyword on the runhost. Or, do not specify a project.

8077

Did not find PROJ function

<name>

A Solaris project function could not be found in the list of libraries specified by the sharedlibsolarisprojects keyword.

Add the appropriate library to the sharedlibsolarisprojects keyword.

8100

Access Denied

The Application ID ACLs do no provide the permissions required for the current operation.

Use a different Application ID or add new ACL permissions.

8101

Bad constraint [<CONSRAINT>],

<REASON>

The constraint supplied to the event log search are invalid.

Specify a valid constraint.

8102

Error parsing JSON near:

<STRING>

The JSON data supplied to the REST API call is invalid.

Correct the JSON data supplied to the REST API call.

8103

Error parsing policy file

<FILE>, <REASON>

The policy file is syntactically invalid.

Correct the syntax of the policy file.

8104

Failed to allocate memory,

<REASON>

General - failed to allocate memory.

The REST API plugin should restart. If not, check general system health and restart the httpd.

8105

Failed to compile regular expression '<STRING>', <REASON>

The supplied regular expression is invalid.

Correct the syntax of the regular expression supplied.

8106

Failed to create file <FILE>,

<REASON>

Could not create the specified error.

Check the health of the filesystem and the specified file.

8107

Failed to decode data, <REASON>

Failed to Base64 decode the supplied data.

Correct the supplied file encoding.

8108

Failed to encode file <FILE>,

<REASON>

Failed to Base64 encode the supplied data.

Correct the supplied file encoding.

8109

Failed to initMangle

Failed to initialize file encryption.

Contact BeyondTrust Support.

8110

Failed to open file <FILE>,

<REASON>

Failed to open specified file.

Check the health of the filesystem and the specified file.

8111

Failed to override lock,

<REASON>

Failed to override the specified lock.

Lockfiles should only exist for milliseconds - check for stalled processes.

8112

Failed to read file <FILE>,

<REASON>

Failed to read the specified file.

Check the health of the filesystem and the specified file.

8113

Failed to rename file from

<FILE> to <FILE>, <REASON>

Failed to rename the specified file to the destination file.

Check the health of the filesystem and the specified file.

8114

Failed to write file <FILE>,

<REASON>

Failed to write the specified file.

Check the health of the filesystem and the specified file.

8115

File is too large <FILE>,

<REASON>

File specified is too large to transfer.

The file is too large to transfer using REST. Manually copy the file.

8116

Invalid ACL

The specified ACL is invalid.

Correct the REST call parameters on the URL.

8117

Invalid application ID or Key,

<REASON>

The specified Application ID or Application Key is incorrect.

Correct the parameters on the REST call to comply with documentation.

8118

Invalid attribute <NAME>, type

<TYPE>

The event log has an invalid attribute type.

Check the event file with pblog.

8119

Invalid Authentication

Invalid authentication signature supplied.

Correct the HMAC authentication signature on the REST call.

8120

Invalid event log file

The specified event log is invalid.

Check the event file with pblog.

8121

Invalid event log file entry

The specified event log has an invalid entry.

Check the event file with pblog.

8122

Invalid new key

The specified pb.key data is invalid.

Correct the missing or invalid key data in the REST call.

8123

Invalid parameter '<PARAMETER>'

A specified parameter is missing or is invalid.

Correct the missing or invalid parameter in the REST call.

8124

Invalid policy file <FILE>,

<REASON>

The specified policy file is invalid.

Check the policy file exists and correct the syntax of the file and check with pbcheck.

8125

Permission denied - '<FILE|PATH>' is a system file

The specified file is a system file and cannot be read or written.

Certain named files are system files and cannot be overwritten.

8126

Timeout trying to create lockfile

There was a timeout trying to lock the specified file for updates.

Lockfiles should only exist for milliseconds - check for hung processes.

8128

Invalid REST request [<STRING>/<STRING/<STRING>]

Invalid REST request submitted.

Fix the REST request in accordance with documentation.

8129

Could not get pbrest host name

pbrest could not determine its host name. This is followed by a system-specific diagnostic message.

Verify that /etc/hosts and host name resolution is setup correctly.

8130

Failed to generate and store credential - <NUMBER>

pbrest could not store the newly generated App ID and Key.

Verify the health of the
/etc filesystem, and the permissions on /etc/pb.restkeys.

8131

Failed to delete credential -

<NUMBER>

pbrest could not delete the named credential - either it doesn’t exist or there was an error.

Verify the health of the /etc filesystem, and the permissions on /etc/pb.restkeys.

8132

Failed to read settings file

pbrest could not read /etc/pb.settings.

Verify the health of the /etc filesystem, and the health of /etc/pb.settings

8133

Failed to allocate memory for

<STRING> in <FUNCTION>,

<REASON>

pbrest could not allocate memory.

Verify the health of the host system, and the available virtual memory.

8134

Failed to contact SOLR, <ERROR>

Failed to contact SOLR from this REST service.

Check SOLR configuration and network connectivity.

8135

SOLR search failed, <NUMBER>

Failed to search for the given query in SOLR.

Lookup error message in SOLR document, and fix query if required.

8140.2

Missing event log destination filename Internal error.

Contact BeyondTrust Software.

8140.3

Invalid destination directory: %s

logarchivedir setting may be pointing to a protected system path that should not be overwritten.

Specify a different directory path, preferably on a filesystem that can handle all incoming archived logfiles.

8140.4

 

Failed to create log archive destination directory:%s errno:%d %s

An error prevented the creation of the subdirectories under the path specified in the logarchivedir setting.

Resolve the problem described by the accompanying system- specific diagnostic message.

8140.5

Invalid destination directory

%s, %d %s

Failed to get the status of the path specified in the logarchivedir setting.

Resolve the problem described by the accompanying system- specific diagnostic message.

8140.7

Log archive failed to move the logfile to the final destination directory (%d:%s)

Problem encountered in finalizing the archive logfile at the destination archive host.

Resolve the problem described by the accompanying system- specific diagnostic message.

8141.1

Failed to remove target file %s (%d:%s)

When backing out the archiving of a log, PowerBroker for Unix and Linux was not able to delete the file at thedestination archive host.

Resolve the problem described by the accompanying system- specific diagnostic message.

8123.130

Invalid setting '%s'

Log Archive Storage Server settings file is missing logarchivedir or it contains an invalid value.

Check the settings file on the Log Archive Storage Server.

8143

Destination file '%s' already exists.

The logfile to be archived is mapped to a destination directory that already contains the target filename.

Verify the preexisting file at the destination. Or specify a different location for logarchivedir.

8144.1

Missing log filename to process

Internal error.

Contact BeyondTrust Software.

8150.1

Failed to update database with event logfile location [%s]

A SQL error occurred while trying to update the log tracking database.

See the accompanying error message for more details.

 

8150.10

Unable to update the log tracking database. Undoing the archive.

Log archiving cannot be completed if the log tracking database cannot be updated.

 

 

8150.11

Unable to remove %s after successfully archived %d %s

 

See the accompanying system-specific diagnostic message.

8150.13

Could not connect to Log Archiver Database Server [%d:%s]

Problem encountered when trying to contact the Log Archiver Database Server.

See the accompanying system-specific diagnostic message.

8150.14

Could not access log tracking database [%s]

Problem encountered when trying to check status of the log tracking database.

See the accompanying system-specific diagnostic message.

8150.15

Failed to read the log - %s

 

Check the encryption settings for the logfile on the log server host.

8150.2

Failed to remove logfile to

undo archiving due to error: %s

When backing out the archiving of a log, PowerBroker for Unix and Linux was not able to delete the file at the destination archive host.

 

8150.3

Failed to archive logfile due to error: %s

Log archiving failed.

See the accompanying system-specific diagnostic message.

8150.4

Could not record logfile location in the tracking database [%s]

Failed to update the log tracking database.

See the accompanying system-specific diagnostic message.

8150.5

Failed to determine archive host's enforcehighsecurity setting [%s]

Problem encountered getting the enforcehighsecurity setting on the Log Archive Storage Server.

See the accompanying system-specific diagnostic message.

8150.6

Failed to determine archive host's encryption info [%s]

Problem encountered getting the logfile encryption setting on the Log Archive Storage Server.

See the accompanying system-specific diagnostic message.

8150.7

Failed to get archive host's keyfile [%s]

Problem encountered getting the encryption key on the Log Archive Storage Server.

See the accompanying system-specific diagnostic message.

 

8150.8

Invalid log name %s : %s

The logfile name provided to pblogarchive has invalid characters.

 

8150.9

Could not access file %s (%d:%s)

The logfile name provided to pblogarchive does not exist.

 

8151.1

Settings file is missing required log archive host.\n

pblogarchive requires logarchivehost setting in the settings file of the log server.

 

8151.2

pblogarchive: -e, -E and -i, -I

You cannot use the event log options (-e,-E) with the I/O log options (-i, -I) in the same pblogarchive command.

Archive only similar type logfiles per pblogarchive command.

8151.3

No logfile to archive

pblogarchive cannot find the eventLog to be archived.

You must explicitly provide an argument to -e option if the event log is defined in the policy and not in the settings file.

8151.4

pblogarchive: Error occurred matching pattern '%s' (%d:%s)

pblogarchive was unable to find matching files using the provided search pattern.

See the accompanying system-specific diagnostic message.

8151.5

pblogarchive: Failed to initialize CURL/SSL libraries

One or more of the shared libraries listed in the sharedlibssldependencies or sharedlibcurldependencies could not be loaded.

 

8151.6

pblogarchive: Error opening %s (%d:%s)

pblogarchive encountered an error while finding matching files using the provided search pattern.

See the accompanying system-specific diagnostic message.

8151.7

Settings file is missing required log archive DB host.

pblogarchive requires logarchivedbhost setting in the settings file of the log server.

 

8152

Failed to update the log tracking database.

enablelogtrackingdb is set to yes in the settings file of the log host. Every time an event log is created, the log tracking database on the Log Archiver Database Server is updated. This error indicates a problem with the database update.

See the PowerBroker for Unix and Linux System Administration Guide and verify if the Log Archiver Database Server is set-up properly.

8500

Invalid high security setting '%s' must be %s.

The named keyword is set incorrectly in accordance with the enforcehighsecurity setting.

Fix the named setting in accordance with existing documentation.

8501

Can not stat SSL private key file <filename>

Could not access the named keyfile. This is followed by the system-specific reason.

 

8502

SSL_CTX_set_cipher_list

An invalid cipher list option was specified.

Check the sslpbruncipherlist and sslservercipherlist settings.

8503

Private key file not specified

An SSL private key was not specified in the settings file.

 

8504

<SSL diagnostic>

A problem was encountered with a certificate file. The SSL diagnostic describes the reason.

 

8505

<SSL diagnostic>

A problem was encountered with a private key file. The SSL diagnostic describes the reason.

 

8506

<SSL diagnostic>

A problem was encountered when checking a private key file. The SSL diagnostic describes the reason.

 

8507

<SSL diagnostic>

A problem was encountered when loading a certificate authority file. The SSL diagnostic describes the reason.

 

8508

<SSL diagnostic>

A problem was encountered when processing a certificate authority directory. The SSL diagnostic describes the reason.

 

8509

Could not initialize server connection parameters

An SSL server connection could not be established. This diagnostic generally follows other diagnostics that lead up to it.

 

8510

Could not find server certificate file

A server could not find a certificate file.

Check your settings file to see if sslservercertificatefile was specified.

8511

Could not establish new server SSL context

An SSL server context could not be established. This diagnostic generally follows other diagnostics that lead up to it.

 

8512

Could not initialize server SSL context

An SSL server context could not be initialized. This diagnostic generally follows other diagnostics that lead up to it.

 

8513

Server could not load client CA file.

An SSL server could not find a certificate authority file to send to its client when client certificates are required. The SSL diagnostic describes the reason.

 

8514

Server failure in SSL_new()

An SSL server could not start a connection. The SSL diagnostic describes the reason.

 

8515

Server failure in SSL_set_fd()

An SSL server could not connect its context to a file descriptor. The SSL diagnostic describes the reason.

 

8516

Server failure in SSL_accept()

An SSL server could not accept a connection. The SSL diagnostic describes the reason.

 

8517

Could not initialize client connection parameters

An SSL client could not be initialized. This diagnostic generally follows other diagnostics that lead up to it.

 

8518

Could not find intermediate server certificate file

An intermediate SSL server (pbmasterd or pblocald) could not find its certificate file.

Check your settings file to see how the sslservercertificate file was specified.

8519

Could not establish new client SSL context

An SSL client context could not be established. This diagnostic generally follows other diagnostics that lead up to it.

 

8520

Could not initialize client SSL context

An SSL client context could not be initialized. This diagnostic generally follows other diagnostics that lead up to it.

 

8521

Client failure in SSL_new()

An SSL client could not start a connection. The SSL diagnostic describes the reason.

 

8522

Client failure in SSL_set_fd()

An SSL client could not connect its context to a file descriptor. The SSL diagnostic describes the reason.

 

8523

Client failure in SSL_connect()

An SSL client could not establish a new connection. The SSL diagnostic describes the reason.

 

8524

SSL log server initialization failure

An SSL client could not connect to a log server. This diagnostic generally follows other diagnostics that lead up to it.

 

8525

SSL Policy Server daemon initialization failure

The run host could not establish an SSL connection from a policy server. This diagnostic generally follows other diagnostics that lead up to it.

 

8526

SSL log server reconnect initialization failure

pblocald could not establish an SSL connection to the log server during a log reconnect. This diagnostic generally follows other diagnostics that lead up to it.

 

8527

SSL client initialization failure

pblocald could not establish an SSL connection to its client. This diagnostic generally follows other diagnostics that lead up to it.

 

8528

SSL <Policy Server/local daemon> initialization failure

The log server could not establish an SSL connection to pbmasterd/pblocald. This diagnostic generally follows other diagnostics that lead up to it.

 

8529

SSL log reconnect initialization failure

The log server could not establish an SSL connection to pblocald during a log reconnect. This diagnostic generally follows other diagnostics that lead up to it.

 

8530

SSL client initialization failure

pbmasterd could not establish an SSL connection to pbrun during a connection. This diagnostic generally follows other diagnostics that lead up to it.

 

8531

Could not initiate SSL to <run host>

pbmasterd could not establish an SSL connection to pblocald. This diagnostic generally follows other diagnostics that lead up to it.

 

8532

Locald on <run host> is not SSL enabled

pbrun expects an SSL connection, but pblocald is not SSL-enabled.

Check the local daemon configuration.

Add allownonssl to the pbrun setting ssloptions.

8533

Failed SSL initialization to pblocald on <run host>

SSL initialization failed during a reconnect to the listed client host.

 

8534

Policy Server on <Policy Server> is not SSL enabled

pbrun expects an SSL connection, but pbmasterd is not SSL-enabled.

Check the local daemon configuration.

Add allownonssl to the pbrun setting ssloptions.

8535

Policy Server not SSL enabled

pbguid expects an SSL connection, but pbmasterd is not SSL-enabled.

Check the local daemon configuration.

Add allownonssl to the pbrun setting ssloptions.

8536

Could not initialize SSL to Policy Server

pbguid could not initialize an SSL connection to pbmasterd.

 

8537

<SSL diagnostic>

pbguid could not initialize its SSL parameters. The SSL diagnostic describes the reason in more detail.

 

8538

<SSL diagnostic>

pbguid could not set up an SSL connection to the browser.

The SSL diagnostic describes the reason in more detail.

 

8538.1

log server is not SSL enabled

The requested log server is not configured for SSL, but the requesting program requires SSL.

Enable SSL for the log server, disable SSL for the requesting program, or enable allownonssl for the requesting program.

8538.2

logserver is not SSL enabled

The requested log server is not configured for SSL, but the requesting program requires SSL.

Enable SSL for the log server, disable SSL for the requesting program, or enable allownonssl for the requesting program.

8539.1

Policy Server daemon on %s is not SSL enabled

The requested policy server is not configured for SSL, but the requesting program requires SSL.

Enable SSL for the policy server, disable SSL for the requesting program, or enable allownonssl for the requesting program.

8540.1

client on <submit host> is not SSL enabled

The requested client is not configured for SSL, but therequesting program requires SSL.

Enable SSL for the client, or disable SSL for the requesting program, or enable allownonssl for the requesting program.

8540.2

client on <submit host> is not SSL enabled

The requested client is not configured for SSL, but the requesting program requires SSL.

Enable SSL for the client, disable SSL for the requesting program, or enable allownonssl for the requesting program.

8541.1

Policy Server/local daemon on <Policy Server/run host name> is not SSL enabled

The requested policy server/local daemon is not configured for SSL, but the log server requires SSL.

Enable SSL for the policy server/local daemon, disable SSL for the log server, or enable allownonssl for the log server.

8541.2

Policy Server/local daemon on <Policy Server/run host name> is not SSL enabled

The requested policy server/local daemon is not configured for SSL, but the log server requires SSL.

Enable SSL for the policy server/local daemon, disable SSL for the log server, or enable allownonssl for the log server.

8542

pblocald on <run host> is not SSL enabled

The requested pblocald on the specified host is not configured for SSL, but the requesting program requires SSL.

Enable SSL for the local daemon, disable SSL for the requesting program, or enable allownonssl for the requesting program.

8543

Unable to load ssl engine:

<name>

The SSL engine could not be loaded.

Verify that the library exists.

8544

unable to satisfy randomness requirements

SSL needs a certain amount of randomness. This requirement could be met using RAND_ seed() functions.

Contact BeyondTrust Support.

 

8701

Failed to allocate a TCP/IP port for X11 forwarding - exiting

The TCP/IP port to use for X11 forwarding could not be allocated.

Check the available ports.

8702

Failed to allocate memory to X11 forwarding for new X11 application - exiting

Could not allocate memory.

 

8703

Invalid X11 forwarding channel message - exiting

The X11 forwarding channel message is invalid.

 

8704

X11 forwarding is enabled, but no DISPLAY environment variable set

The environment variable DISPLAY is not set.

Set the DISPLAY variable and restart the operation (pbrun -X).

8801

Could not load PAM function

<function name>

The named PAM function could not be loaded at runtime.

Check that the PAM libraries exist and can be found.

8802

Could not open PAM library

<library name>

The named PAM library could not be found.

Check that the PAM libraries exist and are accessible.

8803

PAM account management failed -<reason>

The PAM account management module returned a failure. This is followed by a PAM-specific diagnostic.

Correct the situation described in the PAM- specific diagnostic message.

8804

PAM session start failed -<reason>

A PAM session start call failed. This is followed by a PAM- specific diagnostic message.

Correct the situation described in the PAM- specific diagnostic message.

8805

PAM session close failed -

<reason>

A PAM session end call failed. This is followed by a PAM- specific diagnostic.

Correct the situation described in the PAM- specific diagnostic message.

8806

PAM account management failure - <reason>

A PAM account management call failed. This is followed by a PAM-specific diagnostic message.

Correct the situation described in the PAM- specific diagnostic message.

8807

PAM authentication failed -

<reason>

A PAM password authentication call failed. This is followed by a PAM-specific diagnostic message.

Correct the situation described in the PAM- specific diagnostic message.

8808

PAM is not available on this platform

PAM is not available on the host.

Turn off the PAM setting in your settings file.

8809

PAM account management failure - <message>

The PAM account mechanism returned something other than PAM_SUCCESS. This could indicate an error, or an account failure (such as account is locked).

Review and address the <message> portion.