@bushrager:
Do you what kind aof advantage that new version has over 5.0? Im just curious
Posts by blub_smile
-
-
Hi
the easiest way I think is to use the actual version of MySQl 5.0.45 and install it with the instaler and run the configuration process, there set the root password and the approx. connection you will be having (probably around 100).
Then download MySql Administrator and connect to MySql, server host: localhost user: root and the password you have set before.
With that program you first create a databese "conquest", then a user "conquest" and assign the user all possible actions for the catalouge (db) conquest - done
The only thing you still have to set ist the db, password and user name in the dicom ini.
greetz -
Hi, this is a bug in 1.4.12 and is fixed in the new beta.
-
Hi!
Seems to work fine in 1.4.13 beta -
"Native mysql in 1.4.13beta will automatically create the mysql database and ask to set the TCPIP registry parameters. "
..cool
-
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....
-
@ Marcel: Do you think it would be useful to set MySQL to Debug mode and see if any Errors pop up? The normal error log file ist free of any uncommon messages.
greetz -
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:conquestServer 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 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 -
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!
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 -
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?
greetzPS:
System setup:
Pentium D 3,2Ghz
3GB DDR2 ECC Ram
Sys HD WD Raptor 150GB
RAID5 with 4x750GB Seagate ES Drives
Windows XP ProfConquest 1.4.12c using native MySQL
MySQL 5.0.41 -
-
Hi!
I encountered problems when deleting a study from patient which has multiple studies present.
When I try to delete a certain study, Images are deleted correctly but the entry of this specific study still remains in the DB.
So when a query is made for that patient 2 studies are visible but only one really exists on the drive.Conquest 1.4.12c with MySQL 5.0.41
Can anyone confirm this?
greetz -
Hi!
Ok, Error happpened again, so the new MySQl installation did not solve the problem.
However I traced the imgae that was supposedly to be missing and it appeared on the disk, and in the Databse - so its actually not missing at all.
Series showed 40 files in the directory, and showed 40 images in Conquest web server and 40 images could be retrieved from any other workstation.
greetz -
hi!
I tested quite a lot with the new MySQl 5.0.37 and I did not get an with the new version.
It has benn running on the server fpr about 2 weeks now without a flaw - well we will see :-).
greetz..by the way I am using the libmysql provided with MySQL installation
-
Hi Marcel!
It seems that this is quite a rare error message. And at the moment there is no further development in this case. I would like to help but sadly I have absolutely zero experience with MySQL.
In the past I have randomly checked studies with this error to see if the image is in fact missing or not. It turned out that suprisingly all studies were complete. (at least the few I looked into)
What I would like to ask is how Conquest handles such error mesages.
Is the normal procedure that the program retries the query and then saves the images or is it possible that images will get lost?
greetz
Stephan -
Hi!
So after quite a while I managed to log a SQL Erro event on our Server machine.
Details:PCAS Error log: 20070301 12:07:00 ***Error saving to SQL: 240662\1.2.840.113619.2.135.3596.3078814.8148.1172467839.711\1.2.840.113619.2.135.3596.3078814.8069.1172468194.936\1.2.840.113619.2.135.3596.3078814.8069.1172468195.2.v2
Serverstatus log with Debug L. 4.
20070301 12:07:00
20070301 12:07:00 Calling Application Title : "EFilmMR "
20070301 12:07:00 Called Application Title : "PACS "
20070301 12:07:00 Presentation Context 0 "1.2.840.10008.5.1.4.1.1.4"
20070301 12:07:00 Presentation Context 1 "1.2.840.10008.5.1.4.1.1.4"
20070301 12:07:00 Presentation Context 2 "1.2.840.10008.5.1.4.1.1.7"
20070301 12:07:00 Presentation Context 3 "1.2.840.10008.5.1.4.1.1.7"
20070301 12:07:00 Written file: D:\conquestarchive\240662\1.2.840.113619.2.135.3596.3078814.8148.1172467839.705\1.2.840.113619.2.135.3596.3078814.8069.1172468194.101\1.2.840.113619.2.135.3596.3078814.8069.1172468194.167.v2
20070301 12:07:00 [recompress]: recompressed with mode = n2 (strip=1)
20070301 12:07:00 Written file: D:\conquestarchive\060747\1.2.840.113619.2.135.3596.3078814.8148.1172467839.714\1.2.840.113619.2.135.3596.3078814.8069.1172468195.95\1.2.840.113619.2.135.3596.3078814.8069.1172468195.161.v2
20070301 12:07:00 ***Error saving to SQL: 240662\1.2.840.113619.2.135.3596.3078814.8148.1172467839.711\1.2.840.113619.2.135.3596.3078814.8069.1172468194.936\1.2.840.113619.2.135.3596.3078814.8069.1172468195.2.v2
20070301 12:07:00 Written file: D:\conquestarchive\030344\1.2.840.113619.2.135.3596.3078814.8148.1172467839.696\1.2.840.113619.2.135.3596.3078814.8069.1172468192.845\1.2.840.113619.2.135.3596.3078814.8069.1172468192.911.v2
20070301 12:07:00 Written file: D:\conquestarchive\211048\1.2.840.113619.2.135.3596.3078814.8148.1172467839.702\1.2.840.113619.2.135.3596.3078814.8069.1172468193.686\1.2.840.113619.2.135.3596.3078814.8069.1172468193.752.v2
20070301 12:07:00 Written file: D:\conquestarchive\140435\1.2.840.113619.2.135.3596.3078814.8148.1172467839.708\1.2.840.113619.2.135.3596.3078814.8069.1172468194.560\1.2.840.113619.2.135.3596.3078814.8069.1172468194.626.v2
20070301 12:07:00
20070301 12:07:00 UPACS THREAD 355: STARTED AT: Thu Mar 01 12:06:59 2007
20070301 12:07:00 Calling Application Title : "EFilmMR "
20070301 12:07:00 Called Application Title : "PACS "
20070301 12:07:00 Application Context : "1.2.840.10008.3.1.1.1"
20070301 12:07:00 Presentation Context 0 "1.2.840.10008.5.1.4.1.1.4"
20070301 12:07:00 Presentation Context 1 "1.2.840.10008.5.1.4.1.1.4"
20070301 12:07:00 Presentation Context 2 "1.2.840.10008.5.1.4.1.1.7"
20070301 12:07:00 Presentation Context 3 "1.2.840.10008.5.1.4.1.1.7"
20070301 12:07:00 [recompress]: recompressed with mode = n2 (strip=1)
20070301 12:07:00 Written file: D:\conquestarchive\300943\1.2.840.113619.2.135.3596.3078814.8148.1172467839.674\1.2.840.113619.2.135.3596.3078814.8069.1172468190.188\1.2.840.113619.2.135.3596.3078814.8069.1172468190.254.v2
20070301 12:07:00I hope this will help a litte
greetz -
..same with me. I just checked las weeks log files, guess what? No errors :-)?
strange.. -
hi!
I just moved 15GB of images on my test installation, and guess what - no error!
I will try to switch the debug level on next time I take a look at the server, maybe this way we will get more information.
greetz