[asterisk-users] Anyone ever experienced a crash where Asterisk debug output a line with all nulls

Dan Cropp dan at amtelco.com
Wed Aug 14 11:12:09 CDT 2019


> 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!

Yes, the last line in in the log before asterisk starts again after the reboot is the [nul]-line.

I believe you are right about the system using ext4 and the [nul]-line  problem

> 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?
syslog has items before asterisk is starting, but once the Asterisk log files show it's starting to completed, /var/log/syslog has nothing.  
Syslog has nothing for about 10 minutes after that.

The strange thing is the customer did a manual restart of Ubuntu 20 minutes later and the same slow startup time happened. 


More information about the asterisk-users mailing list