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
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
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
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
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
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
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
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
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
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
LEARN ABOUT SUNOS
rem_drv
rem_drv(1M) rem_drv(1M)
NAME
rem_drv - remove a device driver from the system
SYNOPSIS
rem_drv [-b basedir] device_driver
The rem_drv command informs the system that the device driver device_driver is no longer valid. If possible, rem_drv unloads device_driver
from memory. rem_drv also updates the system driver configuration files.
If rem_drv has been executed, the next time the system is rebooted it automatically performs a reconfiguration boot (see kernel(1M)).
The following options are supported:
-b basedir Sets the path to the root directory of the diskless client. Used on the server to execute rem_drv for a client. The client
machine must be rebooted to unload the driver.
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).
Example 1: Removing the sd Driver
The following example removes the sd driver from use:
example% rem_drv sd
Example 2: Removing a Diskless Client
The following example removes the driver from the sun1 diskless client. The driver is not uninstalled or unloaded until the client machine
is rebooted.
example% rem_drv -b /export/root/sun1 sd
Note the caveat on the use of the -b option in the description of that option, above.
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcsu |
+-----------------------------+-----------------------------+
add_drv(1M), kernel(1M), update_drv(1M), attributes(5), devfs(7FS)
6 Apr 2005 rem_drv(1M)