MySQL "chokes" or Conquest issue ???

    Hi!
    Today I wanted to compress all of my files and to use my own filename syntax in the archive. So I decided to create an new database and a new folder.
    After I had tested the new installatin I cleared the DB and used "drag and drop" to "drop" my "old" (570GB) archive into the Conquest user interface.
    It all looked fine until, after about 45 minutes, the screen only read "unable to cennect to SQL".......all over the place.............. . System load was about 40-60% before.
    So well I thought, maybe MySQL crashed. I logged into MySQLAdministrator without a problem and MySQL was running perfectly, just Conquest could not connect.
    I randomly discovered similar problems in the Pacstrouble log but ignored them and thought it was just some kind of machine overload, though it only appeared once every few months.
    But this time the System only began to work again after I restarted the Server, restarting MySQL did not help (or at least not while conqest was still running).
    Does anybody expirience that kind of problem before?
    greetz


    PS:
    System setup:
    Pentium D 3,2Ghz
    3GB DDR2 ECC Ram
    Sys HD WD Raptor 150GB
    RAID5 with 4x750GB Seagate ES Drives
    Windows XP Prof


    Conquest 1.4.12c using native MySQL
    MySQL 5.0.41

    http://www.image-systems.biz/phpBB2/viewtopic.php?t=577


    Longhorn Beta 3, Mysql 5.1, Conquest 1.4.13.


    Setup is 2 dual core Xeon 5060, 6 GB Ram, 3 TB Raid 50, Dual gb NICs.


    Set windows to give background services higher priority. Pagefile is set at 4gb min and 16gb max.


    Use Mysql.dll from Conquest Download site. (DLL with 5.1 didn't work for me)


    Up and running, set prefs in dicom.ini.


    Start Conquest. Do not install as a service.


    Set affinity on Dgate to any non 0 cpu. Conquest to another non 0 and mysql to a different non 0 cpu.


    Raise priority of those three to real-time.


    Drag and drop 860 GB from external USB drive with no errors.


    Memory usage went to 5 gb and stayed there, pagefile usage went between 800mb and 1.6 gb.


    Still took almost 90 hours though. Left wondering if I missed a "tweak" somewhere.

    hi!


    Thanks for the help!


    But what do you mean by "any non 0 cpu"??
    I have two CPUs in the System, would that mean o set all three processes tc CPU 1 - and I would only use 50% of the PCU power?
    greetz

    Sorry that was for 'my' setup.



    I believe that increasing the amount of memory to Dgate and to mysql plus letting them have higher priority is what put me over the top in being able to drop large datasets into conquest.


    Replace your two Cpus with dual (or quad core) variants if available? :-)

    though dropping all the files did not work on my machine I just did a rebuild. Over the weekend I can make an new DB and drop the files again to see which process might be using all the memory.
    greetz

    Hi!
    I did a test-run on my machine with dropping 234 studies into the conquest user interface using MySQL 5.0.41 Conquest 1.4.12c an native Mysql.
    After a about 80-90 studies it read: "Error connecting to SQL" on the Display.
    So about half the images that were loaded did not show up in he DB, however MySQL was running without flaws when the message poped up.
    Neither Conquest user interface or dgate.exe showed exceptional CPU or Memory usage, between 4-17% CPU oad an about 8MB Memory usage.


    Thoug I forgot to turn on the Debug mode I did a re-run this morning, this time witout errors, seems very hard to reproduce....
    greetz

    Hi,


    This is all ysing the native mysql interface I assume? Could somebody try and compare with MyODBC? Apperently I use up a certain resource, but a simple code reread showed no obvious problems.


    Marcel

    Hi!


    Yes - native MySQL.


    I just did some more test runs. Every time I turn on Debug Mode - NO ERROR 3 out of 4 test runs!!
    Almost every time with no Debug mode set - Erros..a looooot!
    3 out of 4 runs with errors, 1 without. .. little strange but I think that has to be some kind of coincidence :-).
    On one of the runs, I finally got a more specific error message " error 12", see below:


    Pacs trouble log:
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error Connecting to SQL
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:41 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error Connecting to SQL
    20070701 15:59:42 ***Error Connecting to SQL
    20070701 15:59:42 ***Error Connecting to SQL
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest
    20070701 15:59:42 ***Error connecting datasource:conquest user:conquest password:conquest




    Server Status log:
    01.07.2007 15:59:41 [PACS] [recompress]: recompressed with mode = n2 (strip=1)
    01.07.2007 15:59:41 [PACS] Added file: E:\ConquestArchive\199551\1.2.840.113619.2.55.1.1762864713.1985.1169534198.516\1.2.840.113619.2.55.1.1762864713.1985.1169534198.549\1.2.840.113619.2.55.1.1762864713.1985.1169534198.723.v2
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 ---- Processing directory: D:\eFilm Archive\1.2.840.113619.2.55.1.1762864713.1985.1169534198.516\1.2.840.113619.2.55.1.1762864713.1985.1169534198.549.4
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:41 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:42 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:42 [PACS] ***Error Connecting to SQL
    01.07.2007 15:59:42 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:42 *** Restarted dead server after error 12
    01.07.2007 15:59:44 [PACS] ***Error connecting datasource:conquest user:conquest password:conquest
    01.07.2007 15:59:44 [PACS] DGATE (1.4.12c, build Thu Feb 01 23:22:00 2007) is running as threaded server
    01.07.2007 15:59:44 [PACS] User interface test: local server is running!
    01.07.2007 15:59:44 -----------------------------------------------------

    Hi!


    I just set all log files for MySQL and ran thetest again.
    It was as mentioned before, Conquest with Debug info - all smoothe.
    Conquest without Debug mode - errors after 4-5 Minutes.


    Sql logfiles were ALL without any Error, not even a warning message (I enabled that too).
    For now it looks to me that this is a Conquest only problem!?


    will try more....

    Thanks to blub:)


    it is a mysql/windows issue: mysql uses temporary ports that are not released quickly enough. Mysql dies after several thousand connects/disconnects because all temporary ports are allocated. With the debug log, the server is slightly slower and the problem does not happen.


    See:


    http://support.microsoft.com/kb/q196271/


    http://bugs.mysql.com/bug.php?id=6580


    http://bugs.mysql.com/bug.php?id=10498


    The error can be fixed by changing the following TCPIP parameters of windows by saving this snippet as as .reg file and double clicking it.


    Code
    REGEDIT4

    

    

    [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters]

    "MaxUserPort"=dword:0000fffe

    "TcpTimedWaitDelay"=dword:0000001e


    P.S. 1) Fix relates both to native and ODBC use of MySQL


    2) There is a bug in native MySQL that affects queries of empty fields: these are not read correctly and show "ghost" data of other records. Will be fixed in next release.

Participate now!

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

Register Yourself Login