Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Use this forum for questions regarding installation, upgrading and configuration of OpenEMM

Moderator: moderator

JuergenB
Posts: 140
Joined: Thu Dec 05, 2019 9:03 pm

Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Post by JuergenB »

Hi,
during an upgrade from 21.04 to 21.10 i get this error after upgrading.
In the Status, the Jobqeue and Overall show error.

I tried to start single Jobs with the option Start Jobs by description.
But i only get a small box saying Error.

This is last part of openemm-log

Code: Select all

2022-03-02 12:27:49,251: ERROR [https-openssl-apr-8443-exec-8] com.agnitas.emm.core.serverstatus.web.ServerStatusControllerBasic - Error while starting job queue by description AutoOptimization
java.lang.Exception: This JobQueueNode is currently not active
	at org.agnitas.service.JobQueueService.startSpecificJobQueueJob(JobQueueService.java:267)
	at com.agnitas.emm.core.serverstatus.web.ServerStatusControllerBasic.startJob(ServerStatusControllerBasic.java:208)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:205)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:133)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:97)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:854)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:765)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:967)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:901)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
	at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:691)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
	at jakarta.servlet.http.HttpServlet.service(HttpServlet.java:774)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:223)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:53)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at com.agnitas.emm.core.commons.filter.OriginUriFilter.doFilter(OriginUriFilter.java:43)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at com.agnitas.emm.core.commons.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:80)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at com.agnitas.emm.core.sessionhijacking.web.GroupingSessionHijackingPreventionFilter.doFilter(GroupingSessionHijackingPreventionFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at com.agnitas.web.filter.HttpSecurityHeaderFilter.doFilter(HttpSecurityHeaderFilter.java:113)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at com.agnitas.emm.core.commons.filter.LoadBalancerFilter.doFilter(LoadBalancerFilter.java:153)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:185)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:158)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:197)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:97)
	at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:668)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:119)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:92)
	at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:690)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:78)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:353)
	at org.apache.coyote.http11.Http11Processor.service(Http11Processor.java:382)
	at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:65)
	at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:870)
	at org.apache.tomcat.util.net.AprEndpoint$SocketProcessor.doRun(AprEndpoint.java:2058)
	at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:49)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1191)
	at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.base/java.lang.Thread.run(Thread.java:829)
	
This is the Status page

Code: Select all

=============================================
= OpenEMM Maintenance Tool (OMT) v21.10.044 =
=============================================
Root mode: On
Hostname: localhost.localdomain
OpenEMM License: OpenEMM (ID: 0)
OpenEMM Runtime Version: 21.10.044
OpenEMM Version: 21.10.000.108
System-Url: https://192.168.200.163

Current menu: Show OpenEMM status

OpenEMM status:
Operating System (OS): Alma 8
Python version: 3.8.8
Postfix Version: 3.5.8
Database client version: /usr/bin/mysql  Ver 15.1 Distrib 10.3.28-MariaDB, for Linux (x86_64) using readline 5.1
Database Connection: OK
System-Time: 2022-03-02 12:30:11
System-Time-DB: 2022-03-02 12:30:11
Database version: MariaDB 10.3.28-MariaDB
OpenEMM database structure exists (Version 21.10.384)
Database table emm_db_errorlog_tbl: OK
Jobqueue status: 8 errorneous jobs (BirtReports, LoginTrackTableCleaner, CalendarCommentMailingService, ...)
DKIM keys available for domains: None
Java version: 11.0.13 (Oracle)
Tomcat version: 10.0.10.0
Tomcat-Native version: 1.2.30
Wkhtml version: wkhtmltopdf 0.12.6 (with patched qt)
OpenEMM Application is running (Tomcat ProcessID: 4075, started at: 12:11 1:15)
OpenEMM Backend ok: once
OpenEMM Backend running: mailout, update, trigger, generate, mta, pickdist, slrtscn, direct-path, bav-update, bavd, bav, mlcontrol
aso
Posts: 33
Joined: Fri Jun 19, 2015 12:43 pm

Re: Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Post by aso »

Please have a look in your db table "config_tbl".
There should be an entry like:
class, name, value, hostname
jobqueue, execute, 1, null

The meaning of this is, that your OpenEMM Server, no matter what is his hostname, is allowed to execute the jobqueue jobs (batchjobs).
In former versions (<= 21.04) of OpenEMM this entry looked like:
class, name, value, hostname
system, <hostname>.IsActive, 1, null

This was simplified in version 21.10.
Maybe this migration was not executed properly during the OpenEMM update.
JuergenB
Posts: 140
Joined: Thu Dec 05, 2019 9:03 pm

Re: Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Post by JuergenB »

Thanks,

i verified these settings, ERROR is still there.

The installation was fine until i imported a mariadb Dump from Production.
Scratch Install and Production have the same OpenEMM Versions.
maschoff
Site Admin
Posts: 2596
Joined: Thu Aug 03, 2006 10:20 am
Location: Munich, Germany
Contact:

Re: Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Post by maschoff »

If you import from a different server, you probably have to change the value for <hostname>, because the new server will have a different name.
OpenEMM Maintainer
JuergenB
Posts: 140
Joined: Thu Dec 05, 2019 9:03 pm

Re: Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Post by JuergenB »

Hi,
i change most of the settings where i have the hostname.

But even if i only upgrade the production from 21.04 to 21.10 on the same machine, it fails with the same error.

As a second test i have a clone from production and upgraded this clone, it still fails.

Only difference..

Produktion is on Centos 8 Stream
New Maschine is on AlmaLinux 8.5
JuergenB
Posts: 140
Joined: Thu Dec 05, 2019 9:03 pm

Re: Jobqueue Status ERROR (Overall Status ERROR) - after Upgrade 21.04 to 21.10.000.108

Post by JuergenB »

Hi,

Thanks aso :D

i verified the database again and this is what i found in config_tbl of Version 21.10!

jobqueue, execute,1,<hostname> [to be defined]

I had some problems with mariadb cmd line client, so i verified with HeidiSQL today and was able to modify the value [set to (NULL)].
Jobqueue Status and Overall Status is fine now.

So, my advice is to update/change the update script for the new release 21.10, to verify these settings!

In 21.04 there is no jobqeue value in config_tbl, this must be added with some new release 21.10.*****

Thanks
Post Reply