Sometime around Aug 8-10 my log files (/var/log/asterisk/messages) went to 0. I don't recall exactly, but I think I ran the 6.0.1.74 update around that time. I just noticed last night the messages file was empty because a customer called to complain the FMFM did not ring out to the cell phone as it should (which is usually their cell phone but the logs prove that) and I wanted to look at the CLI output to see what happened, but nothing. Is there a setting in MTE or asterisk to set that verbosity level higher?
Storage is cheap and I like having the ability to go back and look at what happened. Please help turn this back on
-Adam
My mistake
First, I agree with you on the Disk I/O, I actually have a subnet setup just for syslog traffic on my entire server rack and a syslog server taking in all the data. Although this does take a little CPU cycle it does not have much effect on disk I/O.
Second, my mind was focused on MTE and as I hit send I realized this was an asterisk issue in the logger.conf and almost posted a retraction to my post.
I have a long IT background but a not so long VoIP background and even shorter to MTE so I appologize if I sometimes post stupid questions, but the only way we learn is by asking questions and everyones help and patience is always appreciated. I also like to find out how other people handle things becuase, although my way may work, it may not always be most effecient.
-Adam
any time you move a file; to
any time you move a file; to get asterisk to re-create a file pointer to the new file, albeit the same filename, you need to issue 'logger reload' also issued asterisk -rx "logger reload". This makes it possible to start logging again without having to restart the entire asterisk process. As far as the book goes, I think you'd really enjoy reading it. It will make the light come on with how everything interacts.
You can find it
You can find it here:
I'd go for the pdf version - I dont mind reading from screen, and searching is much easier than with the paper version :o)
/Ole
dude, get a book and do some reading here. I recommend TFOT revision 2. The version of PBX Manager's webmin module doesn't have a thing to do with your asterisk log nor does it modify it during an upgrade. You have botched your logrotate somewhere. If your file is zero bytes its probably because you rotated the file and didn't issue a logger reload command, so the file pointer is pointing to a different inode. Restart asterisk until you discover how logger rotate and logger reload work. Also check to make sure you didnt do anything to logger.conf (not maintained by pbxmanager) which specifies what is written to logs.
while you state storage is cheap, disk I/O isn't. If you send too much to get logged then you are creating a bottleneck that will only restrict further as call volume increases. Suddenly you have choppy transcoding, choppy file playback and choppy conference calls because disk i/o is saturated. I would warn against a full debug option until such time its actually needed.
Smith
CTO
BluegrassNet Voice
dCAP