cancel
Showing results for 
Search instead for 
Did you mean: 

11.31 Install

SOLVED
Go to solution
Nyck_1
Super Advisor

11.31 Install

I installed 11.31 onto an Itanium rx4640 server yesterday, after 3 hours or so the install was complete. So I went to access the server remotely as root and it would not allow me to do so. So I logged in as root on the console no issue. So how do I enable 11.31 so that I can login as root remotely?

On Solaris I edit a particular file and comment out CONSOLE

Then for some daft reason I edited /etc/securetty and commented out console and now I'm unable to login period, D'oah!

Can someone put me back on track again as I do not want to reinstall this server again?
12 REPLIES
sujit kumar singh
Honored Contributor
Solution

Re: 11.31 Install

hi

reboot the server in single user mode and edit back the /etc/securetty file.


booting rx4640 in single user mode:


go to the EFI shell

Shell> fs0:
fs0:> boot hpux -is

regards
sujit
Nyck_1
Super Advisor

Re: 11.31 Install

Hello,

Once I have uncommented the console line from this file how can I login as root remotely from a different location?
Johnson Punniyalingam
Honored Contributor

Re: 11.31 Install

>>Once I have uncommented the console line from this file how can I login as root remotely from a different location?<<<<<<

Hope your server "Itanium rx4640" which you installed should have hostname or IP address

using "telnet" "ssh" you can connect remotly


if you have pc/laptop which connected to network in same LAN

start>Run>cmd> telnet

or you use "Putty" to connect the server
Problems are common to all, but attitude makes the difference
Nyck_1
Super Advisor

Re: 11.31 Install

This is the strange thing, after I had installed the server I was able to login as root on the console but if I tried to telnet from another server it would not accept the root password.
Michal Kapalka (mikap)
Honored Contributor

Re: 11.31 Install

hi,

use SSH and if you like to use root as login directly.

edit /opt/ssh/etc/sshd_config ( or other installed location )

PermitRootLogin yes ( must be enabled )

mikap
Johnson Punniyalingam
Honored Contributor

Re: 11.31 Install

>>but if I tried to telnet from another server it would not accept the root password.<<

can try ssh
Problems are common to all, but attitude makes the difference
Steven Schweda
Honored Contributor

Re: 11.31 Install

> [...] I edited /etc/securetty [...]

man login

Read first, edit later?

> On Solaris I edit a particular file [...]

Some _other_ particular file, whose contents
are different? ("/etc/default/login" and
"/etc/securetty" _are_ spelled differently.)

If you have some other user set up, then you
could try logging in as that other user, and
then "su".

> reboot the server in single user mode [...]

That may be the only way left.
Nyck_1
Super Advisor

Re: 11.31 Install

I have decided to reinstall this server again as somehow I managed to install a trusted version of 11.31 and I want to know where I went wrong. Thanks for all the excellent responses and I will sort out points later:-)
Bill Hassell
Honored Contributor

Re: 11.31 Install

/etc/securetty has NO concept of a comment. Whatever you put in that file will have /dev/ prepended to it and that will be an allowable login port. So in your case, the allowed device for root login is:

/dev/#console

which of course does not exist and no one can login as root using an HP-UX network port. To allow root logins from any port, just remove the file /etc/securetty.


Bill Hassell, sysadmin
Nyck_1
Super Advisor

Re: 11.31 Install

Well I finally got round to rebuilding the server and this time all was ok. I checked for the /etc/securetty file and this did not exist. I think what I did was to install everything by accident hence ending up with the trusted install.

Once built I noticed that LVM is a bit different, for example:-

/dev/vg00
/dev/disk/disk3_p2
/dev/vg_proj
/dev/dsk/c2t1d0


The disk used for the root volume group is disk3_p2. As you can see I created a volume group called proj and used the legacy naming convention. Is this ok?

There were no errors during the process and all seesm fine.
Michal Kapalka (mikap)
Honored Contributor

Re: 11.31 Install

hi

//
The disk used for the root volume group is disk3_p2. As you can see I created a volume group called proj and used the legacy naming convention. Is this ok?

There were no errors during the process and all seesm fine.
//

yes from config view its ok, but i would use only one type of devices, but its always on the administrator what they like to do.

mikap
Nyck_1
Super Advisor

Re: 11.31 Install

I'm happy now:-)

If and when I create additional volume groups I will use the new naming convention.