| View previous topic :: View next topic |
| Author |
Message |
awss
-
Joined: 29 Nov 2003
Posts: 6
|
 Posted: Sun Nov 21, 2004 7:22 pm Post subject: Problems with Abyss and Firedaemon |
 |
|
I'm currently using Firedaemon to run Abyss as a service so that when people log on and off the server doesn't keep on closing and shutting down.
However, I have a problem when a user logs off, the service gets killed and when it starts back up again, it writes over the configuration file with the default configuration, thereby causing the server to stop running because it gets "confused" (as my configuration is above the default one) or runs on the default configuration, therefore leading to file not found errors and ugly deault error pages.
I get the follwing in the Windows error viewer: -
| Quote: | Event Type: Error
Event Source: Abyss
Event Category: None
Event ID: 116
Date: 21/11/2004
Time: 17:57:16
Description:
Subprocess monitoring failed due to subprocess is no longer active. The subprocess is probably dead. Restarting the process. Error detail: Overlapped I/O operation is in progress.
|
Any ideas as to how to fix this? |
|
| Back to top |
  |
 |
Anonymoose
-
Joined: 09 Sep 2003
Posts: 2192
|
| Posted: Sun Nov 21, 2004 8:28 pm Post subject: |
|
|
| It's been mentioned before and is a known problem with how FireDaemon runs/closes Abyss - search the forum for 'firedaemon' to find out more. However, if all you want to do is run Abyss as a service, take a look at the beta version (link at the bottom of the Forum area lists) which supports installing Abyss as a service natively instead of via a 3rd party app. All reports suggest it's pretty damn stable too :D |
|
| Back to top |
|
|
|
