Hi every one!
I have two problems with my AToM installed.
When I migrate to version 2.2.1 I preserve the 2.2.0 version on atom_old directory with database outdated.
1 - The instance with the 2.2.1 version does not load completely after two weeks of upgrade. Only the first "Browse by" menu, without loading css and javascript. But in other parts of the site it loads normally, only the first page got this error.
- Because of this error, I did a downgrade to version 2.2.0 and then came to database outdated. I create a third directory with the database of instance 2.2.1 and the directory of the version 2.2.0, and them problem two:
2 - When running the command elastic search (./symfony search: populate) got the following message:
Could not find object information (id: 15988).
I see that problem two occurs on version 2.2.1 too.
I think is a problem on database. I see that was a lot of bugs on MySQL version 5.5 , ASAP I will perform a database upgrade to MySQL version 5.7.
See my list of applications and versions required and mandatory to AToM:
Application |
Version |
Status |
||
Required |
||||
Sistema Operacional: Debian 7.8 64bits |
7.8 64bits |
ok |
||
Apache: Apache/2.2.22 |
2.2.22 |
ok |
||
Elasticsearch: 1.7.5 |
1.7.5 |
ok |
||
Java: OpenJDK Runtime Environment (IcedTea6 1.13.8) (6b36-1.13.8-1~deb7u1) 64-bit |
1.13.8 64bits |
ok |
||
MySQL: 5.5.47 |
5.5.47 |
ok |
||
PHP: 5.4.45 |
5.4.45 |
ok |
||
Memcached: 1.4.13 |
1.4.13 |
ok |
||
German job server - Installed |
|
ok |
||
Mandatory |
||||
cURL (php5-curl) = OK 7.26.0 |
7.26.0 |
ok |
||
JSON (php5-json) = Adicionado por padrão... Sem informações |
NA |
ERR |
||
APC (php-apc, or php5-apcu in PHP 5.5) = OK 3.1.13 |
3.1.13 |
ok |
||
PDO and PDO-MySQL (php5-mysql) = OK 5.5.44 |
5.5.44 |
ok |
||
XSL (php5-xsl) = OK 1.1.26 |
1.1.26 |
ok |
||
You'll probably want to clear your cache and restart php5-fpm after:
The "could not find information object" error you encountered when trying to populate the search index may indicate that you have corrupt data? This can occur if you have attempted large requests via the browser that have timed out - for example, imports. I can ask our developers to take a look at this thread and see if they have suggestions to resolve this, or how best to investigate further.
Regards,
--
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/d86013da-d528-4b50-86f0-08da05f7effc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Build nested set:
I would also then clear the cache and restart your services (webserver, php5-fpm, etc).
We have some video tutorials that will show you the basic use of these CLI tasks - video 5 in this series should cover them both:
Let us know if these suggestions help!
If the solutions above don't work, it may be because of data corruption -
some process (like an import, creation, etc) that halted mid-process
and left incomplete data in the system. The most common case is when the
publication status is missing in the database. You will have to add it
directly via SQL queries in this case - see the following thread for
some advice:
For
more details, and if the above solution doesn't work, please see this
thread - it includes a query that should help you identify problem rows
in the database, as well as a proposed query to resolve a much more rare
issue:
Note
that in AtoM 2.3, we will be introducing the use of transactions, to
try to prevent data corruption - essentially, if a request times out
mid-process, AtoM will automatically roll back to the last database
state, instead of leaving corrupted data in the system.
Good luck!
Victor Hase.
--
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/0980edf8-755e-462a-ae7e-4b55abbb7b56%40googlegroups.com.
You might also try putting the application in Debug mode while repeating the errors, to see if there is any useful information. See:
This video tutorial will show you both of the above steps - how to access the Nginx error logs, and how to enable Debug mode:
Hopefully more information about the errors will help us diagnose the issue.
Thanks,
Hi Dan,I move all website content to a server with UBUNTU 14.04, NGINX, MYSQL 5.7 and all mandatory resquisits.
The problem persists, but I discover what causing the problem 1. When user input another traduction to a field, the site become unstable and problem 1 occurs even the traduction don't change.
To solve this problem I recover to last state database.My default language on this version was pt_BR.I discover other problem. When user deletes authority records freezes any adding option.Regards,Victor Tavares.
--
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/01b4a31a-49a4-4dad-ba13-80f6377d383a%40googlegroups.com.
Hi Dan.
I just remove the data which are currupted and $ php symfony search:populate works.
I save the data for future adding.
I think the problem are another.
Thanks,
Victor Tavares.
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/sZki6TtdX00/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/CAC1FhZKM-_--N-u_0d3YeM_bhVs%2B7G44i8O3NHi_Ty1EHJ%3D-YA%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAAj_XjqY%3DN_HXeRQSe0hVsenYfqMjRW9NzBDf4D6ddp55TN1jQ%40mail.gmail.com.
--
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/9df8bd1a-3a06-42e7-a884-af367c3bcda8%40googlegroups.com.