AnsweredAssumed Answered

Initialization Status after G&L V7.0.1 installation

Question asked by Karine Slkuni

on Feb 23, 2017
Latest reply on Feb 28, 2017 by Karine Slkuni

Like • Show 0 Likes0
Comment • 5

Hi All,

Our customer completed the RSA IG&L V7.0.1 installation:

[root@RMSV-LVLGAS01 ~]# /etc/init.d/aveksa_server status

5375

RSA Identity Governance and Lifecycle is running

But when tried to access G&L GUI, the following error is displayed:

After system reboot customer received the following error:

[root@RMSV-LVLGAS01 bin]# /etc/init.d/aveksa_server start

2175

Cannot connect to the database. The watchdog will start the server when it can connect to the database.

Any idea what could be the reason?

Thanks,

Karine

Edwin Mullie

Feb 24, 2017 3:21 AM

Correct Answer

Karine,

the aveksaserver.log that you send says:

2/23/2017 08:21:28.373 ERROR (MSC service thread 1-1) [com.aveksa.migration.jdbctool.CheckDatabase] Error reading Aveksa_System.cfg
java.io.IOException: Permission denied

please check the permission of that Aveksa_System.cfg

Edwin

See the reply in context

Attachments

aveksaServer.log.zip3.8 KB

No one else had this question

Outcomes

5 Replies

Sean Miller Feb 23, 2017 12:25 PM
Mark Correct
Correct Answer
What does the complete stack trace look like in the aveksaServer.log ?

Sean Miller | Senior Manager, Software Engineering | RSA
O: (519) 954 8162
RSA Identity Governance and Lifecycle Community: https://community.rsa.com/community/products/governance-and-lifecycle
Attachments
- image001.png13.1 KB
Like • Show 0 Likes0
Actions
- Karine Slkuni @ Sean Miller on Feb 23, 2017 12:30 PM
  Mark Correct
  Correct Answer
  Hi Sean,
  
  I requested aveksaServer.log from customer and will attach as soon as I receive it.
  
  Thank you for your help,
  Karine
  
  Karine Slkuni | Senior Consultant – RSA Idenitity Governance & Lifecycle | EMEA Professional Services| Am Kronberger Hang 2A | 65824 Schwalbach/Ts. | Germany
  Mobile: +49 (0) 151 23 62 50 49 | karine.slkuni@rsa.com<mailto:karine.slkuni@rsa.com>| CET Time Zone
  IMG Community: https://community.rsa.com/community/products/governance-and-lifecycle/client-partner-community
  <https://community.rsa.com/community/training/governance-and-lifecycle>
  Attachments
  - image002.png108.0 KB
  - image001.jpg1.0 KB
  Like • Show 0 Likes0
  Actions
- Karine Slkuni @ Sean Miller on Feb 23, 2017 1:19 PM
  Mark Correct
  Correct Answer
  Hi Sean,
  
  after system reboot customer received the following error
  # /etc/init.d/aveksa_server start
  2175
  Cannot connect to the database. The watchdog will start the server when it can connect to the database.
  
  I also asked them to verify:
  AVUSER permission: ANALYZE ANY missing.
  AVSDWUSER permission: CREATE PROCEDURE missing.
  AVSDWUSER permission: CREATE SESSION missing.
  
  Any ideas?
  Thank you and
  Kind regards,
  Karine
  
  Karine Slkuni | Senior Consultant – RSA Idenitity Governance & Lifecycle | EMEA Professional Services| Am Kronberger Hang 2A | 65824 Schwalbach/Ts. | Germany
  Mobile: +49 (0) 151 23 62 50 49 | karine.slkuni@rsa.com<mailto:karine.slkuni@rsa.com>| CET Time Zone
  IMG Community: https://community.rsa.com/community/products/governance-and-lifecycle/client-partner-community
  <https://community.rsa.com/community/training/governance-and-lifecycle>
  Attachments
  - image002.png108.0 KB
  - image001.jpg1.0 KB
  Like • Show 0 Likes0
  Actions
  - Edwin Mullie @ Karine Slkuni on Feb 24, 2017 3:21 AM
    Unmark Correct
    Correct Answer
    Karine,
    
    the aveksaserver.log that you send says:
    2/23/2017 08:21:28.373 ERROR (MSC service thread 1-1) [com.aveksa.migration.jdbctool.CheckDatabase] Error reading Aveksa_System.cfg
    java.io.IOException: Permission denied
    
    please check the permission of that Aveksa_System.cfg
    
    Edwin
    Like • Show 1 Like1
    Actions
Karine Slkuni Feb 28, 2017 8:11 AM
Mark Correct
Correct Answer
To resolve the issue added the following 2 lines to the .bash_profile in the /root:
cd /root
vi .bash_profile

### Added:
. ./setDeployEnv.sh
umask 022

Save and start acm:
acm start

RSA Identity Governance and Lifecycle is running.

Thank you, Edwin!
Like • Show 0 Likes0
Actions

Initialization Status after G&L V7.0.1 installation

Attachments

Outcomes

Attachments

Attachments

Attachments

Related Content

Recommended Content