workflow not executed on sheduled time..skiped few workflow and jumped to next..

#1

image

workflow not executed on scheduled time…skiped few workflow and jumped to next…

as you can see in the image scheduler skipped my workflow from running on time…
and jumped to the next one…

and after running multiple workflow the same time , knime closed automatically.

0 Likes

#2

same issue happened today also…

workflow are not running in sequence n few are skiped…

0 Likes

#3

Hi Navinjadhav,

We’d need to look at the log files to understand what is going on. One of our account managers should have been in touch to arrange a call with a support engineer.

Best,

Jon

0 Likes

#4

today also jobs are missed…

what will be the reason ?

i need to monitor it everyday ! after buying server also my purpose is not solved

0 Likes

#5

still waiting for cal

0 Likes

#6

Hi @navinjadhav,

I’ve sent you a PM to follow up on this.

Best,
Marten

0 Likes

#7

https://drive.google.com/drive/folders/1O6d7OK1ug5bfZym7HOC6P38aB-Kn0uQx?usp=sharing

link for log file

today also same problem

0 Likes

#8

Hello Team

please look into a log file
from the last two days, the workflow is not running

https://drive.google.com/open?id=1Apkf_41bkrIq_fpGNOpDh9e0DDR_FZjT

https://drive.google.com/open?id=1Bclnp0qGHVSD9-EaxE6tFlooMmWfOop6

0 Likes

#9

hello Team

I have no use of knime server for automation - still i am manually running woklfows
please let me know what you guys required to analyse problem,

every day workflows are skipped ,
tell what wrong with my system

0 Likes

#10

Hi,

one thought about the screenshots.
I’ve noticed that you run KNIME Server on your local machine. Could it be that the machine was in hibernation mode or suspended at the time the schedule should occur?
I downloaded your log files, however there seem to be too many of them and it’s hard to guess when the error happened.

Could you provide a single log file of the date where the execution hasn’t happened? It would be also useful to know how many jobs and schedules are running at that time and which schedule wasn’t executed.

Cheers,
Moritz

1 Like

#11

in last 5 days i dont have that issue. so i dont have log. i will revert once i have same issue again.

0 Likes

#12

I use AWS instance so hibernation is not issue i guess.

0 Likes

#13

Okay I see.
Another reason might have been that there were too many jobs running while the next job would have been scheduled, but that’s only a wild guess and I would have to check with someone else what happens in said case.

Cheers,
Moritz

1 Like

#14

last workflow run on 16 Aug…
no workflow run in last 3 days…

localhost.2019-08-16.log (1.1 MB)

0 Likes

#15

localhost.2019-08-17.log (869.2 KB)

0 Likes

#16

localhost.2019-08-18.log (776.1 KB)

0 Likes

#17

localhost.2019-08-19.log (304.3 KB)

0 Likes

#18

2019-08-16 12:39:09,433 : DEBUG : KNIME-Temp-File-Deleter : Buffer : : : Deleted temporary file “/srv/knime_server/jobs/8977e9/flowContextTmp/knime_container_20190816_4671835376321101411.bin.gz”
2019-08-16 12:39:09,433 : DEBUG : KNIME-Temp-File-Deleter : Buffer : : : Deleted temporary file “/srv/knime_server/jobs/8977e9/flowContextTmp/knime_container_20190816_4481195273949704670.bin.gz”
2019-08-16 12:39:09,448 : DEBUG : KNIME-Temp-File-Deleter : Buffer : : : Deleted temporary file “/srv/knime_server/jobs/8977e9/flowContextTmp/knime_container_20190816_1491053337385242723.bin.gz”
2019-08-16 12:39:09,450 : DEBUG : KNIME-Temp-File-Deleter : Buffer : : : Deleted temporary file “/srv/knime_server/jobs/8977e9/flowContextTmp/knime_container_20190816_7197489729817500574.bin.gz”
2019-08-16 12:39:10,395 : INFO : KNIME shutdown hooks - com.knime.enterprise.executor.GracefulShutdownHook : GracefulShutdownHook : : : JVM terminate event received, canceling jobs and swapping them to the server
2019-08-17 12:46:19,444 : INFO : main : NodeLogger : : : #########################################################################################
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # Welcome to KNIME Analytics Platform v3.7.2.v201904170949 (Build April 18, 2019) #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # Based on Eclipse, http://www.eclipse.org #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : #########################################################################################
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # Copyright by KNIME AG, Zurich, Switzerland and others. #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # Website: http://www.knime.com #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # E-mail: contact@knime.com #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : #########################################################################################
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # For more details see the KNIME log file: #
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : # /srv/knime_server/runtime/runtime_knime-rmi-50101/.metadata/knime/knime.log
2019-08-17 12:46:19,446 : INFO : main : NodeLogger : : : #---------------------------------------------------------------------------------------#
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # logging date=Sat Aug 17 12:46:19 IST 2019
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # java.version=1.8.0_152
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # java.vm.version=25.152-b16
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # java.vendor=Oracle Corporation
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # os.name=Linux
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # os.arch=amd64
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # number of CPUs=4
2019-08-17 12:46:19,447 : INFO : main : NodeLogger : : : # assertions=off
2019-08-17 12:46:19,448 : INFO : main : NodeLogger : : : # host=ip-172-31-26-36
2019-08-17 12:46:19,449 : INFO : main : NodeLogger : : : # username=knime
2019-08-17 12:46:19,449 : INFO : main : NodeLogger : : : # max mem=7129MB
2019-08-17 12:46:19,449 : INFO : main : NodeLogger : : : # application=org.knime.product.KNIME_APPLICATION
2019-08-17 12:46:19,450 : INFO : main : NodeLogger : : : # ID=01-18e0c8faa19800c7
2019-08-17 12:46:19,450 : INFO : main : NodeLogger : : : #########################################################################################
2019-08-17 12:46:20,001 : DEBUG : main : DatabaseConnectionSettings : : : Settings database timeout to 15 seconds
2019-08-17 12:46:20,405 : DEBUG : main : DatabaseConnectionSettings : : : Database concurrency (sync via database connection) is true.
2019-08-17 12:46:20,406 : DEBUG : main : KNIMECorePlugin : : : Setting KNIME max thread count to 8
2019-08-17 12:46:20,406 : DEBUG : main : KNIMECorePlugin : : : Setting KNIME temp dir to “/tmp”
2019-08-17 12:46:20,484 : DEBUG : main : KnimeEncryption : : : Replacing current encryption key supplier “null” with this new one “org.knime.workbench.core.EclipseEncryptionKeySupplier@63ccb1b2”.
2019-08-17 12:46:20,484 : DEBUG : main : DatabaseConnectionSettings : : : Settings database timeout to 7200 seconds
2019-08-17 12:46:20,500 : INFO : main : RMIRegistryHandler : : : KNIME Slave: Creating RMI registry…
2019-08-17 12:46:20,506 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IVersionChecker to name IVersionChecker at port 50101
2019-08-17 12:46:20,512 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IWorkflowExecutor to name IWorkflowExecutor at port 50101
2019-08-17 12:46:20,519 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IQuickFormController to name IQuickFormController at port 50101
2019-08-17 12:46:20,521 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IWebResourceManager to name IWebResourceManager at port 50101
2019-08-17 12:46:20,523 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IReportExecutor to name IReportExecutor at port 50101
2019-08-17 12:46:20,525 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IJobEventService to name IJobEventService at port 50101
2019-08-17 12:46:20,526 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class IGenericRequestExecutor to name IGenericRequestExecutor at port 50101
2019-08-17 12:46:20,527 : DEBUG : main : RMIRegistryHandler : : : KNIME Slave: Binding class ISlaveManager to name ISlaveManager at port 50101
2019-08-17 12:46:20,528 : INFO : main : RMIRegistryHandler : : : KNIME Slave ready (port=50101)
2019-08-17 12:47:12,638 : DEBUG : KNIME-ConfigurationArea-Checker : ConfigurationAreaChecker : : : Configuration area is at /opt/knime/knime-3.7.2/configuration
2019-08-17 12:47:12,655 : DEBUG : KNIME-ConfigurationArea-Checker : ConfigurationAreaChecker : : : File in configuration area ("/opt/knime/knime-3.7.2/configuration/org.knime.core/knime.lock") cannot be locked by current user knime; either the file is already locked by a different KNIME instance or the file system does not support locking. This may lead to undesired effects in multi-user setups, see KNIME FAQs: https://www.knime.com/faq#q34.
2019-08-17 12:47:12,664 : ERROR : KNIME-ConfigurationArea-Checker : ConfigurationAreaChecker : : : Configuration area ("/opt/knime/knime-3.7.2/configuration") seems to be used by a different process, found file lock on “org.knime.core/root.lock” (used by user root). This may lead to undesired effects in multi-user setups, see KNIME FAQs: https://www.knime.com/faq#q34.
2019-08-17 12:47:12,665 : DEBUG : KNIME-ConfigurationArea-Checker : ConfigurationAreaChecker : : : Configuration area check completed in 0.0s
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IQuickFormController from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IWorkflowExecutor from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IVersionChecker from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IReportExecutor from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IJobEventService from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding ISlaveManager from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IGenericRequestExecutor from RMI registry.
2019-08-18 12:46:34,223 : DEBUG : main : RMIRegistryHandler : : : Unbinding IWebResourceManager from RMI registry.
2019-08-18 12:46:34,223 : INFO : main : RMIRegistryHandler : : : KNIME Slave stopped
2019-08-18 12:46:34,967 : INFO : KNIME shutdown hooks - com.knime.enterprise.executor.GracefulShutdownHook : GracefulShutdownHook : : : JVM terminate event received, canceling jobs and swapping them to the server

0 Likes

#19

16 17 18 log knime.txt (156.4 KB)

0 Likes

#20

Thank you, we will investigate the behavior!

Cheers,
Moritz

0 Likes