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
5 replies
Subscribers
6 subscribers
Views
2506 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Error while trying to accept Work in Bulk: /hosting/appian/logs/db_PX021_2017-01-26_1600.log: Bad file descriptor
naveena113
over 8 years ago
Hello,
We are getting the below error in the logs & its filling up the disk space rapidly. Please let us know if we have seen this issue before.
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) 2017-02-04 20:15:48,403 [Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)] ERROR com.appiancorp.ra.workpoller.WorkPoller - ProcessExec02: Error while trying to accept Work in Bulk: /hosting/appian/logs/db_PX021_2017-01-26_1600.log: Bad file descriptor
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) com.appiancorp.kougar.driver.exceptions.Signal: /hosting/appian/logs/db_PX021_2017-01-26_1600.log: Bad file descriptor
2017-02-04 20:15:48,403 GMT INFO [stdout] (App...
OriginalPostID-262040
Discussion posts and replies are publicly visible
0
naveena113
over 8 years ago
...ian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.driver.ipc.IpcConnection.get(IpcConnection.java:367)
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.driver.ipc.IpcConnection.call(IpcConnection.java:836)
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.driver.ipc.IpcConnection.call(IpcConnection.java:817)
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.driver.KougarConnection.call(KougarConnection.java:320)
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.driver.KougarConnection.call(KougarConnection.java:270)
2017-02-04 20:15:48,403 GMT I...
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
naveena113
over 8 years ago
...NFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.driver.KougarConnection.call(KougarConnection.java:218)
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.mapper.Mapper.request(Mapper.java:65)
2017-02-04 20:15:48,403 GMT INFO [stdout] (Appian WorkPoller - 6 [ProcessExec02] (originally: default-threads - 21)) at com.appiancorp.kougar.services.KougarServiceInvocationHandler$KInvocationHandler.invoke(KougarServiceInvocationHandler.java:178)
Thanks
Naveen
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
nileshr889
over 8 years ago
@Naveen: The above error means that The user that ran the start-suite.bat|sh command does not have read and write permissions over one or more of the .kdb files for the engine(s). To resolve this follow the below steps:
1. Stop Jboss application server.
2. Stop search-server.
3. Stop Appian Engines.
4. Now run cmd as an administrator and run start-suite.bat |sh command.
5. Verify the engine status and once all engines are in OKAY state, follow next steps.
6. Rename suite.ear.failed to suite.ear.dodeploy at location <APPIAN_HOME>\\ear.
7. Delete the *.ds.xml.failed or *.ds.xml.undeployed inside JBOSS deployment folder.
8. Start the search-sever and jboss.
Let me know if it works or you face any other issues.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Alok Mohare
Appian Employee
over 8 years ago
Nilesh is accurate with his root cause.
I would like to add just one more thing to this since it looks like you are using a Linux based OS.
I would do the following:
1) Stop App-server
2) Stop Search-server
3) Stop Appian Engines
***4) chown -R appian:appian /hosting/appian (assuming that the user you created for installing / running the software is appian)
5) Start Appian Engines (as the appian user)
6) Start Search-server (as the appian user)
7) Start App-server (as the appian user)
Hope this helps!
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
naveena113
over 8 years ago
Thank you Nilesh & Alok. Appreciate your help.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel