reinstalling after servercrash

  • Hi


    New to list, but have been using conquest/dgate for a while, mostly without problems.


    Anyway, my server crashed during a power outage, corrupted the root disk with conquest and configuration files on it but not my Mag0, which was on a different RAID1 cluster. I recompiled/reinstalled dgate and configured to save to the old database (just plain maklinux, I don't use postgres or anything). I get two errors:


    [root@ADIlab conquest]# ./dgate -v -r
    Regen Database
    Step 1: Re-intialize SQL Tables
    Dropping Existing tables (if-any)
    Worklist is empty
    Dropping worklist
    Dropping other tables
    WorkList Database
    Segmentation fault


    and


    [root@ADIlab conquest]# ./dgate -v
    DGATE (1.4.13, build Fri Jul 18 13:55:00 2008) is running as threaded server
    ***Failed to Listen () - bind error


    I run dgate from /usr/local/dicom/conquest where the configuration files are located. I usually run dgate as a service and not from the root prompt.


    My dicom.ini file is bleow. THanks for any help.


    Jon





    # This file contains configuration information for the DICOM server


    # Example Linux version using built-in dbaseIII file driver


    # Copy this file to dicom.ini to use it




    [sscscp]


    MicroPACS = sscscp


    Edition = Personal




    # Network configuration: server name and TCP/IP port#


    MyACRNema = ADIlab_pacs


    TCPPort = 50082




    # Reference to other files: known dicom servers; database layout; sops


    ACRNemaMap = acrnema.map


    kFactorFile = dicom.sql


    SOPClassList = dgatesop.lst




    # Host not used, name, username and password for ODBC data source


    # SQLHost = localhost


    SQLServer = ./data/dbase/


    Username = conquest


    Password = conquest


    PostGres = 0




    # Configure database


    TruncateFieldNames = 10


    MaxFieldLength = 254


    FileNameSyntax = 3


    MaxFileNameLength = 255


    FixPhilips = 0


    FixKodak = 0


    DoubleBackSlashToDB = 0


    UIDPrefix = 9999.9999


    EnableReadAheadThread = 1


    PatientQuerySortOrder =


    StudyQuerySortOrder =


    SeriesQuerySortOrder =


    ImageQuerySortOrder =


    IndexDBF = 1


    PackDBF = 0


    LongQueryDBF = 1000


    TCPIPTimeOut = 300


    FailHoldOff = 60


    RetryDelay = 100


    QueueSize = 128


    WorkListMode = 0




    # Configuration of compression for incoming images and archival


    DroppedFileCompression = un


    IncomingCompression = un


    ArchiveCompression = as




    # Names of the database tables


    PatientTableName = DICOMPatients


    StudyTableName = DICOMStudies


    SeriesTableName = DICOMSeries


    ImageTableName = DICOMImages


    DMarkTableName = DICOMAccessUpdates


    RegisteredMOPDeviceTable = RegisteredMOPIDs


    UIDToMOPIDTable = UIDToMOPID


    UIDToCDRIDTable = UIDToCDRID




    # Banner and host for debug information


    PACSName = ADIlab_pacs


    OperatorConsole = 172.24.1.24




    # Configuration of disk(s) to store images


    MAGDeviceThreshhold = 0


    MAGDevices = 1


    MAGDevice0 = /pub/scans/dicom/pacs

  • Thanks for the tips, but no change. Unfortunately, Linux doesn't elaborate on the Seg Fault, so I'm also in the dark there. Looks like it happens when dgate tries to "Worklist database", whatever that is. I've tried to make sure dgate is running with proper credentials and that read/write permissions are appropriate. There is only one instance of dgate running at a time, and netstat does not report port 50082 in use after I shut dgate down. Restarting dgate still gives me the same listen error when I try to connect. Maybe this is connected with the seg fault when I try to initialize the database?


    Any further tips on how to troubleshoot this would be appreciated. I've got a lot of stuff tied up in the database!


    Cheers


    Jon

  • Well, I "fixed" my first problem by wiping out the old installation and recompiling rom a new download. Some kind of corruption somewhere there it seems.


    I still get the bind error and can't establish any associations, even though there is only one instance of dgate running and no other process is trying to use port 50082, as far as I can tell. Any suggestions would be appreciated. Thanks


    Jon

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!