7qubit
June 26, 2022, 12:15pm
1
Infos:
Used Zammad version: 5.2.0-1656011622.80bf57c1.focal
Used Zammad installation type: (package)
Operating system: Ubuntu 20.04
Browser + version: Firefox 101+
Expected behavior:
LDAP Import job run itself into a loop-start.
Once import job is finished and deplay jobs are processed, LDAP import job starts again. This should repeat at one hour intervals.
This also causes permanent load by backgroud workers.
Actual behavior:
LDAP Import Job works without pause.
Steps to reproduce the behavior:
I have tested this on freshly installed machine and believe the problem occurs in zammad 5.2.
1 Like
This was fixed a couple days ago. Would you be kind enough to update and check again ?
opened 07:48AM - 23 Jun 22 UTC
closed 01:20PM - 23 Jun 22 UTC
bug
blocker
LDAP
verified
prioritised by payment
<!--
Hi there - thanks for filing an issue. Please ensure the following things … before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 5.2
* Installation method (package)
* Operating system: Ubuntu 20.04
* Database + version: Postgresql 14+238
* Elasticsearch version: 7.17.4
* Browser + version: Firefox 101
### Expected behavior:
* since update to “zammad 5.2” LDAP import does not start automatically.
### Actual behavior:
*
The scheduler no longer starts importjobs every hours. this must be started manually
Scheduler.find_by(method: ‘ImportJob.start_registered’).last_run
=> Thu, 23 Jun 2022 07:34:45.896000000 UTC +00:00
Delayed::Job.count
=> 0
Yes I'm sure this is a bug and no feature request or a general question.
Ah shit issue was from you also! thx btw! Just wanted to link it so other can find it as well ^^
7qubit
June 30, 2022, 7:56am
4
The problem with “the LDAP import job not starting” has already been fixed, for which I thank you.
But here is a new problem, the LDAP import does not stop and immediately repeats when delayed jobs are finished. This causes just height permanent load.
That’s weird. Can you post some infos?
$ zammad run rails r "pp Scheduler.find_by(name: 'Execute import jobs.')"
$ zammad run rails r "pp ImportJob.where(finished_at: nil).count"
7qubit
June 30, 2022, 9:43am
6
root@testzammad001:~# zammad run rails r “pp Scheduler.find_by(name: ‘Execute import jobs.’)”
#<Scheduler:0x000055eb978c9168
id: 24,
name: "Execute import jobs.",
method: "ImportJob.start_registered",
period: 3600,
running: 0,
last_run: Thu, 30 Jun 2022 09:35:45.698000000 UTC +00:00,
prio: 1,
pid: "20974000",
note: nil,
error_message: "",
status: "ok",
active: true,
updated_by_id: 1,
created_by_id: 1,
created_at: Sun, 04 Jul 2021 15:47:53.947000000 UTC +00:00,
updated_at: Thu, 30 Jun 2022 09:35:45.699000000 UTC +00:00,
timeplan: {}>
root@testzammad001:~# zammad run rails r “pp ImportJob.where(finished_at: nil).count”
1
system
Closed
November 8, 2022, 7:40am
8
This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.