HP 9000 Containers A.03.01 on HP Integrity Server Administrator Guide HP-UX 11i v3 (5900-3112, June 2013)

If the node name on the global container (host system) is longer than 8 characters in length (and
the kernel parameter expanded_node_host_names is set to 1), only two login sessions are
allowed to legacy containers on the system. The workaround is to run the following command:
$ kctune uname_eoverflow=0
If you fail to access HP 9000 system containers using telnet, verify whether the value of kernel
parameters npty and nstrpty are sufficient. Also, verify if there are enough /dev/pty and
/dev/pts devices exposed to the container. If not, run the following commands:
$ kctune npty=<new value>
$ insf -e -n <new npty value>
$ srp –add <srp_name> -tune device=/dev/pty/*
There is a known limitation that legacy inetd services cannot be used with large PIDs. Ensure
that the kernel tunable parameter process_id_max is set to less than or equal to 30000.
NOTE: Though the login services are not functioning properly, login using srp_su <srp_name>
works if the status of the HP 9000 system container is started. This can be used for debugging
purposes. For example, it can be used to get a tusc log on sshd or inetd as described in
Section 12.4 (page 79).
12.4 Collecting application and system call logs
If application fails inside the container:
• Verify whether the application logs and files where stdout or stderr are redirected.
• Install HP-UX system call tracer utility tusc for HP-UX 11.31/Itanium on the host. It can be
downloaded from http://hpux.connect.org.uk/hppd/hpux/Sysadmin/tusc-8.1
• Copy the /usr/local/bin/tusc binary from the global container to the HP 9000 container.
• Log in to the HP 9000 container and run the tusc utility on the failing application:
$ tusc –o <output file path> -lfpkaev \
-s \!sigprocmask,sigaction,sigsetreturn \
<executable> <arguments>
• Search the tusc log for clues like failing system calls. Verify whether any of the HP 9000
container limitations are encountered. For example, analyze execve(2) system calls to see
if any unsupported command is invoked.
12.5 Debugging applications
Use PA-RISC HP WDB to debug applications inside a container, just like on the HP 9000 server.
The only additional requirement is to set the PA_DEBUG environment variable before initiating gdb
using the $ export PA_DEBUG=1 command.
ARIES generates PA-RISC HP-UX core files when the application aborts. WDB can be used to
analyze these core files.
Currently, there is a known limitation with this option; when an application running under ARIES
emulation is debugged or traced, it runs much slower. This is because ARIES emulation of ttrace(2)
system calls works only when ARIES is running in pure interpreter mode with no translations or
caching.
ARIES does not support debugging or tracing applications with GNU GDB and custom tools (in
particular, 64-bit debuggers and tracers).
NOTE: You can recompile and link applications, as long as the required compilers and tools are
available inside the container.
12.4 Collecting application and system call logs 79