All Forums |
Register |
Login |
Search |
Subscriptions |
My Profile |
Inbox |
Tool Warehouse |
FAQs |
Resources |
Help |
Member List |
Address Book |
Logout |
|
|
SFU Interix Random Crashing on Win2K3
|
Logged in as: Guest |
Users viewing this topic: none |
|
Login |
|
|
SFU Interix Random Crashing on Win2K3 - Nov. 26, '04, 6:06:05 AM
|
|
|
ChrisB
Posts: 4
Joined: Nov. 26, '04,
Status: offline
|
We have a problem on a customer site with Interix Crashing at what appears to be random times.
This is the Message that appears in the Windows Application Log at the time of the error.
Faulting application , version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x000070fe.
It is supposed to restart on all errors but does not with the following error in the Application Log.
Interix/Posix subsystem status: PSXSS: Startup could not create directory (0xc0000035), exiting
Any Ideas what is causing the crash? and how to fix it? What directory is it trying to Create at startup and failing?
Thanks, Chris.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 26, '04, 11:52:48 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> It is supposed to restart on all errors but does not with the following error in the Application Log.
Sorry, ambiguous pronoun "It" (to me anyway). Could you clarify please.
What level of Service Pack is the machine running?
(Someone posted a couple of days ago about problems with the beta SP).
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 26, '04, 12:05:34 PM
|
|
|
ChrisB
Posts: 4
Joined: Nov. 26, '04,
Status: offline
|
It => Interix.. In the Windows Services, Properties, Recovery Tab there is what to do on error, the Interix Service is set to restart on all failures after 0 minutes.
The OS is Windows Server 2003 Enterprise Edition.
No Mention of Any Service Pack. It is a live Server in a production enviroment and is not running any kind of Beta Service Pack.
Interix Does Run, Just it (interix) crashes every so often. (Once on Tuesday, now again Friday Morning).
thanks, Chris.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 26, '04, 2:54:51 PM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> It => Interix.. In the Windows Services, Properties, Recovery Tab there is what to do on error, the Interix Service
> is set to restart on all failures after 0 minutes.
There's a misunderstanding then.
Interix is a subsystem just as CSRSS (Win32) is a subsystem (and LSASS, etc).
Once a subsystem stops that's it until a reboot of the system.
The item that has been set is a "dummy" service that makes a request to get the
Interix subsystem started in the absence of another process making a request
for Interix subsystem services (i.e. an Interix process starting/running).
The error (C0*35) is STATUS_OBJECT_NAME_COLLISION. This just means what I
explained above. So, for purposes, this error message is a bit of a red herring.
> Faulting application , version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x000070fe.
This would appear to be the real error. But the information is slightly off.
The "version 0.0.0.0" says to me that it's not the Interix subsystem since it
properly has a version number. With a "0.0.0.0" version on the binary it would
seem to me to be a userspace application.
Is it possible that the customer is confused a bit?
By this I mean the customer sees their application crash and tries to restart (erroneously)
the Interix system when Interix is still running fine. They just need their app restarted.
So the thing to do is to see if, on the machine in question, PSXSS.EXE is still running.
This can be done by looking at Task Manager or trying to start one of the shells.
This will narrow things down.
The other question I should ask is what does the app do?
Does it use sockets? Is it a pthread'd app? Does it use memory mapping? etc.
This info helps scope out possibilities.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 26, '04, 4:37:59 PM
|
|
|
markfunk
Posts: 673
Joined: Mar. 31, '03,
Status: offline
|
quote:
It is supposed to restart on all errors but does not
Why do you think that "it" is supposed to restart ?
What do you think "it" is ? A service or a subsystem ?
[ There is a service called "zzInterix", with a name of "Interix subsystem startup" but it has nothing to do with the successful operation of the "Interix subsystem". All this service does is "trigger" the Interix subsystem to startup at boot time. You can safely ignore any/all messages related to this zzInterix service.
You can, via Service Manager, change this service's 'recovery actions' but it won't do you any good because this service has no direct connection with the Interix subsystem itself. What you really want to look for is if the process PSXSS.EXE is running. ]
The Interix subsytem is a Window's process called "PSXSS.EXE".
You can tell if it is running by starting TaskManager and viewing
the list of running processes.
If PSXSS.EXE ever fails, the only way to get it running again
is to reboot the machine.
quote:
Faulting application , version 0.0.0.0, faulting module ntdll.dll, version 5.2.3790.0, fault address 0x000070fe.
Why do you think this error message has anything to do with the Interix subsystem.
(as opposed to the zzInterix service) ?
If this is an error message from a failing PSXSS.EXE, then you need
to talk to Microsoft support. They are the only ones that can diagnose and
potentially fix your problem.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 27, '04, 5:20:16 AM
|
|
|
ChrisB
Posts: 4
Joined: Nov. 26, '04,
Status: offline
|
quote:
ORIGINAL: Rodney
> . With a "0.0.0.0" version on the binary it would seem to me to be a userspace application.
By Userspace Application, do you mean an application running under interix, or an application running seperate from Interix on the Machine? (For Example MS Word)
quote:
ORIGINAL: Rodney
Is it possible that the customer is confused a bit?
By this I mean the customer sees their application crash and tries to restart (erroneously)
the Interix system when Interix is still running fine. They just need their app restarted.
So the thing to do is to see if, on the machine in question, PSXSS.EXE is still running.
This can be done by looking at Task Manager or trying to start one of the shells.
This will narrow things down.
If the Application running under Interix Crashes There are several logs which would highlight this. From the Logs it is apparent that the Application 'dies' instantly without any warnings. When you try to open a Korn Shell or the like nothing happens (Just a Blank Window) PSXSS.EXE is NOT running in Task Manager. (I have been in and checked for myself)
quote:
ORIGINAL: Rodney
The other question I should ask is what does the app do?
Does it use sockets? Is it a pthread'd app? Does it use memory mapping? etc.
This info helps scope out possibilities.
The App Uses all of the Above. It is a Form of Database that allows direct connections by sockets (via it's own Socket Listeners, by default listening on port 8020,8021 & 2030, 2001, 2003) and the more conventional login via interix supported telnet (enabled in inetd.conf) & ssh. I Beleive it is Threaded and it does rely heavily on shared memory.
The Application also runs on linux & Solaris fine (It's just recompiled on Interix with a few obvious changes). Under our own test enviroment it runs fine, which leads me to beleive it is something to do with some settings on the customers machine.
Also is Interix telnet affected by Windwos Client Access Licences at all, and if so what would happen if the CAL limit has been reached?
Thanks, Chris.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 28, '04, 10:39:01 AM
|
|
|
Rodney
Posts: 3728
Joined: Jul. 9, '02,
From: /Tools lab
Status: offline
|
> By Userspace Application, do you mean an application running under interix, or an application
> running seperate from Interix on the Machine? (For Example MS Word)
It could be either.
Either way, it's not a message about the Interix subsystem or it's related components.
> When you try to open a Korn Shell or the like nothing happens (Just a Blank Window) PSXSS.EXE is NOT running in Task Manager.
Okay that makes things clear.
You are going to need to contact MS support (aka PSS).
They'll be the only ones who will be able to get a fix from the dev team.
You can, from the CD, install the debugging images onto the machine in question.
That with a debugger on the machine (set to automagically start) would capture
the moment if the Interix subsystem is what is crashing. It would provide a
series of stacks (since the subsystem itself is threaded) that PSS could use
to figure out what has happened.
> Also is Interix telnet affected by Windwos Client Access Licences at all, and if so what would happen if the CAL limit has been reached?
There are two different telnet servers. One is Win32-based and the other is Interix/Unix-based.
The Win32 version has no interaction with the Interix system.
The Interix version does interact with the Interix system of course, but CAL has no effect on it.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 28, '04, 7:04:26 PM
|
|
|
markfunk
Posts: 673
Joined: Mar. 31, '03,
Status: offline
|
> The Interix version does interact with the Interix system of course, but CAL has no effect on it.
This means that Interix software does not do explicit CAL enforcement.
All applications on a Window's system are under the perview of CALs.
In this case, CAL licensing enforcement is up to the end-user/customer.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 30, '04, 9:55:02 AM
|
|
|
ChrisB
Posts: 4
Joined: Nov. 26, '04,
Status: offline
|
Thanks, for your help
I'm trying the Logging method mentioned by one of the MS guys
Edit
HKLM\SYSTEM\Current Control Set\Services\zzInterix\ImagePath
to point to PSXRUN-LOG.EXE
and copy PSXRUN.EXE to PSXRUN-LOGEXE
and then reboot.
I'll see what that throws up and then Give MS a call.
Chris.
|
|
|
RE: SFU Interix Random Crashing on Win2K3 - Nov. 30, '04, 7:23:15 PM
|
|
|
markfunk
Posts: 673
Joined: Mar. 31, '03,
Status: offline
|
As I understand your problem, you have an Interix application that
crashes. And after it crashes, you no longer see the PSXSS.EXE process running.
If this is correct, then Psxrun-log.exe isn't going to help you.
What Psxrun-log.exe does is write some debugging messages while it executes.
PSXRUN is just a window's wrapper function that is used to start Interix applications in certain special situations.
So, unless you've installed your Interix database application as a Window's service (ie it's started up by PSXRUN), or you explicitly use PSXRUN to invoke it directly, then psxrun-log isn't likely to help you.
You really need to explain to Microsoft what you are doing, and what is failing, so that they can give you relevant and useful diagnostic guidance. Otherwise, you'll end up wasting a lot of time.
(ie:
after a system reboot, is PSXSS.EXE running ?
can you start a shell and type/run Interix commands (like uname, id, ps ...)
How do you start your application ? Does it run for a while before crashing ? For how long ?
If your application doesn't start up, then how did you compile/build it ?
When do you first notice that Interix isn't responding ? or that PSXSS.EXE doesn't exist anymore.
)
Answers to these questions should help narrow down the problem very quickly.
|
|
|
New Messages |
No New Messages |
Hot Topic w/ New Messages |
Hot Topic w/o New Messages |
|
Locked w/ New Messages |
Locked w/o New Messages |
|
Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
|
|