• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

UnixArena

  • Home
  • kubernetes
  • DevOps
    • Terraform
    • Jenkins
    • Docker
    • Openshift
      • OKD
    • Ansible engine
    • Ansible Tower
      • AWX
    • Puppet
  • Cloud
    • Azure
    • AWS
    • Openstack
    • Docker
  • VMware
    • vCloud Director
    • VMware-Guests
    • Vcenter Appliance 5.5
    • vC OPS
    • VMware SDDC
    • VMware vSphere 5.x
      • vSphere Network
      • vSphere DS
      • vShield Suite
    • VMware vSphere 6.0
    • VSAN
    • VMware Free Tools
  • Backup
    • Vembu BDR
    • Veeam
    • Nakivo
    • Azure Backup
    • Altaro VMBackup
    • Spinbackup
  • Tutorials
    • Openstack Tutorial
    • Openstack Beginner’s Guide
    • VXVM-Training
    • ZFS-Tutorials
    • NetApp cDot
    • LVM
    • Cisco UCS
    • LDOM
    • Oracle VM for x86
  • Linux
    • How to Articles
    • Q&A
    • Networking
    • RHEL7
  • DevOps Instructor-led Training
  • Contact

LDOM console write access issue – Solaris

March 27, 2014 By Cloud_Devops 5 Comments

Now a days i have mostly  dealing with oracle VM for SPARC on T-4 servers.(LDOM). As we all know that hardware console can be writable for only one user at a time and if you take the second session , it will automatically connect in read only mode unless you use the force option. The same way oracle VM for SPARC console also behaves even though its a virtual consoles on the hypervisor levels.

Sometimes , the first console session may terminate unexpectedly due to network issues and if you try take the console for second time ,you may get error that “You do not have write access” on the console screen.

root@sun5#ldm list-domain
NAME             STATE      FLAGS   CONS    VCPU  MEMORY   UTIL  UPTIME
primary          active     -n-cv-  SP      8     2G       0.3%  2h 34m
ua1              active     -n----  1       12    3G       0.1%  1h 37m
ua2              active     -n----  2       12    2560M    0.1%  1h 37m
root@sun5#
root@sun5#telnet 127.0.0.1 1
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

Connecting to console "ua1" in group "ua1" ....
Press ~? for control options ..
You do not have write access
You do not have write access
You do not have write access
You do not have write access
You do not have write access
You do not have write access
You do not have write access
You do not have write access
You do not have write access

telnet> quit
Connection to 127.0.0.1 closed.

To fix this issue, login to the control domain and list the telnet session.

root@sun5#ps -ef |grep telnet
    root  6259  6118   0 12:07:22 pts/4       0:00 telnet 127.0.0.1 1
    root  6035   374   0 12:01:21 ?           0:00 /usr/sbin/in.telnetd
    root  1645   374   0 09:47:55 ?           0:00 /usr/sbin/in.telnetd
    root  5867   374   0 11:57:25 ?           0:00 /usr/sbin/in.telnetd
    root  6004  5870   0 12:00:49 pts/1       0:00 telnet localhost 2
    root  6262  6038   0 12:07:46 pts/2       0:00 grep telnet

Kill the process which is associated to the guest domain. In this case , i am having issue with “ua1” guest domain which has the console port-1.Let me terminate the process of that and try to connect the console again.

root@sun5#kill -9 6259
root@sun5#telnet 127.0.0.1 1
Trying 127.0.0.1...
Connected to 127.0.0.1.
Escape character is '^]'.

Connecting to console "ua1" in group "ua1" ....
Press ~? for control options ..

ua1 console login: root
Password:
Mar 24 13:44:13 ua1 login: ROOT LOGIN /dev/console
Last login: Mon Mar 24 13:16:41 from 192.168.0.117
Oracle Corporation      SunOS 5.11      11.1    September 2012
root@ua1:~# logout

ua1 console login:
telnet> quit
Connection to 127.0.0.1 closed.
root@sun5#

Awesome .We have fixed the issue .This is small trick but you need to remember this when you face this kind of issues while connecting the console.

Share it ! comment it !! Be sociable !!!

Filed Under: LDOM

Reader Interactions

Comments

  1. Michele says

    February 4, 2020 at 7:02 am

    Thanks very much. That worked perfectly.

    Reply
  2. Ruwinda Fernando says

    February 2, 2020 at 2:41 pm

    Nice little very important tip 🙂 Thanks

    Reply
  3. vijay says

    March 1, 2016 at 11:32 am

    Thank you , It is really helpful . You are doing a great job

    Reply
  4. Eathernet says

    November 12, 2014 at 10:52 am

    Thanks, worked a treat.

    Reply
    • Xtrondo says

      November 15, 2015 at 6:34 pm

      You just need do get write access again with option ~w, just check console options with ~?

      Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

Primary Sidebar

Follow UnixArena

  • Facebook
  • LinkedIn
  • Twitter

Copyright © 2025 · UnixArena ·

Go to mobile version