[Xitami] Xitami crashing after FTP

[WhiteShepherd]

Thanks for theinsight.  If it's any help I'm not running Windows.  I'm running OS/2 4.0 
with Xitami for OS/2.  Double checked and no apps are using ports they should not.

Hmm..  new error.  But with no crash still running:

smthttp:  error on socket 11: Invalid argument

Possible corrupted copy of Xitami? 


Ok as a possible aid and to help prevent DOS attacks I have split my web server onto 2 
machines both running Xitami for OS/2.  One is my primary web server.  The second 
runs all CGIs.  I figure if I get hit with a GCI DOS attack worst they'll do is drag down the 
CGI box.  My primary non-cgi box should keep working smoothly.

Gene  

On 9 Jul 2002 at 9:05, Thomas J. Hruska wrote:

> At 12:12 AM 7/9/2002 -0400, WhiteShepherd writeth:
> >Ok ran a netstat -s to check.  FTPD is only using 21 and Xitami is
> listening to 80 and 81.  
> >Here is a common error befor a crash: 
> >
> >No such file or directory
> 
> Xitami could not find the file or directory to load.  Sounds like the FTP
> server is doing some sort of caching it shouldn't...or Windows could be
> corrupted or Xitami is corrupted or something is not right.
> 
> >Broken pipe
> 
> Possibly a further result of the file not opening.  My guess here is that
> Xitami is attempting to use a file or socket anyway.  At this point there
> is trouble later on whatever the case is.
> 
> >Socket operation on non-socket
> 
> The client socket has been closed or we are accessing memory we don't own...
> 
> >Clean-memory assertion failed - xitami.c (208)
> 
> This is (strangely) located at the end of Xitami's execution in main().
> I'm surprised the program got that far.  However, it is due to Xitami
> attempting to use or access memory it doesn't own or no longer owns.
> Xitami appears to be on its way out the door to avoid that great core dump
> in the skies whatever the case is.
> 
> >Abnormal program termination
> 
> It looks like the program exited but then the CPU took over and realized a
> memory fault took place during the clean-memory scan.
> 
> >core dumped
> 
> Hence, the core dump.  So much for avoiding it...
> 
> >Any of this make sense?
> 
> Nope.  Just extrapolating on what seems to be taking place.
> 
> >On 8 Jul 2002 at 16:30, Gunnar Swan wrote:
> >> I would check out a port sniffer. 
> >> Turn the OTHER FTP server completely off ... at the service panel.
> >> Then see what is listening on the ports.
> >> I would think that there are two apps fighting for the same port.
> 
> There should be no problem here.  Any Windows sockets provider worth its
> salt will only allow one program to own a single port on one IP at one
> time.  So, if there are two server programs contending for the same port,
> only one gets it.
> 
> >> Unless two programs are fighting for the same memory or communication
> channel, 
> >> they should co-exist.
> 
> This could be, but with Windows you never know what the OS will decide to
> do next :)  (I'm not an advocate of any OS...I just haven't found any that
> I really like).
> 
> Hope this helps!
> 
> 
>           Thomas J. Hruska -- shinelight@shininglightpro.com
> Shining Light Productions -- "Meeting the needs of fellow programmers"
>                   http://www.shininglightpro.com/
> 
> --
> Xitami Users Mailing List -- For Xitami support
> To unsubscribe: http://lists.xitami.org/mailman/listinfo/xitami


----------------------------------------------------------------
Whiteshepherd ( www.whiteshepherd.net/whiteshp )

http://www.furtopia.org / www.dragoncity.net  - Unlimited fast and free hosting for ALL 
the furry arts.  Personalized subdomains available with accounts.  Furry Sketch-n-Guess 
games held online Sundays at 8PM (www.furtopia.org/sketch).