Was mostly curious and had the RAM, couldn’t get it working and documentation 
is sparse to put it mildly so left it alone for now.


Matthew Loraditch
Sr. Network Engineer
p: 443.541.1518
w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com
From: Anthony Holloway <avholloway+cisco-v...@gmail.com>
Sent: Friday, April 3, 2020 4:44 PM
To: Matthew Loraditch <mloradi...@heliontechnologies.com>
Cc: Cisco VoIP Group <cisco-voip@puck.nether.net>
Subject: Re: [cisco-voip] UCCX 12.5(1) Docker Engine Not Running

[EXTERNAL]

No, good point.  I'm on the 100 Agent OVA without cloud support, because, well, 
I don't have a need for that.  Seems to me like Cisco made a goof alerting on a 
service which cannot start, and will not start, due to my use of the system.  
I'll tell the TAC engineer this.  Did you configure the cloud connect?  If so, 
what are you using it for.

On Fri, Apr 3, 2020 at 2:50 PM Matthew Loraditch 
<mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>> 
wrote:
Didn’t think about that….

It’s running. Curious did you put enough RAM on for the cloud stuff to run? I’m 
wondering if it’s part of that. Mine has the RAM for the cloud services.


Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
From: Anthony Holloway 
<avholloway+cisco-v...@gmail.com<mailto:avholloway%2bcisco-v...@gmail.com>>
Sent: Friday, April 3, 2020 3:45 PM
To: Matthew Loraditch 
<mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>>
Cc: Cisco VoIP Group 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: Re: [cisco-voip] UCCX 12.5(1) Docker Engine Not Running

[EXTERNAL]

Thanks for the reply Matt.  You could just use the web interface to see if it's 
running or not.  It's not in CCX Seviceability, just plain Seviceability, under 
Network Services.

On Fri, Apr 3, 2020 at 2:43 PM Matthew Loraditch 
<mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>> 
wrote:
If I could get RTMT to load on my one 12.5 install I’d let you know… some crazy 
java error but haven’t had time to deal with TAC on it. Happens on multiple 
PCs, Fresh RTMT installs and all.



Matthew Loraditch​
Sr. Network Engineer
p: 443.541.1518<tel:443.541.1518>
w: www.heliontechnologies.com<http://www.heliontechnologies.com/>
 |
e: mloradi...@heliontechnologies.com<mailto:mloradi...@heliontechnologies.com>
[Helion Technologies]<http://www.heliontechnologies.com/>
[Facebook]<https://facebook.com/heliontech>
[Twitter]<https://twitter.com/heliontech>
[LinkedIn]<https://www.linkedin.com/company/helion-technologies>
From: cisco-voip 
<cisco-voip-boun...@puck.nether.net<mailto:cisco-voip-boun...@puck.nether.net>> 
On Behalf Of Anthony Holloway
Sent: Friday, April 3, 2020 3:27 PM
To: Cisco VoIP Group 
<cisco-voip@puck.nether.net<mailto:cisco-voip@puck.nether.net>>
Subject: [cisco-voip] UCCX 12.5(1) Docker Engine Not Running

[EXTERNAL]

Anyone else running UCCX 12.5(1) and their Docker Engine is Not Running?

It's being caught by CriticalServicesDown and SyslogSeverityMatchFound and 
sending a lot of emails to tech support.

TAC is telling me the Docker Engine is not a UCCX service, so likely just some 
bloat on the UCOS/VOS image, however, that doesn't solve the problem of the 
alerts which are being sent.

I've asked for BU escalation at this point, and am waiting to hear back, but in 
the meantime, it would be good to know if others have already been down this 
path, or simply to put this information out there, for when you deploy your 
first UCCX 12.5(1).
_______________________________________________
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

Reply via email to