Page 3 of 4

Re: Eva_tool error

Posted: 12 Aug 2011 10:20
by airwolf
After 2 reboots the problem is resolved

Re: Eva_tool error

Posted: 12 Aug 2011 18:06
by swinstu
It will come back so a permanent solution is needed

Re: Eva_tool error

Posted: 15 Aug 2011 01:39
by Eliott
swinstu wrote:It will come back so a permanent solution is needed
I didn't found the root cause. It disappeared after a reboot so I've not opened an eSR.
The binary files were okay (checked the md5) - seems to be a problem in the memory.

Re: Eva_tool error

Posted: 15 Aug 2011 02:01
by swinstu
Elliot,

I have seen it on 3 seperate sites, 1 BICs install and 1 Appliance Server and 1 common hardware site. All issues were resolved on mine aswell after reboots. In some cases 2 reboots. Issue came back at 2 sites after sometime but ran same process and havent heard from client since. Advised if issue will reoccur then will log an eSR myself.

Thanks for the update :)

Re: Eva_tool error

Posted: 15 Aug 2011 02:06
by Eliott
swinstu wrote:if issue will reoccur then will log an eSR myself.
Ok, let my know the eSR number and answer/solution, please.

For me it happens in R7.0 f4.401.24 in Jan 2010 - so I can not open an eSR (phase out).

Code: Select all

(1)xa000000> Eva_tool
Grammar error

===========================
    LIBC caught SIGSEGV  in 9606
===========================
Registers:
  EFLAGS = 0x00010282
  EAX    = 0x0000000e
  EDX    = 0x0000000e
  EIP    = 0x08071148
  EDI    = 0x08071148
  ESI    = 0x0808214b
  EBP    = 0xbffffba0
  EBX    = 0x33333333
  ECX    = 0x0807ee80

Backtrace :
Backtrace recurence:  0  pc:0x08071148 ebp:0xbffffba0
Backtrace recurence:  1  pc:0x08071877 ebp:0xbffffbb0
Backtrace recurence:  2  pc:0x08071687 ebp:0xbffffbc0
Backtrace recurence:  3  pc:0x0807165e ebp:0xbffffbd4
Backtrace recurence:  4  pc:0x08066bc7 ebp:0xbffffbf0
Backtrace recurence:  5  pc:0x08066bf8 ebp:0xbffffc0c
Backtrace recurence:  6  pc:0x4002d5a0 ebp:0xbffffc48
Backtrace recurence:  7  pc:0x08062986 ebp:0x00000000

Re: Eva_tool error

Posted: 15 Aug 2011 02:39
by swinstu
No problem I will update in future :)

Re: Eva_tool error

Posted: 06 Mar 2012 06:11
by abhishekawasthi_12
Hello ,

May you ellaborate on the Eva_tool Format & retore option as I am also facing the same issue at one of my Customer end.

Which backup do I need to take before the activity.Please suggest.


Regards
Abhishek A.

Re: Eva_tool error

Posted: 08 Mar 2012 23:13
by swinstu
Run backup on 4645. File names - eva or eva-msg depending on your preference.

Re: Eva_tool error

Posted: 29 Mar 2012 11:40
by cabelghost
Hi had the same problem, this is the answer from alcatel:


Hi Heiko,

This is in reference to the issues with getting backtraces Eva tool running.

Thank you for your update.

I have tried to reach you but was not successful.

As per our analysis we found that issue may be due to the corrupted Eva_tool.dct file in the OXE. This issue can be resolve by replacing the corrupted Eva_tool.dct and Eva tool file with a new Eva_tool.dct and Eva tool file.


1. Login to system via root. , remove the existing Eva_tool.dct and Eva_tool FILE from /usr2/oneshot/mtcl and /usr2/servers respectively.
2. Do ftp to the oxe using Swinst login and transfer the new files to the following location (FTP to the system using Swinst user id and password. Transfer the new Eva_tool.dct and Eva_tool.)

Locations of the file:
Eva_tool ( /usr2/servers)
Eva_tool.dct ( /usr2/oneshot/mtcl)

3. Then login to root and give the rights as chmod 755 file name.
Example:
[root@xa000000 servers]# cd /usr2/servers/
[root@xa000000 servers]# chmod 755 Eva_tool
[root@xa000000 servers]# cd /usr2/oneshot/mtcl/
[root@xa000000 mtcl]# chmod 755 Eva_tool.dct

Note: After this operation, re-boot of OXE is mandatory to take the changes in to account.

Please do the suggested in the site and update me your feedback.

Please feel free to contact me if you have any further issues. I will be waiting for your update.


I send you the tool, when you send me a e-mail baeuerle@cpls.de

best regards :-)

Re: Eva_tool error

Posted: 05 Jun 2012 08:36
by Tha Tawa'S
Hi,
Did you did it ?
Did the process resolved your issue ? Ans last question, Is it a final solution or will it be corrected into a future patch ?
Bye.