Thunderstone Support Forums

There's a process for texis.exe still running.
The walk status is still refreshing, it's just hanging on 7,828 pages.

There may be multiple texis.exes for a single walk. Generally at least 2. cururls.PID# being present without it's process generally indicates a problem.

I only have one texis.exe process and three monitor processes.

Any ideas with regards to a solution?

The process for your cururls file died unexpectedly. I would expect to see something in vortex.log about it exiting or something in the walk status. If neither of those I'd have to guess that the OS is killing the process without giving it a change to close out. Does event viewer say anything about it?

There is nothing in Vortex log about cururls.

I've just tried running a walk from scratch again and checked the processes running.

Whilst I have processes for texis.exe and monitor.exe, I don't, at any point have a cururls process.

I wonder would this be an installation issue?

cururls.### is a file, not a process. The ### is the process id (PID) of texis.exe that created that file.
Look in vortex.log and process list for the PID, not "cururls".

Doesn't seem like an install issue.

The file is cururls.5104

This is in vortex.log

Cannot write to stdin for process 5104: The pipe is being closed in the function tx_prw_finishiotask

Hi Mark,

Does that message from the log tell you anything about this issue?

Not really. There are no other messages with that process number in vortex.log or the event log?

Are you using the latest v5 scripts? That would be 5.1.88
available from http://www.thunderstone.com/texis/site/ ... ripts.html