Powertool convertTo-UcsCmdlet returns error message

[Alois Gritsch]

Hi

our customer is getting an error message when he tries to start the convertto-ucscmdlet.

he has installed the actual powertool version 1.0.0.0 on two systems and both getting the same message.

There is no difference if he is connected or not to an UCS system.

i searched for the logfile directory from the UCSM but wasn't successfull.

Here the message:

C:\> disconnect-ucs
C:\> ConvertTo-UcsCmdlet -verbose
WARNING: Please review the generated cmdlets before deployment.
ConvertTo-UcsCmdlet : Could not find the log files directory
At line:1 char:20
+ ConvertTo-UcsCmdlet <<<<  -verbose
     + CategoryInfo          : NotSpecified: (:) [ConvertTo-UcsCmdlet], Exception
     + FullyQualifiedErrorId : Cisco.Ucs.Cmdlets.ConvertToUcsCmdlet

C:\> ConvertTo-UcsCmdlet
WARNING: Please review the generated cmdlets before deployment.
ConvertTo-UcsCmdlet : Could not find the log files directory
At line:1 char:20
+ ConvertTo-UcsCmdlet <<<<
     + CategoryInfo          : NotSpecified: (:) [ConvertTo-UcsCmdlet], Exception
     + FullyQualifiedErrorId : Cisco.Ucs.Cmdlets.ConvertToUcsCmdlet

C:\>

thx Alois

[padramas]

Hello Alois,

Do you have UCSM client logs in the folder from where you are executing the cmdlet ?

For example, centrale logs are saved in following location

Location on XP - C:\Documents and Settings\\Application Data\Sun\Java\Deployment\log

Location on Windows 7 - C:\Users\\AppData\LocalLow\Sun\Java\Deployment\log\

Once you find the directory, try specifying the path

ConvertTo-UcsCmdlet -GuiLog -LiteralPath 'C:\Work\centrale_7128.log.1'

ConvertTo-UcsCmdlet -GuiLog -Path 'C:\Work\centrale_71*.log.?'

--------------------------

http://developer.cisco.com/web/unifiedcomputing/pshell-download

Padma

[todd.shawcross]

Hello Padma,

I have the same problem as Alois.

When I checked the following path the directory was empty:

C:\Users\\AppData\LocalLow\Sun\Java\Deployment\log\

I have tried this on two computers Win7 and Win8.  I am unable to specify a path as I do not have a log file.

Does this cmdlet specifically need this java log file?

thx Todd

[olivier.boudry]

Hi Padma,

Exact same problem here. I also looked all over the place for those logs and did not found them. I even used Procmon to look where UCS manager could save these logs but did not found anything.

I tried to change the path for the logs in the java logging.properties file but it did not help.

When I start UCS Manager I get the Java Console window that pops up, and at the end of the logging procedure I'm getting this message:

log4j:WARN No appenders could be found for logger (com.nuova.centrale.core.comms.NuLoginService).

log4j:WARN Please initialize the log4j system properly.

I don't know if this is relevant or not.

Any help fixing this would be greatly appreciated.

Thanks,

Olivier.

[ericwill]

Check your Java settings in your Control Panel.  Some customers I've worked with in the past have had the Java logging 100% disabled.  If you don't have "Keep Temporary Files On My Computer" checked in the Java settings in the control panel, then convertto-ucscmdlet won't work.  It uses the log files stored normally in the previous replies to generate the cmdlet's.

I normally set the temporary file max for Java at around 250MB.  For my system (Windows 7) the logs are stored here:

C:\Users\ericwill\AppData\LocalLow\Sun\Java\Deployment\log\.ucsm

You will see files with name central_XXX.log where XXX is a 3 or 4 digit number generally.

[olivier.boudry]

Hi Eric,

Thanks for the quick reply. I checked the Java settings and the "Keep Temporary Files On My Computer" is checked. The size limit is 32768 MB. I tried resetting the defaults but it does not change anything.

C:\Users\obou\AppData\LocalLow\Sun\Java\Deployment\log>dir

Volume in drive C is OSDisk

Volume Serial Number is C2CD-AAEA

Directory of C:\Users\obou\AppData\LocalLow\Sun\Java\Deployment\log

28.06.2013  12:04   

          .

28.06.2013  12:04   

          ..

               0 File(s)              0 bytes

               2 Dir(s)   7'413'706'752 bytes free

I forgot to say that I'm running this on the emulator. I will get a real UCS in a couple weeks and wanted to practice before getting it. But I've seen posts from people running this CmdLet on the Emulator so I assume it should work.

I also reviewed the options on the Cisco UCS Manager and tried to turn off and then on again the logging. Log level is now on "ALL" again.

Each time I create or edit some elements in the UCS manager but it does not create any logs. I tried the same on the computer of a colleague and he gets the same problem.

Thanks,

Olivier.

[ericwill]

What version of Java are you using?

[olivier.boudry]

C:\Users\obou\AppData\LocalLow\Sun\Java\Deployment\log>"C:\Program Files (x86)\Java\jre7\bin\java.exe" -version

java version "1.7.0_45"

Java(TM) SE Runtime Environment (build 1.7.0_45-b18)

Java HotSpot(TM) Client VM (build 24.45-b08, mixed mode, sharing)

I'm on a Win7 x64 machine and have both Java 32 and 64 bits installed. I checked in the process monitor and noticed that UCS Manager is running on the x32 version, which I would expect knowing it's started from a 32bits browser.

[benjaminCH]

Hi Eric and Olivier,

I have exactly the same problem as indicated.

I've tried on Windows 32 and 64 bits.

Could you please help me ?

Best regards

[olivier.boudry]

Hi Benjamin,

I still have the same problem. Could not resolve it so far.

Best regards,

Olivier.

[tlijnse]

Hi,

I am also running into the same problem. As far as I can see the problem is related to Java, as I am experiencing the same issue on both Windows 7, as well as on Mac OS X. I am running Java 7 update 45 on both systems and neither is generating log messages in the .ucsm directory.

I have older log files in the .ucsm directories on both systems, so I know that on some previous java version UCSM has created log entries as it should. However, if I start UCSM on these systems now, no logs are created and hence the "ConvertTo-UcsCmdlet" powershell cmdlet does not work, because it depends on these logs.

The fact that I have older entries in the .ucsm log directory and the fact that the problem appears on two different operating systems to me indicates that this is a Java and/or UCSM problem that was introduced during some java upgrade.

Another thing that I noticed is the following: When I enable logging for java itself I see the following entries in the java log file:

cat *.log | grep ucsm

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/centrale-min.jar

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/centrale-min.jar

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/centrale-min.jar

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/centrale-min.jar

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/centrale-min.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/centrale-min.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/cres.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/foxtrot-core-3.0.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/swingx-1.0.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/swing-worker.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/TimingFramework-1.0.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/OfficeLnFs_2.7.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/prefuse.2007.10.21.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/log4j-1.2.15.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/log4j-1.2.15.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/Stub.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jgraph.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jna.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/examples.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jfreechart-1.0.9.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jcommon-1.0.12.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/miglayout-3.6-swing.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jxlayer.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/JBusyComponent.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jautocomp.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/lablib-checkboxtree-3.2.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/osx.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/osx2.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/TimingFramework-1.0.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/swingx-1.0.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/osx2.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/foxtrot-core-3.0.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/prefuse.2007.10.21.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/JBusyComponent.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/lablib-checkboxtree-3.2.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/miglayout-3.6-swing.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/examples.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jna.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/swing-worker.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/Stub.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jgraph.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jxlayer.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jautocomp.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/OfficeLnFs_2.7.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jfreechart-1.0.9.jar.pack.gz

  Missing Application-Name: manifest attribute for: http://192.168.218.147/ucsm/signed/jcommon-1.0.12.jar.pack.gz

I am hoping some of the developers out here can pick up a clue from this as I am stuck at this point. The only available course of action would be to downgrade Java, and see if that fixes the problem, but unfortunately I can't do that on these systems because of other Java applications that I need to run.

[olivier.boudry]

Hi,

Thanks for this very detailed description of the problem. Good to know it might be related to the Java version and affects multiple OS.

Agreed, let's hope the developers will look into this.

[tlijnse]

Just to confirm my hypothesis, I decided to temporarily rollback to java 7 update 40 and this fixed the problem. The "ConvertTo-UcsCmdlet" cmdlet found the log in the .ucsm directory and properly generated a cmdlet after I made a change in the GUI.

When I then upgraded back to java 7 update 45 the "ConvertTo-UcsCmdlet" broke again.

So for sure this is a java 7 update 45 related problem.

[olivier.boudry]

Apparently something did change with Java 7.45.

I found the following "stackoverflow" post that talks about system properties not more set from jnlp tag properties since java update 7.45. Wondering if this could be the guilt.

http://stackoverflow.com/questions/19400725/with-java-update-7-45-the-system-properties-no-more-set-from-jnlp-tag-property

Not sure how to fix this though.

[Anuj Thapa]

more info here,

https://bugs.openjdk.java.net/browse/JDK-8023821