Atom 2.0.1: 502 Bad Gateway

[Igor Castro]

Hi,

I'm using Atom 2.0.1 with Nginx and when I print the dossier's reports, for example, I get the error "502 Bad Gateway". 

I would like to know how can I improve the Atom's performance and avoid this error.  Are there best practices to improve peformance when you've a archival description with many connections? For example, we've a Fond in our institution with about 6500 associated information objects.

Thanks in advance.

Igor Machado,

Oswaldo Cruz Foundation

[Mike G]

Hi Igor,

I think if it was a performance/time out issue you'd get a different error. Can you set AtoM to debug mode and see if there is any additional information about the error?

Cheers

[Igor Castro]

Hi Mike,

This is the error:

Catchable fatal error: Argument 1 passed to QubitInformationObject::getStandardsBasedInstance() must be an instance of QubitInformationObject, null given, called in /usr/share/nginx/atom/apps/qubit/modules/informationobject/actions/itemListAction.class.php on line 153 and defined in /usr/share/nginx/atom/lib/model/QubitInformationObject.php on line 2504

Thanks in advance

Igor Machado,

Oswaldo Cruz Foundation

[Mike G]

Hi Igor,

I looked at the code and it's failing when trying to pass an archival description's parent, apparently it is set to NULL, which should never be the case in AtoM. Can you try running the task:

php symfony propel:build-nested-set

And then once that is finished try again?

Hope this helps

[Igor Castro]

Hi Mike,

We tried to run the command you suggested but the error still persists. Is there another suggestion?

Thanks in advance.

Igor Machado,

Oswaldo Cruz Foundation

[Ben Stewart]

I had this error if I did not have the www-data user setup correct 

www-data:x:500:500:nginx:/usr/share/nginx/atom:/sbin/nologin

make sure the default.conf is removed from /etc/ngix/conf.d/

Also make sure the folder is is owned by www-data

I  also seemed to have an issue if I could not finish the script for the setup and it broke I have to replace the atom web director and start again.

~Ben

[Igor Castro]

Hi, Ben

First of all, thanks for the answer. I did like you said but the error still persists. Like I said before, for example, in our institution we've a Fond with about 6500 associated information objects and when I print dossier's reports I get the error "502 Bad Gateway". I don't know if the Fond is too big and because of it the Atom requires some special software configuration or hardware's improvement.

When I try printing a Fond with few associated information objects, the PDF file is normally generated. When a Foun is a little bigger, the PDF file is generated incompleted and, finally, when the Fond is too big I get the 502 Bad Gateway error.

I really dont know where could be the failure point. I'm thinking about three possibilities:  Nginx's configuration problem,  Atom's limitation or hardware's improvement.

Thanks very much for help.  

Igor Machado

Oswaldo Cruz Foundation