Subject: Re: [asterisk-users] Anyone ever experienced a crash where Asterisk
debug output a line with all nulls
On 14.08.19 at 18:12 Dan Cropp wrote:
>
>> Maybe because the machine is performing a file system check on some other
>> partitions in parallel and it's slowed down therefore
On 14.08.19 at 18:12 Dan Cropp wrote:
Maybe because the machine is performing a file system check on some other
partitions in parallel and it's slowed down therefore?
Wouldn't /var/log/syslog show something like this if it's happening in parallel?
Well, it was just speculation. Is it even
Thank you.
Appreciate the help on this.
Dan
From: asterisk-users On Behalf Of
John Runyon
Sent: Wednesday, August 14, 2019 10:51 AM
To: Asterisk Users Mailing List - Non-Commercial Discussion
Subject: Re: [asterisk-users] Anyone ever experienced a crash where Asterisk
debug output a line
> Did I get it correctly: the last line in the log before asterisk starts again
> after the reboot is the [nul]-line? If so, are you probably using ext4 or
> maybe reiserfs? I know of this problem if the machine crashes, open files can
> end up like described. AFAIK it's a file system bug!
Agree with Michael, this sounds like an OS crash to me. Given that you're
not seeing anything in the logs, it's likely that by the time the crash
occurs, the kernel is unable to write to disk, so the only real way to get
info is to be looking at the console when it crashes. See also:
On 14.08.19 at 16:26 Dan Cropp wrote:
> We have a customer where their VM running Asterisk appears to have crashed.
> Fortunately, we had some debugging enabled.
> The asterisk messages file has this... (in notepad+ the blank line in the
> middle is all [NUL][NUL] [NUL][NUL])
>
> [08/12
We have a customer where their VM running Asterisk appears to have crashed.
Fortunately, we had some debugging enabled.
The asterisk messages file has this... (in notepad+ the blank line in the
middle is all [NUL][NUL] [NUL][NUL])
[08/12 15:30:55.880] VERBOSE[6920] app_mixmonitor.c: Begin
