• State Suggested Answer
  • Replies 26 replies
  • Answers 2 answers
  • Subscribers 7 subscribers
  • Views 11446 views
  • Users 0 members are here
Related Discussions
Home » Discussions » General

Hi, I have the message below starting the engines. Collabo

vsebastiao
Hi,

I have the message below starting the engines.

Collaboration Statistics 1/1 FATAL! No gateway is active.
Inconsistent DBID on GW1
Server Database ID: 3673, Gateway Database ID: 0N

Process-Analytics0000 1/1 FATAL! No gateway is active.
Inconsistent DBID on GW1
Server Database ID: 378, Gateway Database ID: 0N

Process-Exec00 1/1 FATAL! No gateway is active.
Inconsistent DBID on GW1
Server Database ID: 3293, Gateway Database ID: 0N

What can I do?

Thanks.

OriginalPostID-215548

OriginalPostID-215548

  Discussion posts and replies are publicly visible

Parents
  • 0
    Thank you.

    I solved the problem by performing the steps below.
    1 - Stop the JBoss
    2 - Stop the Appian search service
    3 - Stop the Appian service windows
    4 - run the stop-suite.bat
    5 - copy the last good .kdb file and renamed to the latest file name+1 in folder (eg pe111.kdb to pe112.kdb). I made for all engines with problem.
    6 - start the Apppian service windows.
    7 - ran the checkengine.bat to confirm that all engines were ok and active.
    8 - start the Appian search service
    9 - start JBoss.
  • 0 in reply to vsebastiao
    this didn't work for me can u please suggest the solution.

    whenever I transfer KDB files all the engines stop working .
  • 0 in reply to sonamg
    I have transferred only last working KDB file in all engines with +1 name . Do I need to transfer all KDB files or only last good one ?
  • 0
    Certified Lead Developer
     in reply to sonamg

    if the old instance of Appian is working fine, last one is good...Please verify below steps once..

    1. Stop all engines for the currently running Appian suite.
    2. Navigate to old instance(which you were using before update)
    3. Start the engines and verify all engines are in OKAY status.

    If any problem here, there is an issue with your old kdbs . we need fix it by following the steps I mentioned in my previous comments.

  • 0 in reply to Rama Thummala
    The old instance of appian was not properly shutdown and we got log4j error that's y we have reinstalled the fresh appian server and after transferring the old KDBS files we are getting this error in new installation.
  • 0
    Certified Lead Developer
     in reply to sonamg

    sonamg

    What do you are planning to do now? Fresh installation or Updation.

    If fresh installation, Do it by following installation guide.

    If Updation, follow below steps.

    1. Switch back to old instance.
      • Stop Application server, search server and engines (Verify all processes are stopped by executing ps -ef , kill if any not stopped)
      • rename it to different name or delete the 'Appian' folder.
      • Rename your old instance to 'Appian'
    2. Start Appian engines (now you are running old instance)
      • Make sure all engines are started with 'Okay' status(If any FATAL error follow steps I have mentioned earlier)
      • Run check point script and followed by clean up script
    3. Start Search server
    4. Start Application server, make sure suite.ear is successfully deployed and you are able to login
    5. Stop the suite(Stop Application server, Search server and engines and Verify all processes are stopped)
    6. Now either do the fresh installation of your required version
    7. If you are updating follow the update guide.
  • 0 in reply to Rama Thummala
    ramanjaneyulut

    We did fresh installation by following the installation guide. The "suite.ear" also had deployed successfully. Everything's fine. It's only after transferring the KDB files, 12 out of 15 gateways are inactive.

    We tried to repair and rename the KDB files. There was no change.

    What can we do now ?
  • 0
    Certified Lead Developer
     in reply to sonamg

    We have to do either repair or rename only.

    The problem is with your old instance. First you need fix that issue, then only you can do the update.So before going for fresh installation first fix the issue with old kdb files either by following my instruction in earlier comment or by raising support ticket.

    I would suggest you contact Appian support, so you could get better help. Below are the contact details.

    Email: support@appian.com

    Call:

    United States: +1 703 442 1066          

    United Kingdom: +44 20 3695 0246

    France: +33 184 886 650    

    Australia: +61 285 203 042

  • 0 in reply to Rama Thummala

    ramanjaneyulut,

    I'd raised the ticket and mailed the support team.

    We have checked in the task manager for engines which are inactive. It is showing the below error(screenshot attached):

     

  • 0
    A Score Level 2
     in reply to Rama Thummala
    @sonamg - Can you please check the kdb files available in all the folders in new Appian installation. Ideally there should be only one kdb file after upgrade steps are finished. For e.g. If old Appian kdb number is 15 then there must not be a kdb in new installation with version number 1. We had faced this kind of issue previously. We reinstalled Appian and upgraded before starting Appian engines. Hope this helps.
  • 0 in reply to sagarl511
    we have 3 KDBs files in each folder after installing the server again and starting the checkengine but we want to transfer old kdb files from previous version for recovering the data. After transferring old KDB files Engines stop working.
  • 0
    A Score Level 2
     in reply to sonamg
    Have you performed following steps -
    1) Install fresh Appian and do not start Appian engines yet
    2) Copy the latest kdb from each folder as mentioned in Migration procedure.
    3) Now start Appian engines and see if it is working.

    Another diagnostic if above does not work.
    1) See the latest version number of kdbs in folder in old installation
    2) Perform checkpoint on old Appian version and now see if version number is increased. If not increased then there is issue with your old server.
Reply
  • 0
    A Score Level 2
     in reply to sonamg
    Have you performed following steps -
    1) Install fresh Appian and do not start Appian engines yet
    2) Copy the latest kdb from each folder as mentioned in Migration procedure.
    3) Now start Appian engines and see if it is working.

    Another diagnostic if above does not work.
    1) See the latest version number of kdbs in folder in old installation
    2) Perform checkpoint on old Appian version and now see if version number is increased. If not increased then there is issue with your old server.
Children
No Data
© 2024 Appian. All rights reserved.
We want to hear from you! Submit a review on Gartner or G2.