Reboot schedule fails
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Reboot schedule fails
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I have set up a reboot schedule for my EAPs. However this seems to fail 100%
[Failed]Reboot schedule regularReboot failed to execute on 3 EAPs and 0 switches and 0 gateways.
What can I do? Where can I find more detailed logs?
Best regards
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
Dear @wuppi,
wuppi wrote
I have set up a reboot schedule for my EAPs. However this seems to fail 100%
[Failed]Reboot schedule regularReboot failed to execute on 3 EAPs and 0 switches and 0 gateways.
To better assist you, may I know the hardware and firmware version of your EAP?
If you can provide the screenshot of your settings about reboot schedule, it will be more helpful.
Please also go to Maintenance to confirm that your system time is set correctly.
Best Regards!
- Copy Link
- Report Inappropriate Content
my detailed setup:
- Linux Software Controller 5.0.30
- EAP615-Wall(EU) v1.0 FW: 1.0.2 Build 20210823 Rel. 3585
- EAP620 HD(EU) v1.0 FW: 1.1.0 Build 20211028 Rel. 68287 (root-mesh-ap)
- EAP225-Outdoor(EU) v1.0 FW: 5.0.5 Build 20210604 Rel. 51118
Controller Status Controller Name: SomeCoolName MAC Address: XX System Time: Feb 15, 202209:40:16 Uptime: 24h 28m 54s Controller Version: 5.0.30
- Copy Link
- Report Inappropriate Content
Dear @wuppi ,
1. Is this the first time the problem has arisen? Or did you set up a reboot schedule that was working and it suddenly stopped working?
2. You can try setting up several reboot schedules and test if they work and also try setting it on separate EAPs to test again.
3. Please also note the connection status of the EAP on the controller when this function is not active.
Best Regards!
- Copy Link
- Report Inappropriate Content
Hi,
1. I think this worked in a controller version pre 5.xx
3. The Controller is online...
regarding the 2nd point: I can try that. But try and error is useless without being able to analyze it somehow. Is there a log somewhere available with more information that that one-liner error message? I strongly believe that there should be a log but I do not know where.
br
Andre
- Copy Link
- Report Inappropriate Content
Dear @wuppi,
wuppi wrote
1. I think this worked in a controller version pre 5.xx
3. The Controller is online...
regarding the 2nd point: I can try that. But try and error is useless without being able to analyze it somehow. Is there a log somewhere available with more information that that one-liner error message? I strongly believe that there should be a log but I do not know where.
It is advisable to try the second step of the troubleshooting process, which will help us to identify the problem.
For more detailed logs, you can find them in the Alerts, Events section.
Best Regards!
- Copy Link
- Report Inappropriate Content
I have exactly the same issue.
I have several different reboot schedules running. The reboot schedule itself works. But somehow, after every reboot of my OC200 it shows the Failed reboot notifications.
It does not matter when the OC200 reboots, it always show the following notifications:
| [Failed]Reboot schedule Weelky Mesh Access Pooint failed to execute on 1 EAPs and 0 switches and 0 gateways. |
Feb 18, 2022 13:10:28 |
old |
| [Failed]Reboot schedule Weelky Access Point failed to execute on 3 EAPs and 0 switches and 0 gateways. |
Feb 18, 2022 13:10:28 |
old |
| [Failed]Reboot schedule Outdoor_Access_Points_(Weekly) failed to execute on 2 EAPs and 0 switches and 0 gateways. |
Feb 18, 2022 13:10:28 |
old |
| [Failed]Reboot schedule Weekly Gateway failed to execute on 0 EAPs and 0 switches and 1 gateways. |
Feb 18, 2022 13:10:28 |
old |
| [Failed]Reboot schedule Gateway_(Weekly) failed to execute on 0 EAPs and 0 switches and 1 gateways. |
Feb 18, 2022 13:10:28 |
old |
| [Failed]Reboot schedule Indoor_Access_Points_(Weekly) failed to execute on 2 EAPs and 0 switches and 0 gateways. |
Feb 18, 2022 13:10:28 |
old |
The interesting part is, I have tried to recreate the reboot schedules apparently it still shows the old schedules.
Se below for my current reboot schedules::
| Weekly Access Point |
Feb 21, 2022 02:00:00 |
xxxx |
||
| Weekly Gateway |
Feb 21, 2022 01:30:00 |
xxxx |
||
| Weekly Mesh Access Pooint |
Feb 21, 2022 02:10:00 |
xxxx |
||
| Weekly Switches |
Feb 21, 2022 01:45:00 |
xxxx |
apparently it does not completely delete the schedules. Maybe it has something to do with the logs full error.
- Copy Link
- Report Inappropriate Content
I created another new reboot schedule and that one works - deleted the old one now.
So that worked around the arisen problem.
- Copy Link
- Report Inappropriate Content
Hi again
so I have to revert my "the workaround does its job" answer. Those freshly created reboot schedules failed now too...
| CONTENT | TIME | ARCHIVE ALL |
|---|
| [Failed]Reboot schedule test failed to execute on 3 EAPs and 0 switches and 0 gateways. |
Feb 19, 2022 17:38:24 |
|
| [Failed]Reboot schedule regularReboot failed to execute on 3 EAPs and 0 switches and 0 gateways. |
Feb 19, 2022 17:38:24 |
- Copy Link
- Report Inappropriate Content
Dear @wuppi ,
The issue you are experiencing sounds unusual, I'd like to escalate your case to the TP-Link support team for further investigation.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Once the issue is addressed or resolved, I'd encourage you to share it with the community.
Thank you so much for your cooperation and patience!
- Copy Link
- Report Inappropriate Content
just to "link" the issues: it looks similar: https://community.tp-link.com/en/business/forum/topic/528492
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2303
Replies: 15
Voters 0
No one has voted for it yet.