starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

Schedules running at 2 different times. #165

New Issue
Closed
opened 2026-02-05 17:12:59 +03:00 by OVERLORD · 8 comments
OVERLORD commented 2026-02-05 17:12:59 +03:00
Owner
Copy Link

Originally created by @BrianDLC on GitHub (Oct 3, 2024).

Originally assigned to: @Boy132 on GitHub.

Current Behavior

Schedules seem to run twice at two different times, today I was able to notice all schedules run at other times, I had set up an alarm to run every 3 hours, another to run at 0 0 * * * and another to run at */3, which would be every 3 hours, all 3 ran at the same time at 0 UTC. The 0 0 * * * schedule ran at 4PM and again at 8PM (it should run at 8PM), after it ran again at 8PM, it claims the next scheduled run time is at 4PM, meaning it'll most likely run at 4PM and 8PM again the next day. I did have this issue a month ago and had more information but decided to turn off all schedules due to wanting to progress on a game server.

The issue persists, If I run a schedule it will run at the time I designated and at another time around 4 hours before the scheduled time. I do not understand how to troubleshoot this and would love some assistance.

I've even tried updating the panel as well as setting the schedule on another server and node, still same issue, seems to have started happening after some time using the panel as it did work for a time.

Expected Behavior

Schedules should run as intended by the cron schedule

Steps to Reproduce

Create any schedule and see when it runs.

Panel Version

1.0.0-beta10

Wings Version

1.0.0-beta4

Games and/or Eggs Affected

All (Testing on Minecraft Neoforge)

Docker Image

No response

Error Logs

https://paste.pelistuff.com/anwT panel
https://paste.pelistuff.com/tjbX wing 1
https://paste.pelistuff.com/3BFF wing 2

Is there an existing issue for this?

  • I have searched the existing issues before opening this issue.
  • I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server.
  • I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
Originally created by @BrianDLC on GitHub (Oct 3, 2024). Originally assigned to: @Boy132 on GitHub. ### Current Behavior Schedules seem to run twice at two different times, today I was able to notice all schedules run at other times, I had set up an alarm to run every 3 hours, another to run at 0 0 * * * and another to run at */3, which would be every 3 hours, all 3 ran at the same time at 0 UTC. The 0 0 * * * schedule ran at 4PM and again at 8PM (it should run at 8PM), after it ran again at 8PM, it claims the next scheduled run time is at 4PM, meaning it'll most likely run at 4PM and 8PM again the next day. I did have this issue a month ago and had more information but decided to turn off all schedules due to wanting to progress on a game server. The issue persists, If I run a schedule it will run at the time I designated and at another time around 4 hours before the scheduled time. I do not understand how to troubleshoot this and would love some assistance. I've even tried updating the panel as well as setting the schedule on another server and node, still same issue, seems to have started happening after some time using the panel as it did work for a time. ### Expected Behavior Schedules should run as intended by the cron schedule ### Steps to Reproduce Create any schedule and see when it runs. ### Panel Version 1.0.0-beta10 ### Wings Version 1.0.0-beta4 ### Games and/or Eggs Affected All (Testing on Minecraft Neoforge) ### Docker Image _No response_ ### Error Logs ```bash https://paste.pelistuff.com/anwT panel https://paste.pelistuff.com/tjbX wing 1 https://paste.pelistuff.com/3BFF wing 2 ``` ### Is there an existing issue for this? - [X] I have searched the existing issues before opening this issue. - [X] I have provided all relevant details, including the specific game and Docker images I am using if this issue is related to running a server. - [X] I have checked in the Discord server and believe this is a bug with the software, and not a configuration issue with my specific system.
OVERLORD added the 🟡 medium label 2026-02-05 17:12:59 +03:00
OVERLORD commented 2026-02-05 17:13:04 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Oct 3, 2024):

Make sure your contab and queue worker are setup correctly. Also make sure that there aren't multiple queue workers running. The queue worker was previously called pelicanq or just pelican, it should now be called pelican-queue.

Also note that the schedule cron time (e.g. 0 0 * * *) is always displayed as UTC while Next run and Last run are displayed in your timezone. Just mentioning it to make sure there are no confusions.

@Boy132 commented on GitHub (Oct 3, 2024): Make sure your [contab](https://pelican.dev/docs/panel/panel-setup#crontab-configuration) and [queue worker](https://pelican.dev/docs/panel/panel-setup#setting-up-queue-service) are setup correctly. Also make sure that there aren't multiple queue workers running. The queue worker was previously called `pelicanq` or just `pelican`, it should now be called `pelican-queue`. Also note that the schedule cron time (e.g. `0 0 * * *`) is _always_ displayed as UTC while `Next run` and `Last run` are displayed in your timezone. Just mentioning it to make sure there are no confusions.
OVERLORD commented 2026-02-05 17:13:06 +03:00
Author
Owner
Copy Link

@BrianDLC commented on GitHub (Oct 3, 2024):

Hey, looks like I only have one queue worker and my crontab config matches what the instructions ask for

admin@vmname:/var/www/pelican$ ps aux | grep 'queue:work'

www-data 1401230  3.2  0.1 264048 98544 ?        Ss   Oct02  32:08 /usr/bin/php /var/www/pelican/artisan queue:work --tries=3

apocadm+ 1493898  0.0  0.0   6620  2216 pts/0    S+   12:39   0:00 grep --color=auto queue:work

image

Yes I am aware about the displayed time, they have helped me see the issue. When I have a job set to run at 0 UTC, it runs at 4PM EST and again at 8PM EST, I can see its going to run again because it lets me know it plans to run at 8PM once the 4PM job is done.

I have one job I disabled that shows an example of that below
image

As you can see, it just ran at 9AM, and its planning to run again at 5AM.

@BrianDLC commented on GitHub (Oct 3, 2024): Hey, looks like I only have one queue worker and my crontab config matches what the instructions ask for ``` admin@vmname:/var/www/pelican$ ps aux | grep 'queue:work' www-data 1401230 3.2 0.1 264048 98544 ? Ss Oct02 32:08 /usr/bin/php /var/www/pelican/artisan queue:work --tries=3 apocadm+ 1493898 0.0 0.0 6620 2216 pts/0 S+ 12:39 0:00 grep --color=auto queue:work ``` ![image](https://github.com/user-attachments/assets/f2f350dd-451c-4ec6-9a5c-7a5a978a6fe4) Yes I am aware about the displayed time, they have helped me see the issue. When I have a job set to run at 0 UTC, it runs at 4PM EST and again at 8PM EST, I can see its going to run again because it lets me know it plans to run at 8PM once the 4PM job is done. I have one job I disabled that shows an example of that below ![image](https://github.com/user-attachments/assets/c7afa44e-c06b-4c3f-acdc-5e6d6f108499) As you can see, it just ran at 9AM, and its planning to run again at 5AM.
OVERLORD commented 2026-02-05 17:13:07 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Oct 4, 2024):

Did you change the APP_TIMEZONE in your .env file? It should be set to UTC.

@Boy132 commented on GitHub (Oct 4, 2024): Did you change the `APP_TIMEZONE` in your .env file? It should be set to `UTC`.
OVERLORD commented 2026-02-05 17:13:10 +03:00
Author
Owner
Copy Link

@BrianDLC commented on GitHub (Oct 4, 2024):

No as I have not made any additional changes to the config outside of the panel GUI, as in, after setting up the panel/nodes after following the guide on the pelican panel docs I made no other changes to them.

@BrianDLC commented on GitHub (Oct 4, 2024): No as I have not made any additional changes to the config outside of the panel GUI, as in, after setting up the panel/nodes after following the guide on the pelican panel docs I made no other changes to them.
OVERLORD commented 2026-02-05 17:13:14 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Oct 10, 2024):

Please try the changes from here and see if the problem still occurs.

@Boy132 commented on GitHub (Oct 10, 2024): Please try the changes from [here](https://github.com/pelican-dev/panel/compare/main...Boy132:pelican-panel:fix/schedule-timezones) and see if the problem still occurs.
OVERLORD commented 2026-02-05 17:13:16 +03:00
Author
Owner
Copy Link

@BrianDLC commented on GitHub (Oct 10, 2024):

Alright I've made the changes, will set up some schedules to test.

@BrianDLC commented on GitHub (Oct 10, 2024): Alright I've made the changes, will set up some schedules to test.
OVERLORD commented 2026-02-05 17:13:18 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Oct 23, 2024):

@BrianDLC Were you able to test the changes? Is the issue still occurring?

@Boy132 commented on GitHub (Oct 23, 2024): @BrianDLC Were you able to test the changes? Is the issue still occurring?
OVERLORD commented 2026-02-05 17:13:21 +03:00
Author
Owner
Copy Link

@BrianDLC commented on GitHub (Oct 23, 2024):

After testing, I would have to say that this change did resolve the issue, thanks!

From: Boy132 @.>
Sent: Wednesday, October 23, 2024 3:39 PM
To: pelican-dev/panel @.>
Cc: Brian A De La Cruz @.>; Mention @.>
Subject: Re: [pelican-dev/panel] Schedules running at 2 different times. (Issue #605)

@BrianDLChttps://github.com/BrianDLC Were you able to test the changes? Is the issue still occurring?

—
Reply to this email directly, view it on GitHubhttps://github.com/pelican-dev/panel/issues/605#issuecomment-2433283488, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHPJO57MQWW3XIACRKFI2ZLZ473PXAVCNFSM6AAAAABPKDZAZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZTGI4DGNBYHA.
You are receiving this because you were mentioned.Message ID: @.***>

@BrianDLC commented on GitHub (Oct 23, 2024): After testing, I would have to say that this change did resolve the issue, thanks! ________________________________ From: Boy132 ***@***.***> Sent: Wednesday, October 23, 2024 3:39 PM To: pelican-dev/panel ***@***.***> Cc: Brian A De La Cruz ***@***.***>; Mention ***@***.***> Subject: Re: [pelican-dev/panel] Schedules running at 2 different times. (Issue #605) @BrianDLC<https://github.com/BrianDLC> Were you able to test the changes? Is the issue still occurring? — Reply to this email directly, view it on GitHub<https://github.com/pelican-dev/panel/issues/605#issuecomment-2433283488>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AHPJO57MQWW3XIACRKFI2ZLZ473PXAVCNFSM6AAAAABPKDZAZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMZTGI4DGNBYHA>. You are receiving this because you were mentioned.Message ID: ***@***.***>
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label 🟡 medium
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#165
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?