Re: not able to view DFM reports ...

viveksingh183 · ‎2012-01-01

Hi

I am not able to view/generate any dfm reports in our environmnet . We have oncommand 5 installed . I am getting following error - Error: http_get_request failed with return value 500. Please vaildate dfm http a nd webui services are running correctly. Please refer dfm and jetty log for more detailed information. I have checked dfm services, its running fine. Please advice.

prasads · ‎2012-01-02

Hi,

Can you please provide more details about the system configurations?

Can you attach the output of "dfm about" to this thread.

You may want to remove the private data (like IP, Host Name etc) before attaching.

thanks,

Prasad

viveksingh183 · ‎2012-01-02

Hi Prasad

We have oncommand 5 installed on windows 2008 server. We have added our 4 FAS3140 controllers in same.

I have attached "dfm about" o/op here.

C:\>dfm about Version 5.0.0.7636 (5.0) Executable Type 64-bit Serial Number 1-50-113908 Edition Standard edition of DataFabric Manager server Administrator Name MUMCLDOPS\118670 Host Name MUMCLDOPS Host IP Address 10.10.11.130 Host Full Name MUMCLDOPS Node limit 250 (currently managing 4) Operating System Microsoft Windows Server 2008 R2 Service Pack 1 (Build 7601) x64 based CPU Count 2 System Memory 4095 MB (load: 74%) Installation Directory C:/Program Files/NetApp/DataFabric Manager/DFM 8.84 GB free (21.6%) Perf Data Directory C:/Program Files/NetApp/DataFabric Manager/DFM/ perfdata Data Export Directory C:/Program Files/NetApp/DataFabric Manager/DFM/ dataExport Database Backup Directory C:\Program Files\NetApp\DataFabric Manager\DFM\ data Reports Archival Directory C:\Program Files\NetApp\DataFabric Manager\DFM\ reports Licensed Features DataFabric Manager server: installed Installed Plugins Storage System Config 6.5.1 (6.5.1) - storage s ystems and vFilers Storage System Config 6.5.2 (6.5.2) - storage s ystems and vFilers Storage System Config 6.5.3 (6.5.3) - storage s ystems and vFilers Storage System Config 6.5.4 (6.5.4) - storage s ystems and vFilers Storage System Config 6.5.5 (6.5.5) - storage s ystems and vFilers Storage System Config 6.5.6 (6.5.6) - storage s ystems and vFilers Storage System Config 6.5.7 (6.5.7) - storage s ystems and vFilers Storage System Config 7.0 (7.0.0.1) - storage s ystems and vFilers Storage System Config 7.0.1 (7.0.1.1) - storage systems and vFilers Storage System Config 7.0.2 (7.0.2) - storage s ystems and vFilers Storage System Config 7.0.3 (7.0.3) - storage s ystems and vFilers Storage System Config 7.0.4 (7.0.4) - storage s ystems and vFilers Storage System Config 7.0.5 (7.0.5) - storage s ystems and vFilers Storage System Config 7.0.6 (7.0.6) - storage s ystems and vFilers Storage System Config 7.0.7 (7.0.7) - storage s ystems and vFilers Storage System Config 7.1 (7.1.0.1) - storage s ystems and vFilers Storage System Config 7.1.1 (7.1.1.1) - storage systems and vFilers Storage System Config 7.1.2 (7.1.2.1) - storage systems and vFilers Storage System Config 7.1.3 (7.1.3) - storage s ystems and vFilers Storage System Config 7.2 (7.2) - storage syste ms and vFilers Storage System Config 7.2.1 (7.2.1.1) - storage systems and vFilers Storage System Config 7.2.2 (7.2.2) - storage s ystems and vFilers Storage System Config 7.2.3 (7.2.3) - storage s ystems and vFilers Storage System Config 7.2.4 (7.2.4) - storage s ystems and vFilers Storage System Config 7.2.5 (7.2.5.1) - storage systems and vFilers Storage System Config 7.2.6 (7.2.6.1) - storage systems and vFilers Storage System Config 7.2.7 (7.2.7) - storage s ystems and vFilers Storage System Config 7.3 (7.3) - storage syste ms and vFilers Storage System Config 7.3.1 (7.3.1.1) - storage systems and vFilers Storage System Config 7.3.2 (7.3.2) - storage s ystems and vFilers Storage System Config 7.3.3 (7.3.3) - storage s ystems and vFilers Storage System Config 7.3.4 (7.3.4) - storage s ystems and vFilers Storage System Config 7.3.5 (7.3.5) - storage s ystems and vFilers Storage System Config 8.0 (8.0) - storage syste ms and vFilers Storage System Config 8.0.1 (8.0.1) - storage s ystems and vFilers

Regards

Vivek

prasads · ‎2012-01-02

Thanks Vivek.

Developers are investigating on this issue now.

viveksingh183 · ‎2012-02-07

Hi Prasad Any updates from developers ? Thanks & Regards, Vivek

viveksingh183 · ‎2012-02-29

Hi Prasad Shall I log case with Netapp support for this issue ? Thanks & Regards, Vivek

FLUFFYBOB · ‎2013-05-28

Hi Vivek, was there any outcome to the NetApp Support case you logged? I'm experiencing the same issue.

Regards,

Michael

adaikkap · ‎2013-05-29

Hi Michael,

Pls try this workaround and let me know if you still face this issue.

This issue is generally seen when the temporary directory for SYSTEM account

is missing. Create the temporary directory from system explorer.

On Windows 2008 64-bit edition, create the directory by name "temp" with "default" permissions at the following path:

'C:\Windows\SysWOW64\config\systemprofile\AppData\Local\'

Regards

adai

adaikkap · ‎2013-05-29

Also in a few days look for the work around in bug online for bug 540524

Regards

adai

john_meyer · ‎2013-11-19

This work around worked for me, thanks!

HESHIMA91 · ‎2014-03-21

Wich workaround can you provide the link ?

martin_jencik · ‎2014-08-11

Hello guys,

I have also the experience with the described error message: http_get_request failed with return value 500. Please vaildate dfm http a nd webui services are running correctly. Please refer dfm and jetty log for more detailed information.

The issue happend on friday after I wanted to view a report in cli using command: dfm report view qtree-capacity.

After that I have checked the dfm services which were running but I have restarted the webui and http services to be sure.

It happened on Friday when I was leaving the office and return to investigate the issue today (after weekend). The reports can be viewed now but in jetty log from that

day I see:

2014-08-08 11:15:12.538:INFO::jetty-6.1.24

2014-08-08 11:15:33.014:INFO:/ActuateJavaComponent:Temp files will be saved to : /opt/NTAPdfm/jetty/webapps/ActuateJavaComponent/temp

2014-08-08 11:15:33.058:INFO:/ActuateJavaComponent:Initialising logging mechanism

2014-08-08 11:15:33.058:INFO:/ActuateJavaComponent:Writing logs to /logs

2014-08-08 11:15:33.058:INFO:/ActuateJavaComponent:Enabling logging mechanism

Aug 8, 2014 11:15:33 AM com.actuate.common.timezones.TimeZones

WARNING: "Asia/Jerusalem " is not a valid time zone id

2014-08-08 11:15:34.878:INFO:/ActuateJavaComponent:Transient files will be saved to : /tmp/transientStore

2014-08-08 11:15:36.166:WARN::failed SelectChannelConnector@localhost:8123: java.net.SocketException: Invalid argument

2014-08-08 11:15:36.166:WARN::failed Server@31930611: java.net.SocketException: Invalid argument

2014-08-08 11:15:36.166:WARN::EXCEPTION

java.net.SocketException: Invalid argument

at sun.nio.ch.Net.bind(Native Method)

at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)

at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)

at org.mortbay.jetty.nio.SelectChannelConnector.open(SelectChannelConnector.java:216)

at org.mortbay.jetty.nio.SelectChannelConnector.doStart(SelectChannelConnector.java:315)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.jetty.Server.doStart(Server.java:235)

at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:50)

at org.mortbay.xml.XmlConfiguration.main(XmlConfiguration.java:985)

at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)

at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)

at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)

at java.lang.reflect.Method.invoke(Unknown Source)

at org.mortbay.start.Main.invokeMain(Main.java:194)

at org.mortbay.start.Main.start(Main.java:534)

at org.mortbay.start.Main.start(Main.java:441)

at org.mortbay.start.Main.main(Main.java:119)

# dfm version

dfm 5.2 (5.2R1)

# dfm about

Version 5.2 (5.2R1)

Executable Type 64-bit

Serial Number 1-50-154850

Edition Standard edition of DataFabric Manager server

Data ONTAP Operating Mode 7-Mode

Administrator Name root

Host Name hostname

Host IP Address IP

Host Full Name full hostname

Node limit 250 (currently managing 123)

Operating System SUSE Linux Enterprise Server 11 (x86_64) 3.0.74-0.6.8-default x86_64

CPU Count 4

System Memory 19866 MB (load excluding cached memory: 40%)

Installation Directory /opt/NTAPdfm

109 GB free (55.6%)

Perf Data Directory /opt/NTAPdfm/perfdata

Data Export Directory /opt/NTAPdfm/dataExport

Database Backup Directory /opt/NTAPdfm/data

Reports Archival Directory /opt/NTAPdfm/reports

Licensed Features DataFabric Manager server: installed

Installed Plugins Storage System Config 6.5.1 (6.5.1) - storage systems and vFilers

Storage System Config 6.5.2 (6.5.2) - storage systems and vFilers

Storage System Config 6.5.3 (6.5.3) - storage systems and vFilers

Storage System Config 6.5.4 (6.5.4) - storage systems and vFilers

Storage System Config 6.5.5 (6.5.5) - storage systems and vFilers

Storage System Config 6.5.6 (6.5.6) - storage systems and vFilers

Storage System Config 6.5.7 (6.5.7) - storage systems and vFilers

Storage System Config 7.0 (7.0.0.1) - storage systems and vFilers

Storage System Config 7.0.1 (7.0.1.1) - storage systems and vFilers

Storage System Config 7.0.2 (7.0.2) - storage systems and vFilers

Storage System Config 7.0.3 (7.0.3) - storage systems and vFilers

Storage System Config 7.0.4 (7.0.4) - storage systems and vFilers

Storage System Config 7.0.5 (7.0.5) - storage systems and vFilers

Storage System Config 7.0.6 (7.0.6) - storage systems and vFilers

Storage System Config 7.0.7 (7.0.7) - storage systems and vFilers

Storage System Config 7.1 (7.1.0.1) - storage systems and vFilers

Storage System Config 7.1.1 (7.1.1.1) - storage systems and vFilers

Storage System Config 7.1.2 (7.1.2.1) - storage systems and vFilers

Storage System Config 7.1.3 (7.1.3) - storage systems and vFilers

Storage System Config 7.2 (7.2) - storage systems and vFilers

Storage System Config 7.2.1 (7.2.1.1) - storage systems and vFilers

Storage System Config 7.2.2 (7.2.2) - storage systems and vFilers

Storage System Config 7.2.3 (7.2.3) - storage systems and vFilers

Storage System Config 7.2.4 (7.2.4) - storage systems and vFilers

Storage System Config 7.2.5 (7.2.5.1) - storage systems and vFilers

Storage System Config 7.2.6 (7.2.6.1) - storage systems and vFilers

Storage System Config 7.2.7 (7.2.7) - storage systems and vFilers

Storage System Config 7.3 (7.3) - storage systems and vFilers

Storage System Config 7.3.1 (7.3.1.1) - storage systems and vFilers

Storage System Config 7.3.2 (7.3.2) - storage systems and vFilers

Storage System Config 7.3.3 (7.3.3) - storage systems and vFilers

Storage System Config 7.3.4 (7.3.4) - storage systems and vFilers

Storage System Config 7.3.5 (7.3.5.1) - storage systems and vFilers

Storage System Config 7.3.6 (7.3.6) - storage systems and vFilers

Storage System Config 7.3.7 (7.3.7) - storage systems and vFilers

Storage System Config 8.0 (8.0) - storage systems and vFilers

Storage System Config 8.0.1 (8.0.1) - storage systems and vFilers

Storage System Config 8.0.2 (8.0.2) - storage systems and vFilers

Storage System Config 8.0.3 (8.0.3) - storage systems and vFilers

Storage System Config 8.0.4 (8.0.4) - storage systems and vFilers

Storage System Config 8.1 (8.1) - storage systems and vFilers

Do you guys see something suspicious in jetty log (except that time zone warning)?

thank you,

Martin

*update: so probably this was only the temporary issue. Folder /opt/NTAPdfm/jetty/webapps/ActuateJavaComponent/temp exists with a correct permissions. I had to restart also the eventd service as it became 'not started'. Everything seems to be OK now.

Also I did not find port 8123 to be used by dfm: 2014-08-08 11:15:36.166:WARN::failed SelectChannelConnector@localhost:8123: java.net.SocketException: Invalid argument. Maybe some process has been terminated in the process and this unfortunate dfm issue has been created as a result.