Solaris cmd line: new error

ian_sg · Post by **ian_sg** » Tue Jan 03, 2006 10:09 pm

James,

It might also be helpful to upgrade the client on your Solaris machine to 3.1.6.

We specifically fixed an error that looks a lot like yours. My guess is that 3.1.6 won't fix the problem outright, but will give you the "real" error message, which should be an error during (or prior to) login.

James Jeffers · Post by **James Jeffers** » Wed Jan 04, 2006 12:57 pm

I've upgraded to 1.1.12.1, finally, on our Solaris machine.

I've updated the client binaries to 3.16.

The result, sadly, is still desultory.

bash-2.03$ vault listworkingfolders

Unhandled Exception: System.NullReferenceException: Object reference not set to an instance of an object
in <0x0007c> VaultClientNetLib.VaultConnection:Logout ()
in <0x00020> VaultClientOperationsLib.ClientInstance:Logout ()
in <0x00058> VaultCmdLineClient.VaultCmdLineClient:Logout (Boolean bForceLogout)
in <0x00468> VaultCmdLineClient.VaultCmdLineClient:Main (System.String[] args)

bash-2.03$ mono -V
Mono JIT compiler version 1.1.12.1, (C) 2002-2005 Novell, Inc and Contributors. www.mono-project.com
TLS: normal
GC: Included Boehm (with typed GC)
SIGSEGV : normal

James Jeffers · Post by **James Jeffers** » Wed Jan 04, 2006 1:03 pm

Ah! Ok, I found 2 instalations of the Client API binaries. I removed the other one so now we are really running 3.1.6, not 3.1.5, etc.

The result:

bash-2.03$ vault listworkingfolders
<vault>
<error>
An exception was thrown by the type initializer for System.Xml.Serialization.XmlSerializer
</error>
<exception>
System.TypeInitializationException: An exception was thrown by the type initializer for System.Xml.Serialization.XmlSerializer ---> System.Configuration.ConfigurationException: The `indentsize' attribute must be an integral value. (/usr/local/etc/mono/1.0/machine.config line 1) ---> System.NotImplementedException: The requested feature is not implemented.
in <0x00000> <unknown method>
in (wrapper managed-to-native) System.Threading.Thread:MemoryBarrier ()
in <0x0004c> System.Diagnostics.TraceImpl:InitOnce ()
in <0x00004> System.Diagnostics.TraceImpl:get_Listeners ()
in <0x00004> System.Diagnostics.TraceImpl:get_ListenersSyncRoot ()
in <0x00010> System.Diagnostics.TraceImpl:set_IndentSize (Int32 value)
in <0x00208> System.Diagnostics.DiagnosticsConfigurationHandler:AddTraceAttributes (IDictionary d, System.Xml.XmlNode node)--- End of inner exception stack trace ---

in <0x0026c> System.Diagnostics.DiagnosticsConfigurationHandler:AddTraceAttributes (IDictionary d, System.Xml.XmlNode node)
in <0x0001c> System.Diagnostics.DiagnosticsConfigurationHandler:AddTraceNode (IDictionary d, System.Xml.XmlNode node)
in (wrapper delegate-invoke) System.MulticastDelegate:invoke_void_IDictionary_XmlNode (System.Collections.IDictionary,System.Xml.XmlNode)
in <0x00368> System.Diagnostics.DiagnosticsConfigurationHandler:Create (System.Object parent, System.Object configContext, System.Xml.XmlNode section)
in <0x001cc> System.Configuration.ConfigurationData:GetConfigInternal (System.String sectionName)
in <0x000d0> System.Configuration.ConfigurationData:GetConfig (System.String sectionName)
in <0x00024> System.Configuration.DefaultConfig:GetConfig (System.String sectionName)
in <0x00028> System.Configuration.ConfigurationSettings:GetConfig (System.String sectionName)
in <0x00200> System.Xml.Serialization.XmlSerializer:.cctor ()--- End of inner exception stack trace ---

in <0x00000> <unknown method>
in <0x000b4> System.Web.Services.Protocols.TypeStubInfo:Initialize ()
in <0x00090> System.Web.Services.Protocols.LogicalTypeInfo:CreateTypeStubInfo (System.Type type)
in <0x00074> System.Web.Services.Protocols.LogicalTypeInfo:GetTypeStub (System.String protocolName)
in <0x00024> System.Web.Services.Protocols.TypeStubManager:GetTypeStub (System.Type t, System.String protocolName)
in <0x00024> System.Web.Services.Protocols.SoapHttpClientProtocol:.ctor ()
in <0x00008> VaultClientNetLib.ClientService.VaultService:.ctor ()
in (wrapper remoting-invoke-with-check) VaultClientNetLib.ClientService.VaultService:.ctor ()
in <0x000d8> VaultClientNetLib.VaultConnection:InitService (AccessLevelType accessLevel)
in <0x00014> VaultClientOperationsLib.ClientInstance:Init (AccessLevelType accessLevel)
in <0x00134> VaultCmdLineClient.VaultCmdLineClient:Login (Boolean bAllowAuto, Boolean bSaveSession)
in <0x00010> VaultCmdLineClient.VaultCmdLineClient:Login ()
in <0x03214> VaultCmdLineClient.VaultCmdLineClient:ProcessCommand (VaultCmdLineClient.Args curArg)
</exception>
<result success="no" />
</vault>

So, back to the other problem...

Post by **jclausius** » Wed Jan 04, 2006 1:14 pm

James:

Can you try this out on Solaris?

Run the attached binary file w/ Mono. What are the results?

James Jeffers · Post by **James Jeffers** » Wed Jan 04, 2006 1:18 pm

Here is the result:

bash-2.03$ mono /usr/local/Vault/MethodName.exe
DoSomething Beg
System.Reflection.MethodInfo.GetCurrentMethod().Name = DoSomething
DoSomething End

Post by **jclausius** » Wed Jan 04, 2006 1:36 pm

It looks like there's something wrong with mono reading the machine.config file.

Did you verify the indentsize in that file?

James Jeffers · Post by **James Jeffers** » Wed Jan 04, 2006 2:16 pm

The value for indentsize is:

<system.diagnostics>
<trace autoflush="false" indentsize="4" />
</system.diagnostics>

Post by **jclausius** » Wed Jan 04, 2006 2:26 pm

Hmm...

I don't want to give the "Solaris is unsupported" line just yet. I'll need some time to see if there's anything that can help us track this down.

James Jeffers · Post by **James Jeffers** » Wed Jan 04, 2006 2:46 pm

Understood, and thanks for the help.

Post by **jclausius** » Fri Jan 06, 2006 10:21 am

James:

OK. It took some time, but here's what I did to get this running.

1) Made / Installed mono 1.1.12.1 on the SPARC

2) Off the bat, running vault.exe caused the same identsize error you were seeing. This seems to be some kind of bug in mono. Anyway, we don't really need to to any debugging / tracing, so the line was commented.

Code: Select all

<!-- <trace autoflush="false" indentsize="4" /> -->

3) Ran vault.exe again, now got a keypairs error. This is expected when Vault CLC is run for the first time on a non-windows platform.

4) Next created the missing directories from step 3 (/usr/share/.mono and /usr/share/.mono/keypairs), and changed the persmissions to 0755.

5) Finally, since only root has write access to the folders from step 4, ran the first instance of vault.exe as root. This will generate the information in /usr/share/.mono/keypairs

6) Next ran vault.exe as a normal user. Vault CLC now works successfully.

I'm hopeful the same steps will work on your installation.