while connectiong
on OXE through telnet with mtcl
here is the message i got
Welcome to XXXX_Alcatel
Linux Mandrake for eMediate release 7.2 (Odyssey) for i486
Kernel 2.4.1-ll-dhs3 on an i486
login: mtcl
Password:
Last login: Tue Jan 15 11:35:38 from 172.16.0.53
Alcatel OmniPCX Enterprise 6.0
standard installation last performed: 21-Nov-2005 02:06:32
No directory /DHS3bin/mtcl!
Logging in with home = "/".
There is a crash dump on /dev/crashdump, date: 2005/11/03 13:40:48
bash: /DHS3bin/mtcl/.bash_profile: Not a directory
bash-2.04$
i cant be connected
how to FIX THIS and what is it
Thanks
HELP mtcl connecting
Re: HELP mtcl connecting
Crash dump is bad, means your system abruptly stopped. You have some corruption due to this, you are missing pertinent directories. I would reload software and load the last good known database.
Re: HELP mtcl connecting
thanx for your response,
but can u tell me how i can reload the software
and database.
another thing is that the system is still working call are made as usual,
except some capricious behaviour of the system.
Thanx
but can u tell me how i can reload the software
and database.
another thing is that the system is still working call are made as usual,
except some capricious behaviour of the system.
Thanx
Re: HELP mtcl connecting
To load the linux follow the documentation. I would recommend to do this by a trained personnel.
- frank
- Alcatel Unleashed Certified Guru
- Posts: 3355
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
Re: HELP mtcl connecting
As a quick fix..
Login as mtcl (edit by cavagnaro: No passwords allowed
Frank?!
)
and give me the informations for /usr2 by doing:
(8123)xa081023> cd /usr2
(8123)xa081023> l
total 116
drwxr-xr-x 25 root root 4096 Dec 6 15:43 .
drwxr-xr-x 26 root root 4096 Jan 11 23:29 ..
drwxrwxr-x 5 root other 4096 Dec 6 15:43 PKG
drwxrwxr-x 2 adfexc tel 4096 Dec 6 15:43 adfexc
drwxrwxr-x 2 root tel 4096 Dec 6 15:47 afe
drwxrwxr-x 2 mtcl other 4096 Dec 6 15:43 client
drwxr-xr-x 2 root tel 4096 Dec 6 15:44 com
drwxr-xr-x 3 root tel 4096 Dec 6 15:47 cpu_tools
drwxr-xr-x 2 root tel 4096 Dec 6 15:50 descript
drwxr-xr-x 6 root tel 4096 Dec 6 15:50 downbin
drwxr-xr-x 2 root root 4096 Dec 6 15:43 emulation
drwxr-xr-x 2 root tel 8192 Dec 6 15:50 fab
drwxr-xr-x 2 mtcl tel 4096 Dec 6 15:47 incid
drwxr-xr-x 2 root tel 4096 Dec 6 15:43 io2
drwxr-xr-x 3 root root 4096 Dec 6 15:49 lib
drwxr-xr-x 2 root root 16384 Nov 6 1903 lost+found
drwxrwxr-x 4 mtcl other 4096 Jan 20 11:31 mtcl
drwxr-xr-x 4 mtcl tel 4096 Dec 6 15:44 nmc
drwxr-xr-x 3 root tel 4096 Dec 6 15:43 oneshot
drwxr-xr-x 2 mtcl tel 4096 Dec 8 15:38 patches
drwxr-xr-x 2 mtcl tel 4096 Dec 6 15:43 rpm
drwxr-xr-x 2 root tel 4096 Dec 6 15:50 servers
drwxrwxrwx 4 root other 4096 Dec 8 15:33 soft_install
drwxr-xr-x 2 root tel 4096 Dec 6 15:49 tel
drwxr-xr-x 2 root tel 4096 Dec 6 15:47 x25
you should see a mtcl folder in here.
if you don't, su to root by doing su - , enter the password, then do
mkdir /usr2/mtcl
chown mtcl.other /usr2/mtcl
exit
exit
and try to login again...
After that, we have to work on your partitions that migt be fucked up
Login as mtcl (edit by cavagnaro: No passwords allowed


and give me the informations for /usr2 by doing:
(8123)xa081023> cd /usr2
(8123)xa081023> l
total 116
drwxr-xr-x 25 root root 4096 Dec 6 15:43 .
drwxr-xr-x 26 root root 4096 Jan 11 23:29 ..
drwxrwxr-x 5 root other 4096 Dec 6 15:43 PKG
drwxrwxr-x 2 adfexc tel 4096 Dec 6 15:43 adfexc
drwxrwxr-x 2 root tel 4096 Dec 6 15:47 afe
drwxrwxr-x 2 mtcl other 4096 Dec 6 15:43 client
drwxr-xr-x 2 root tel 4096 Dec 6 15:44 com
drwxr-xr-x 3 root tel 4096 Dec 6 15:47 cpu_tools
drwxr-xr-x 2 root tel 4096 Dec 6 15:50 descript
drwxr-xr-x 6 root tel 4096 Dec 6 15:50 downbin
drwxr-xr-x 2 root root 4096 Dec 6 15:43 emulation
drwxr-xr-x 2 root tel 8192 Dec 6 15:50 fab
drwxr-xr-x 2 mtcl tel 4096 Dec 6 15:47 incid
drwxr-xr-x 2 root tel 4096 Dec 6 15:43 io2
drwxr-xr-x 3 root root 4096 Dec 6 15:49 lib
drwxr-xr-x 2 root root 16384 Nov 6 1903 lost+found
drwxrwxr-x 4 mtcl other 4096 Jan 20 11:31 mtcl
drwxr-xr-x 4 mtcl tel 4096 Dec 6 15:44 nmc
drwxr-xr-x 3 root tel 4096 Dec 6 15:43 oneshot
drwxr-xr-x 2 mtcl tel 4096 Dec 8 15:38 patches
drwxr-xr-x 2 mtcl tel 4096 Dec 6 15:43 rpm
drwxr-xr-x 2 root tel 4096 Dec 6 15:50 servers
drwxrwxrwx 4 root other 4096 Dec 8 15:33 soft_install
drwxr-xr-x 2 root tel 4096 Dec 6 15:49 tel
drwxr-xr-x 2 root tel 4096 Dec 6 15:47 x25
you should see a mtcl folder in here.
if you don't, su to root by doing su - , enter the password, then do
mkdir /usr2/mtcl
chown mtcl.other /usr2/mtcl
exit
exit
and try to login again...
After that, we have to work on your partitions that migt be fucked up
Code Free Or Die
Re: HELP mtcl connecting
So, the moral of the story here is - when someone is in real deep shit... send a post to Ihthisham because his response was the best one
Frank did not even get a thank you for all his trouble!
I disappear for a few weeks and all hell breaks loose!
So much so, that someone else even tries to steal my avatar! BRING BACK THAT MASK OR ELSE! 

Frank did not even get a thank you for all his trouble!

I disappear for a few weeks and all hell breaks loose!

