Stats

  • Locked Locked
  • Replies 2
  • Subscribers 126
  • Views 2579
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Error running DRC on Assura - "The Assura DRC Run Failed"

fanelli

Hello,

I've recently installed the Cadence software in my institution's computer, I'm running IC6.1.7 on a CentOS 7. When I tried using the Assura package (ASSURA41) for a DRC run , it failed. The Log ends with this message: 

Running in restart mode.

*WARNING* m2connect fd 6, 1 tries, errno 113 No route to host
*WARNING* Failed to connect to frmpsd on mentorlabge2. Success.
*WARNING* Failed to append to the database.


*****  aveng terminated abnormally  *****



*****  aveng fork terminated abnormally  *****


*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

Perhaps I should note that "mentorlabge2" is the Computer's name. I'm using the PVS license to run Assura.

I've looked in several different forum posts and also in the documentation on the support website but couldn't find a similar problem...

I'm not sure what the error means so I don't even know how to begin troubleshooting this...

The full Log message is attached below.

Fullscreen log_assura.txt Download 
  Assura (R) Physical Verification Version av4.1:Production:dfII6.1.7-64b:IC6.1.7-64b.500.4
            Release 4.1_USR5_HF11

Copyright (c) Cadence Design Systems. All rights reserved.
@(#)$CDS: assura_64 version av4.1:Production:dfII6.1.7-64b:IC6.1.7-64b.500.4 07/10/2017 21:38 (sjfnl321) $
sub-version 4.1_USR5_HF11, integ signature 2017-07-10-2113

run on mentorlabge2 from /home/labge/cadence/installs/ASSURA41/tools.lnx86/assura/bin/64bit/assura on Wed Sep  6 17:14:00 2017


Starting /home/labge/cadence/installs/ASSURA41//tools.lnx86/assura/bin/aveng /home/labge/Work/tsmc/Assura/x.rsf -restart -cdslib /home/labge/Work/tsmc/cds.lib
@(#)$CDS: aveng_64 version av4.1:Production:dfII6.1.7-64b:IC6.1.7-64b.500.4 07/10/2017 21:38 (sjfnl321) $
sub-version 4.1_USR5_HF11, integ signature 2017-07-10-2113

run on mentorlabge2 from /home/labge/cadence/installs/ASSURA41/tools.lnx86/assura/bin/64bit/aveng on Wed Sep  6 17:14:00 2017


Loading tech rule set file : /home/labge/Work/tsmc/Assura/techRuleSets

Loading tech rule set file : /home/labge/Work/tsmc/Assura/techRuleSets

Loading tech rule set file : /home/labge/Work/tsmc/Assura/techRuleSets

Loading tech rule set file : /home/labge/Work/tsmc/Assura/techRuleSets

Loading tech rule set file : /home/labge/Work/tsmc/Assura/techRuleSets
 Summary Report: x.sum
 RSF           : /home/labge/Work/tsmc/Assura/x.rsf
 Library Name  : test
 CDSLIB Path   : "/home/labge/Work/tsmc/cds.lib"
 Cell Name     : inversor
 View Name     : layout
 Rules File    : /home/labge/Work/tsmc/Assura/./drc/assura.drc
 Options       : -restart -cdslib /home/labge/Work/tsmc/cds.lib
 Work Directory: /home/labge/Work/tsmc/Assura
 Operating Mode: Legacy Mode is Off

Checking out 2 licenses for Phys_Ver_Sys_DRC_XL
Restarting with VDB Build 2

Building the VDB part 2 in background mode.

Executing: chip = cellBoundary(root)

Building the VDB part 3 in background mode.


Running in restart mode.

*WARNING* m2connect fd 6, 1 tries, errno 113 No route to host
*WARNING* Failed to connect to frmpsd on mentorlabge2. Success.
*WARNING* Failed to append to the database.


*****  aveng terminated abnormally  *****



*****  aveng fork terminated abnormally  *****


*WARNING* aveng exit with bad status
*WARNING* Status 256
*WARNING* Assura execution terminated

Thanks in advance!

Gabriel Fanelli

  • Andrew Beckett

    It's a little odd that the message is referring to frmpsd because that is an executable that was removed something like 6 years ago. I've not found anything reporting the message as you describe it - so you'll probably need to go via your support channel. If you're from a European University, that would be Europractice...

    Note that CentOS 7 (or even RHEL7) is not supported for Assura - maybe that's the reason? The other problem might be that there's something wrong with the set up of the machine so it can't find itself - what is in /etc/hosts ?

    Regards,

    Andrew.

  • fanelli
    Hi Andrew,
    You nailed it! I edited the /etc/hosts file and it worked! The file contained references to two machines which I believe were once used with a fixed IP configuration.
    I commented both lines and that made the trick:
    #192.168.129.207 mentorlabge2 mentorlabge2
    #192.168.128.205 mentorlabge1 mentorlabge1

    Thank you very much for your help!
    Best regards,

    Gabriel Fanelli

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.