LPAR2RRD 6.0 error after update from 5.07 version
Hi
I updated to version 6.0 from 5.07 and now I didn't collect any data from vmware
After Update I got this error in error-vmware.log
SOAP request error - possibly a protocol issue: 500 read timeout
Here the test connection result (VMWARE 6.0 3h)
/home/lpar2rrd/lpar2rrd/vmware-lib/apps/connect.pl --version
vSphere SDK for Perl version: 6.0.0
Script 'connect.pl' version: 1.0
vSphere SDK for Perl version: 6.0.0
Script 'connect.pl' version: 1.0
VMWare 6
perl /home/lpar2rrd/lpar2rrd/bin/conntest.pl 10.209.49.12 443
Connection to "x.x.x.x" on port "443" is ok
Connection to "x.x.x.x" on port "443" is ok
in load_vmware.log
vmware timeout : timeout has been set to 3500
vmware timeout : timeout has been set to 3500
Waiting for VMware: 25171
LPAR2RRD free version 6.00
Vmware start: VC5|svzvrsgvvc001w8.servizi|sa_VMWAR-Prod@sistemi.group Tue Feb 26 12:00:02 2019
RRDp version: 1.4008
RRDtool version: 1.4.8
Perl version : 5.016003
LPAR2RRD free version 6.00
Vmware start: VC6|sisvrsgvvc001w8.sistemi.group|sa_VMWAR-Prod@sistemi.group Tue Feb 26 12:00:02 2019
RRDp version: 1.4008
RRDtool version: 1.4.8
Perl version : 5.016003
SDK : VC5, vSphere SDK for Perl version-a: 6.0.0
SDK : VC6, vSphere SDK for Perl version-a: 6.0.0
vmware timeout : expired after 3500, killing : kill -TERM -25171
Waiting for VMware: 25172
vmware timeout : expired after 3500, killing : kill -TERM -25172
reducing : vm names : start 1551179086
vmware timeout : timeout has been set to 3500
Waiting for VMware: 25171
LPAR2RRD free version 6.00
Vmware start: VC5|svzvrsgvvc001w8.servizi|sa_VMWAR-Prod@sistemi.group Tue Feb 26 12:00:02 2019
RRDp version: 1.4008
RRDtool version: 1.4.8
Perl version : 5.016003
LPAR2RRD free version 6.00
Vmware start: VC6|sisvrsgvvc001w8.sistemi.group|sa_VMWAR-Prod@sistemi.group Tue Feb 26 12:00:02 2019
RRDp version: 1.4008
RRDtool version: 1.4.8
Perl version : 5.016003
SDK : VC5, vSphere SDK for Perl version-a: 6.0.0
SDK : VC6, vSphere SDK for Perl version-a: 6.0.0
vmware timeout : expired after 3500, killing : kill -TERM -25171
Waiting for VMware: 25172
vmware timeout : expired after 3500, killing : kill -TERM -25172
reducing : vm names : start 1551179086
reducing : vm names : stop 1551179086 lines read:2705, lines written:2705
installing WWW : install-html.sh vmware
Host identif : Linux
timestamp : Tue Feb 26 12:04:46 CET 2019
Menu : no menu refresh for vmware
heatmap : start Tue Feb 26 12:04:46 2019
heatmap : (VMware) set cpu utilization for 0 vm
heatmap : (VMware) set memory utilization for 0 vm
heatmap : (VMware) set cpu utilization for 0 pools
heatmap : (VMware) set memory utilization for 0 pools
heatmap : end Tue Feb 26 12:04:49 2019
CPU cfg VM advs: not this time 26 == 26
installing WWW : install-html.sh vmware
Host identif : Linux
timestamp : Tue Feb 26 12:04:46 CET 2019
Menu : no menu refresh for vmware
heatmap : start Tue Feb 26 12:04:46 2019
heatmap : (VMware) set cpu utilization for 0 vm
heatmap : (VMware) set memory utilization for 0 vm
heatmap : (VMware) set cpu utilization for 0 pools
heatmap : (VMware) set memory utilization for 0 pools
heatmap : end Tue Feb 26 12:04:49 2019
CPU cfg VM advs: not this time 26 == 26
-----------------------------------
Could you help to solve the problem ?
Thanks
Emilio
Comments
-
Hi expertin the file error.log-daemon I found this error:/home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl:120 : Address already in use
Wed Feb 27 08:40:01 2019: ERROR in Socket Creation listen:0.0.0.0, port:8162: Ad
dress already in use
/home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl:120 : Address already in use
Wed Feb 27 09:00:01 2019: ERROR in Socket Creation listen:0.0.0.0, port:8162: Ad
dress already in use
/home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl:120 : Address already in use
Wed Feb 27 09:20:02 2019: ERROR in Socket Creation listen:0.0.0.0, port:8162: Ad
dress already in use
/home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl:120 : Address already in use
Wed Feb 27 09:40:02 2019: ERROR in Socket Creation listen:0.0.0.0, port:8162: Ad
dress already in use
/home/lpar2rrd/lpar2rrd/bin/lpar2rrd-daemon.pl:120 : Address already in useHave you any idea about this error ?ThanksEmilio
-
Hi,ps -ef| grep lpar2rrd-daemonls -l /home/lpar2rrd/lpar2rrd/tmp/lpar2rrd-daemon.pidcat /home/lpar2rrd/lpar2rrd/tmp/lpar2rrd-daemon.pid
Howdy, Stranger!
Categories
- 1.6K All Categories
- 41 XORMON NG
- 25 XORMON
- 149 LPAR2RRD
- 13 VMware
- 16 IBM i
- 2 oVirt / RHV
- 4 MS Windows and Hyper-V
- Solaris / OracleVM
- XenServer / Citrix
- Nutanix
- 6 Database
- 2 Cloud
- 10 Kubernetes / OpenShift / Docker
- 122 STOR2RRD
- 19 SAN
- 7 LAN
- 17 IBM
- 3 EMC
- 12 Hitachi
- 5 NetApp
- 15 HPE
- Lenovo
- 1 Huawei
- 1 Dell
- Fujitsu
- 2 DataCore
- INFINIDAT
- 3 Pure Storage
- Oracle