Export CSV fails depending on the selected UI language

[tat...@gmail.com]

Hi everybody,

The export CSV feature works fine in my Atom 2.3 instance as long as I have English as the current UI language.

As soon as I change the language to Brazilian Portuguese (pt_BR) by using the language icon on the top menu, the export operation starts to fail with error 500.

My /var/log/nginx/error.log file shows:

2016/08/03 03:12:41 [error] 1927#0: *1118 FastCGI sent in stderr: "PHP message: No Gearman worker available that can handle the job arInformationObjectCsvExportJob" while reading response header from upstream, client: 179.187.100.30, server: www.arqunb.com.br, request: "GET /index.php/informationobject/exportCsv?sf_culture=pt_BR&sort=alphabetic HTTP/1.1", upstream: "fastcgi://unix:/var/run/php5-fpm.atom.sock:", host: "www.arqunb.com.br", referrer: "http://www.arqunb.com.br/index.php/informationobject/browse?sf_culture=pt_BR&sort=alphabetic"

My /var/log/nginx/atom23/log/atom-worker.log doesn't show anything related to the failed export operation.

The command sudo status atom-worker shows:

atom-worker start/running, process 6332

Running sudo restart atom-worker does not affect the outcome.

Changing the UI language back to English fixes the problem. The export then runs smoothly with the job progress showing on atom-worker.log:

2016-08-02 20:12:31 > Job 2033 "arInformationObjectCsvExportJob": Starting export to /tmp/search_export_2033.

2016-08-02 20:12:31 > Job 2033 "arInformationObjectCsvExportJob": Exported 1 descriptions.

2016-08-02 20:12:31 > Job 2033 "arInformationObjectCsvExportJob": Creating ZIP file /usr/share/nginx/atom23/downloads/jobs/2033.zip.

2016-08-02 20:12:31 > Job 2033 "arInformationObjectCsvExportJob": Export and archiving complete.

2016-08-02 20:12:31 > Job 2033 "arInformationObjectCsvExportJob": Job finished.

How can the selected UI language affect atom's ability to reach gearman?

Thanks in advance,

Tatiana Canelhas

[Jesús García Crespo]

Hi Tatiana,

How can the selected UI language affect atom's ability to reach Gearman?

I'm afraid I don't have a response to your question yet. I wasn't able to reproduce - I specifically tried to to generate the export after switching my user interface to Brazilian Portuguese and it worked.

Could you take a look to the atom-worker.log file under /var/log/upstart? Is there anything interesting in there? Any error? Also, can you please compare the PID of the atom-worker before and after the 500 error? I'm wondering if the worker is maybe dying even before AtoM tries to reach it.

Thank you! We'll keep an eye on this thread to make sure that you issue is solved!

--
You received this message because you are subscribed to the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/face5c5b-2c1d-4dff-816d-d37e461d234f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Jesús García Crespo,
Software Engineer, Artefactual Systems Inc.
http://www.artefactual.com | +1.604.527.2056

[Tatiana]

Dear Jesús,

Thank you for your reply!

> Could you take a look to the atom-worker.log file under /var/log/upstart? Is there anything interesting in there? Any error?

Nothing interesting. In fact, there are only .gz files, that is, there's no recent activity:

ubuntu@ip-172-31-39-169:~$ ls /var/log/upstart/atom* -l

-rw-r----- 1 root root 144 Aug  3 02:46 /var/log/upstart/atom-worker.log.1.gz

-rw-r----- 1 root root 125 Aug  1 17:54 /var/log/upstart/atom-worker.log.2.gz

-rw-r----- 1 root root 134 Jul 26 16:06 /var/log/upstart/atom-worker.log.3.gz

-rw-r----- 1 root root 121 Jun 30 19:37 /var/log/upstart/atom-worker.log.4.gz

-rw-r----- 1 root root 121 Jun 24 12:40 /var/log/upstart/atom-worker.log.5.gz

-rw-r----- 1 root root 121 Jun 16 14:06 /var/log/upstart/atom-worker.log.6.gz

-rw-r----- 1 root root 129 Jun 13 21:58 /var/log/upstart/atom-worker.log.7.gz

The most recent activity, from a day ago, is some old errors related to log directory permissions which I already corrected.

> Also, can you please compare the PID of the atom-worker before and after the 500 error?

There's no change in the PID. I'm not sure if you mean the PID from the "php" process or the "sh" process, so I observed both:

ubuntu@ip-172-31-39-169:~$ ps -A a | grep "jobs:worker"

 2692 ?        S      0:00 php -d memory_limit=-1 -d error_reporting=E_ALL /usr/share/nginx/atom23/symfony jobs:worker

 2810 pts/0    S+     0:00 grep --color=auto jobs:worker

ubuntu@ip-172-31-39-169:~$ sudo status atom-worker

atom-worker start/running, process 2690

ubuntu@ip-172-31-39-169:~$ ps -A a | grep "2690"

 2690 ?        Ss     0:00 /bin/sh -e /proc/self/fd/9

 2814 pts/0    S+     0:00 grep --color=auto 2690

 The output from the commands above is unchanged before and after the 500 error.

Are there more tests you'd like me to run?

Kind regards,

Tatiana Canelhas

--
You received this message because you are subscribed to a topic in the Google Groups "ICA-AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/dacpdpUP4ZQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to ica-atom-user...@googlegroups.com.

To post to this group, send email to ica-ato...@googlegroups.com.
Visit this group at https://groups.google.com/group/ica-atom-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CALavCbRSMs3cZJwM4Vn_MURtzhYeSA%2BpWqCRtATLgL1Z%3DTX7ag%40mail.gmail.com.

[Mike G]

Hi,

Can you try stopping the atom-worker job then manually running it and see if that helps? It might be useful to rule out upstart config issues.

sudo stop atom-worker

# cd to your AtoM directory

sudo php symfony jobs:worker  # use sudo so we can rule out any permissions issues

# try your export job from the UI now

thanks