Something in the shutdown triggers a start of a service or doesn't stop in time. Since something is still running the shutdown never completes.

Looking at the screenshot for instance it says "Stopping monitoring of LVM2 mirrors, snapshots etc. using dmeventd or progress polling...".
But there is no acknowledgment [OK] that it has completed.

I'd start looking there.

@jaredbusch said in FreePBX 14 super slow to update and then reboot:

I did not post a bug report there yet as I have no idea if this is reproducible.

I mean I reverted to the snapshot prior to the update and then did all of this. But I reverted because I had exactly this same problem after the update last night.

But I would expect a system to perform the exact same under this scenario.

@scottalanmiller said in Reboot a Yealink phone from the command line of a FreePBX system:

@dbeato said in Reboot a Yealink phone from the command line of a FreePBX system:

@jaredbusch said in Reboot a Yealink phone from the command line of a FreePBX system:

@dbeato said in Reboot a Yealink phone from the command line of a FreePBX system:

some changes to the configuration of the phone.

This is one reason I want it done, but rarely do i need to do it from the PBX itself.

Because I create my own config files, I do not get the magic "rebuild config and reboot" button that the paid EPM has in FreePBX.

Generally I only need this when things happen like today when an internal FreePBX system went unexpectedly offline and was rebooted along with the entire Hyper-V server.

BLF subscriptions seem to not update real well to events like that.

Understood, talking about the Paid EPM, Do you see a reason to use it in the Small Business World?

Loads. Even for internal staff, why walk to a phone if you can reboot from your desk?

I like the exercise. 🙂

In larger teams, you normally have 24x7 staff. So the reboot schedule goes to the current shift to monitor. It's only shops that lack round the clock scheduling that have this as a real issue, and if you don't have 24x7, shouldn't you be outsourcing to a shop that does if you really need that at all? I think that this normally (maybe not always) becomes a problem when you are dealing with layers and layers of other problems like not having enough IT staff to properly staff a department without causing unnecessary cost and risk and choosing not to outsource to an MSP/ITSP that could do this cost effectively.

Seems to be that way.