Conductor Application Failure

Question

All,
I have seen this error several times before on different Conductors.  What causes this issue and do we really need to restart the Conductor each time?
"An unexpected software error was detected in python /share/python/site-packages/ni/conferencefactory/controller/application_watchdog.pyc2>&1: 1"       
This appears as a warning on the Conductor as "Application Failed".
Thank you,
Justin Ferello
Technical Support Specialist
KBZ, a Cisco Authorized Distributor
http://www.kbz.com
e/v: [email protected]       

Answer 1

Hi, I have the same alert:
But no impact on the application. Everything is working perfectly.
Software version XC2.3
Software build 308748
Software release date 2014-04-10 14:05
Software ID s42800
please, Any ideas on the root cause or fix? it really looks like a file system error.
I didn't restart the server as it is working without issues.
This is the event log:
syslog-ng[17373]: Configuration reload request received, reloading configuration;
2014-12-23T19:12:13+08:00
supervisor: Level="INFO" Event="Alarm Raised" Id="15019" UUID="1a18bfa6-f822-11e1-b0db-c35cb1b8e3e5" Severity="error" Detail="Application failed: An unexpected software error was detected in : " UTCTime="2014-12-23 11:12:13,267"
2014-12-23T19:11:25+08:00
conferencefactory.controller: Level="WARNING" Event="An error occurred while communicating externally, retrying." Detail="Error=\"Connection disconnected unexpectedly, Message=\"{ message_type : flex.resource.query, params : {'authenticationPassword': 'hidden', 'authenticationUser': u'conductoradmin'} }\" Conference Bridge=\"a982c4f4-316c-11e4-a654-0050569d05d9\"" Conference_bridge_address="10.22.77.241" Conference_bridge_UUID="a982c4f4-316c-11e4-a654-0050569d05d9" UTCTime="2014-12-23 11:11:25,284"
2014-12-23T19:10:04+08:00
conferencefactory.controller: Level="WARNING" Event="An error occurred while communicating externally, retrying." Detail="Error=\"Connection disconnected unexpectedly, Message=\"{ message_type : flex.resource.query, params : {'authenticationPassword': 'hidden', 'authenticationUser': u'conductoradmin'} }\" Conference Bridge=\"a982c4f4-316c-11e4-a654-0050569d05d9\"" Conference_bridge_address="10.22.77.241" Conference_bridge_UUID="a982c4f4-316c-11e4-a654-0050569d05d9" UTCTime="2014-12-23 11:10:04,825"
2014-12-23T19:10:04+08:00
kernel: EXT3-fs (sda7): error: remounting filesystem read-only
2014-12-23T19:10:04+08:00
kernel: EXT3-fs (sda7): error: ext3_journal_start_sb: Detected aborted journal
2014-12-23T19:10:04+08:00
kernel: Aborting journal on device sda7.
2014-12-23T19:10:04+08:00
kernel: end_request: I/O error, dev sda, sector 5042509
2014-12-23T19:10:04+08:00
kernel: sd 0:0:0:0: timing out command, waited 180s
2014-12-23T19:10:04+08:00
kernel: end_request: I/O error, dev sdb, sector 229575168
2014-12-23T19:10:04+08:00
kernel: sd 0:0:1:0: timing out command, waited 180s
2014-12-23T19:10:04+08:00
kernel: end_request: I/O error, dev sdb, sector 229574208
2014-12-23T19:10:04+08:00
kernel: sd 0:0:1:0: timing out command, waited 180s
2014-12-23T19:10:04+08:00
kernel: end_request: I/O error, dev sdb, sector 240257768
2014-12-23T19:10:04+08:00
kernel: sd 0:0:1:0: timing out command, waited 180s
2014-12-23T19:10:04+08:00
kernel: Buffer I/O error on device sdb2, logical block 26071843