Diagnostic Messages 5001 - 5723

Number Diagnostic Text Meaning Action

5001

Connection closed unexpectedly

Generic error indicating that a failure occurred while communicating.

Make sure the pb.settings path to the log files is correct. An invalid path can cause a security failure to shutdown pbmasterd.

Determine the problem from other error messages or log files.

5001.01

Connection closed unexpectedly while trying to send prompt '<prompt>' to fd #

A connection closed while pbmasterd tried to send a prompt.

 

5001.08

Connection closed unexpectedly while trying to send a check ACK

A connection closed while pbmasterd tried to authorize a local mode command.

 

5001.09

Connection closed unexpectedly while sending end status

A connection closed while trying to send exit status from pblocald to pbmasterd/pblogd.

 

5001.10

Connection closed unexpectedly while sending info table elements

An error occurred while trying to send an info table.

1. Make sure the pb.settings path to the log files is correct. An invalid path can cause a security failure to shutdown pbmasterd.

2. Determine the problem from other error messages or log files.

5001.13

Connection closed unexpectedly during NAK

A connection closed while pbmasterd tried to reject a command.

 

5001.14

Connection closed unexpectedly while trying to send a swaptty command

A connection closed while pbmasterd tried to send a tty swap command.

 

5001.15

Connection closed unexpectedly during local NAK

A connection closed while pbmasterd tried to reject a local mode command.

 

5001.16

Connection closed unexpectedly while trying to send exit status

A connection closed while pbmasterd tried to send exit status.

 

5001.17

Connection closed unexpectedly while trying to send reconnect command

A connection closed while pbmasterd tried to send a reconnect command.

 

5001.18

Connection closed unexpectedly while writing localPrompt, '<string>' to fd ##

A connection closed while pblocald tried to write a prompt string.

 

5001.19

Connection closed unexpectedly while trying to send prompt '<prompt>' to fd #

A connection closed while pbmasterd tried to send a prompt.

This is followed by an operating system diagnostic with more detail.

5002

atomic read from <host>

A read failure occurred. This is followed by a system-specific diagnostic message.

Contact BeyondTrust Support.

5003

read

Internal error.

Contact BeyondTrust Support.

5004

atomic write to <host>

A problem occurred while attempting to perform an atomic write. This is followed by a system-specific diagnostic message.

 

5004.02

atomic write error sending prompt '<prompt>' to channel ## [##]

A problem was encountered writing the specified prompt string to the listed fd in pbmasterd.

 

5004.07

sendInfoElements write failure writing ## bytes to fd ##

pbrun is connecting to the pbmasterd machine, but the connection is closing immediately. Most likely inetd is accepting the connection, but is unable to start pbmasterd. This is followed by a system-specific diagnostic message.

Check if the path in inetd.conf is correct and make sure that the executable is OK.

5004.13

atomic write size in backBind#Redirect

pbmasterd is connecting to the pblocald machine, but the connection is closing immediately. Most likely inetd is accepting the connection but is not able to start pblocald.

This is followed by a system-specific diagnostic message.

Check if the path in inetd.conf is correct and make sure that the executable is OK.

5004.14

atomic write hostname in backBind#Redirect

pbmasterd is connecting to the pblocald machine, but the connection is closing immediately. Most likely inetd is accepting the connection but is not able to start pblocald.

This is followed by a system-specific diagnostic message.

Check if the path in inetd.conf is correct and make sure that the executable is OK.

5004.15

atomic write ports in backBind#Redirect

pbmasterd is connecting to the pblocald machine, but the connection is closing immediately. Most likely inetd is accepting the connection but is not able to start pblocald.

This is followed by a system-specific diagnostic message.

Check if the path in inetd.conf is correct and make sure that the executable is OK.

5004.17

Problem writing localPrompt, '<prompt>' to fd #

A problem was encountered writing the specified prompt string to the listed fd in pblocald.

 

5004.18

atomic write error sending prompt '<prompt>' to channel ## [##]

A problem was encountered writing the specified prompt string to the listed fd in pbmasterd.

An operating system diagnostic with more detail follows this.

5005

write

 

Contact BeyondTrust Support.

5006

Multiplexed local prompt error

pblocald failed to write a prompt to pbrun when doing a runconfirmuser.

 

5007

multiplexed masterPrompt error sending prompt '<prompt>' to fd #

pbmasterd experienced a write error when attempting to issue a prompt through masterPrompt.

This is followed by a more detailed operating system diagnostic.

 

5007.01

multiplexed masterPrompt error sending prompt '<prompt>' to fd

#

pbmasterd experienced a write error when attempting to issue a prompt through masterPrompt.

An operating system diagnostic with more detail follows this.

5008

listen timed out from backBind# i= ##

A listening socket timed out while trying to back bind a connection. This is followed by a system-specific diagnostic message.

 

5009

Policy Server port checksum mismatch from <machine>.

Expected 1234 got ##/##

An expected checksum did not match during a backConnect.

 

5010

info packed (###) too large to transmit (max ####)

The inter-process info packet exceeded 64K.

Reduce the size of the program environment by removing unneeded environment variables or unsetting unneeded policy variables.

5101

Communication error <from host>-><to host>

 

Contact BeyondTrust Support.

5102

setuser setgroups error: number of groups=##, uid=##, euid=##, gid=##, egid=##

A setgroups call failed during a setuser sequence. This is followed by a system-specific diagnostic message.

 

5102

Invalid communication startup

<from host>-><to host>

 

 

5102.02

Invalid communications startup

<from host> -> <to host>

This could be a /etc/pb.key mismatch between machines.

 

5102.04

Keyword <name> must have exactly one setting

A setting had more than one value listed. It may only contain a single value.

 

5103

Expected CMD_CHARS

 

Contact BeyondTrust Support.

5104

Expected CMD_WINCH

A handshake error occurred between two Privilege Management modules. While one program waited for a window size packet, the other did not send it.

Contact BeyondTrust Support.

5105

failed to get ACK packet

A handshake error occurred between two Privilege Management modules. While one program waited for an acknowledgement, the other did not send it.

Check the error log of the remote program.

5106

Ignored 0xff## command.

 

Contact BeyondTrust Support.

5107

port checksum mismatch from

<host>. Expected ### got ###

 

Contact BeyondTrust Support.

5108

Invalid start record

 

Contact BeyondTrust Support.

5109

Invalid Checksum

 

Contact BeyondTrust Support.

5110

Abnormal termination (## ##)

 

Contact BeyondTrust Support.

5111

Error reading log

This may occur when reading a very old log file if a backwards fseek fails while trying to read the start record.

 

5112

Protocol error, received <command> (<command number>)

The log server received an unknown command.

Check the configuration of the policy server and the log server machines.

5113

Protocol error waiting for reconnect/noreconnect - received <command name> (<command number>)

 

 

5114

I/O log open failure.

Failed to write an OPEN_IO_ LOG command to the log server

 

5115

ioLogMktemp send error

A send command failed during an ioLogMktemp.

 

5116

ioLogMktemp fetch result error

Could not retrieve the result of an ioLogMktemp

 

5117

ioLogMktemp read header error

Could not retrieve the result of an ioLogMktemp

 

5118

ignoring unknown command

<command name> (<number>)

The log server received an invalid command.

 

5119

non-command input not allowed

The log server received regular data. The log server is only meant to process command data.

 

5120

header problem in readMuxHeader fd <file descriptor>. Expected <number> bytes, got <number>.

readMuxHeader received an invalid header.

 

5121

readMuxHeader invalid data channel <file descriptor>

Invalid or improperly encrypted data was received during a read. This is often an error message from a child that improperly found its way into the data stream.

Check the log files on the pbmasterd/pblocald/pblogd machines.

Try disabling encryption temporarily to see if the error message makes it through.

This is believed to only happen in 2.8.0. Try upgrading.

5122

data problem in readMuxData fd <file descriptor>. Expected <number> bytes

 

 

5123

Protocol error

Something other than an ACK was received during a recvAck ().

 

5124

received invalid command prefix

<number>

An invalid command prefix was received during a command fetch.

 

5125

Did not receive CMD_WINCH

Communications protocol failure. A system-specific diagnostic follows this message.

 

5126

Command channel closed while waiting for CMD_WINCH

Communications protocol failure.

 

5127

Command channel closed while waiting for CMD_CHARS

Communications protocol failure.

 

5128

Did not receive CMD_CHARS

Communications protocol failure. A system-specific diagnostic follows this message.

 

5129

Command channel closed during reconnect

pbrun's command channel closed during a reconnect.

 

5130

Unknown command during reconnect ## <identifier>

pbrun received an improper command during a reconnect.

 

5131

Invalid data stream (##) while reading multiplexed command

Unexpected data was found while trying to read a command.

Check the diagnostic logs for the affected program and the programs to which it is connected.

5132

Invalid internal command

<command name> (##)

pbguid received a command it does not expect to handle.

This is an internal error.

Contact BeyondTrust Support.

5133

Command packet size (actual size) exceeds maximum size (maximum size)

A command packet exceeds the maximum size allowed.

Contact BeyondTrust Support.

5134

Could not find info packet body

An information packet was missing or corrupt.

Check the source of the data to see if it was valid. If this is from pblog, check that the input file is a valid event log.

5135

Could not form info table

An information packet was missing or corrupt.

Check the source of the data to see if it was valid. If this is from pblog, check that the input file is a valid event log.

5136

writeIOLog prior stdin is still pending.

A buffer contains stdin that should have already been written to the IO log.

Contact BeyondTrust Support.

5137

writeIOLog stdin buffer is full.

IO Logging comparison buffer for stdin is full. The current stdin data will not be added to the buffer and will not be written to the IO log.

Contact BeyondTrust Support.

5401

accept

 

Contact BeyondTrust Support.

5401.05

Accept failed on socket #

pbguid failed to accept an incoming connection.

Contact BeyondTrust Support.

5402

connect

This is an error from Unix/Linux during an attempted back connection from pbmasterd to pbrun or from pblocald to pbmasterd/pblocald.

Contact BeyondTrust Support.

5403

bind

 

Contact BeyondTrust Support.

5403.08

bind

pbguid failed to bind a socket.

Contact BeyondTrust Support.

5403.09

bind

pbguid failed to bind a socket.

Contact BeyondTrust Support.

5404

getgroups

A return indicating invalid number means that the number of supplemental groups specified for the user exceeds the number allowed by the host operating system.

Contact BeyondTrust Support.

5405

gethostname

 

Contact BeyondTrust Support.

5405.04

gethostname

pbguid failed to determine systems hostname.

Contact BeyondTrust Support.

5405.06

Could not determine host name

pbguid failed to determine systems hostname.

Contact BeyondTrust Support.

5405.07

gethostname

pbguid failed to determine systems hostname.

Contact BeyondTrust Support.

5406

listen

 

Contact BeyondTrust Support.

5406.05

listen

pbguid failed to listen for incoming connections.

Contact BeyondTrust Support.

5407

pipe

 

Contact BeyondTrust Support.

5408.##

select

The program encountered an error in a select system call. This is followed by an operating system diagnostic that details the problem.

Contact BeyondTrust Support.

5409

socket

 

Contact BeyondTrust Support.

5409.01

Error updating adding utmp record

Could not add a new record to the utmp or utmpx database. This is a fatal error message.

 

5409.02

Error updating wtmp files

Could not add a record to the wtmp or wtmpx database. This is not a fatal error.

 

5409.05

socket

pbguid failed to acquire a socket for binding.

Contact BeyondTrust Support.

5410

sysinfo(SI_HW_SERIAL)

 

Contact BeyondTrust Support.

5411

tcgetattr

 

Contact BeyondTrust Support.

5412

tcsetattr

 

Contact BeyondTrust Support.

5418

Timeout on fd: <number>

Select timed out waiting for fd to become writable.

Contact BeyondTrust Support.

5418.01

SSL_connect timeout on fd:<number>

Select timed out waiting for fd to become writable.

Contact BeyondTrust Support.

5418.02

SSL_write timeout on fd:<number>

Select timed out waiting for fd to become writable.

Contact BeyondTrust Support.

5418.03

SSL_read timeout on fd:<number>

Select timed out waiting for fd to become writable.

Contact BeyondTrust Support.

5419

TIOCSWINSZ

 

Contact BeyondTrust Support.

5420

getrlimit

 

Contact BeyondTrust Support.

5422

AIX select timeout

 

Contact BeyondTrust Support.

5424

ptysystem_io_loop

A read error occurred during a ptysystem call from the policy language.

 

5425

ptyfork failed in ptysystem.

<error string>

An error occurred while trying to create a subprocess from the policy language - most likely a call to system().

 

5426

I/O log open header failure

A readMuxHeader failed while trying to open an I/O log. This usually means the log server daemon failed after it started.

Check pblogd.log to see if an error was logged there.

5427

I/O log entry write.

A write called while making an I/O log entry.

Check the error logs and why a connection may have failed.

5428

I/O log write.

A write failed while making an I/O log header entry.

 

5429

I/O log write.

A write error occurred while writing I/O log data.

 

5430

header problem in readMuxHeader fd <file descriptor>. Expected <number> bytes

readMuxHeader received an error during a read.

This is usually a secondary error caused by a prior communications problem. Check the prior problem number.

5431

readMuxData <number>

An undiagnosed readMuxData error occurred. The number may indicate a system error number.

 

5432

Error sending command <command number>. Expected length <number>

 

 

5433

Event log write failure

Write failed during an event log record.

 

5434

atomic read

Read failure during fetchCommandBuffer

 

5435

getSocketHostname on fd ## getsockname

The system could not determine the local hostname for a socket. This is followed by the system-specific reason.

 

5435.01

getSocketHostname <function name> on fd ## - <operating system message>

The program could not find the name of a host on a connection. If the function name is gethostname, the problem was finding the local host name. If the function name is getpeername, the problem was finding the remote host's name. This is followed by an operating-system specific diagnostic.

Check if name services (for example, DNS, NIS, and nsswitch.conf) are configured properly.

5435.02

getSocketAddress <function name> on fd ## - <operating system message>

The program could not find the address of a host on a connection. If the function name is gethostname, the problem was finding the local host address. If the function name is getpeername, the problem was finding the remote host's address. This is followed by an operating system specific diagnostic.

This usually indicates a connection failure. Check the diagnostic logs for both hosts in the connection.

5436

getSocketHostname on fd ## getpeername

The system could not determine the remote hostname for a socket. This is followed by the system- specific reason.

 

5437

fd: <number> is open and not writable, cmd: <number>

Unable to send a control message because the fd is not writable

Contact BeyondTrust Support.

5438

backBind## could not unblock socket

A socket could not be set to non-blocking status. This is followed by a system-specific diagnostic message.

 

5439

backBind## could not reblock socket

A socket could not be set to blocking status. This is followed by a system-specific diagnostic message.

 

5440

backConnect# could not unblock socket:

A socket could not be set to non-blocking status. This is followed by a system-specific diagnostic message.

 

5441

backConnect# timed out from i =

###

A timeout occurred waiting for a connection. This is followed by a system-specific diagnostic message.

 

5442

backConnect# could not reblock socket

A socket could not be set to non-blocking status. This is followed by a system-specific diagnostic message.

 

5443

write error in sendRawIOLogBody log:

A write error occurred while sending a log packet to the log server. This is followed by a system-specific diagnostic message.

 

5444

Could not get full client host name '<short host name>'

The full host name could not be found.

 

5445

Could not get full run host name '<short run host name>'

The full run host name could not be found.

 

5446

Error in setsockopt() from connectMaster

An error occurred while trying to set socket options. This is followed by a system-specific diagnostic message.

 

5447

connectClient getpeername

The submit host could not be verified. This is followed by system-specific diagnostic message.

 

5448

Could not get local host interface name:

pbrun could not determine the name for its network interface. This is followed by a system- specific diagnostic message.

 

5449

Could not get full local host name

pbrun could not determine the full host name for a specific interface. This is followed by a system-specific diagnostic message.

 

5450

Setup failure in server child

A daemon could not perform setup actions for standalone server mode. This is followed by a system-specific diagnostic message.

 

5451

Could not find service port for

<service name>

The default port for the listed service name could not be determined.

 

5452

Could not obtain server socket for <service> port ##:

A socket could not be created for the listed service and port. This is followed by a system- specific diagnostic message.

 

5453

Could not set server socket options for <service> port ##:

The options for a socket could not be set for the listed service and port. This is followed by a system-specific diagnostic message.

 

5454

Could not bind server socket for <service> port ##:

A socket could not be bound for the listed service and port. This is followed by a system- specific diagnostic message.

 

5455

Server process <pid number> accept error for <service> port

##

A standalone server daemon could not accept an incoming connection. This is followed by a system-specific diagnostic message.

 

5456

Could not access utmpuser '<username>'

The run host could not identify the requested user name to use in utmp.

 

5457

Could not reacquire root - setreuid

pbrun could not reacquire root privileges. This is followed by a system-specific diagnostic message.

 

5458

Could not relinquish root - setreuid(<effective uid>, <real uid>)

pbrun could not relinquish root privileges. This is followed by a system-specific diagnostic message.

 

5459

Could not read settings file '<settings file name>'

The listed settings file could not be read. This is followed by a system-specific diagnostic message.

 

5460

Short read on settings file '<settings file name>'

Could not read the expected number of bytes from the listed settings file.

 

5461

Could not resolve local host name

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

 

5462

Could not get Policy Server name

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

 

5463

Error setting up -n mode

pbrun could not set up -n mode. This is a failure to open /dev/null or to duplicate a temporary file descriptor. This is followed by a system-specific diagnostic message.

 

5464.01

setuser failed:

The setuser() function failed. This followed by a system- specific diagnostic message.

Check the pbmasterd log files/syslog to see what caused the problem.

5464.02

setuser failed:

The setuser() function failed. This is followed by a system- specific diagnostic message.

Check the pblocald, pbrun and syslog files to see what caused the problem.

5464.03

setuser failed:

Failed to set user and group permissions

pbguid's set user function failed to properly set the group.

5465

setuser could not setgid to ##

A setgid call failed during a setuser sequence. This is followed by a system-specific diagnostic message.

 

5466

setuser could not setuid to ##

A setuid call failed during a setuser sequence. This is followed by a system-specific diagnostic message.

 

5467

Could not determine auditing status

An attempt to determine Solaris 8 auditing status failed. This is followed by a system- specific diagnostic message.

 

5468

Could not obtain auditmask for <user>

An attempt to load a Solaris 8 auditing mask for the listed user failed. This is followed by a system-specific diagnostic message.

 

5469

Could not set auditing ##

An attempt to establish Solaris 8 auditing failed. This is followed by a system-specific diagnostic message.

 

5470

Could not get pbguid host name

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

 

5471

Could not get Policy Server name

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

 

5472

Can not get host name

pbguid could not obtain the local host name.

 

5473

Could not set resource limit <name> to <value>

The named resource limit could not be set to the listed value.

Check that the value is valid for the resource.

5474

Getaddrinfo failed for host

<host name> - <operating system message>

A call to find the address information for the listed host failed. The operating-specific diagnostic contains more detail.

 

5475.01

openSyncPipe failed - <operating system message>

An attempt to open a synchronization pipe between two processes failed. The operating system specific diagnostic contains more information.

 

5475.02

openSocketpair for "<command>" failed - <operating system message>

An attempt to open a synchronization socket between two processes failed. The operating system specific diagnostic contains more information.

 

5476

Could not obtain primary local host name.

The local host name could not be found. This is often preceded by another diagnostic that details the problem.

 

5476.##

dup2 failed on control socket - <operating system message>

An attempt to move a control socket failed. The operating system specific diagnostic contains more information.

 

 

5477

Could not resolve address/port for <extended port> -

<operating system message>

The address and port combination in the extended port could not be resolved.

Correct the extended port or correct your name services.

5478

Could not find <network family> hostname for fd ##

The program could not find the host name for a network connection.

Check name services.

5479

Could not resolve <network family> local host name.

The program could not determine the host name for the local machine in the listed network family.

Check name services.

5480

Could not resolve primary local host name

The program could not determine the primary local host name.

Check name services.

5481

Could not get submit host name

The program could not determine the submit host's name.

Check name services.

5481.01

openSyncPipe failed - <operating system message>

An attempt to open a synchronization pipe between two processes failed. The operating-system specific diagnostic contains moreinformation.

 

5482.02

openSocketpair for "<command>" failed - <operating system message>

An attempt to open a synchronization socket between two processes failed. The operating-system specific diagnostic contains more information.

 

5483

Could not remove named port <port name>

The program could not remove the Unix/Linux Domain Socket with the listed name. This is followed by an operating system message that details the error.

 

5484

Could not change directory to <directory name> - <operating system message>

The program could not change to the named directory. This is followed an operating system message detailing the problem.

 

5485

Could not set block status for fd #

Internal error.

Contact BeyondTrust Support.

5485.01

Write error

A write failed. This is followed by an operating-system diagnostic that details the problem.

Correct the situation described in the operating-system diagnostic.

5485.02

Write error

A write failed. This is followed by an operating system diagnostic that details the problem.

Correct the situation described in the operating-systemdiagnostic.

5486

Could not clear block status for fd #

Internal error.

Contact BeyondTrust Support.

5487

Could not retrieve start time

The starting time of the request could not be determined. This is followed by an operating system diagnostic message.

Correct the situation described in the operating-system diagnostic message.

5488

Error opening environment file:

<filename> <system error string>

Privilege Management was unable to open the specified file due to the reason indicated

Resolve the indicated system error.

5489

fatal error on environment file: <filename> <system error message>

fstat() failed due to the reason indicated

Resolve the system error.

5490

environment file is a directory: <filename>

The file must be a regular file.

Specify a proper environment file.

5491

environment file is not a regular file or symlink:

<filename>

The environment file must be a regular file or a symlink to a regular file.

 

Specify a proper environment file.

5492

environment file is too large:

<filename>

 

Create a smaller environment file.

5501

Expected eventlog to be a string

 

Change the configuration file to a string.

5502.##

status undefined or not a number.

 

Contact BeyondTrust Support.

5504

unknown arch: don't know how to get hostid!

 

Contact BeyondTrust Support.

5505

unknown info. type ##

 

Contact BeyondTrust Support.

5507

writeInfoRecord: unknown type

## -- shouldn't happen!

 

Contact BeyondTrust Support.

5508

sendInfoPacket: unknown type ## -- shouldn't happen!

 

Contact BeyondTrust Support.

 

5509

hostname size invalid ### (<host>)

 

Contact BeyondTrust Support.

5510

Expected list variable for

<name>

 

Contact BeyondTrust Support.

5511

Expected string variable for

<name>

 

Contact BeyondTrust Support.

5512

Expected integer variable for

<name>

 

Contact BeyondTrust Support.

5513

runenv should be a list

 

Contact BeyondTrust Support.

5514

runenv is undefined

 

Contact BeyondTrust Support.

5515

String variable <name> is undefined

 

Contact BeyondTrust Support.

5516

List variable <name> is undefined

 

Contact BeyondTrust Support.

5517

Integer variable <name> is undefined

 

Contact BeyondTrust Support.

5518

runargv is undefined

 

Contact BeyondTrust Support.

5519

Expected lognopassword to be a number

lognopassword is a string or a list.

Contact BeyondTrust Support.

5520

Protocol string overflow

The startup protocol string between pbrun/pbmasterd or pbmasterd/pblocald is too long.

 

5521

lastYylval stack underflow

An internal parser error occurred.

Contact BeyondTrust Support.

5522

Invalid channel type in pbAtomicRead - <type>

Internal error.

Contact BeyondTrust Support.

5523

Invalid channel type in pbAtomicWrite - <type>

Internal error.

Contact BeyondTrust Support.

5524

getSettingsDefaultString not implemented for type <type>

Internal error.

Contact BeyondTrust Support.

5525

Type mismatch wanted <desired type> for <setting name>, got

<actual type>

Internal error.

Contact BeyondTrust Support.

5526

Could not find settings keyword

<settings name>

Internal error.

Contact BeyondTrust Support.

5527

Internal error - invalid mode setting <value>

Internal error.

Contact BeyondTrust Support.

5528

Disabling localmode for SELinux runhost <hostname>

The Privilege Management policy had set runlocalmode=true; however the submithost is confined by SELinux, and pbrun does not support localmode when SELinux is used. After Privilege Management policy execution, pbmasterd reset runlocalmode to false.

None required.

5529

Local mode (-l, --local_mode) cannot be specified with SELinux confined pbrun

pbrun is confined by SELinux and cannot support local mode; however, the -l option (or --local_mode) was specified.

Change the pbrun command line so that -l and --local_mode are not used.

5597

The file <file> is already encrypted - please select plain text version to encrypt

The file chosen to encrypt is already encrypted.

Use the plain text version of the file to encrypt.

5598

Failed to read file <FILE>,

<REASON>

Failed to read the file we are going to encrypt.

Check it has read permission and has bytes in it.

5599

Failed to open file <file>,

<reason>

Failed to open the file that we are going to encrypt (system error is displayed after the filename).

Check file exists and is readable and is a regular file.

5600

must be run as root

pbencode needs to be run as root to have access to the /etc/pb.key and the /etc/pb.conf files (the defaults).

 

5601

<file name> does not exist

The listed file does not exist.

Check the command line for misspellings.

5602

<file name>is not a regular file

The file used to read the key or the unencrypted text is not a regular file.

 

5603

ioLogMktemp returned file name too long

The returned filename was longer than the template.

 

5604

block length(number) on fd

<file descriptor> exceeds remaining buffer size (<number>)

 

 

5605

psPath() called without prior call to setPrefixAndSuffix()

Internal error

Contact BeyondTrust Support.

5606

Could not send info packet to pbmasterd

pbguid could not transmit its environment information to pbmasterd.

 

5607

Can not find terminal type

pbreplay could not determine its terminal type.

 

5608

Unable to initialize terminal -

<terminal type>

pbreplay could not initialize the listed terminal type.

 

5609

UID stack overflow

An attempt was made to store too many UID states.

Contact BeyondTrust Support.

5610

UID stack underflow

An attempt was made to restore the UID state when no state was stored.

Contact BeyondTrust Support.

5611

waitpid error: <number> <error string> on running job: <pid>

The waitpid() system call failed.

Contact BeyondTrust Support.

5612

waitpid error: <number> <error string> kill0:

<errno><errstring>

The waitpid() system call failed. The kill(jobPID,0) status indicates whether the job is running or not.

Contact BeyondTrust Support.

5613

Error <errno> opening settings file <filename>

The pb.settings file could not be opened due to the error indicated by errno.

 

5614

Error <errno> opening lock file

<filename>

The indicated lock file could not be opened due to the error indicated by errno.

 

5615

termcap info for <terminal name> not found error:<error number>

The terminal type specified does not have a termcap entry.

Add an appropriate termcap entry on the server where pbreplay is used. Or replay the iolog on a different host that has an appropriate termcap entry.

5617

pbPamSessionStart Solaris 9 projname specified but solarisprojects is not enabled

The pbrun commandline, or the Privilege Management for Unix and Linux policy specified a Solaris project, however the Solaris 9 runhost does not have Solaris projects enabled.

Enable Solaris projects on the runhost. Or change the commandline or policy so that a Solaris project is not specified for that runhost.

5618

allList1ElementsNotInTreeList2 ERROR 1

An internal Privilege Management entitlement reporting error has occurred.

Contact BeyondTrust Support.

5619

ERROR 2 ID NOT FOUND: <variable name>

An internal Privilege Management entitlement reporting error has occurred.

Contact BeyondTrust Support.

5620

allList1ElementsNotInTreeList2 ERROR 3:<lexical type>

An internal Privilege Management entitlement reporting error has occurred.

Contact BeyondTrust Support.

5621

error updating aux license db. no nodename

pbrn did not properly communicate the submithost's nodename to pbmasterd.

Verify the submithost is properly configured with a nodename.

5622

error getting peer name

pbmasterd could not get the peername from the socket connected to pbrun.

Ensure that networking is properly configured.

5623

terminal size error for file:<io log filename>

The screen size captured in the I/O log was too large to be replayed with the amount of memory contained in the server where pbreplay was run.

Increase the memory on the host where pbreplay is run.

5624

REGEX ERROR: <regular expression error description returned by regerror>

The pbreplay -O -- regex <PATTERN> command had an invalid regex PATTERN specified.

Change the PATTERN to be a valid extended POSIX regex pattern.

5625

regexec ERROR

The regular expression engine regexec encountered an unknown error.

Contact BeyondTrust Support.

5626

Bad match format <specified format>

The pbreplay print format expression, specified with the -p option, is invalid.

Change the print format expression to include a valid Privilege Management for Unix and Linux Policy expression.

5701

Did not find Kerberos function

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibkrb5dependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibkrb5dependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibkrb5dependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses Kerberos to determine which libraries are needed.

5702

Unable to load KRB5 library.

One or more of the shared libraries listed in the sharedlibkrb5dependencies keyword could not be loaded.

See the previous error message for the name of the shared library that could not be loaded.

5703

Unable to resolve KRB5 symbol

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibkrb5dependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibkrb5dependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibkrb5dependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses Kerberos to determine which libraries are needed.

5704

Unexpected number of arguments:

<count>

 

Contact BeyondTrust Support.

5705

Error loading library: <name>

The shared library indicated could not be loaded.

Make sure the file exists. Use the file command to verify the file is a shared library for the appropriate architecture.

5706

Did not find LDAP function

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibldapdependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibldapdependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibldapdependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses LDAP to determine which libraries are needed.

5707

Unable to load LDAP library.

One or more of the shared libraries listed in the sharedlibldapdependencies keyword could not be loaded.

See the previous error message for the name of the shared library that could not be loaded.

5708

Unable to resolve LDAP symbol

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibldapdependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibldapdependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibldapdependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses LDAP to determine which libraries are needed.

5709

Error loading library: <name>

The shared library indicated could not be loaded.

Make sure the file exists. Use the file command to verify the file is a shared library for the appropriate architecture.

5710

Did not find SSL function

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibssldependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibssldependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibssldependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses SSL to determine which libraries are needed.

5711

Unable to load SSL library.

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

See the previous error message for the name of the shared library that could not be loaded.

5712

Unable to resolve SSL symbol:

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibssldependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibssldependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibssldependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses SSL to determine which libraries are needed.

5713

Error loading library: <name>

The shared library indicated could not be loaded.

Make sure the file exists. Use the file command to verify the file is a shared library for the appropriate architecture.

5714

Sleep select failed <errno string>

The select system call failed due to the reason specified in the <errno string>

Examine the <errno string>

5714

Sleep select failed <errno string>

The select system call failed due to the reason specified in the <errno string>

Examine the <errno string>

5715

Unable to load AD Bridge event log library.

One or more of the shared libraries listed in the sharedlibpbisdependencies keyword could not be loaded.

See the previous error message for the name of the shared library that could not be loaded.

5716

Unable to resolve AD Bridge event log symbol: <name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibpbisdependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the

sharedlibpbisdependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibpbisdependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses AD Bridge event log to determine which libraries are needed.

5717

Did not find AD Bridge event log function <name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibpbisdependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibpbisdependencies keyword. nm can be run against all known shared libraries to locate the function. ldd can be run against libraries already listed in the sharedlibpbisdependencies keyword, to determine if a dependent library needs to be listed as well. truss can be used with a working service that uses AD Bridge event log to determine which libraries are needed.

5718

Privilege Management for Unix and Linux encountered a AD Bridge error: <error message>

Privilege Management for Unix and Linux encountered a AD Bridge interface error.

Contact BeyondTrust Support.

5719

Location of CURL library is unknown.

The keyword sharedlibcurldependencies is missing or has no value.

Add the sharedlibcurldependencies keyword to the settings file and provide a valid path. You may also disable the Privilege Management for Unix and Linux features that require libcurl.

5720

Did not find CURL function

<name>

The function indicated is not located in the shared libraries currently loaded using the sharedlibcurldependencies keyword.

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibcurldependencies keyword.

nm can be run against all known shared libraries to locate the function. ldd can be run against libraries alrea.

5721

Unable to load CURL library.

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

See the previous error message for the name of the shared library that could not be loaded. Ensure it exists and is valid.

5722

Unable to resolve CURL symbol:

<symbol>

The function indicated is not located in the shared libraries currently loaded using the sharedlibcurldependencies keyword

Use nm, ldd, or truss to determine which library contains the named function, then add that library to the sharedlibcurldependencies keyword.

nm can be run against all known shared libraries to locate the function. ldd can be run against libraries area.

5723

Error loading library: <name>

The shared library specified by sharedlibcurldependencies keyword could not be loaded.

Make sure the file exists. Use the file command to verify the file is a shared library for the appropriate architecture.