Highlighted
pablis
New Member.
247 views

BSM Support Tip: Errors in capture.log after upgrading RUM

After upgrading, capture.log shows errors like the following:

 

2015-03-24 14:26:34 [140336961672960] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:63> - Could not find channel rum-poor-requests

2015-03-24 14:26:39 [140336961672960] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:63> - Could not find channel rum-streaming

 

RUM at the moment does not contain any application definition, therefore probe has nothing to publish to channels and

since none of the applications is being monitored the channel directories rum-pages, rum-actions etc. are not created by default under /var/spool/rum_probe/channels,

they are created when Probe has to publish some data to channels.

 

When the Engine requests channels data, Probe is trying to read non-existing channel directories.

As soon as you will assign/sync any application to probe and start getting traffic for monitored application, the problem should be gone.

 

 

HP Support

If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Labels (1)
0 Likes
1 Reply
Learner185 Valued Contributor.
Valued Contributor.

Re: BSM Support Tip: Errors in capture.log after upgrading RUM

Dears,

We are having exactly same issue - capture.log is full of errors as shown below. And we have many applications assigned to this probe - actually it was a working probe, we just rebooted the machine and after we started seeing this error.

we reinstall the probe from start but same issue.

The support tip is not working as posted originally here.

So any help fast is highly appreciated.

 

ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-pages
2018-05-03 19:07:37 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-actions
2018-05-03 19:07:38 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-connections
2018-05-03 19:07:38 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-cbd
2018-05-03 19:07:41 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-poor-requests
2018-05-03 19:07:41 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-ud-discovery
2018-05-03 19:07:42 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-streaming
2018-05-03 19:07:42 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-tier-discovery
2018-05-03 19:07:47 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-sessions
2018-05-03 19:07:49 [140158194149120] ERROR webconsole.ChannelsReader <collector/webconsole/ChannelsReader.cpp:64> - Could not find channel rum-components

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.