Loading Profile...
Carousel Hang-Up
Over the last 4 days or so, Carousel (running as a bundle on a CG250) has hung up twice, both times showing only the splash screen on our outgoing video. The second time this happened, I opened Windoze Task Manager, and CarouselDisplayEngine.exe was still int the process list, however it was not taking any cpu cycles (it's normally about 40-50%). In both instances, I rebooted the server to get it back up.
I looked in the TRMS log (in event viewer) , and it appears that it's filling up with a warning that says "Exception when pinging server: No connection could be made because the target machine actively refused it 127.0.0.1:56901". The source for the warning is DisplayEngine.Utils.Rem. I did try pinging the TCP loop-back (127.0.0.1) from a command line and was successful.
This warning is registering in the log approximately every 4 seconds - I don't know when it started since the log appears to have filled up with this warning and is deleting earlier warnings/errors.
Ideas? Should I open a ticket?
I looked in the TRMS log (in event viewer) , and it appears that it's filling up with a warning that says "Exception when pinging server: No connection could be made because the target machine actively refused it 127.0.0.1:56901". The source for the warning is DisplayEngine.Utils.Rem. I did try pinging the TCP loop-back (127.0.0.1) from a command line and was successful.
This warning is registering in the log approximately every 4 seconds - I don't know when it started since the log appears to have filled up with this warning and is deleting earlier warnings/errors.
Ideas? Should I open a ticket?
I’m sad
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hey Nick,
127.0.0.1 is a loop back, so a ping from the command line should always work (unless something is really screwy). The error messages make it sound like your display engine is not able to get any info from the Carousel Server.
Restarting the machine restarts the Carousel Server service and the display engine is able to get what it needs again.
The first thing to do would be open a ticket with TRMS support:
support@trms.com
That way they can beam into your machine and see whats causing the server to go down. Did this start happening after anything specific. Like maybe a dynamic bulletin upload (video, interactive bulletin). These types of slides normally don't cause the server to crash, but its a place to start.
-ray -
Inappropriate?Thanks, Ray.
I tried to ping 127.0.0.1 because that was in the error message. I also successfully pinged the IP of the machine - as you would expect, that was successful too.
We had not done anything specific before this started. We have a couple of dynamic bulletins running, but they've been running for some months with no problem. I did change the background music on the afternoon that we saw the first hang up (mp3s) - not sure if that's relevant or not.
I'll get a tic going with TRMS.
nick -
Inappropriate?The trouble ticket will be best for resolving this issue, but I just wanted to add a comment for the listeners at home.
The 'ping' in question is actually in the communication with the service, we have a command called 'ping' to test communication with the carousel service (sent across TCP port 56901). Thus, this error means the service has stopped for some reason or is no longer communicating on this port.
It is different than a ping on the command line which is testing to see if the machine is reachable at that IP.
CHAMP
EMPLOYEE
