laoniu2020 / orthanc

Automatically exported from code.google.com/p/orthanc
GNU General Public License v3.0
0 stars 0 forks source link

running orthanc #4

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1.run orthanc
2.alter config file
3.try to run with new options

What is the expected output? What do you see instead?
it wont start, saying that mongoose server cant initiate.  if i just run 
./Orthanc I get the error that something is all ready using the address.  can i 
restart or fully shut down Orthanc and mongoose.  This seems like a very dumb 
question

What version of the product are you using? On what operating system?
build from 3/13/13 mercurial drop
RedHat 6

Please provide any additional information below.

Original issue reported on code.google.com by rico....@gmail.com on 15 Mar 2013 at 11:11

GoogleCodeExporter commented 9 years ago
This probably means that another program is already listening on the TCP ports 
that are used by Orthanc. By default, Orthanc listens on 4242 for the DICOM 
protocol, and on 8042 for its GUI and for the REST services. You can check 
whether other programs already use these ports running the following commands 
as root:

# netstat -tulpn | grep :8042
# netstat -tulpn | grep :4242

If this does not help, try adding the "--verbose" or "--trace" options when 
starting Orthanc to try and get more debug information, and paste them on this 
page.

Original comment by s.jodo...@gmail.com on 16 Mar 2013 at 7:50

GoogleCodeExporter commented 9 years ago
Found a process on 4242.  nothing on 8042 or 8080, I'm guessing the mongoose 
server is here.

Killed it.  Still cant run with the new configuration file.  But I can run it 
on the previous settings.  yay

# ./Orthanc ./Configuration.json --verbose
I0316 12:07:30.462805 99026 OrthancInitialization.cpp:61] Using the 
configuration from: ./Configuration.json
I0316 12:07:30.468830 99026 DatabaseWrapper.cpp:766] Version of the Orthanc 
database: 3
W0316 12:07:30.469157 99026 ServerContext.cpp:67] Disk compression is enabled
W0316 12:07:30.469184 99026 ServerIndex.cpp:899] No limit on the number of 
stored patients
W0316 12:07:30.469209 99026 ServerIndex.cpp:920] At most 1048576MB will be used 
for the storage area
I0316 12:07:30.469435 99027 ServerIndex.cpp:232] Starting the database flushing 
thread (sleep = 10)
W0316 12:07:30.469488 99026 main.cpp:264] DICOM server listening on port: 13010
W0316 12:07:30.469521 99026 main.cpp:265] HTTP server listening on port: 8042
I0316 12:07:30.470581 99026 ServerIndex.cpp:293] Stopping the database flushing 
thread
E0316 12:07:30.470849 99026 main.cpp:290] EXCEPTION [Unable to launch the 
Mongoose server]

# ./Orthanc ./Configuration.json --trace
I0316 12:08:26.883911 99033 OrthancInitialization.cpp:61] Using the 
configuration from: ./Configuration.json
I0316 12:08:26.888149 99033 Connection.cpp:155] SQLite::Connection::Execute 
PRAGMA FOREIGN_KEYS=ON;
I0316 12:08:26.888339 99033 Connection.cpp:155] SQLite::Connection::Execute 
PRAGMA RECURSIVE_TRIGGERS=ON;
I0316 12:08:26.888394 99033 Connection.cpp:155] SQLite::Connection::Execute 
PRAGMA SYNCHRONOUS=NORMAL;
I0316 12:08:26.890635 99033 Connection.cpp:155] SQLite::Connection::Execute 
PRAGMA JOURNAL_MODE=WAL;
I0316 12:08:26.890712 99033 Connection.cpp:155] SQLite::Connection::Execute 
PRAGMA LOCKING_MODE=EXCLUSIVE;
I0316 12:08:26.890756 99033 Connection.cpp:155] SQLite::Connection::Execute 
PRAGMA WAL_AUTOCHECKPOINT=1000;
I0316 12:08:26.890900 99033 Statement.cpp:116] SQLite::Statement::Step SELECT 
name FROM sqlite_master WHERE type=? AND name=?
I0316 12:08:26.891083 99033 Statement.cpp:116] SQLite::Statement::Step SELECT 
value FROM GlobalProperties WHERE property=?
I0316 12:08:26.891165 99033 DatabaseWrapper.cpp:766] Version of the Orthanc 
database: 3
I0316 12:08:26.891269 99033 Statement.cpp:110] SQLite::Statement::Run SELECT 
SUM(compressedSize) FROM AttachedFiles
I0316 12:08:26.891343 99033 Statement.cpp:110] SQLite::Statement::Run BEGIN 
TRANSACTION
I0316 12:08:26.891379 99033 Statement.cpp:110] SQLite::Statement::Run COMMIT
I0316 12:08:26.891404 99033 Statement.cpp:116] SQLite::Statement::Step SELECT 
value FROM GlobalProperties WHERE property=?
W0316 12:08:26.891695 99033 ServerContext.cpp:67] Disk compression is enabled
W0316 12:08:26.891710 99033 ServerIndex.cpp:899] No limit on the number of 
stored patients
I0316 12:08:26.891720 99033 Statement.cpp:110] SQLite::Statement::Run BEGIN 
TRANSACTION
I0316 12:08:26.891731 99033 Statement.cpp:110] SQLite::Statement::Run COMMIT
W0316 12:08:26.891741 99033 ServerIndex.cpp:920] At most 1048576MB will be used 
for the storage area
I0316 12:08:26.891751 99033 Statement.cpp:110] SQLite::Statement::Run BEGIN 
TRANSACTION
I0316 12:08:26.891759 99033 Statement.cpp:110] SQLite::Statement::Run COMMIT
W0316 12:08:26.891976 99033 main.cpp:264] DICOM server listening on port: 13010
W0316 12:08:26.891995 99033 main.cpp:265] HTTP server listening on port: 8042
I0316 12:08:26.891996 99034 ServerIndex.cpp:232] Starting the database flushing 
thread (sleep = 10)
I0316 12:08:26.892719 99033 ServerIndex.cpp:293] Stopping the database flushing 
thread
E0316 12:08:26.892889 99033 main.cpp:290] EXCEPTION [Unable to launch the 
Mongoose server]

Original comment by rico....@gmail.com on 16 Mar 2013 at 7:11

GoogleCodeExporter commented 9 years ago
Please could you attach your two "Configuration.json" files (for the working 
"previous settings" and for the problematic "new settings")?

Could you try using another HTTP port than 8042? There is perhaps a 
RHEL-related restriction on this port.

Original comment by s.jodo...@gmail.com on 16 Mar 2013 at 10:09

GoogleCodeExporter commented 9 years ago
here is the new one

Original comment by rico....@gmail.com on 18 Mar 2013 at 5:28

Attachments:

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
original 

Original comment by rico....@gmail.com on 18 Mar 2013 at 5:56

Attachments:

GoogleCodeExporter commented 9 years ago
Sorry for the delay. Your SSL certificate for HTTPS encryption is presumably 
badly formatted. The instructions to build a proper certificate can be found on 
the FAQ:
https://code.google.com/p/orthanc/wiki/FAQ#How_can_I_use_HTTPS_(SSL_encryption)_
with_Orthanc?

Could you tell me whether this FAQ entry indeed solves your problem? TIA!

Original comment by s.jodo...@gmail.com on 19 Apr 2013 at 10:28

GoogleCodeExporter commented 9 years ago
I assume that this issue is fixed now, after 3 months of inactivity. Please ask 
me to reopen it if you have further issue.

Original comment by s.jodo...@gmail.com on 18 Jul 2013 at 7:13