Beginner, studying logs I found some errors
I think they may be not bugs but misconfiguration... Anyway here are some errors I found in my logs:
1. Wed Nov 14 00:00:29 2012 ERROR - REPORT: Failed to run script: /home/PacsOne/php/dailyreport.php, error = 139
2. Wed Nov 14 08:00:03 2012 ERROR - AUTO-AGE: Failed to copy from [/DICOM/2012-09-08-SAT/1.2.840.113543.6.6.1.5.2.6254878720000065281.209355381021280] to [/mnt/s3/pacs-devel/2012-11-14-WED/1.2.840.113543.6.6.1.5.2.6254878720000065281.209355381021280]
this one could be due to wrong write permission at target folder, I made it 777 and will check again tommorow
3. Wed Nov 14 08:00:04 2012 ERROR - AUTO-AGE: Failed to access image file [/DICOM/2.16.840.1.113669.632.10.20111101.112729642.47956.5110.3]
the files are really missing still I have no idea why they dissapeared. perhaps the aging process deleted them anyway even if it is unable to copy to the long term archive in the first place?
1. Wed Nov 14 00:00:29 2012 ERROR - REPORT: Failed to run script: /home/PacsOne/php/dailyreport.php, error = 139
2. Wed Nov 14 08:00:03 2012 ERROR - AUTO-AGE: Failed to copy from [/DICOM/2012-09-08-SAT/1.2.840.113543.6.6.1.5.2.6254878720000065281.209355381021280] to [/mnt/s3/pacs-devel/2012-11-14-WED/1.2.840.113543.6.6.1.5.2.6254878720000065281.209355381021280]
this one could be due to wrong write permission at target folder, I made it 777 and will check again tommorow
3. Wed Nov 14 08:00:04 2012 ERROR - AUTO-AGE: Failed to access image file [/DICOM/2.16.840.1.113669.632.10.20111101.112729642.47956.5110.3]
the files are really missing still I have no idea why they dissapeared. perhaps the aging process deleted them anyway even if it is unable to copy to the long term archive in the first place?
1. You can find the detailed error from the statistics report via the following log file under the directory where PacsOne is installed:
where $WeekDay is the Day of the Week, and $AeTitle is the AE Title assigned to this instance of PacsOne Server.
2 & 3. During automatic aging, PacsOne Server does NOT remove the original Dicom image file under unless it has been copied successfully to the new/destination folder.
Code: Select all
log/report/daily-$WeekDay-$AeTitle.htm
2 & 3. During automatic aging, PacsOne Server does NOT remove the original Dicom image file under unless it has been copied successfully to the new/destination folder.
OK, I will watch that.
In the meanwhile I noticed that the browser sometimes gets errors such as:
I have been into apache error_log and I found this kind of error everytime I experiente de browser error mentioned above
I will search about this error in the internet but if you have any idea just let me know please
In the meanwhile I noticed that the browser sometimes gets errors such as:
Code: Select all
Error 324 (net::ERR_EMPTY_RESPONSE): The server closed the connection without sending data
Code: Select all
[Fri Nov 16 23:55:42 2012] [notice] child pid 8078 exit signal Segmentation fault (11)
I am still failing to create the php log file... but I just noticed something: all segmentation faults are temporary while php tries to read or write files on disk.
For instance when I progress with the localization and upload a new $locale.mo file, then I try to access the website I get 6 to 7 faults then everything runs very smoothly.
When I access a serie with images that are converted in at server side to JPG (for thumbnails, etc) I get sometimes segmentation faults during the processing of the conversion. After all thumbnails are ready there is no more problem.
For instance when I progress with the localization and upload a new $locale.mo file, then I try to access the website I get 6 to 7 faults then everything runs very smoothly.
When I access a serie with images that are converted in at server side to JPG (for thumbnails, etc) I get sometimes segmentation faults during the processing of the conversion. After all thumbnails are ready there is no more problem.
The symptom suggests the problem is with the Apache build, because you would NOT get any converted JPG/GIF thumbnails if there's any issue with the ImageMagick PHP extension.
You should upgrade to the latest stable release of the Apache 2.2 branch. If you must stay with the current release, then try enabling core dumps then submit a bug report with Apache bugzilla and attach the dumped core files.
You should upgrade to the latest stable release of the Apache 2.2 branch. If you must stay with the current release, then try enabling core dumps then submit a bug report with Apache bugzilla and attach the dumped core files.