Tasks not loading since OJS3 upgrade

Hi!
I was reported today by a user, that the tasks function on admin page is not working:

It keeps loading, so I’ve checked on errors log and I’m getting this messages:

2017/05/08 09:36:50 [error] 5222#5222: *84775 FastCGI sent in stderr: "PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347" while reading response header from upstream, client: 192.168.192.153, server: _, request: "GET /periodicos/index.php/desafios/$$$call$$$/page/page/user-nav-backend?_=1494247055517 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sistemas.uft.edu.br", referrer: "https://sistemas.uft.edu.br/periodicos/index.php/desafios/submissions"

2017/05/08 09:36:50 [error] 5222#5222: *84777 FastCGI sent in stderr: "PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347" while reading response header from upstream, client: 192.168.192.153, server: _, request: "GET /periodicos/index.php/desafios/submissions/myQueue?_=1494247055518 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sistemas.uft.edu.br", referrer: "https://sistemas.uft.edu.br/periodicos/index.php/desafios/submissions"

2017/05/08 09:36:52 [error] 5222#5222: *84779 FastCGI sent in stderr: "PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347

PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php on line 347
PHP message: PHP Notice:  unserialize(): Error at offset 1011 of 1040 bytes in /srv/ojs/releases/3/lib/pkp/classes/db/DAO.inc.php 

2017/05/08 09:36:52 [error] 5222#5222: *84779 upstream sent too big header while reading response header from upstream, client: 192.168.192.153, server: _, request: "GET /periodicos/index.php/desafios/$$$call$$$/grid/notifications/task-notifications-grid/fetch-grid?_=1494247055519 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sistemas.uft.edu.br", referrer: "https://sistemas.uft.edu.br/periodicos/index.php/desafios/submissions"

Does anyone has a idea what is causing this?

Hi @rafaelmansilha,

Is it possible that you accidentally changed your database charset configuration during upgrade?

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher,

I really believe that we didn’t have changed. I give a look, and the database is in latin1, the application works on UTF8, or it doesn’t make difference?

Regards,
Rafael Mansilha.

Hi @rafaelmansilha,

Yes, that makes a difference. Everything should ideally be utf8, but rather than trying to adapt that and upgrade at the same time, I’d suggest ensuring that your old and new config.inc.php files have the same configuration. That should resolve the unserialize warnings. Then investigate using a tool like iconv to convert a database dump, so that your setup is fully UTF8. Do these separately – it’s fiddly, and if you operate with an incorrect configuration, you’ll end up with mixed content that’s really tough to disentangle.

Regards,
Alec Smecher
Public Knowledge Project Team

I’ve looked to convert my mysqldump and I find UTF8 chars, Windows-1251 Chars and ISO-8859-9 chars. Seems Impossible to resolve this.

Hi @rafaelmansilha,

I’m afraid this is complex to resolve and outside of OJS’s sphere – I recall seeing some useful information/tools on StackOverflow, so it might be worth a search.

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher,

I’ve manage to fix the the database problem, now it’s all set to utf8:

Database info:
Captura de tela de 2017-09-27 13-29-32

Tables info:
Captura de tela de 2017-09-27 13-30-09

config.inc.php Localization Settings:
Captura de tela de 2017-09-27 13-42-53

But, we are still getting this error message about Tasks:

2017/09/27 13:22:42 [error] 16158#16158: *25347 upstream sent too big header while reading response header from upstream, client: 192.168.192.153, server: _, request: "GET /periodicos/index.php/index/$$$call$$$/grid/notifications/task-notifications-grid/fetch-grid?_=1506529562343 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sistemas.uft.edu.br", referrer: "https://sistemas.uft.edu.br/periodicos/index.php/index/admin/index"

Hi @rafaelmansilha,

I’m not sure this will solve the problem, but connection_charset should be utf8, not utf-8. (The inconsistency in these settings is caused by upstream libraries that have different requirements.)

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher

I’ve made the change now. I don’t know if it was like that before, but I’ve noticed that when I change to another journal it works, but in another I get that error message and it not works.

2017/09/27 14:32:19 [error] 16160#16160: *33068 upstream sent too big header while reading response header from upstream, client: 192.168.192.153, server: _, request: "GET /periodicos/index.php/desafios/$$$call$$$/grid/notifications/task-notifications-grid/fetch-grid?_=1506533740930 HTTP/1.0", upstream: "fastcgi://unix:/var/run/php5-fpm.sock:", host: "sistemas.uft.edu.br", referrer: "https://sistemas.uft.edu.br/periodicos/index.php/desafios/submissions"

i @rafaelmansilha,

I’ve never seen that message before – it’s coming from something further up your server stack. Have a look at this thread.

Regards,
Alec Smecher
Public Knowledge Project Team

Hi @asmecher,

Sorry for my ignorance, this link solved the problem, I’ve never linked the problem with nginx!

Thank You!