console login: tmchild: exec service failed

the machine can startup normally , but when telnet or logon from  the console.It failed.
when logon from the console :

HOSTNAME console login: root
tmchild: exec service failed, errno = 13

but the ftp service work ok!

then i used
{1}OK boot disk -s
to start the system, i can logon on normally,

all slice can mount normally,no slice is full

what can i do then ?please give me your advice!
Who is Participating?
moduloConnect With a Mentor Commented:
PAQed with no points refunded (of 350)

Community Support Moderator
root telnet remote login is disable by default!

have a look at /etc/default/login file, you should see:
# If CONSOLE is set, root can only login on that device.
# Comment this line out to allow remote login by root.

If you comment it out, root can telnet login (warning, not secure, consider use
secure shell instead). you can get openssh from:

Now, get back to your question, can you login as a normal user to the system?
can a normal user "su" as root?

Can you login as root from the REAL console screen (NOT remote).

check /var/adm/messages file to see any errors. has anyone make any change to
your system?(change system config files, install software etc).
I think he said he was trying to login as "root" from the actual system console.
Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.


   Is it a Solaris 8 system? If yes, please check the patch 111041-04

(1) In /etc/default/kbd, set "KEYBOARD_ABORT=alternate"
(2) In /etc/system, "set abort_enable=2"
(3) reboot

Good luck,

>  failed, errno = 13

you have a permission problem somewhere
Check if you homedir has propper permissions for that user (read, execute)
Probably there is something in your shell's startup files which causes the permission violation
Considering this is root -- it's hard to imagine root getting a permission issue during login.

So this sorta sounds like root is attempting to login but there is a secondary process trying to run during the login cycle but its running as non-root.  What I can't say ... never dug into the login process that deeply.

Did this just start happening recently ?

What changes have been made the system recently ?
some kind of attack affect the telnet or login, this attack may changed your /etc/inetd.conf to other one.

try this
1-          check if there is an output to this cmd:
              /usr/ucb/ps -aux | grep srload
2-          see the last line of inittab if it contains srload:
               more /etc/inittab | grep srload
3-          check also /etc/init.d/rootusr for srload

if one or more of these items are true, just remove the system from the network and reply to me (to continue); this means that you are under attack.
According to SunSolve, this is casued by "su driver alternate break capability" on "break signal" (Ctrl+b) issue.
You may need to apply the patch or two setting as I mentioned above.

martinbjleeAuthor Commented:
   the system is solaris 7,
   i can't find the patch for such error.
   cause the ftp can still work , i upload some ssh install pkg , in the single user mode
  i install the ssh and now i can  logon use ssh.
  in the message i found such message:
   Oct 26 12:13:59 Wireless unix: fd0 is /pci@1f,4000/ebus@1/fdthree@14,3023f0
   Oct 26 12:16:58 Wireless unix: WARNING: interrupt level 6 not serviced
   Oct 26 14:25:37 Wireless unix: panic[cpu3]/thread=2a1001b1d60:
   Oct 26 14:25:38 Wireless unix: WARNING: interrupt level 6 not serviced

  i  use the CMD /usr/ucb/ps -aux | grep srload , and more /etc/init.d/rootusr | grep srload               nothing find out.

   what's the meaning of    "interrupt level 6 not serviced"
Is this box your own or a box you support at work ?

If this is a box you own, upgrade the box to Solaris 9 or even Solaris 10.

If this is a server at work, you should have a serious discussion with your management about upgrading this server to Solaris 9.
IIRC Solaris 7 had a very short lifetime 'cause of tooooo much trouble ...
Solaris 7 is definitely EOLed. Oldest still-supported version is Solaris 8.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.