I found this writeup in an old case:
This message can be reported by ASE when there is a shortage of alarms. It
occurs when ASE removes an alarm (to free it so that it can be reused), but the
alarm is not present. This can be considered a minor corruption of internal ASE
structures (not data, to be clear).
In most cases this is seen as a harmless message. However, there is a small percentage of reports where first seeing the 'uaremove' message is followed at some time by a stacktrace, further error messages and potentially ASE becoming unresponsive. In particular, this sequence may be seen:
kernel uaremove: alarm id 0 not within range
kernel uasetalarm: no more alarms available
server Error: 11006,
Severity: 20, State: 1
server Unable to set a kernel alarm; timerange manager is unable to run.
followed by stacktrace containing
rg_alarm_adjacent_range
Recommendations when message
"kernel uaremove: alarm id 0 not within range" is seen:
- immediately
increase 'number of alarms' significantly
- check sp_monitorconfig regularly
to track if there are free alarms and if you get close to 100% in use, raise it
again
- reboot ASE when it is convenient, the messages may not fully go away
until ASE is rebooted
Resolution
Generally a harmless message caused by a shortage of alarms. Raise 'number of alarms' and reboot ASE.