Carolyn Beeton wrote:
-----Original Message-----
From: Laurentiu Ceausescu [mailto:[email protected]]
Sent: Friday, November 06, 2009 10:28 AM
The problem gets reproduced only after a fresh install and
when "Apply" button from Alarms Configuration page is not pressed.
Laurentiu
That makes it sound like a sipXconfig issue - perhaps the xmlrpc request
to generate the alarm is failing? or maybe something is not being
replicated automatically on startup (maybe alarm-config.xml?)? If it is
reproducible, then create an issue with snapshot attached.
Carolyn
I followed the following scenario:
- I made a fresh install and I started sipX;
- looked in log directory, sipXalarms.log was missing;
- I thrown few alarms (logging in with wrong credentials for a few
times) but sipXalarms.log is still missing;
So, if the alarms log doesn't exist that doesn't mean we don't have
alarms - we have alarms but they aren't logged.
And I think it's ok that sipXconfig will throw UserException based on
404 error code.
- after "Apply" button is pressed (from Alarms Configuration page),
sipXalarms.log is created and any alarm is logged;
In fact when "Apply" button is pressed, sipXconfig send a xmlRpc
"reloadAlarms" command to the supervisor.
I guess that is the reason that sipXalarms.log is created.
Note that after this xmlRpc call the issue is unreproducible (the alarms
log is created for every sipX re-start).
sipXalarms.log should have been created when sipX is started. If
sipXconfig does not find it - then it's ok to display error message.
I opened http://track.sipfoundry.org/browse/XX-6970 for that.
Laurentiu
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
