I would suggest increasing the bulk size in the spooler to 250. This can be done through the IM GUI for the spooler probe.
Then I would stop the robot service on that machine.
Delete the <nimsoft>\robot\*.rdb files there should be two of these.
Then start the robot service.
this should correct the problem moving forward.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
------------------------------
Original Message:
Sent: 07-15-2019 03:05 PM
From: Miller Grisepe Echagarreta Parra
Subject: boot_time is diffrent to arrival_time
Hi @Gene_Howard
I am checking the spooler probe and I see "spooler: QueueAdmin - expire old messages"
I think that maybe this is the problem, What can I do? delete the queues? or maybe uninstall and install CDM againg? I have 6.34 cdm probe and 7.97 version robot
Original Message:
Sent: 07-15-2019 02:30 PM
From: Gene HOWARD
Subject: boot_time is diffrent to arrival_time
the only thing I can think of is that there was a backup in the spooler on the robot and so the alarm was delayed.
Might want to check the spooler log file for messages about expired messages.
If you see that you can increase the bulk size and see if that helps.
the spooler bulk size defaults to 1 and on some robots can cause a slowdown in the delivery of alarms.
------------------------------
Gene Howard
Principal Support Engineer
Broadcom
Original Message:
Sent: 07-15-2019 12:52 PM
From: Miller Grisepe Echagarreta Parra
Subject: boot_time is diffrent to arrival_time
Hi all.
I have a question. I am receiving alarm of "Computer has been rebooted" but I don´t know why the alarm time notification via email it's different the variable $boot_time from the message.
any idea?
thanks for your help.
Best regards.