Skip to Content.
Sympa Menu

perfsonar-user - Re: [perfsonar-user] Installation errors in perfSONAR-toolkit

Subject: perfSONAR User Q&A and Other Discussion

List archive

Re: [perfsonar-user] Installation errors in perfSONAR-toolkit


Chronological Thread 
  • From: dan dev <>
  • To: Antoine Delvaux <>
  • Cc:
  • Subject: Re: [perfsonar-user] Installation errors in perfSONAR-toolkit
  • Date: Wed, 10 Jan 2018 15:12:07 +0900
  • Ironport-phdr: 9a23:NoH0tBeQiYkwMfqCrhWaXLr9lGMj4u6mDksu8pMizoh2WeGdxcS5bR7h7PlgxGXEQZ/co6odzbaO6ua4ASQp2tWoiDg6aptCVhsI2409vjcLJ4q7M3D9N+PgdCcgHc5PBxdP9nC/NlVJSo6lPwWB6nK94iQPFRrhKAF7Ovr6GpLIj8Swyuu+54Dfbx9HiTahfL9+Ngm6oRnMvcQKnIVuLbo8xAHUqXVSYeRWwm1oJVOXnxni48q74YBu/SdNtf8/7sBMSar1cbg2QrxeFzQmLns65Nb3uhnZTAuA/WUTX2MLmRdVGQfF7RX6XpDssivms+d2xSeXMdHqQb0yRD+v9LlgRgP2hygbNj456GDXhdJ2jKJHuxKquhhzz5fJbI2JKPZye6XQds4YS2VcRMZcTy5OAo28YYUBDOQPIPhWoJXmqlQUsRezHxOhCP/zxjJKgHL9wK000/4mEQHDxAEvAsgBsHLJp9roKqgST/2+wa7VwjrdcfNZxCny6I7Ifx0huvyMUrdwftDQyUkrDQ/KklKQqYn8Mj6Ty+8DvW+b7+96WuKujW4qsxt+oia1ycc3lonFnJ4aylfB9Sh/3Y07JsW4RVZlbdOlDJddtSSXN4V1T8w5X21lvSk3xqEatZGmeSUF1IgryAPaZvGCbYSF7B3uWeCMKjlinn1lYqiwhxOq/Eig1OL8Us603U5PriVfk9nMsmkB1wXP6sSbU/d88Vmt1DiA2gzJ5eFEJkc0laXfK5E/2LI/ip0TsUHbEi/3nkX5krOWe1069uWp9+jqYLDrppGfOoBvlg3zN6sjltCjDeslNwUBQ3SX9vm52bDm40H0TrpHguUzkqbDsZDaIcobprS+Aw9Qyoss9giwDym739sGm3kKLFJIdQmIj4jsIV7OIfT4Ae2jjFSrlTdn3+rGMaH5ApXRMnjDl6/sfa5j5E5Gxgoz1tdf55ROBbEbOf7zR1Txu8LCDhIiNwy0wv3nCMlm1o8AQ26PA6mZML/Mvl+S4OIgPfWMaJEPtDnjNvcl+q2msXhssFkBeqiv0NM7ZXSmF+l2axGQZ2brg9EMV2sHuhQ3UfzCjVSEFyZUdXC7WeQk4mdoJpihCNLPT4bljLGflHO3E4Naa2YbV3iDFH7pc8OPXPJaO3HaGdNojjFRDevpcIQmzxz78Vaik7c=

Hello,

The hardware of the system used for perfSONAR's installation is as below, 

 
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    4
Socket(s):             1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 45
Model name:            Intel(R) Xeon(R) CPU E5-2609 0 @ 2.40GHz
Stepping:              7
CPU MHz:               2399.965
BogoMIPS:              4800.14
Hypervisor vendor:     Xen
Virtualization type:   none
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              10240K
NUMA node0 CPU(s):     0-3

After running the command 'systemctl -l start perfsonar-configure_nic_parameters.service', I got this message,

Job for perfsonar-configure_nic_parameters.service failed because the control process exited with error code. See "systemctl status perfsonar-configure_nic_parameters.service" and "journalctl -xe" for details.



Then the command 'systemctl status perfsonar-configure_nic_parameters.service" shows this result;



● perfsonar-configure_nic_parameters.service - LSB: pS-Performance Toolkit script to configure the NIC parameters
   Loaded: loaded (/etc/init.d/perfsonar-configure_nic_parameters; bad; vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-01-10 14:51:30 KST; 58s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 6909 ExecStart=/etc/init.d/perfsonar-configure_nic_parameters start (code=exited, status=1/FAILURE)

Jan 10 14:51:29 Box perfsonar-configure_nic_parameters[6909]:  * Setting txqueuelen for eth1 to 10000...
Jan 10 14:51:29 Box perfsonar-configure_nic_parameters[6909]:    ...done.
Jan 10 14:51:30 Box perfsonar-configure_nic_parameters[6909]:  * Disabling TCP offload for interface br-ex...
Jan 10 14:51:30 Box perfsonar-configure_nic_parameters[6909]:    ...done.
Jan 10 14:51:30 Box perfsonar-configure_nic_parameters[6909]:  * Setting txqueuelen for br-ex to 10000...
Jan 10 14:51:30 Box perfsonar-configure_nic_parameters[6909]:    ...done.
Jan 10 14:51:30 Box systemd[1]: perfsonar-configure_nic_parameters.service: Control process exited, code=exited status=1
Jan 10 14:51:30 Box systemd[1]: Failed to start LSB: pS-Performance Toolkit script to configure the NIC parameters.
Jan 10 14:51:30 Box systemd[1]: perfsonar-configure_nic_parameters.service: Unit entered failed state.
Jan 10 14:51:30 Box systemd[1]: perfsonar-configure_nic_parameters.service: Failed with result 'exit-code'.


"journalctl -xe' shows this result (first few lines);

Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.1774] device (eth3): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jan 10 14:59:00 BoxNetworkManager[1860]: <warn>  [1515563940.1794] device (eth3): Activation: failed for connection 'Wired connection 2'
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.1810] device (eth3): state change: failed -> disconnected (reason 'none') [120 30 0]
Jan 10 14:59:00 Boxavahi-daemon[1869]: Withdrawing address record for fe80::a88a:1f24:a15c:6c8 on eth3.
Jan 10 14:59:00 Boxavahi-daemon[1869]: Leaving mDNS multicast group on interface eth3.IPv6 with address fe80::a88a:1f24:a15c:6c8.
Jan 10 14:59:00 Boxavahi-daemon[1869]: Interface eth3.IPv6 no longer relevant for mDNS.
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.1996] policy: auto-activating connection 'Wired connection 2'
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.2042] device (eth3): Activation: starting connection 'Wired connection 2' (495648c4-305c-3e3f-8344-409588a7bd14)
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.2048] device (eth3): state change: disconnected -> prepare (reason 'none') [30 40 0]
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.2057] device (eth3): state change: prepare -> config (reason 'none') [40 50 0]
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.2528] device (eth3): state change: config -> ip-config (reason 'none') [50 70 0]
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.2534] dhcp4 (eth3): activation: beginning transaction (timeout in 45 seconds)
Jan 10 14:59:00 BoxNetworkManager[1860]: <info>  [1515563940.2954] dhcp4 (eth3): dhclient started with pid 10542
Jan 10 14:59:00 Boxdhclient[10542]: DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 3 (xid=0xc9950229)
Jan 10 14:59:01 Boxavahi-daemon[1869]: Joining mDNS multicast group on interface eth3.IPv6 with address fe80::a88a:1f24:a15c:6c8.
Jan 10 14:59:01 Boxavahi-daemon[1869]: New relevant interface eth3.IPv6 for mDNS.
Jan 10 14:59:01 Boxavahi-daemon[1869]: Registering new address record for fe80::a88a:1f24:a15c:6c8 on eth3.*.
Jan 10 14:59:03 Boxdhclient[10542]: DHCPDISCOVER on eth3 to 255.255.255.255 port 67 interval 8 (xid=0xc9950229)
Jan 10 14:59:08 BoxNetworkManager[1860]: <warn>  [1515563948.1391] dhcp4 (enp0s29u1u1u5): request timed out
Jan 10 14:59:08 BoxNetworkManager[1860]: <info>  [1515563948.1392] dhcp4 (enp0s29u1u1u5): state changed unknown -> timeout
Jan 10 14:59:08 BoxNetworkManager[1860]: <info>  [1515563948.1720] dhcp4 (enp0s29u1u1u5): canceled DHCP transaction, DHCP client pid 10464
Jan 10 14:59:08 BoxNetworkManager[1860]: <info>  [1515563948.1721] dhcp4 (enp0s29u1u1u5): state changed timeout -> done
Jan 10 14:59:08 BoxNetworkManager[1860]: <info>  [1515563948.1729] device (enp0s29u1u1u5): state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Jan 10 14:59:08 BoxNetworkManager[1860]: <warn>  [1515563948.1740] device (enp0s29u1u1u5): Activation: failed for connection 'Wired connection 1'
Jan 10 14:59:08 BoxNetworkManager[1860]: <info>  [1515563948.1779] device (enp0s29u1u1u5): state change: failed -> disconnected (reason 'none') [120 30 0]
Jan 10 14:59:08 Boxavahi-daemon[1869]: Withdrawing address record for fe80::e5a0:55:4abf:1e05 on enp0s29u1u1u5.
Jan 10 14:59:08 Boxavahi-daemon[1869]: Leaving mDNS multicast group on interface enp0s29u1u1u5.IPv6 with address fe80::e5a0:55:4abf:1e05.
Jan 10 14:59:08 Boxavahi-daemon[1869]: Interface enp0s29u1u1u5.IPv6 no longer relevant for mDNS.
Jan 10 14:59:08 Boxkernel: net_ratelimit: 2 callbacks suppressed
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
Jan 10 14:59:08 Boxkernel: cdc_ether 2-1.1.5:1.0 enp0s29u1u1u5: kevent 12 may have been dropped
.
.

Regards,

On Tue, Jan 9, 2018 at 6:53 PM, Antoine Delvaux <> wrote:
Hello Danny,

Can you share with us some details about the hardware of the system you're using to run this perfSONAR installation? The perfsonar-configure_nic_parameters script sometimes gives error with some virtualisation technologies that don't give access to fine tuning the NIC parameters.

Can you also try to run `systemctl -l start perfsonar-configure_nic_parameters.service` to see if you can get more output of that command?

Thanks,

Antoine.


> Le 9 janv. 2018 à 05:16, Danny <> a écrit :
>
> hI,
> I am using Ubuntu 16.04.3 LTS.
> After running the  the installation script for perfSONAR toolkit "apt-get
> install perfsonar-toolkit" I have received following errors,
>
> perfsonar-configure_nic_parameters.service - LSB: pS-Performance Toolkit
> script to configure the NIC parameters
>   Loaded: loaded (/etc/init.d/perfsonar-configure_nic_parameters; bad; vendor
> preset: enabled)
>   Active: failed (Result: exit-code) since Tue 2018-01-09 14:02:54 KST; 10ms
> ago
>     Docs: man:systemd-sysv-generator(8)
>  Process: 1727 ExecStart=/etc/init.d/perfsonar-configure_nic_parameters start
> (code=exited, status=1/FAILURE)
>
> Jan 09 14:02:54 SmartX-Box-CHULA perfsonar-configure_nic_parameters[1727]:
> *...
> Jan 09 14:02:54 SmartX-Box-CHULA perfsonar-configure_nic_parameters[1727]:
> ...
> Jan 09 14:02:54 SmartX-Box-CHULA perfsonar-configure_nic_parameters[1727]:
> *...
> Jan 09 14:02:54 SmartX-Box-CHULA perfsonar-configure_nic_parameters[1727]:
> ...
> Jan 09 14:02:54 SmartX-Box-CHULA perfsonar-configure_nic_parameters[1727]:
> *...
> Jan 09 14:02:54 SmartX-Box-CHULA perfsonar-configure_nic_parameters[1727]:
> ...
> Jan 09 14:02:54 SmartX-Box-CHULA systemd[1]:
> perfsonar-configure_nic_paramet...1
> Jan 09 14:02:54 SmartX-Box-CHULA systemd[1]: Failed to start LSB:
> pS-Perform....
> Jan 09 14:02:54 SmartX-Box-CHULA systemd[1]:
> perfsonar-configure_nic_paramet....
> Jan 09 14:02:54 SmartX-Box-CHULA systemd[1]:
> perfsonar-configure_nic_paramet....
> Hint: Some lines were ellipsized, use -l to show in full.
> dpkg: error processing package perfsonar-toolkit (--configure):
> subprocess installed post-installation script returned error exit status 1
> Setting up psutils (1.17.dfsg-2) ...
> Setting up python-django-guardian (1.4.1-1) ...
> Setting up python-flup (1.0.2-5) ...
> Setting up python-markdown (2.6.6-1) ...
> Setting up python-pysnmp4-apps (0.3.2-1) ...
> Setting up python-pysnmp4-mibs (0.1.3-1) ...
> Setting up python3-pyinotify (0.9.6-0fakesync1) ...
> setting up sysstat (11.2.0-1ubuntu0.2) ...
> locale: Cannot set LC_ALL to default locale: No such file or directory
>
> Creating config file /etc/default/sysstat with new version
> update-alternatives: using /usr/bin/sar.sysstat to provide /usr/bin/sar (sar)
> in auto mode
> insserv: warning: script 'K01start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'start_ovs.sh' missing LSB tags and overrides
> Processing triggers for libc-bin (2.23-0ubuntu9) ...
> Processing triggers for systemd (229-4ubuntu21) ...
> Processing triggers for ureadahead (0.100.0-19) ...
> Processing triggers for dbus (1.10.6-1ubuntu3.3) ...
> Processing triggers for pscheduler-server (1.0.2-1) ...
> insserv: warning: script 'K01start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'K01start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'K01start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'K01start_ovs.sh' missing LSB tags and overrides
> insserv: warning: script 'start_ovs.sh' missing LSB tags and overrides
> Errors were encountered while processing:
> perfsonar-toolkit
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>
> Can you please help in understanding and solving this error?
>
> Regards,



Virus-free. www.avast.com



Archive powered by MHonArc 2.6.19.

Top of Page