Search Engine: Elastic

Article ID: 129002, created on Jun 23, 2016, last review on Jun 29, 2016

  • Applies to:
  • Business Automation 6.0


The tasks are not processed, in the list of active tasks (Home > Operations > Tasks > Active tasks) there are no running tasks (or only 1) and lots of waiting.

Previously there was a lack of diskspace of the BA application sever (which was fixed). In logsrv.out.log there are records similar to

[16-06-18 00:18:03.236 AFWriter    TH03626 ERR] Coult not write logs to file  . write() failed - written 30 of 56 bytes: No space left on device
[16-06-18 00:18:03.238 AFWriter    TH03626 FTL] Thread terminated by throwing an instance of 'N5STLRT3Log6Server9ExceptionE'.


Initially the issue is caused by the lack of free disk space. Due to #PBA-74563 ("Scheduler does not resume work after no disk space left on device") scheduler did not resume operating after disk space clean up.


As a workaround, restart scheduler (or whole ba) after disk spaced is cleaned up:

service pba restart scheduler


service pba restart

198398b282069eaf2d94a6af87dcb3ff caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 3627d36199b8ff577605df76e2fa222b bb7e9177fb03488961a3ea554120f328

Email subscription for changes to this article
Save as PDF