Don't know if anyone has picked up on this but the swinst lock-up issue seems to be linked to the embedded 4645 issue.
If (when the swinst script locks up) you look in the process list you will see the UMOUNT command consuming all of cpu's resources.
If you are in via telnet then you can leave the first swinst session running and launch another which in the times that I have done so has worked.
Swinst locked or does not load with easy and expert options
- Krusty65
- Alcatel Unleashed Certified Guru

- Posts: 242
- Joined: 26 Sep 2007 13:30
- Location: Normally in a comms room
Re: Swinst locked or does not load with easy and expert options
When I was a boy of fourteen, my father was so ignorant I could hardly stand to have the old man around.
But when I got to be twenty-one, I was astonished at how much the old man had learned in seven years.
But when I got to be twenty-one, I was astonished at how much the old man had learned in seven years.
-
krzysioD
Re: Swinst locked or does not load with easy and expert options
Try:
ps -auxwwww
under linux to see full process list with wrapped command lines, if you see:
umount /dev/hdX ...
Then you know which partition is being un-mounterd.
Kill the umount & swinst login, then try to umount this partion as root.
It could be used by VM application, or it could have some errors (in filesystem, need to be fsck'ed like scandisk/chkdsk, or on harddrive, then you will need to replace faulty hdd).
Had some error when OXE was working, but every disk writing like "immed backup" caused hangups, it was fault of hdd.
ps -auxwwww
under linux to see full process list with wrapped command lines, if you see:
umount /dev/hdX ...
Then you know which partition is being un-mounterd.
Kill the umount & swinst login, then try to umount this partion as root.
It could be used by VM application, or it could have some errors (in filesystem, need to be fsck'ed like scandisk/chkdsk, or on harddrive, then you will need to replace faulty hdd).
Had some error when OXE was working, but every disk writing like "immed backup" caused hangups, it was fault of hdd.
-
BILLY_SHAW
Re: Swinst locked or does not load with easy and expert options
Hi, i am new here but also facing this similer swinst problem.
my OXE is v8 with 4645 voice. when tried using swinst over telnet, the 4645 voice recording quality is unhearable. checked the ps and found 'umount \root2_d', tried to kill 9 pid, not working, finally have to reboot OXE.
another experience is also over telnet login as swinst, the screen stay for more than 2 hours to respond and the 4645 recording unhearable.
my tech serive company said it a bug in v8, alcatel is fixing this now. they also mentioned some tc/ta#, can remember.
so bad experience on alcatel PABX.
my OXE is v8 with 4645 voice. when tried using swinst over telnet, the 4645 voice recording quality is unhearable. checked the ps and found 'umount \root2_d', tried to kill 9 pid, not working, finally have to reboot OXE.
another experience is also over telnet login as swinst, the screen stay for more than 2 hours to respond and the 4645 recording unhearable.
my tech serive company said it a bug in v8, alcatel is fixing this now. they also mentioned some tc/ta#, can remember.
so bad experience on alcatel PABX.
-
cavagnaro
Re: Swinst locked or does not load with easy and expert options
Things with new releases are "common" however once software reaches a mature process everything goes fine.
Re: Swinst locked or does not load with easy and expert options
Another way of solving this issue has been by entering the following on the command line:
su swinst
(swinst password) then
exit
swinst
(swinst password)
And this has allowed to access the swinst menu options.
su swinst
(swinst password) then
exit
swinst
(swinst password)
And this has allowed to access the swinst menu options.
SWINSTU
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
ACSE OXE R12.1
ACSE 8770 R3.2(4760 R5.x)
ACSE OT R2.3 IP/SIP and UC&C
-
Eliott_DUP
Re: Swinst locked or does not load with easy and expert options
SometimeskrzysioD wrote: it was fault of hdd.
smartctl -e /dev/hda
smartctl -a /dev/hda
can give an idea.
