File startup occuping big space

RE: File startup occuping big space

Justin Watts — Thu, 01 Feb 2018 16:40:46 GMT

Unfortunately, I'm not familiar with this specific error. It looks like the issue started around January 17. Were there any maintenance or deployment activities occurring during that time?

If you haven't opened a Support case with Appian, please do so. Their engineers should be able to provide the best guidance.

RE: File startup occuping big space

Guilherme Canteiro — Thu, 01 Feb 2018 15:17:05 GMT

Hi Justin,

I am having this error in the gw of the 3 engine logs:

"Attempt to get server statistics failed: index"

In attach the logs:

community.appian.com/.../gw_5F00_CO1_5F00_2017_2D00_12_2D00_14_5F00_1500.log

community.appian.com/.../gw_5F00_PX001_5F00_2017_2D00_12_2D00_14_5F00_1500.log

community.appian.com/.../gw_5F00_PX021_5F00_2017_2D00_12_2D00_14_5F00_1500.log

Thanks

RE: File startup occuping big space

Justin Watts — Thu, 01 Feb 2018 14:48:25 GMT

What version of Appian is this? That may change my recommendation, but generally, I would look for the Engine DB/GW logs like (using Exec 02 as an example) db_PX021_<timestamp>.log or gw_PX021_<timestamp>.log (if on an older version of Appian) and see if there are any more specific error messages that we can diagnose. There should be corresponding logs for CO1/CS1 (collab) and PX001 (exec 00) as well.

docs.appian.com/.../Logging.html

RE: File startup occuping big space

Guilherme Canteiro — Thu, 01 Feb 2018 14:41:55 GMT

I have noticed that process-Exec00, process-Exec02 and collaboration are in Fatal status.

And i have already shut down and restart with older kdb's files and still are failling.

How can i see what is causing this?

Thanks

RE: File startup occuping big space

Justin Watts — Wed, 31 Jan 2018 19:35:05 GMT

I haven't seen that specific error before, but its clear your engines are in some error state. Can you run checkengine.bat and see if that provides any more useful information?

I also recommend opening a Support case since Appian Support is typically the best channel for discussion this class of error.

RE: File startup occuping big space

Guilherme Canteiro — Wed, 31 Jan 2018 18:41:34 GMT

[Appian WorkPoller - 0 [Collaboration]] ERROR com.appiancorp.ra.workpoller.WorkPoller - Collaboration: Error while trying to accept Work in Bulk: index
com.appiancorp.kougar.driver.exceptions.Signal: index

[Appian WorkPoller - 5 [ProcessExec02]] ERROR com.appiancorp.ra.workpoller.WorkPoller - ProcessExec02: Error while trying to accept Work in Bulk: index
com.appiancorp.kougar.driver.exceptions.Signal: index

[Appian WorkPoller - 2 [ProcessExec01]] ERROR com.appiancorp.kougar.driver.ipc.IpcConnection - Could not initialize engine: [process-execution1:]
com.appiancorp.kougar.driver.exceptions.TcpException: java.io.EOFException: there is a problem with the database server: process-execution1 (localhost:5026)

I am having this errors on the log. Any one knows what is it about?

RE: File startup occuping big space

Justin Watts — Wed, 31 Jan 2018 17:58:10 GMT

Is this related to the server in your previous post? community.appian.com/.../generating-application-server-log-file-every-minute

How are you starting JBOSS? Windows service, command line script? What parameters are part of that execution. To my knowledge, there isn't a startup log generated unless you explicitly pipe output of run.bat to a file.

Given the vast amount of logging occurring as referencing in your other post, my guess is that all of those same log entries are also being written to this file. My advice is the same as in the other post - locate what is spamming those logs, whether its an error or a DEBUG logging level, and adjust.