Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
37 replies
Subscribers
8 subscribers
Views
13519 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
I am trying to install Appian 7.9 on WAS. getting below error. Can some one help
somnathg
over 9 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...
OriginalPostID-153183
OriginalPostID-153183
Discussion posts and replies are publicly visible
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Ah that means that is not a k process using the port, but something else, or the port might be blocked.
By default Appian will use from port 5000 to 5031. It seems that these ports are in use by other application or blocked by the firewall
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aneeshv713
over 9 years ago
How do we check if those ports are being utilized by some other application?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aneeshv713
over 9 years ago
These two commands give me no output:-
netstat -nlp|grep 5030
fuser 5030/tcp
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aneeshv713
over 9 years ago
And, I see this in the logs.
[root@lcdrs0dceaps2i appian]# ls -l /proc/5879/exe
lrwxrwxrwx 1 root root 0 Jul 9 00:29 /proc/5879/exe -> /hosting/products/appian/server/_bin/k/linux64/k
[root@lcdrs0dceaps2i appian]# netstat -nlp|grep 5039
[root@lcdrs0dceaps2i appian]# netstat -nlp|grep 5029
tcp 0 0 0.0.0.0:5029 0.0.0.0:* LISTEN 8855/k
[root@lcdrs0dceaps2i appian]# ls -l /proc/8855/exe
lrwxrwxrwx 1 hosting hostnggp 0 Jul 9 00:20 /proc/8855/exe -> /hosting/products/appian/server/_bin/k/linux64/k
[root@lcdrs0dceaps2i appian]# fuser 5029/tcp
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
It seems there's indeed something running in those ports right?
Can you restart the server to kill everything?
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
aneeshv713
over 9 years ago
This command helped cleanup --> kill -9 `ps -ef |grep hosting |grep appian |awk '{print $2}'`
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Glad it's working now.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
<