FreePBX | Register | Issues | Wiki | Portal | Support

PBX takes 2 minutes to shut down on reboot


#1

When I ssh in and tell the system to reboot, or I use Admin->System Admin->Power Options->Reboot, the system takes just over 120 seconds to stop responding to ping and shut down before restarting.

It’s probably some kind of housekeeping timeout, but is there a way to shorten the time?

Brand new install and fully upgraded to 12.7.6-1904-1.sng7 if that helps.

Thanks!


(Dave Burgess) #2

The established timeout for waiting for current calls to expire is about 2 minutes. Check the /var/log/asterisk/full log and see what’s is holding you up.


#3

Hmm, I’mm seeing myself login with ssh and type shutdown:
[2019-08-02 07:00:37] VERBOSE[10726] asterisk.c: Remote UNIX connection
[2019-08-02 07:00:37] VERBOSE[8472] asterisk.c: Waiting for inactivity to perform halt…
then lotsa stuff at that same timestamp, then:
[2019-08-02 07:00:37] WARNING[8472] logger: Log queue threshold (1000) exceeded. Discarding new messages.
[2019-08-02 07:00:37] WARNING[10727] logger: Logging resumed. 869 messages discarded.
[2019-08-02 07:01:07] VERBOSE[10726] asterisk.c: Remote UNIX connection
[2019-08-02 07:01:07] VERBOSE[9592] asterisk.c: Ignoring asterisk shutdown request, already in progress.
[2019-08-02 07:01:07] VERBOSE[9592] asterisk.c: Remote UNIX connection disconnected
[2019-08-02 07:01:07] VERBOSE[10720] asterisk.c: Ignoring asterisk shutdown request, already in progress.
[2019-08-02 07:01:07] VERBOSE[10720] asterisk.c: Ignoring asterisk shutdown request, already in progress.
[2019-08-02 07:01:59] ERROR[9604] manager.c: Unable to process manager action ‘login’. Asterisk is shutting down.
[2019-08-02 07:01:59] ERROR[9604] manager.c: Unable to process manager action ‘Logoff’. Asterisk is shutting down.

Then the restart:

[2019-08-02 07:03:50] Asterisk 13.22.0 built by mockbuild @ jenkins7 on a x86_64 running Linux on 2018-07-25 22:30:39 UTC

Note that there was an initial flurry of activity at 07:00:37, then a few things 30 seconds later at 07:01:07, the two manager.c warnings at 07:01:59, but the machine didn’t actually stop responding to ping and reboot till 07:02:37 or thereabouts.

There’s nothing in /var/log/messages in that timeframe:
Aug 2 07:00:29 Chime systemd: Stopping Getty on tty1…
Aug 2 07:03:15 Chime systemd-journald[95]: Received SIGTERM from PID 1 (systemd).

I’ve poked around with emacs and grep in other log files and have not found anything in the 07:02:37 timeframe either, is there some other way I can determine what’s hanging up?

Addenda: When shutting down, the console says: A stop job is running for FreePBX VoIP Server (count-up to 2 mins, 8 seconds)

Thanks!


(Dave Burgess) #4

Those are reasonably normal. Since the system is waiting for inactivity to shut down, there’s no point letting FreePBX log in to Asterisk to poke it some more and become active.

Your syslog thing is peculiar. Something’s happening that causing your syslogs to go nuts. I’d start there.


(system) closed #5

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.