MID Server Issue

sahityamalipedd
Kilo Contributor

Hi,

Mid server is not executing ecc queue output records. ECC queue records are in stuck in ready state. MID Server is Up state. Checked mid server logs only heart beat probe is executed. There are no logs related to other queue records.

Please help me on this.

Thanks in advance.

10 REPLIES 10

Hi 

this solution is related to input in ready state, but mine is output in ready state.

 

Harsh Vardhan
Giga Patron

this is just a workaround. 

 

can you try to get one ecc queue record which has not executed or processed . 

give a try with below step and see if it's working or not. 

 

  1. Get the sys id of the ecc_queue record
  2. Go to "System Definition > Scripts - Background"
  3. Run the following script, replace <ecc_queue_sys_id> with the correct sys ID.`

 

var eccRecord = new GlideRecord('ecc_queue');
eccRecord.get(‘<ecc_queue_sys_id>');
var sp = new SncSensorProcessor(eccRecord);
sp.process(); 
 

I have created an ecc queue output record with

agent: midserver dev

Topic: Command

Name: ls -l

executed the code and got below error

Evaluator: java.lang.NullPointerException
   Caused by error in script at line 3

      1: var eccRecord = new GlideRecord('ecc_queue');
      2: eccRecord.get('48782b96db303b006a0dfd371d96198c');
==>   3: var sp = new SncSensorProcessor(eccRecord);
      4: sp.process(); 

com.snc.core_automation.Probe.getPayload(Probe.java:279)
com.snc.core_automation.Probe.createProbeResponse(Probe.java:262)
com.snc.discovery.SensorProcessor.init(SensorProcessor.java:154)
com.snc.discovery.SensorProcessor.<init>(SensorProcessor.java:117)
sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
java.lang.reflect.Constructor.newInstance(Constructor.java:423)
org.mozilla.javascript.MemberBox.newInstance(MemberBox.java:184)

not exactly sure here why this error came. 

 

but to set the state as processed , there is OOTB business rule, which set the state to processed 

BR name : Set State ( which is running on ecc queue table)

Yes it is there it has a condition current.processed.changes() && !current.processed.nil().

And also it is output record. Generally sensor will be there for input record.