Ah, very good.
I had the following log levels when the error occured:
info on: trunking, registrar, proxy and supervisor.
Notice on rest.
Do you think it info on these services is ok?
//Ola
2010-02-26 14:38, Scott Lawrence skrev:
On Fri, 2010-02-26 at 14:26 +0100, Ola Samuelson wrote:
So, what you are saying: Next time it suddenly fails...trace a call
before restarting.
I'll try to do that.
If you took a snapshot, you may be able to get what you need from that.
If your logging was set to INFO, then the messages are in that snapshot.
If the logs are at the default NOTICE level, there won't be much there,
and you should change that as soon as you can (it requires restarting
some things, so you'll have to wait for a time when you can briefly
interrupt service).
To analyze a snapshot, create a temporary directory somewhere and untar
the snapshot in it:
tar xzf<snapshot-file>
you can then use sipx-trace as described on the wiki - just add the
option:
-P<snapshot-directory>
where<snapshot-directory> is the directory that was created when you
untarred the file.
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
