Ghost Solution Suite

 View Only
  • 1.  GSS2.0 NGServer Issues

    Posted Jan 19, 2007 01:24 PM
    Hey everybody,

    I have been running the new GSS2.0 for a few weeks now and just had a couple issues come up. For some reason, the Symantec Ghost Configuration Server Service will randomly stop. It will then restart, but it stops about 30 seconds later.

    Through a series of reboots, the problem seems to have corrected itself (for now). However, I did just get a new error that popped up while I was running a Refresh Config task against the Default group of PC's (~250 currently).

    Anyone know what this error is all about?

    ---Begin Error Message----

    Symantec Ghost Configuration Server
    An exception has occurred of type C0000005
    C:\Program Files\Symantec\Ghost - C:\Program Files\Symantec\Ghost\ngserver.exe 11.0.0.1502

    e:\depot\ghost\gsstrunk\ghost\configureagent\library\src\gc\gc.cpp#990:Library::Gc::GCMarkCopy::scanPointerIn

    e:\depot\ghost\gsstrunk\ghost\configureagent\library\src\gc\objinit.cpp#606:Library::Gc::SObject::gcScan

    e:\depot\ghost\gsstrunk\ghost\configureagent\library\src\gc\gc.cpp#187:Library::Gc::GCSpace::scanAll

    e:\depot\ghost\gsstrunk\ghost\configureagent\library\src\gc\gc.cpp#1261:Library::Gc::GCGeneration::collectSpace
    unsigned int required = 0xC0854046
    bool matureSpace = false
    int save = 0x2484C700
    unsigned int spaceNeeded = 0x2484C700
    0x8BD275FF

    ---End Error Message---


  • 2.  RE: GSS2.0 NGServer Issues

    Posted Jan 19, 2007 08:06 PM
    It's an internal bug of some kind that is tripping up one of the internal subsystems that walks over all the memory in the program looking for data to free up, it looks to be running into some bad data in memory.

    To determine the root cause, I really need to inspect the NGERROR.DMP file that should have been written out to the "C:\Program Files\Symantec\Ghost" directory; it's a memory image of the process at the time of failure that I can load into a debugger and work back to try and determine why that bad data is there.

    If you e-mail me at nigel dot bree at gmail dot com I can send you some instructions of how to upload it for analysis so we can fix it up.


  • 3.  RE: GSS2.0 NGServer Issues

    Posted Jan 24, 2007 04:38 AM
    Thanks to Dustin kindly sending me a dumpfile, I've tracked the cause down to the COM connection code that hooks up the console and the server; a design change in GSS2 means it stores some extra things, but for one piece of information it can leave some corrupt data behind for the garbage-collection code to run into, up to days or weeks later.

    I've sent Dustin a fixed ngserver.exe to test, and hopefully that resolves it for him.


  • 4.  RE: GSS2.0 NGServer Issues

    Posted Jan 29, 2007 05:46 PM
    This fix seems to have worked. I haven't been getting the errors like I was before.