Hi Abraham and Zhipeng Hope to join you. And I'll update to you once I make any progress.

Thanks again Zhipeng, Ran!

Looks like the manifest that configures and starts the collectd process is failing. Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause. # Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error * # get the collectd startup failure logs cat /var/log/daemon.log | grep collectd one startup block is fine ; start to exit should show the error. Eric MacDonald

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

That's interesting. It looks like the python plugin manager for collectd is missing yet the 'network' on of the same is ok. Please execute this command to see what related packages exists (or are missing) rpm -qa | grep collect Eric.

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:25 AM To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Hi Eric,

Thanks for your comment!! Could you help further check the error I saw below? ============================================================================= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! =============================================================================== ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ======================================================================

Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Looks like the manifest that configures and starts the collectd process is failing.

Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause.

# Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error *

# get the collectd startup failure logs cat /var/log/daemon.log | grep collectd

one startup block is fine ; start to exit should show the error.

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

That looks ok, I'll continue to investigate ... stay tuned

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:47 AM To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

controller-0:~# rpm -qa | grep collect libcollection-0.6.2-27.el7.x86_64 openstack-ceilometer-collector-9.0.1-1.tis.3.noarch collectd-extensions-1.0-0.tis.1.x86_64 collector-1.0-24.tis.x86_64 collectd-5.7.1-2.el7.x86_64 puppet-collectd-5.1.0-2.4a3843cgit.el7.noarch python2-debtcollector-1.17.0-1.el7.noarch controller-0:~#

-----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 22:45 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

That's interesting. It looks like the python plugin manager for collectd is missing yet the 'network' on of the same is ok.

Please execute this command to see what related packages exists (or are missing)

rpm -qa | grep collect

Eric.

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:25 AM To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Hi Eric,

Thanks for your comment!! Could you help further check the error I saw below? ====================================================================== ======= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! ====================================================================== ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ======================================================================

Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Looks like the manifest that configures and starts the collectd process is failing.

Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause.

# Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error *

# get the collectd startup failure logs cat /var/log/daemon.log | grep collectd

one startup block is fine ; start to exit should show the error.

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Do we need collected-python package in mirror? -----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月26日 22:25 To: MacDonald, Eric <Eric.MacDonald@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide Hi Eric, Thanks for your comment!! Could you help further check the error I saw below? ============================================================================= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! =============================================================================== ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ====================================================================== Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Looks like the manifest that configures and starts the collectd process is failing. Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause. # Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error * # get the collectd startup failure logs cat /var/log/daemon.log | grep collectd one startup block is fine ; start to exit should show the error. Eric MacDonald

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

I've been able to reproduce the log failure signature with a change to the collectd.conf file The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so Eric.

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:45 AM To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Do we need collected-python package in mirror?

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月26日 22:25 To: MacDonald, Eric <Eric.MacDonald@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Eric,

Thanks for your comment!! Could you help further check the error I saw below? ============================================================================= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! =============================================================================== ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ======================================================================

Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Looks like the manifest that configures and starts the collectd process is failing.

Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause.

# Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error *

# get the collectd startup failure logs cat /var/log/daemon.log | grep collectd

one startup block is fine ; start to exit should show the error.

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

---

Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Thanks Eric!! Use below 2 commands, no python.so found. However, RC found that a wrong collectd-5.7.1-2.el7.x86_64.rpm used. Its size is not the same as the one used by Abraham. After used the right collectd-5.7.1-2.el7.x86_64.rpm, no issue anymore The iso can be deloyed successfully on multimode. Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 23:28 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide I've been able to reproduce the log failure signature with a change to the collectd.conf file The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so Eric.

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:45 AM To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Do we need collected-python package in mirror?

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月26日 22:25 To: MacDonald, Eric <Eric.MacDonald@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Eric,

Thanks for your comment!! Could you help further check the error I saw below? ====================================================================== ======= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! ====================================================================== ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ======================================================================

Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Looks like the manifest that configures and starts the collectd process is failing.

Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause.

# Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error *

# get the collectd startup failure logs cat /var/log/daemon.log | grep collectd

one startup block is fine ; start to exit should show the error.

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

---

Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Hi Eric, Sorry for missing your email. Actually, I tried serial times to download this package through download_mirror.sh But could not got it, then I got one through google and download, it seems a little small Than the right one. (Right one is 683K) zhipengl@zhipengl-nuc:~/stx-tools/centos-mirror-tools$ rpm -K collectd-5.7.1-2.el7.x86_64.rpm collectd-5.7.1-2.el7.x86_64.rpm: sha1 md5 OK zhipengl@zhipengl-nuc:~/stx-tools/centos-mirror-tools$ ll collectd-5.7.1-2.el7.x86_64.rpm -rw-rw-r-- 1 zhipengl zhipengl 613644 8月 1 18:24 collectd-5.7.1-2.el7.x86_64.rpm Thanks again! BRs zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月27日 21:08 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Ok, interesting. Glad your unblocked. However, I have to ask. Have you or will you be root causing what caused the build system to choose and include the wrong package ? even one of the same name and version but without the correct fundamental content. Weird. Wonder if that is hitting use elsewhere not or will again in the future ? Eric.

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:54 PM To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Thanks Eric!! Use below 2 commands, no python.so found.

However, RC found that a wrong collectd-5.7.1-2.el7.x86_64.rpm used. Its size is not the same as the one used by Abraham. After used the right collectd-5.7.1-2.el7.x86_64.rpm, no issue anymore The iso can be deloyed successfully on multimode.

Zhipeng

-----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 23:28 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

I've been able to reproduce the log failure signature with a change to the collectd.conf file

The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands

ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so

Eric.

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:45 AM To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Do we need collected-python package in mirror?

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月26日 22:25 To: MacDonald, Eric <Eric.MacDonald@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Eric,

Thanks for your comment!! Could you help further check the error I saw below? ==================================================================== == ======= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! ==================================================================== == ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ==================================================================== ==

Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Looks like the manifest that configures and starts the collectd process is failing.

Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause.

# Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error *

# get the collectd startup failure logs cat /var/log/daemon.log | grep collectd

one startup block is fine ; start to exit should show the error.

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu ss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu ss

---

Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Hi Eric, My initial issue has already been resolved. We should take care when download packages from 3rd party. I will use storyboard to track issue next time. Thanks! Zhipeng 发自我的 iPhone

在 2018年8月1日，21:38，MacDonald, Eric <Eric.MacDonald@windriver.com> 写道：

Hi Zhipeng,

OK, thanks for the follow-up. So, the issue you reported was self-inflicted but only after you experienced a real issue with collectd in terms of your build process. Has that initial issue been resolved ?

In retrospect (generally to the discussion group), is that if you are reporting an issue for debug it would be useful to include in that request anything that was done outside of 'standard process' (like in this case) as that would provide an initial perspective and potential starting point for the investigation.

Cheers,

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Tuesday, July 31, 2018 9:33 PM To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Hi Eric,

Sorry for missing your email. Actually, I tried serial times to download this package through download_mirror.sh But could not got it, then I got one through google and download, it seems a little small Than the right one. (Right one is 683K)

zhipengl@zhipengl-nuc:~/stx-tools/centos-mirror-tools$ rpm -K collectd-5.7.1-2.el7.x86_64.rpm collectd-5.7.1-2.el7.x86_64.rpm: sha1 md5 OK zhipengl@zhipengl-nuc:~/stx-tools/centos-mirror-tools$ ll collectd-5.7.1-2.el7.x86_64.rpm -rw-rw-r-- 1 zhipengl zhipengl 613644 8月 1 18:24 collectd-5.7.1-2.el7.x86_64.rpm

Thanks again! BRs zhipeng

-----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月27日 21:08 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Ok, interesting. Glad your unblocked.

However, I have to ask. Have you or will you be root causing what caused the build system to choose and include the wrong package ? even one of the same name and version but without the correct fundamental content. Weird. Wonder if that is hitting use elsewhere not or will again in the future ?

Eric.

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:54 PM To: MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Thanks Eric!! Use below 2 commands, no python.so found.

However, RC found that a wrong collectd-5.7.1-2.el7.x86_64.rpm used. Its size is not the same as the one used by Abraham. After used the right collectd-5.7.1-2.el7.x86_64.rpm, no issue anymore The iso can be deloyed successfully on multimode.

Zhipeng

-----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 23:28 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

I've been able to reproduce the log failure signature with a change to the collectd.conf file

The issue is definitely related to the python library but it is packed in the collectd rpm. The one you call out is not in my working env. To further this investigation please provide the output of the following commands

ls -lrt /usr/lib64/collectd/python.so ldd /usr/lib64/collectd/python.so

Eric.

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 10:45 AM To: Liu, ZhipengS; MacDonald, Eric; Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide Importance: High

Do we need collected-python package in mirror?

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: 2018年7月26日 22:25 To: MacDonald, Eric <Eric.MacDonald@windriver.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Eric,

Thanks for your comment!! Could you help further check the error I saw below? ==================================================================== == ======= controller-0:/var/log/puppet# grep -R Error* latest/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! latest/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.125 Error: 2018-07-26 16:36:33 +0000 Systemd start for collectd failed! 2018-07-26-16-34-02_controller/puppet.log:2018-07-26T16:36:33.236 Error: 2018-07-26 16:36:33 +0000 /Stage[main]/Platform::Collectd/Service[collectd]/ensure: change from stopped to running failed: Systemd start for collectd failed! ==================================================================== == ========= ontroller-0:~$ cat /var/log/daemon.log | grep collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "network" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.072 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "threshold" successfully loaded. 2018-07-26T16:36:33.072 localhost collectd[25253]: info plugin_load: plugin "df" successfully loaded. 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info plugin_load: Could not find plugin "python" in /usr/lib64/collectd 2018-07-26T16:36:33.073 localhost collectd[25253]: info Automatically loading plugin "python" failed with status 1. 2018-07-26T16:36:33.073 localhost collectd[25253]: info Error: Reading the config file failed! 2018-07-26T16:36:33.073 localhost collectd[25253]: info Read the syslog for details. 2018-07-26T16:36:33.073 localhost collectd[25253]: info = 2018-07-26T16:36:33.100 localhost systemd[1]: notice collectd.service: main process exited, code=exited, status=1/FAILURE 2018-07-26T16:36:33.110 localhost systemd[1]: notice Unit collectd.service entered failed state. 2018-07-26T16:36:33.110 localhost systemd[1]: warning collectd.service failed. ==================================================================== ==

Thanks! Zhipeng -----Original Message----- From: MacDonald, Eric [mailto:Eric.MacDonald@windriver.com] Sent: 2018年7月26日 21:19 To: Liu, ZhipengS <zhipengs.liu@intel.com>; Arce Moreno, Abraham <abraham.arce.moreno@intel.com>; starlingx-discuss@lists.starlingx.io Subject: RE: [RFC] StarlingX Developer Guide

Looks like the manifest that configures and starts the collectd process is failing.

Can you please execute the following commands on the host that shows collectd failing and publish the errors you see that might reveal the cause.

# Get the config error logs ... sudo -i cd /var/log/puppet ; fgrep -R Error *

# get the collectd startup failure logs cat /var/log/daemon.log | grep collectd

one startup block is fine ; start to exit should show the error.

Eric MacDonald

...

-----Original Message----- From: Liu, ZhipengS [mailto:zhipengs.liu@intel.com] Sent: Thursday, July 26, 2018 4:53 AM To: Arce Moreno, Abraham; starlingx-discuss@lists.starlingx.io Subject: Re: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi Abraham and Hayde

I rebuilt and deployed my iso again, but still fail at step 6 with the same cause. Start collectd failed. Could you help deploy ISO I built to see if it can work in your environment, thanks!

Zhipeng

-----Original Message----- From: Arce Moreno, Abraham [mailto:abraham.arce.moreno@intel.com] Sent: 2018年7月26日 10:13 To: starlingx-discuss@lists.starlingx.io Subject: [Starlingx-discuss] [RFC] StarlingX Developer Guide

Hi again,

Can someone please help test the process to build an ISO based on master using Developer Guide [0]? Please use Github page [1] as a documentation support.

Requirements:

- Repo status checked 7/25/2018 19:12 PST - stx-tools master branch - latest change: b65fa0a0ec6297199843b1455615d0126bb7e7c7 Update RPM macros - Temporal! Changes, already in Developer Guide - RPM: selinux-policy-devel required https://review.openstack.org/#/c/585915

[0] https://wiki.openstack.org/wiki/StarlingX/Developer_Guide [1] https://github.com/xe1gyq/starlingx/blob/master/DeveloperGuide.md

_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu ss _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discu ss

---

Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss

Thanks Zhipeng!

Some place need to be changed in GUIDE. 1) Setup Building Docker Container

Need change to below. ENV http_proxy " http://your.actual_http_proxy.com:your_port " ENV https_proxy " https://your.actual_https_proxy.com:your_port " ENV ftp_proxy " http://your.actual_ftp_proxy.com:your_port " RUN echo " proxy=http://your-proxy.com:port " >> /etc/yum.conf

Story raised: https://storyboard.openstack.org/#!/story/2003169

Done

2) Update the symbolic links Update the symbolic links $ generate-cgcs-centos-repo.sh /import/mirrors/CentOS/stx-r1/CentOS/pike/ Need change to $ generate-cgcs-centos-repo /import/mirrors/CentOS/stx-r1/CentOS/pike/

Done

Hi Zhipeng,

I have some proposals as below.

Thanks for bringing this up.

In current developer guide, we have 2 containers for mirror download and build. Can we change it to only use 1 container for both? We will have 2 benefits at least 1) Simplify developer guide and remove some steps, such as mirror copy. 2) Developer can do mirror integrity check before start building. We always encounter this kind of issue that when build has been started for a while, then it told us some package missing. If we can do integrity check before building, it will be friendly to Developer.

Yes, we are using 2 containers due to the way we approach to replicate Wind River build environment and I also agree it is time to get new improvements into the build process. Let's wait for some feedback from the rest of the team about pros and cons, if any.

For mirror integrity check, just need to check if local mirror is complete compare to the latest Download list. If not, need download missing package first before start building.

Yes