On startup of multiple of the multicloud pods an error similar to the error below occurs.

This is caused by the followinng configs

./charts/multicloud-lenovo/resources/config/log/log.yml:37: maxBytes: 1024*1024*50
./charts/multicloud-pike/resources/config/log/log.yml:37: maxBytes: 1024*1024*50
./charts/multicloud-vio/resources/config/log/log.yml:28: maxBytes: 52428800
./charts/multicloud-azure/resources/config/log/log.yml:28: maxBytes: 52428800
./charts/multicloud-starlingx/resources/config/log/log.yml:37: maxBytes: 1024*1024*50
./charts/multicloud-windriver/resources/config/log/log.yml:37: maxBytes: 1024*1024*50
./charts/multicloud-fcaps/resources/config/log/log.yml:37: maxBytes: 1024*1024*50

these should be 52428800 instead of 1024*1024*50

• • • Starting uWSGI 2.0.18 (64bit) on [Thu Oct 10 12:03:59 2019] ***
      compiled with version: 8.3.0 on 04 September 2019 13:46:41
      os: Linux-4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018
      nodename: dev-multicloud-multicloud-fcaps-658f46b595-95xkt
      machine: x86_64
      clock source: unix
      pcre jit disabled
      detected number of CPU cores: 16
      current working directory: /opt/fcaps
      detected binary path: /usr/local/bin/uwsgi
      your memory page size is 4096 bytes
      detected max file descriptor number: 1048576
      lock engine: pthread robust mutexes
      thunder lock: disabled (you can enable it with --thunder-lock)
      uWSGI http bound on :9011 fd 4
      uwsgi socket 0 bound to TCP address 127.0.0.1:43055 (port auto-assigned) fd 3
      Python version: 3.7.4 (default, Aug 21 2019, 00:19:59) [GCC 8.3.0]
      Python main interpreter initialized at 0x55b011506a60
      python threads support enabled
      your server socket listen backlog is limited to 100 connections
      your mercy for graceful operations on workers is 60 seconds
      mapped 364600 bytes (356 KB) for 4 cores
    • Operational MODE: preforking ***
      /usr/local/lib/python3.7/site-packages/onaplogging/logWatchDog.py:29: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
      return yaml.load(f.read())
      Traceback (most recent call last):
      File "/usr/local/lib/python3.7/logging/config.py", line 562, in configure
      handler = self.configure_handler(handlers[name])
      File "/usr/local/lib/python3.7/logging/config.py", line 735, in configure_handler
      result = factory(**kwargs)
      File "/usr/local/lib/python3.7/logging/handlers.py", line 146, in _init_
      if maxBytes > 0:./charts/multicloud-starlingx/resources/config/log/log.ymlvim
      TypeError: '>' not supported between instances of 'str' and 'int'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/onaplogging/logWatchDog.py", line 83, in _yamlConfig
config.dictConfig(dictConfig)
File "/usr/local/lib/python3.7/logging/config.py", line 799, in dictConfig
dictConfigClass(config).configure()
File "/usr/local/lib/python3.7/logging/config.py", line 570, in configure
'%r' % name) from e
ValueError: Unable to configure handler 'fcaps_handler'
/usr/local/lib/python3.7/site-packages/onaplogging/logWatchDog.py:29: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
return yaml.load(f.read())
WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0x55b011506a60 pid: 9 (default app)

• • • uWSGI is running in multiple interpreter mode ***
      spawned uWSGI master process (pid: 9)
      spawned uWSGI worker 1 (pid: 33, cores: 1)
      spawned uWSGI worker 2 (pid: 34, cores: 1)
      spawned uWSGI worker 3 (pid: 35, cores: 1)
      spawned uWSGI worker 4 (pid: 36, cores: 1)
      spawned uWSGI http 1 (pid: 37)
      Traceback (most recent call last):
      File "/usr/local/lib/python3.7/site-packages/kombu/utils/objects.py", line 42, in _get_
      return obj._dict_[self.__name__]
      KeyError: 'data'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
File "/usr/local/lib/python3.7/logging/config.py", line 562, in configure
handler = self.configure_handler(handlers[name])
File "/usr/local/lib/python3.7/logging/config.py", line 735, in configure_handler
result = factory(**kwargs)
File "/usr/local/lib/python3.7/logging/handlers.py", line 146, in _init_
if maxBytes > 0:
TypeError: '>' not supported between instances of 'str' and 'int'

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "/usr/local/lib/python3.7/site-packages/onaplogging/logWatchDog.py", line 83, in _yamlConfig
config.dictConfig(dictConfig)
File "/usr/local/lib/python3.7/logging/config.py", line 799, in dictConfig
dictConfigClass(config).configure()
File "/usr/local/lib/python3.7/logging/config.py", line 570, in configure
'%r' % name) from e
ValueError: Unable to configure handler 'fcaps_handler'
[2019-10-10 12:04:00,991: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Trying again in 2.00 seconds...

[2019-10-10 12:04:03,002: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Trying again in 4.00 seconds...

[2019-10-10 12:04:07,015: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.
Trying again in 6.00 seconds...

[2019-10-10 12:04:13,033: ERROR/MainProcess] consumer: Cannot connect to amqp://guest:**@127.0.0.1:5672//: [Errno 111] Connection refused.