Search found 20 matches
- Thu Mar 18, 2010 3:05 am
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
otool and uname results
Below is the output from the otool and uname commands sh-3.2# otool -L PacsOneSrv.exe PacsOneSrv.exe: /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 88.3.11) /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation (compatibility version 150.0.0, curren...
- Sat Mar 13, 2010 8:13 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
The license.dat file is there. Via the web interface, it reports an expiration date of April 12. I tried the PacsOneSrv.exe command without redirecting output, but nothing seems to happen. No errors, no output, no process running, no pid file. Below is the output. Are there any switches I can pass t...
- Sat Mar 13, 2010 2:06 am
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
still nothing - it just doesn't want to run PacsOneSrv.exe
The "ps Aux" version still doen't show anything. Also, there are no logs besides the install log. In fact, I tried to directly use the command in the startup script. Below is the output. As you can see, the process quickly says "Done" and no logs are ever created. sh-3.2# cd /home/pacsone/log sh-3.2...
- Fri Mar 12, 2010 10:14 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
sanity check
Just as a sanity check, shouldn't I get something when I enter the commands
/sbin/SystemStarter start "PacsOne Server Premium Edition"
or
/sbin/SystemStarter stop "PacsOne Server Premium Edition"
because right now, I see nothing.
/sbin/SystemStarter start "PacsOne Server Premium Edition"
or
/sbin/SystemStarter stop "PacsOne Server Premium Edition"
because right now, I see nothing.
- Fri Mar 12, 2010 9:57 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
sample outputs
First, thank you for your responses. I really appreciate you taking the time to help me. Below is the output that correspond to your suggestions. sh-3.2# /sbin/SystemStarter start "PacsOne Server Premium Edition" sh-3.2# ps -ef | grep PacsOne 0 1062 1053 0 0:00.00 ttys000 0:00.00 grep PacsOne sh-3.2...
- Fri Mar 12, 2010 8:43 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
Cannot reinstall - missing pacsone.pid
I attempted a complete reinstall from scratch. I have the license.dat file backed up and copied it back into place. However, I run into trouble at near the end. It says it cannot find /home/pacsone/pacsone.pid I am running out of ideas. ***************************************************************...
- Fri Mar 12, 2010 8:26 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
There is only one .ini in the pacsone installation directory. There was never more than one. When I mentioned the additional AE titles, I was referring to the additional dicom nodes that I entered through the pacsone web interface under the "DICOM AE" tab. When I execute "ps -ef|grep PacsOne" I see ...
- Fri Mar 12, 2010 2:42 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
The remaining half of the problem - can't receive DICOM
So, I am able to login into the web interface of pacsone successfully and can see the images that I previously sent to pacsone. However, I cannot send any new dicom. The dicom association fails from a node which previously successfully sent dicom to pacsone. I looked at some of the pacsone logs, and...
- Fri Mar 12, 2010 2:30 pm
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
Half of the problem solved
I finally solved half of the problem, and it was my own fault. In the process of getting the installation pacsone to work, I had used macports to install "universal". i.e. 32 bit, versions of Apache and PHP so that imagick.so would work. I eventually found that I could convert the 64-bit Apache and ...
- Fri Mar 12, 2010 2:49 am
- Forum: Installation Trouble
- Topic: Installation broken after reboot - only acess from localhost
- Replies: 17
- Views: 7919
Installation broken after reboot - only acess from localhost
PacsOne premium has been working on my iMac just fine for about a week. Then I had to reboot today. After the reboot, I can only successfully login when using a URL such as http://localhost/pacsone/home.php Using http://127.0.0.1/pacsone/home.php shows the login page but leads to a blank page after ...
- Tue Mar 02, 2010 7:37 pm
- Forum: Known Bugs
- Topic: Philips SOP classes
- Replies: 4
- Views: 8741
Thank you for your reply. I also think handling private/custom SOP classes is frustrating, but it is unfortunately a reality. In this case, it is not necessary for PacsOne to do anything with the binary blobs of information which have the DICOM header wrapped around it. I just need for the files to ...
- Tue Mar 02, 2010 4:33 pm
- Forum: Known Bugs
- Topic: Philips SOP classes
- Replies: 4
- Views: 8741
Philips SOP classes
I am putting this under "known bugs" even though it might be considered to be a "desired feature". Basically, I believe I have confirmed that PacsOne.exe does not support all of the SOP classes that come from our Philips MR scanner. This is a significant problem because we want to use PacsOne to arc...
- Mon Mar 01, 2010 2:36 am
- Forum: Installation Trouble
- Topic: cannot connect to database
- Replies: 9
- Views: 4042
path to mysql.sock in php.ini was incorrect
I finally found the problem. The path to the mysql socket was incorrect in the php.ini file. I was careful to enter the correct path into the pacsone installation and it appeared correctly in the .ini created for my pacsone instance, but that wasn't enough. The path must also be correct in the php.i...
- Sat Feb 27, 2010 6:13 am
- Forum: Installation Trouble
- Topic: cannot connect to database
- Replies: 9
- Views: 4042
pacsone log contents
Below are the contents of the pacsone log file. There is an error reported for binding to the specified DICOM listening port (3010). Is this a serious problem? Sat Feb 27 00:09:06 2010 INFO - Server Process [15725] Initialized as AE Title: [appa_pacsone_1] Sat Feb 27 00:09:06 2010 INFO - Server Sock...
- Sat Feb 27, 2010 5:07 am
- Forum: Installation Trouble
- Topic: cannot connect to database
- Replies: 9
- Views: 4042