2.4: Maintenance doesn't works #3626
Comments
|
Not sure if it helps, but I can confirm this on a fresh installation |
|
Same problem here, also when I create the maintenance from the dashboard, it end on a 500 error |
|
Why have you closed the issue, have you fixed your instance ? |
|
@ArthurKnoep, oups bad manipulation on my smartphone, now open ^^ thx for notification |
|
Same issue, can't create any maintenance. |
|
I'm going to investigate this now. |
|
This is weird, I've just created maintenance without issue:
Can someone please try this again and then provide me with your error logs? |
|
@jbrooksuk when trying to create a maintenance I get this 500 error page When I run |
|
@jbrooksuk I just checkout the code on the last revision (2.4) (cache/config/route cleaned) and I have the same issue: But nothing appear on status page. Moreover, I didn't have any errors in apache or php/laravel logs (with PHP 7.2) :( |
|
We have the same problem and I'm running the latest 2.4.0-dev revision as of this post. We have had to resort to using Stickied Incidents. |
|
This is working for me on a new installation, if anyone incorrectly read (as I sadly did) |
|
@pridit Indeed, I confirm, thx! I f I remove "maintenance complete", it works but it's confusing ^^ |
|
I tried removing the completed date/time but on each save it puts it back. I would think that the completed field should really be the end time of the maintenance. Ie, after this time the maintenance will be removed. I edited the database manually to remove the completed_at time, but noticed that on other schedules that I did not view or edit, the scheduled_at time had all changed to now(). |
|
If I leave the |
|
Maintenance not work for me in 2.4 I edit page code, and see missing div class="section-scheduled" in home page This page have this section |
I see that it is currently working for you. May I ask what it was that fixed it? I already tried removing the |
|
Hello, framasoft is not my page, I found the internet to show by example. in my installation 2.4 does not work. I sent an email to framasoft asking the version, reported that they use version 2.3.10 I tried anyway to install 2.3.10 and I could not. Does anyone have the tutorial on how to install 2.3.10? thanks |
After some tests I noticed that the timezone when creating the maintenance event is being inserted incorrectly in the database. in the example below I created the schedule at 12 o'clock to run between 12 and 13 o'clock on 07/13/2019 and it was recorded on the bench as below. Timezone in Cachet is -3, but I verify that the event only appears after a few hours. 7 Maint Maint TEST 0 2019-07-13 15:00:00 2019-07-13 16:00:00 2019-07-12 14:50:57 2019-07-12 14:50:57 Could it be just my confusion or is it some error in the system? |
|
Hello same problem, is there a update for this problem? |
|
Hi all, I found the problem! Please do not set time at "When did this maintenance complete?" Your maintenance event will be shown on status page. |
|
No, thats not the problem. I have test it and this does not help. |
|
That did not solve it for me last time, but somehow it does work right now when I create a maintenance, set it to 'upcoming' and it not having an end date. Do note that editing a maintenance by removing the end date does not work, but creating a new maintenance and not filling in the end date does make the maintenance appear on the homepage. |
This Work for me... Thanks. The Email to subscribers users when schendule mainteinance still does not work :-( |
That is being worked on in #3687 |
|
@Pimorez @MichaelOrtnerINFO
|
|
@mbrother2 we have just test this, if we create a maintenance at 12:00 clock then the item is hidden on the status page on the admin panel i can see it, but it will be not show on the status page. the problem is still there |
|
Fixable as follows. In Models - Schedule.php - remove the following line. Now it will still show completed maintenance. However, it will now never be removed. If someone wants to make a proper replacement to this line, so it shows future completed maintenance but not already completed maintenance. |
thanks |
|
thank you very much! That has resolved the problem! |
|
so now i must ask the next question, is there a workaround, if the maintenance arrived at the date, where it should be to make automatically create a new incident? On the stable versions there will be created automatically. |
|
@MichaelOrtnerINFO Im sick right but I need something similar for work so ill be trying that monday. |
|
@Korthoutrody Did you maybe already find a way to get the incident creation working as it does on stable releases? |
|
I added my own query in the statuspage controller to show all historic
schedules in the incident timeline.
…On Thu, 25 Jul 2019, 12:47 realraphi, ***@***.***> wrote:
@Korthoutrody <https://github.com/Korthoutrody> Did you maybe already
find a way to get the incident creation working as it does on stable
releases?
Your workaround is pretty helpful, but it's probably not ideal for
documentation of completed schedules since it'll get cluttered from my
point of view.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3626?email_source=notifications&email_token=AK5KRY22XWLBMZG7NJMJS5TQBGAEDA5CNFSM4HQMAHW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2ZDOAI#issuecomment-514995969>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AK5KRY2P6VOXRXBAWPIRLM3QBGAEDANCNFSM4HQMAHWQ>
.
|
|
Maybe this helps someone, but I extended the Schedule Controller to automatically create a new incident when creating a scheduled maintenance. I'm aware that in this example data won't get validated properly. First, we need to import the Incident model: And then the details from the schedule form get assigned to a new array data, from which a new incident will be created: public function addScheduleAction()
{
try {
execute(new CreateScheduleCommand(
Binput::get('name'),
Binput::get('message', null, false, false),
Binput::get('status', Schedule::UPCOMING),
Binput::get('scheduled_at'),
Binput::get('completed_at'),
Binput::get('components', []),
Binput::get('notify', false)
));
$data = [
'user_id' => 1,
'name' => Binput::get('name'),
'message' => Binput::get('message', null, false, false),
'status' => 4,
'notify' => 0,
'visible' => 1,
'stickied' => false,
'component_id' => 0
];
if (Binput::get('completed_at') == "") {
$data['occurred_at'] = Binput::get('scheduled_at') . ':00';
} else {
$data['occurred_at'] = Binput::get('completed_at') . ':00';
}
// Create a new incident
$incident = Incident::create($data);
} catch (ValidationException $e) {
return cachet_redirect('dashboard.schedule.create')
->withInput(Binput::all())
->withTitle(sprintf('%s %s', trans('dashboard.notifications.whoops'), trans('dashboard.schedule.edit.failure')))
->withErrors($e->getMessageBag());
}
return cachet_redirect('dashboard.schedule')
->withSuccess(sprintf('%s %s', trans('dashboard.notifications.awesome'), trans('dashboard.schedule.add.success')));
}It's not pretty and just some quick code, but it works.
|
|
New 2.4.0-dev today installation. Maintenanche request screenshot Here's the error in laravel.log: the SQLSTATE: and the Debug Error screenshot tnx, |
|
Same here |
|
Works for me. |
|
@TheBags @clmssz |
|
I got the same issue with 2.4. I would like to have a solution for this. Has anyone found this? Or when i expect to get this fixed? |
|
There are several issues gathered in this thread. Mine also started when I activated the email notifications. Once I did this email notifications would be sent but the maintenance would not be created in Cachet (error 500). Looking at the Laravel logs, I saw: After a search, installing |
|
This is caused by the removal of the "reserved" column: |
|
I have got a fresh installation of Cachet version 2.4.0-dev, I am not able to notify user (email) for scheduled maintenance. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
and others
Hello,
In 2.4 (last commit as this day), maintenance seems doesn't works.
I try to insert a maintenance event between 28 & 31 May 2019 with differents status and no maintenance are showed on status page.
Best regards,
The text was updated successfully, but these errors were encountered: