Docker container do not start after having changed network configuration

fine

#1

i have launched the latest docker manageiq (20180404) container.
it was working fine.

i had the “strange” idea to change network configuration, adding a second network interface, and removing it after.

Now the container do not start and i don’t know why since the network conf looks like before.

The log error is:

Error something seems wrong, we need at least two parameters to check service status
== Checking MIQ database status ==
** DB already initialized

{"@timestamp":“2018-04-05T15:47:32.690234 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for evm.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.690894 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for vim.log has been changed to [WARN]”}
{”@timestamp”:“2018-04-05T15:47:32.691549 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for rhevm.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.692014 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for aws.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.692380 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for kubernetes.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.692814 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for datawarehouse.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.693234 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for container_monitoring.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.693607 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for scvmm.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.693993 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for api.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.694350 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for fog.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.694738 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for azure.log has been changed to [WARN]”}
{”@timestamp”:“2018-04-05T15:47:32.695077 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for lenovo.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.695500 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for websocket.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.695935 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for vcloud.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:32.696293 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(Vmdb::Loggers.apply_config) Log level for nuage.log has been changed to [INFO]”}
{”@timestamp”:“2018-04-05T15:47:33.068484 “,“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“info”,“message”:“MIQ(SessionStore) Using session_store: ActionDispatch::Session::MemCacheStore”}
{”@timestamp”:"2018-04-05T15:47:33.451305 ",“hostname”:“manageiq”,“pid”:7,“tid”:“3a7140”,“level”:“warning”,“message”:“127.0.0.1:11211 failed (count: 0) Errno::ECONNREFUSED: Connection refused - connect(2) for “127.0.0.1” port 11211”}

/usr/local/lib/ruby/gems/2.3.0/gems/dalli-2.7.6/lib/dalli/ring.rb:45:in server_for_key': No server available (Dalli::RingError) from /usr/local/lib/ruby/gems/2.3.0/gems/dalli-2.7.6/lib/dalli/client.rb:236:inalive!’
from /usr/local/lib/ruby/gems/2.3.0/gems/dalli-2.7.6/lib/rack/session/dalli.rb:19:in initialize' from /usr/local/lib/ruby/gems/2.3.0/gems/actionpack-5.0.6/lib/action_dispatch/middleware/session/abstract_store.rb:32:ininitialize’

il looks like a memcache network connectivity problem.

What should i modify to make it start again?

Regards.


#2

I am facing the same issue. Any news on this?