system files

[Cordell Robinson_2]

I moved some system files over as a tar file. Then untarred them. I rebooted the machine and now I cannot login at the console...

[RAC_1]

what files you moved?? what files you tarred?? More details required.

[Cordell Robinson_2]

patches, products, hosts fies, tcb files, usr/home file

[Ken Penland_1]

what kind of error message are you getting? login incorrect or something?

[Cordell Robinson_2]

When I login at the console, it just goes back to login promt no error message or anything.

[John Kittel]

perhaps too obvious, but if you moved the tcb, if the account you're trying to log in with had different passwords on the two systems, you'll need to use the password from the system you moved from...

[Ken Penland_1]

Okay, as I understand it, you have a system that you tarred up a bunch of stuff such as /tcb/files/auth, /var/adm/sw, and the like, and copied it over to another box, untarred it, and now you cannot log on...is that correct?
there could be a lot of issues here, what sticks out in my mind is if the system you copied from was a trusted system, but you untarred on an untrusted system, then it would consider every account LOCKED. you would need to boot to single user mode, change roots password, and then boot back up, and do a tsconvert if that were the case

[Cordell Robinson_2]

I did that via telnet to the system. I can login via telnet with any account that I have but at the console none of the accounts work.

[Ken Penland_1]

what is in your /etc/securetty file?

[Cordell Robinson_2]

ok the securetty file was not transfered over, that must be the issue.

[Cordell Robinson_2]

I moved the securetty file over and that did not do the trick.

[Ken Penland_1 · Accepted solution]

well, the only other thing I can think of is to null out utmp and reboot, perhaps that is corrupt..*shrug*

[TwoProc]

Get the /etc/gettydefs file from the other machine and put it on the dest machine. I think that your getty ain't getting it...
:-)

[MarkSyder]

I think this might be an appropriate time to ask if you have an ignite backup of the system.

Mark Syder (like the drink but spelt different)

[Cordell Robinson_2]

yes I do have an ignite backup and will probably have to go that route, then sift through the tar files I created to se what the issue is.

[Bill Hassell]

Moving some selected system files over to another system will almost always cause major problems. Let's start with the hardware...are the two boxes the same model, I/O layout and opsystem version? If not, you'll have major problems. Did you move the /var/adm/sw directory? If so, you'll have major problems because the sw directory documents what is currently patched on the system (including the kernel) and this is not the case. Did you move everything in /etc? Major, major problems as there are several binary files that map the physical I/O and LVM tables. The /tcb directory can be moved but *MUST* have the original /etc/passwd and /etc/group moved too, along with all the home directories for the users.

As mentioned, if you need to make a duplicate system, use Ignite/UX which can handle all the differences in the hardware and configurations.

[Cordell Robinson_2]

The two boxes are identicle. I did not move /var/adm/sw but I did move over products ie tcpwrappers, iq, secureshell. When I untarred the files they do not install unless I run a script. The only script I ran was a patch script which installs all of the necessary patches.