Sponsored Content
Operating Systems Solaris Unable to fully log into non-global-zones after a SRU Post 303029627 by samthewildone on Tuesday 29th of January 2019 10:22:31 PM
Old 01-29-2019
Unable to fully log into non-global-zones after a SRU

tldr; after SRU patches applied on newly created boot environment, reboot with ability to log into global zone but unable to "fully" log into non-global-zones.

Without going into much detail here's what we did;
  • 1) Activated new boot environment with latest SRU patches from Oracle
  • 2) Successfully boot / login to new BE with latest SRU
  • 3) Non-global-zones appear to be in "running" status.
  • 4) Upon logging into Non-global-zones, we get kicked back to global zone in seconds
  • 5) Due to time constrains, unable to do further investigation reverted back to original be; able to successfully log into non-global zones

What gives? Have any of you experience such darkness ?!
 

9 More Discussions You Might Find Interesting

1. IP Networking

Unable to ping freebsd machine using fully qualified domain name

hi all. am unable to ping a freebsd machine using fully qualified domain name from a windows machine. i have already set the fqdn for the machine. plz advise me. thanks. (2 Replies)
Discussion started by: coolatt
2 Replies

2. Solaris

Global Zones

I'm logged into a non-global zone server. How would I find out what the global zone server name is from there? (1 Reply)
Discussion started by: soupbone38
1 Replies

3. Solaris

Global zones - not allow log via SSH

Hi, I have Global zone and 2 users: root and app. I know password root and app. When a user app log - putty displays Access denied Using keyboard-interactive authentication. In file /etc/security/policy.conf I set CRYPT_DEFAULT=2a And in file /etc/ssh/sshd_config I set PermitRootLogin... (1 Reply)
Discussion started by: bieszczaders
1 Replies

4. Solaris

How to access ENV variables of non global zones in global zone???

Hi Guys, My requirement is I have file called /opt/orahome/.profile in non global zone. PATH=/usr/bin:/usr/ucb:/etc:/usr/sbin:/usr/local/bin:/usr/openwin/bin:. export PATH PS1="\${ORACLE_SID}:`hostname`:\$PWD$ " export PS1 EDITOR=vi export EDITOR ENV=/opt/orahome/.kshrc export ENV... (1 Reply)
Discussion started by: vijaysachin
1 Replies

5. Solaris

How to see global hostname by logging in non global zones?

Hi guru Could any one help me by letting me know, how to see global hostname by logging in non global zones Regards (2 Replies)
Discussion started by: girish.batra
2 Replies

6. Solaris

How to share/mount ZFS in two non-global zones?

Hi All, first time here. :o I need a some assistance with ZFS. I have two ZFS pools: zoneA/nfs_export zoneB/nfs_export Each dataset is mounted in a particular zone (zoneA and zoneB respectively). I have created a new dataset "zoneA/nfs_tmp" which I want to mount or share... (8 Replies)
Discussion started by: gabriel4
8 Replies

7. Solaris

cpu- requirements for non-global zones

Hello Admins, Does anyone has any idea on how to assign no. of cpu and memory to non-global zones on solaris 10..... We have few zones in our environment. We wanted to assign memory and no of cpu's ..(e.g. 4Gb / 2 CPU's) Thanks... (4 Replies)
Discussion started by: snchaudhari2
4 Replies

8. Solaris

Solaris 10 - rexplorer and Non-Global zones

Hi all - not really a problem as such, but just hoping someone can shed some light. We point rexplorer to multiple Global zones and it works as expected. However, each Non-Global zone get around a hundred of root su'ing to root messages, i.e.: SU 07/14 03:02 + ??? root-root SU 07/14 03:02 +... (5 Replies)
Discussion started by: dlam
5 Replies

9. Solaris

Solaris Global/Zones patching

Issue is : We have Solaris Global with 12 Zones and some have 15 Zones. All the OS version are10. Is it possible to apply patch at Zone level instead of patching at Global level? Please let me know. (10 Replies)
Discussion started by: baladelaware73
10 Replies
sysidconfig(1M) 														   sysidconfig(1M)

NAME
sysidconfig - execute system configuration applications, or define set of system configuration applications SYNOPSIS
sysidconfig [-lv] [-a application] [-b basedir] [-r application] Invoked without any options, the sysidconfig program executes a list of applications. An application on this list is referred to as a "sys- tem configuration application." Every application on this list will be passed one command-line argument, -c. This flag will cause the sys- tem configuration application to perform its configuration function. Without options, sysidconfig should only be invoked by startup scripts, which occurs during the initial installation and during a reconfigure reboot. All applications on the list will be executed, if possible. All activity taken by the sysidconfig program is logged in the sysidconfig log file, /var/log/sysidconfig.log. If one or more of the applications on the list are either not present at execution time, are not exe- cutable, or execute but return a failure code upon completion, then that information will be logged as well. Successful completion of the program can be assumed if no error message is present in the log file. Programs are executed sequentially, with only one configuration application active at a time. Executed with the -l, -a, or -r options, the sysidconfig program allows the super-user to list the defined configuration applications, and to add items to or remove items from that list. Running sysidconfig with options is the only way to view or manipulate the list. Only the super-user can execute the sysidconfig program with options. The -b and -v options change the behavior of sysidconfig, and can be used with or without the list manipulation options discussed above. The -b basedir option is used to specify a reference root directory other than the default, /. The -v option duplicates the log file output on stdout. By default, no SPARC based applications exist on this list. However, the based systems are delivered with one application, kdmconfig(1M), on the list. kdmconfig is not delivered on SPARC based systems. This application is an extension of the sysidtool(1M) suite of programs. It is executed during initial installation and during a reconfig- ure reboot, before the window system has been started. Graphical User Interface (GUI) applications will not execute successfully if they are added to the list of configuration applications via sysidconfig -a. This program is referenced, but not fully described, in the sysidtool(1M) manual page. The valid options are: -a application Add the named application to the list of defined applications. When next invoked without arguments, sysidconfig will run this newly added application after all previously defined applications. application must be a fully qualified path name that is not currently on the list of applications to execute. -b basedir Specify an alternate base directory (/ is defined as the default base directory if no other is specified). The specified directory is used as the root directory when adding, listing, removing, or executing configuration applications. The log file where information is recorded is in /var/log, relative to the specified basedir. In the log file, the basedir is not noted. This means, for example, that if the super-user on a diskless client's server executes: sysidconfig -b /export/root/client -a /sbin/someapp then the diskless client client would have /sbin/someapp executed upon reconfigure reboot. The diskless client's log file would note that /sbin/someapp was added, not /export/root/client/sbin/someapp. Note - The root file system of any non-global zones must not be referenced with the -b option. Doing so might damage the global zone's file system, might compromise the security of the global zone, and might damage the non-global zone's file system. See zones(5). -l List defined configuration applications. Applications will be executed one at a time, in the order shown in the list. -r application Remove the named application from the list of defined applications. application must be a fully qualified path name and it must be on the existing list of applications to execute. -v Verbose mode. This option echoes all information sent to the log file to stdout. Such information includes timestamp infor- mation about when the program was executed, the names of applications being executed, and results of those executions. The sysidconfig program will return 0 if it completes successfully. When executed with the -r or -a options, error conditions or warnings will be reported on stderr. If the requested action completes suc- cessfully, an exit code of 0 will be returned. EPERM The program was executed by a user other than the super-user. EINVAL Option -l, -a, or -r was passed and the action could not be completed successfully. /var/log/sysidconfig.log sysidconfig log file See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWadmap | +-----------------------------+-----------------------------+ sys-unconfig(1M), sysidtool(1M), attributes(5) Only kdmconfig(1M) When run without options, a log of the sysidconfig program's activity can be found in /var/log/sysidconfig.log. This file contains a time- stamp log of each program executed, its resulting stderr output, and its exit code. If an application in the list was not found or is not executable, that will also be noted. 6 Apr 2005 sysidconfig(1M)
All times are GMT -4. The time now is 07:51 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy