Up to Discussions in General Topics

This Question is Possibly Answered

1 "correct" answer available (4 pts) 2 "helpful" answers available (2 pts)
17 Replies Last post: Oct 29, 2008 4:23 PM by godefroi  
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated

Jun 14, 2008 12:53 AM

Trouble with Powershell and NAnt during build

I'm trying out Teamcity as a possible replacement for our current CruiseControl installation.  Everything was going great until I got the agent up and running:

 

My NAnt build has an EXEC task for a powershell build.  Agent will hang indefinitely( > 30 minutes) on this task without moving.  Same task works fine if I execute NAnt from the commandline(even from the Work directory on the Agent).

 

Any ideas?

Tags: teamcity, nant, hang, powershell
Eugene Petrenko JetBrains
Eugene Petrenko
2,209 posts since
Oct 4, 2004
Currently Being Moderated
Jun 18, 2008 1:47 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

What version of TeamCity do you use?

What version of NAnt is used?

 

Could you please send me hanging part of the script to reproduce.

 

Could you please try to capture logs from .NET part of TeamCity. For doing it please do the following:

- select some build agent

- open /tmp/buildTmp/TeamCity.NET folder.

Please attach all the files from that folder.

 

Thanks!

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Jun 18, 2008 6:24 PM in response to: Eugene Petrenko
Re: Trouble with Powershell and NAnt during build

Eugene,

 

TeamCity Version - 3.1.1(build 6828)

NAnt version .85

 

Hangs on this target:


     <target name="create.db.verify">
          <exec program="powershell">
               <arg value="..\script\create_db.ps1"></arg>
               <arg value="bca_verify"></arg>
          </exec>
     </target>

 

I've attached the log file that was generated by the steps you detailed.

 

Thanks,

 

-Pete

Attachments:
Report Abuse
Eugene Petrenko JetBrains
Eugene Petrenko
2,209 posts since
Oct 4, 2004
Currently Being Moderated
Jun 18, 2008 6:34 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

Thanks. Seems array is broken.

You may email it to eugene[dot]petrenko]at[jetbrains.com

 

What is done under that powershell call? Does it produces much output?

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Jun 18, 2008 6:39 PM in response to: Eugene Petrenko
Re: Trouble with Powershell and NAnt during build

The powershell call is a DB build script.  It generates about 300 lines of messages during the build process.  Last week I tested without the status messages being printed by the script and it failed in the exact same fashion.

 

-Pete

Report Abuse
Eugene Petrenko JetBrains
Eugene Petrenko
2,209 posts since
Oct 4, 2004
Currently Being Moderated
Jun 18, 2008 6:42 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

I got the logs.

 

Could you please try taking thread dumps feature for that hanging build. What is shown for NAnt process?

Thanks!

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Jun 18, 2008 6:48 PM in response to: Eugene Petrenko
Re: Trouble with Powershell and NAnt during build

Two processes listed in the thread dump, dumps below:

 


PID: 10508 Error
6/18/2008 8:44:26 AM

Stack trace depth is set to show all frames

Thread id=10512 priority=10 state=Wait reason=UserRequest
   at System.Threading.WaitHandle.WaitOne(System.Int64 timeout, System.Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(System.Int32 millisecondsTimeout, System.Boolean exitContext)
   at System.Diagnostics.Process.WaitForExit(System.Int32 milliseconds)
   at NAnt.Core.Tasks.ExternalProgramBase.ExecuteTask()
   at NAnt.Core.Tasks.ExecTask.ExecuteTask()
   at JetBrains.BuildServer.NAntLoggers.NUnit2LoggingTask.ExecTaskEx.ExecuteTask() in ExecTaskEx.cs:line 19
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(System.String targetName, System.Boolean forceDependencies)
   at NAnt.Core.Tasks.CallTask.ExecuteTask()
   at NAnt.Core.Task.Execute()
   at NAnt.Core.Target.Execute()
   at NAnt.Core.Project.Execute(System.String targetName, System.Boolean forceDependencies)
   at NAnt.Core.Project.Execute()
   at NAnt.Core.Project.Run()
   at NAnt.Core.ConsoleDriver.Main(System.String args)
   at System.RuntimeMethodHandle.InvokeMethodFast(System.Object target, System.Object arguments, System.Signature sig, System.Reflection.MethodAttributes methodAttributes, System.RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object parameters, System.Globalization.CultureInfo culture, System.Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object parameters, System.Globalization.CultureInfo culture)
   at NAnt.Console.ConsoleStub+HelperArguments.CallConsoleRunner()
   at System.AppDomain.DoCallBack(System.CrossAppDomainDelegate callBackDelegate)
   at NAnt.Console.ConsoleStub.Main(System.String args)

Thread id=10524 priority=12 state=Wait reason=UserRequest

Thread id=10552 priority=8 state=Wait reason=EventPairLow

Thread id=10560 priority=8 state=Wait reason=ExecutionDelay

Thread id=10568 priority=8 state=Wait reason=UserRequest
   at System.Threading.WaitHandle.WaitOne(System.Int64 timeout, System.Boolean exitContext)
   at System.Threading.WaitHandle.WaitOne(System.Int32 millisecondsTimeout, System.Boolean exitContext)
   at JetBrains.BuildServer.CommonLoggers.Impl.LoggerThread.Run() in LoggerThread.cs:line 73
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object state)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Thread id=10648 priority=8 state=Wait reason=Executive
   at [Internal thisFrame, 'M-->U', Microsoft.Win32.Win32Native::ReadFile]
   at System.IO.FileStream.ReadFileNative(Microsoft.Win32.SafeHandles.SafeFileHandle handle, System.Byte bytes, System.Int32 offset, System.Int32 count, System.Threading.NativeOverlapped overlapped, System.Int32 hr)
   at System.IO.FileStream.ReadCore(System.Byte buffer, System.Int32 offset, System.Int32 count)
   at System.IO.FileStream.Read(System.Byte array, System.Int32 offset, System.Int32 count)
   at System.IO.StreamReader.ReadBuffer()
   at System.IO.StreamReader.ReadLine()
   at NAnt.Core.Tasks.ExternalProgramBase.StreamReaderThread_Output()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object state)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state)
   at System.Threading.ThreadHelper.ThreadStart()

Thread id=10652 priority=8 state=Wait reason=Executive
   at [Internal thisFrame, 'M-->U', Microsoft.Win32.Win32Native::ReadFile]
   at System.IO.FileStream.ReadFileNative(Microsoft.Win32.SafeHandles.SafeFileHandle handle, System.Byte bytes, System.Int32 offset, System.Int32 count, System.Threading.NativeOverlapped overlapped, System.Int32 hr)
   at System.IO.FileStream.ReadCore(System.Byte buffer, System.Int32 offset, System.Int32 count)
   at System.IO.FileStream.Read(System.Byte array, System.Int32 offset, System.Int32 count)
   at System.IO.StreamReader.ReadBuffer()
   at System.IO.StreamReader.ReadLine()
   at NAnt.Core.Tasks.ExternalProgramBase.StreamReaderThread_Error()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object state)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state)
   at System.Threading.ThreadHelper.ThreadStart()


Process command line
Error -11. Timeout.

6/18/2008 8:44:25 AM

Stack trace depth is set to show all frames

Thread id=10644 priority=8 state=Wait reason=Executive
   at [Internal thisFrame, 'M-->U', Microsoft.Win32.Win32Native::ReadFile]
   at System.IO.FileStream.ReadFileNative(Microsoft.Win32.SafeHandles.SafeFileHandle handle, System.Byte bytes, System.Int32 offset, System.Int32 count, System.Threading.NativeOverlapped overlapped, System.Int32 hr)
   at System.IO.FileStream.ReadCore(System.Byte buffer, System.Int32 offset, System.Int32 count)
   at System.IO.FileStream.Read(System.Byte array, System.Int32 offset, System.Int32 count)
   at System.IO.StreamReader.ReadBuffer()
   at System.IO.StreamReader.ReadLine()
   at System.IO.TextReader+SyncTextReader.ReadLine()
   at Microsoft.PowerShell.WrappedDeserializer..ctor(Microsoft.PowerShell.SerializationDataFormat dataFormat, System.String streamName, System.IO.TextReader input)
   at Microsoft.PowerShell.Executor.ExecuteCommandAsyncHelper(System.Management.Automation.Runspaces.Pipeline tempPipeline, System.Exception exceptionThrown, Microsoft.PowerShell.ExecutorExecutionOptions options)
   at Microsoft.PowerShell.ConsoleHost.InitializeRunspace(System.String initialCommand, System.Boolean skipProfiles, System.Collections.ObjectModel.Collection initialCommandArgs)
   at Microsoft.PowerShell.ConsoleHost.DoRunspaceLoop(System.String initialCommand, System.Boolean skipProfiles, System.Collections.ObjectModel.Collection initialCommandArgs)
   at Microsoft.PowerShell.ConsoleHost.Run(System.String bannerText, System.String helpText, System.Boolean isPrestartWarned, System.String args)
   at Microsoft.PowerShell.ConsoleHost.Start(System.Management.Automation.Runspaces.RunspaceConfiguration configuration, System.String bannerText, System.String helpText, System.String preStartWarning, System.String args)
   at Microsoft.PowerShell.ConsoleShell.Start(System.Management.Automation.Runspaces.RunspaceConfiguration configuration, System.String bannerText, System.String helpText, System.String preStartWarning, System.String args)
   at Microsoft.PowerShell.UnmanagedPSEntry.Start(System.String consoleFilePath, System.String args)
   at System.RuntimeMethodHandle.InvokeMethodFast(System.Object target, System.Object arguments, System.Signature sig, System.Reflection.MethodAttributes methodAttributes, System.RuntimeTypeHandle typeOwner)
   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object parameters, System.Globalization.CultureInfo culture, System.Boolean skipVisibilityChecks)
   at System.Reflection.RuntimeMethodInfo.Invoke(System.Object obj, System.Reflection.BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object parameters, System.Globalization.CultureInfo culture)

Thread id=10664 priority=12 state=Wait reason=UserRequest

Thread id=10672 priority=9 state=Wait reason=UserRequest
   at System.Threading.WaitHandle.WaitAny(System.Threading.WaitHandle waitHandles, System.Int32 millisecondsTimeout, System.Boolean exitContext)
   at System.Management.Automation.Internal.ObjectStream.WaitRead()
   at System.Management.Automation.Internal.ObjectStream.Read(System.Int32 count)
   at System.Management.Automation.Internal.ObjectStream.Read()
   at System.Management.Automation.Internal.ObjectReader.Read()
   at System.Management.Automation.Internal.Pipe.Retrieve()
   at System.Management.Automation.CommandProcessorBase.Read()
   at System.Management.Automation.ShellFunctionCommandProcessor.ProcessRecord()
   at System.Management.Automation.CommandProcessorBase.DoExecute()
   at System.Management.Automation.Internal.PipelineProcessor.Inject(System.Object input, System.Boolean enumerate)
   at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(System.Object input, System.Collections.Hashtable errorResults, System.Boolean enumerate)
   at System.Management.Automation.Internal.PipelineProcessor.Execute(System.Array input)
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()
   at System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()
   at System.Threading.ThreadHelper.ThreadStart_Context(System.Object state)
   at System.Threading.ExecutionContext.runTryCode(System.Object userData)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, System.Object state)
   at System.Threading.ThreadHelper.ThreadStart()

 

Report Abuse
Eugene Petrenko JetBrains
Eugene Petrenko
2,209 posts since
Oct 4, 2004
Currently Being Moderated
Jun 19, 2008 9:52 AM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

So according to logs, I see that NAnt process is waiting for powershell to finish, while powershell is trying to read some file.

 

What user is used for build agent service? Does that user have enough rights to work? Sometimes SYSTEM accound does not match.

 

Could you please try settings some working folder for the script.

 

Let's replace powershell script with 'hello world' like script. Does that still hang?

 

Thanks!

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Jun 19, 2008 6:22 PM in response to: Eugene Petrenko
Re: Trouble with Powershell and NAnt during build

I have created the following test script, called "test.ps1":

 


Write-Output "Hello World!"

 

I created a new task in my NAnt.build file:

 


     <target name="hello.world">
          <exec program="powershell">
               <arg value="..\script\test.ps1"></arg>
          </exec>
     </target>

 

I modified the build agent to run the new task, same behavior, hangs indefinitely.

 

I also checked the permissions for the service, service is set to run under SYSTEM, SYSTEM has full privileges on the BuildAgent directory and all subdirectories.

 

-Pete

Report Abuse
Eugene Petrenko JetBrains
Eugene Petrenko
2,209 posts since
Oct 4, 2004
Currently Being Moderated
Jun 19, 2008 6:31 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

Thanks!

 

Could you please try running it under some real user on the machine. There were several issue on SYSTEM account used for build agent.

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Jun 19, 2008 6:56 PM in response to: Eugene Petrenko
Re: Trouble with Powershell and NAnt during build

Created a new user with administrator privileges on the machine, set build agent service to run under the new user, restarted the service.

 

Same behavior, hangs on the hello.world task.

Report Abuse
Oleg Gerovich Novice
Oleg Gerovich
104 posts since
Jun 4, 2008
Currently Being Moderated
Jun 19, 2008 11:31 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

Maybe the builder in TeamCity cannot find "..\script\test.ps1" because it starts in a different directory from the one you start in by hand?

Report Abuse
Oleg Gerovich Novice
Oleg Gerovich
104 posts since
Jun 4, 2008
Currently Being Moderated
Jun 18, 2008 6:50 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

Peter,

 

I had something similar happen to me in Ant when I was trying to use task without the full path to the executable for perl. I ended up having to write something like this:

 


<property name="perl.dir" value="C:\Perl\bin">
...
<target name="mytarget">
    <exec executable="${perl.dir}\perl.exe">
        <arg value="myscript.pl"></arg>
    </exec>
</target>

 

I don't know if it would work in NAnt though.

 

Hope this helps,

Oleg.

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Jun 18, 2008 7:07 PM in response to: Oleg Gerovich
Re: Trouble with Powershell and NAnt during build

Oleg,

 

Thanks for the tip, but unfortunately specifying the entire path didn't seem to have an affect.

 

-Pete

Report Abuse
godefroi Newbie
godefroi
4 posts since
Oct 28, 2008
Currently Being Moderated
Oct 28, 2008 11:09 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

Peter,

 

Did you ever find a solution to the problem of powershell hanging waiting for input? I've managed to run into the same issue, and my thread trace looks identical. PowerShell.exe seems to be waiting for input.

 

I've actually managed to work around the issue by writing a batch file and causing TC to execute that instead of powershell.exe directly, and in the batch file I have something like this:

 

@echo off

echo whatsthedeal | powershell.exe -noninteractive -noprofile -nologo -command "& 'my_script.ps1'"

 

But that's not ideal for obvious reasons.

Report Abuse
Peter Fransen Newbie
Peter Fransen
8 posts since
Jun 14, 2008
Currently Being Moderated
Oct 28, 2008 11:13 PM in response to: godefroi
Re: Trouble with Powershell and NAnt during build

Issue was never resolved.  I switched to Cruise Control.

Report Abuse
Yegor Yarko JetBrains
Yegor Yarko
1,425 posts since
May 5, 2004
Currently Being Moderated
Oct 29, 2008 3:51 PM in response to: Peter Fransen
Re: Trouble with Powershell and NAnt during build

We created the issue to address the problem.  Eugene will look into it to investigate if this powershell limitation can be workarounded.

Report Abuse
godefroi Newbie
godefroi
4 posts since
Oct 28, 2008
Currently Being Moderated
Oct 29, 2008 4:23 PM in response to: Yegor Yarko
Re: Trouble with Powershell and NAnt during build

Note than I'm executing powershell.exe directly using the command line runner, and I've also tried executing a batch file instead that launched powershell.exe instead. Neither worked. The only way I got it to work was to put in my batch file something like:

 

echo something_nonsensical_here | powershell.exe {command line parameters here}

 

... in which case it worked. I ended up working around the issue by writing a small replacement tool for powershell.exe that would execute my powershell script.

Report Abuse

More Like This

  • Retrieving data ...