Beginner, studying logs I found some errors

Known bugs reported by PacsOne users
Post Reply
rvencu
Posts:53
Joined:Thu Aug 16, 2012 9:46 am
Beginner, studying logs I found some errors

Post by rvencu » Wed Nov 14, 2012 8:14 am

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?

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Wed Nov 14, 2012 4:45 pm

1. You can find the detailed error from the statistics report via the following log file under the directory where PacsOne is installed:

Code: Select all

log/report/daily-$WeekDay-$AeTitle.htm
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.

rvencu
Posts:53
Joined:Thu Aug 16, 2012 9:46 am

Post by rvencu » Fri Nov 16, 2012 10:08 pm

OK, I will watch that.

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
I have been into apache error_log and I found this kind of error everytime I experiente de browser error mentioned above

Code: Select all

[Fri Nov 16 23:55:42 2012] [notice] child pid 8078 exit signal Segmentation fault (11)
I will search about this error in the internet but if you have any idea just let me know please

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Sun Nov 18, 2012 12:20 am

What version of Apache are you running and did you also check the PHP error log and see if there's any error logged there?

rvencu
Posts:53
Joined:Thu Aug 16, 2012 9:46 am

Post by rvencu » Tue Nov 20, 2012 7:12 pm

Server version: Apache/2.2.15 (Unix)

php error log was not defined, I set it up in php.ini, will come back when I can catch the errors again...

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Tue Nov 20, 2012 7:15 pm

2.2.15 is out of date as the latest release is 2.2.23 for the 2.2 branch. So maybe you should upgrade to the latest release as well while setting up the PHP error log.

rvencu
Posts:53
Joined:Thu Aug 16, 2012 9:46 am

Post by rvencu » Tue Nov 20, 2012 7:23 pm

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.

pacsone
Site Admin
Posts:3149
Joined:Tue Sep 30, 2003 2:47 am

Post by pacsone » Wed Nov 21, 2012 5:13 pm

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.

Post Reply