I am trying to install Appian 7.9 on WAS. getting below error. Can some one help

somnathg over 10 years ago

I am trying to install Appian 7.9 on WAS. getting below error. Can some one help me to understand where is the missing piece?

om.appiancorp.kougar.services.KougarServiceInvocationHandler - Error getting credentials for Administrator
com.appiancorp.kougar.driver.exceptions.SafeRetryException: Unable to acquire a Read connection. Safe to retry.
at com.appiancorp.kougar.driver.pooling.concurrent.Semaphore.acquireConnection(Semaphore.java:436)
at com.appiancorp.kougar.driver.pooling.concurrent.ConcurrentPools.getReadConnection(ConcurrentPools.java:140)
at com.appiancorp.kougar.driver.pooling.PoolManager.getReadConnection(PoolManager.java:313)
at com.appiancorp.kougar.driver.KougarConnection.getConnection(KougarConnection.java:140)
at com.appiancorp.kougar.driver.KougarConnection.call(KougarConnection.java:207)
at com.appiancorp.kougar.mapper.M...

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 9 years ago

Change the ownership of all files in <APPIAN_HOME> to the right user.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aneeshv713 over 9 years ago

I changed ownership back to root for all files within <APPIAN_HOME>.. But still only 7 engines started. 9 did not.. Any reason why?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

1. Run stop-suite.sh
2. Make sure all k processes shutdown
3. Kill -9 those who remain alive if not using CPU
4. Verify the ownership remains the right way
5. Start again
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aneeshv713 over 9 years ago

Nopes.. I tried the steps.. The 9 engines do not start.. Any idea?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

In a Linux environment you can figure out why they are not starting by looking at the corresponding:

gw-*.log

For example, if EXEC00 is not starting, simply open

gw-process-execution0.log

to see the boot-up process and determine the root cause
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aneeshv713 over 9 years ago

I see many files with PX021_20150708235931_write_to_disk_failure.l
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

Try my suggestion above and see if you have more recent write_to_disk_failure.l files (these were from when the account didn't have privileges to write to the engine database files *.kdb)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aneeshv713 over 9 years ago

Here you are:-

Primary is ready.
("pe10.kdb"
`write_to_disk_failure
"Failed to append transaction to DB (\\"pe10.kdb: Bad file descriptor\\")"
2
-614835607
.((`MG;;)
(`AG;;)
(`UT;;)
(`U;;)
(`GUG;;)
(`LOCALE;;)
(`TZID;;)
(`TSP;;))
(`.a.p.PROCESS.i.firstFireTransaction_eidb
(0;`EXEC00)))
Loading pe10.kdb at 2015-07-08 20:19:53.196.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 aneeshv713 over 9 years ago

Also, Booting pe from '/hosting/products/appian/server/process/exec/':

No transactions for replay
0 (100%) replayed in 50.685s
bind: Address already in use
Booted.
bind: Address already in use
Booted.
bind: Address already in use
Booted.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 9 years ago

Not sure which is the most recent entry but:

1. "Address already in use" means there was still a k process running when you started the engines
2. The "Bad file descriptor" was related to the lack of permissions

It seems this is a new installation, isn't it? If that's the case, simply re-install
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel