SOLVED

MCAS Collector - RHEL 8.x - Docker Issues

%3CLINGO-SUB%20id%3D%22lingo-sub-1793982%22%20slang%3D%22en-US%22%3EMCAS%20Collector%20-%20RHEL%208.x%20-%20Docker%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1793982%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20all%2C%3C%2FP%3E%3CP%3EI'm%20trying%20to%20deploy%20the%20MCAS%20log%20collector%20on%20RHEL%208.1%20with%20no%20luck.%26nbsp%3B%3C%2FP%3E%3CP%3EFirst%2C%20the%20repo%20that%20is%20being%20added%20via%20the%20script%20does%20not%20have%20docker-ce%20for%208.1%20-%20this%20was%20easily%20fixed%20by%20manually%20adjusting%20the%20repo%20file%20and%20point%20it%20to%20%2F8%20instead%20of%20%2F8.1%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20the%20docker%20does%20not%20start%20up%20correctly%20as%20I'm%20getting%20the%20following%20in%20the%20docker%20logs%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CPRE%20class%3D%22lia-code-sample%20language-applescript%22%3E%3CCODE%3E05%3A58%3A08%2C537%20%7C-INFO%20in%20ch.qos.logback.classic.joran.JoranConfigurator%4067784306%20-%20Registering%20current%20configuration%20as%20safe%20fallback%20point%0A%0AReading%20configuration...%0AError%20reading%20configuration.%0ARemoving%20sensitive%20configuration%0AStarting%20services%0A2020-10-16%2005%3A58%3A14%2C265%20CRIT%20Supervisor%20running%20as%20root%20(no%20user%20in%20config%20file)%0A2020-10-16%2005%3A58%3A14%2C265%20INFO%20Included%20extra%20file%20%22%2Fetc%2Fsupervisor%2Fconf.d%2Fsupervisord.conf%22%20during%20parsing%0A2020-10-16%2005%3A58%3A14%2C272%20INFO%20RPC%20interface%20'supervisor'%20initialized%0A2020-10-16%2005%3A58%3A14%2C272%20CRIT%20Server%20'unix_http_server'%20running%20without%20any%20HTTP%20authentication%20checking%0A2020-10-16%2005%3A58%3A14%2C272%20INFO%20supervisord%20started%20with%20pid%20911%0A2020-10-16%2005%3A58%3A15%2C275%20INFO%20spawned%3A%20'cron'%20with%20pid%20914%0A2020-10-16%2005%3A58%3A15%2C276%20INFO%20spawned%3A%20'rsyslog'%20with%20pid%20915%0A2020-10-16%2005%3A58%3A15%2C279%20INFO%20spawned%3A%20'ftpd'%20with%20pid%20916%0A2020-10-16%2005%3A58%3A15%2C287%20INFO%20spawned%3A%20'columbus'%20with%20pid%20917%0A2020-10-16%2005%3A58%3A16%2C966%20INFO%20success%3A%20cron%20entered%20RUNNING%20state%2C%20process%20has%20stayed%20up%20for%20%26gt%3B%20than%201%20seconds%20(startsecs)%0A2020-10-16%2005%3A58%3A16%2C966%20INFO%20success%3A%20rsyslog%20entered%20RUNNING%20state%2C%20process%20has%20stayed%20up%20for%20%26gt%3B%20than%201%20seconds%20(startsecs)%0A2020-10-16%2005%3A58%3A16%2C966%20INFO%20success%3A%20ftpd%20entered%20RUNNING%20state%2C%20process%20has%20stayed%20up%20for%20%26gt%3B%20than%201%20seconds%20(startsecs)%0A2020-10-16%2005%3A58%3A16%2C966%20INFO%20success%3A%20columbus%20entered%20RUNNING%20state%2C%20process%20has%20stayed%20up%20for%20%26gt%3B%20than%201%20seconds%20(startsecs)%3C%2FCODE%3E%3C%2FPRE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20try%20with%20an%20Ubuntu%2018.04%20next.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1793982%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3ECloud%20App%20Security%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-1801603%22%20slang%3D%22en-US%22%3ERe%3A%20MCAS%20Collector%20-%20RHEL%208.x%20-%20Docker%20Issues%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1801603%22%20slang%3D%22en-US%22%3EI've%20given%20up%20on%20RHEL%208.1%20for%20this%20and%20installed%20the%20collector%20successfully%20on%20Ubuntu%2018.04%3C%2FLINGO-BODY%3E
New Contributor

Hi all,

I'm trying to deploy the MCAS log collector on RHEL 8.1 with no luck. 

First, the repo that is being added via the script does not have docker-ce for 8.1 - this was easily fixed by manually adjusting the repo file and point it to /8 instead of /8.1

 

However the docker does not start up correctly as I'm getting the following in the docker logs

 

 

05:58:08,537 |-INFO in ch.qos.logback.classic.joran.JoranConfigurator@67784306 - Registering current configuration as safe fallback point

Reading configuration...
Error reading configuration.
Removing sensitive configuration
Starting services
2020-10-16 05:58:14,265 CRIT Supervisor running as root (no user in config file)
2020-10-16 05:58:14,265 INFO Included extra file "/etc/supervisor/conf.d/supervisord.conf" during parsing
2020-10-16 05:58:14,272 INFO RPC interface 'supervisor' initialized
2020-10-16 05:58:14,272 CRIT Server 'unix_http_server' running without any HTTP authentication checking
2020-10-16 05:58:14,272 INFO supervisord started with pid 911
2020-10-16 05:58:15,275 INFO spawned: 'cron' with pid 914
2020-10-16 05:58:15,276 INFO spawned: 'rsyslog' with pid 915
2020-10-16 05:58:15,279 INFO spawned: 'ftpd' with pid 916
2020-10-16 05:58:15,287 INFO spawned: 'columbus' with pid 917
2020-10-16 05:58:16,966 INFO success: cron entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-16 05:58:16,966 INFO success: rsyslog entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-16 05:58:16,966 INFO success: ftpd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2020-10-16 05:58:16,966 INFO success: columbus entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

 

 

I'll try with an Ubuntu 18.04 next.

1 Reply
best response confirmed by Marc-R (New Contributor)
Solution
I've given up on RHEL 8.1 for this and installed the collector successfully on Ubuntu 18.04