rundeck runs job for ever, even though it has been completed.

[Aristos Vasiliou]

I have a job that runs for ever in rundeck, but its actually completed within a second on the linux computer.

For some reason rundeck thinks that the job did not finish. What could be causing this behavior?

[Corey Dubin]

I am having this same issue, it started after I updated Rundeck from 2.6.10 to 2.7.1

Anyone else having this issue? 

Better yet, anyone know how to resolve it?

[Edmond Hui]

I am seeing the same issue, ungraded from 2.6.9 to 2.7.1

In my case, only some of the jobs are having this issue.....

A bug we should reported?

[Edmond Hui]

checking the log and I am seeing DB failure, I saw any post reported a similar issue. In my case I am running h2 DB on a file.

The H2 error (the last one of a bunch...):

Caused by: org.h2.jdbc.JdbcSQLException: Value too long for column "FAILED_NODE_LIST VARCHAR(255)": "'xxxxxxxxxxx (taken out for privacy)... (398)"; SQL statement:

insert into base_report (id, version, action_type, author, ctx_name, ctx_project, ctx_type, date_completed, date_started, mapref_uri, message, node, report_id, status, tags, title, aborted_by_user, adhoc_execution, adhoc_script, ctx_command, ctx_controller, failed_node_list, filter_applied, jc_exec_id, jc_job_id, succeeded_node_list, class) values (null, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, 'rundeck.ExecReport') [22001-193]

        at org.h2.message.DbException.getJdbcSQLException(DbException.java:345)

        at org.h2.message.DbException.get(DbException.java:179)

        at org.h2.table.Column.validateConvertUpdateSequence(Column.java:335)

        at org.h2.table.Table.validateConvertUpdateSequence(Table.java:784)

        at org.h2.command.dml.Insert.insertRows(Insert.java:151)

        at org.h2.command.dml.Insert.update(Insert.java:114)

        at org.h2.command.CommandContainer.update(CommandContainer.java:98)

        at org.h2.command.Command.executeUpdate(Command.java:258)

        at org.h2.jdbc.JdbcPreparedStatement.executeUpdateInternal(JdbcPreparedStatement.java:160)

        at org.h2.jdbc.JdbcPreparedStatement.executeUpdate(JdbcPreparedStatement.java:146)

        ... 13 more

2017-01-04 09:03:25,712 WARN  ExecutionJob - Execution 33303 save result status: failed (attempts=9/10), retrying in 184527ms

This looks like the in-place schema failed?

[Corey Dubin]

In case anyone didn't see there are several discussions on this issue.  So this is a bug (https://github.com/rundeck/rundeck/issues/2228 ) and it has been addressed, at least partially.  What I mean is that it appears to be fixed for new installations, but I think you have to manually update the db yourself if you have an existing db, at least that is the way I understand it.  Anyway, the fixed column definition should be in 2.7.2 for new installations, don't know if a migration fix will make it in to that release or not for existing installs.

Hope this helps clear things up a bit.