[jira] [Updated] (UIMA-5390) DUCC may restart failing custom services forever

[Burn Lewis (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Burn Lewis updated UIMA-5390:
-
Fix Version/s: (was: future-DUCC)
   2.2.2-Ducc

Runtime errors are wrongly reset when starting another instance.  

> DUCC may restart failing custom services forever
> 
>
> Key: UIMA-5390
> URL: https://issues.apache.org/jira/browse/UIMA-5390
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Burn Lewis
>Priority: Minor
> Fix For: 2.2.2-Ducc
>
>
> Since custom services have no initialization phase all init errors are 
> counted as run errors, but before the threshold is reached the error count 
> may be reset.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (UIMA-5735) DUCC Web Server (WS) logs queries to DB too verbosely

[Lou DeGenaro (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lou DeGenaro updated UIMA-5735:
---
Fix Version/s: (was: future-DUCC)
   2.2.2-Ducc

> DUCC Web Server (WS) logs queries to DB too verbosely
> -
>
> Key: UIMA-5735
> URL: https://issues.apache.org/jira/browse/UIMA-5735
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Lou DeGenaro
>Assignee: Lou DeGenaro
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> To determine if DB is alive, WS re-uses the DB routine that reads checkpoint 
> data.  This routine correctly logs at the INFO level for the purpose of 
> initial restoration of the checkpoint data, but logs too verbosely for the 
> re-use by WS for DB aliveness test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (UIMA-5734) check_ducc & start_ducc problem when Banner is enabled in sshd_config

[Eddie Epstein (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eddie Epstein updated UIMA-5734:

Fix Version/s: 2.2.2-Ducc

> check_ducc & start_ducc problem when Banner is enabled in sshd_config
> -
>
> Key: UIMA-5734
> URL: https://issues.apache.org/jira/browse/UIMA-5734
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Eddie Epstein
>Assignee: Eddie Epstein
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> ducc_util.py does a check with ssh to confirm the name used by the DUCC head 
> node to reach a machine is the same name the machine returns from running 
> hostname. Any pre-authentication text returned when sshd_config enables 
> Banner interferes with this check.
> ducc_util.py must use -q to suppress this text.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (UIMA-5734) check_ducc & start_ducc problem when Banner is enabled in sshd_config

[Eddie Epstein (JIRA)]

 [ 
https://issues.apache.org/jira/browse/UIMA-5734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Eddie Epstein updated UIMA-5734:

Fix Version/s: (was: future-DUCC)

> check_ducc & start_ducc problem when Banner is enabled in sshd_config
> -
>
> Key: UIMA-5734
> URL: https://issues.apache.org/jira/browse/UIMA-5734
> Project: UIMA
>  Issue Type: Bug
>  Components: DUCC
>Reporter: Eddie Epstein
>Assignee: Eddie Epstein
>Priority: Major
> Fix For: 2.2.2-Ducc
>
>
> ducc_util.py does a check with ssh to confirm the name used by the DUCC head 
> node to reach a machine is the same name the machine returns from running 
> hostname. Any pre-authentication text returned when sshd_config enables 
> Banner interferes with this check.
> ducc_util.py must use -q to suppress this text.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Re: [VOTE] UIMA-DUCC 2.2.2 RC2

[Eddie Epstein]

-1 Not OK to release, because ... two blocking problems. First is massively
excessive logging by duccmon. The other is an infinite loop in restarting
custom service instances on failure.

Eddie

On Thu, Feb 22, 2018 at 10:55 AM, Jerry Cwiklik  wrote:

> Hi,
>
> the UIMA-DUCC 2.2.2 release candidate 2 is ready for voting.
>
> This version contains the following fixes since RC1:
>
> - modified service/jp wrapper to log errors from process()
> - modified to remove calls to XMLUtils
> - modified to fix the cause of error preventing launching jobs with
> wait_for_completion flag
>
> The list of changes in Jira:
> https://issues.apache.org/jira/issues/?jql=fixVersion%20%3D%
> 202.2.2-Ducc%20AND%20project%20%3D%20UIMA
>
> The source and binary zip/tars are staged to
> https://dist.apache.org/repos/dist/dev/uima/uima-ducc/2.2.2/RC2/
>
> The Maven artifacts are here:
> https://repository.apache.org/content/repositories/orgapacheuima-1188
>
> The SVN tags are here:
> http://svn.apache.org/repos/asf/uima/uima-ducc/tags/uima-ducc-2.2.2/
>
> See http://uima.apache.org/testing-builds.html for suggestions on how to
> test release candidates.
>
> Please vote on release:
>
> [ ] +1 OK to release
> [ ] 0   Don't care
> [ ] -1 Not OK to release, because ...
>
> Thanks
>
> --
> Jerry Cwiklik
> Apache UIMA
>
>

[jira] [Created] (UIMA-5735) DUCC Web Server (WS) logs queries to DB too verbosely

[Lou DeGenaro (JIRA)]

Lou DeGenaro created UIMA-5735:
--

 Summary: DUCC Web Server (WS) logs queries to DB too verbosely
 Key: UIMA-5735
 URL: https://issues.apache.org/jira/browse/UIMA-5735
 Project: UIMA
  Issue Type: Bug
  Components: DUCC
Reporter: Lou DeGenaro
Assignee: Lou DeGenaro
 Fix For: future-DUCC


To determine if DB is alive, WS re-uses the DB routine that reads checkpoint 
data.  This routine correctly logs at the INFO level for the purpose of initial 
restoration of the checkpoint data, but logs too verbosely for the re-use by WS 
for DB aliveness test.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (UIMA-5723) MARKTABLE fails to assign feature for single word entry in first CSV column

[Andreas Thiel (JIRA)]

[ 
https://issues.apache.org/jira/browse/UIMA-5723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16378511#comment-16378511
 ] 

Andreas Thiel commented on UIMA-5723:
-

Sorry, but I do not have a minimal example right now. Would have to create one 
but had no free time yet.

> MARKTABLE fails to assign feature for single word entry in first CSV column
> ---
>
> Key: UIMA-5723
> URL: https://issues.apache.org/jira/browse/UIMA-5723
> Project: UIMA
>  Issue Type: Bug
>  Components: Ruta
>Affects Versions: 2.6.1ruta
>Reporter: Andreas Thiel
>Assignee: Peter Klügl
>Priority: Major
>
> When using Ruta's MARKTABLE action with a CSV file {{nl_law_names.csv}} like 
> this
> {code:xml}
> WAZ;WAZELF
> Wet arbeidsongeschiktheidsverzekering zelfstandigen;WAZELF
> {code}
> and corresponding Ruta script containing these lines
> {code:java}
> WORDTABLE LawNameTable = 'nl_law_names.csv';
> Document{->MARKTABLE(WetNaam, 1, LawNameTable, "WetIdentifier" = 2)};
> {code}
> it seems that the text {{WAZ}} is detected, but the {{WetIdentifier}} feature 
> of the resulting annotation is not filled by the string following the 
> semicolon. Instead, it remains empty.
> (Note: _WetNaam_ annotation is defined elsewhere via type system description)
> In contrast, the fully written name {{Wet arbeidsongeschiktheidsverzekering 
> zelfstandigen}} is detected and processed as expected with feature 
> WetIdentifier = WAZELF after annnotating.
> Could it be that problems arise when only a single word (i.e. no spaces or 
> uppercase letters following lowercase chars) is present in the first column 
> in the CSV file? Or is it a matter of configuration?
> We experimented also with the optional arguments of MARKTABLE regarding 
> uppercase/lowercase distinction, but to no avail.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)