Hello, I noticed on my Alfresco server (version 4.2.e ) that a 'gs' process launched by alfresco user is always at 100% CPU, since a lot of days. How can I deal with it?
Here is the detail about the process:
gs -q -dQUIET -dSAFER -dBATCH -dNOPAUSE -dNOPROMPT -dMaxBitmap=500000000 -dAlignToPixels=0 -dGridFitTT=2 -sDEVICE=bmpsep8 -dTextAlphaBits=4 -dGraphicsAlphaBits=4 -r72x72 -dUseCIEColor -dFirstPage=1 -dLastPage=1 -sOutputFile=/tmp/magick-69146BhKdHpuUozNa%d -f/tmp/magick-69146DPKVREKVWdI8 -f/tmp/magick-69146mUYtJrgbjWC6
I found that it is a Ghostscript process, that I suppose is linked with document preview...Since we do not use document preview, is there a way to disable it?
Alfresco 4.2 is an old release. Both Alfresco and the 3rd party software components it uses have evolved since then. It may be worth updating them, since some issues may have already been addressed.
GhostScript may not just be used for document previews, but also for thumbnails, depending on the document mimetype. You'd need to identify which specific document within Alfresco is being processed at this time to potentially check its contents and identify the reason it triggers this 100% CPU utilisation behaviour. For the time being, I would simply kill the GhostScript process when it pops up again, and try to update those 3rd party components or Alfresco as a whole (i.e. if you opted for the monolithic install via the default installer when setting up your system).
There is no way to disable GhostScript individually in Alfresco. It is being called indirectlyas part of an ImageMagick conversion (you can see that from the temporary file name). So you'd have to disable ImageMagick by simply not configuring it correctly in alfresco-global.properties (i.e. incorrect path) for GhostScript to no longer be triggered.
Hi:
Instead of disabling Imagemagick with an incorrect path, maybe a possibility is:
system.thumbnail.generate=false
(in alfresco-global.properties for disabling thumbnails).
Regards.
--C.
Thank you both for your ideas. In the last days I had the chance to restart alfresco, so I manually killed the gs process, and now it does not appear again. I have also added in alfresco-global.properties the option suggested.
In the next few weeks we will perform an Alfresco upgrade, too...since we also had some issues with the old MySQL installation we had on that server.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.