sfInitializationException - You must have APC installed and enabled to use sfAPCCache class.

[calima...@gmail.com]

Hi.
At the end of installation of ICA-AtoM when configure database show this error.

You know how to solve?

[Dan Gillean]

Hi there,

What version of AtoM are you trying to install? We recommend installing the latest release, AtoM 2.3.

The answer to solving this will also depend on what version of Ubuntu and PHP you are installing with. For AtoM 2.3, we have included 2 different sets of instructions - one for Ubuntu 14.04 with PHP 5.5, and one for Ubuntu 16.04 with PHP 7. See:

• https://www.accesstomemory.org/docs/2.3/admin-manual/installation/linux/linux/

Depending on your version, the short answer is: use APCu with AtoM for newer versions of PHP, instead of APC. For more details on why, and what the difference is, please see this related thread:

• https://groups.google.com/d/msg/ica-atom-users/Gj47L1rUBsg/M1OvEaVUDAAJ

There was a user who posted additional tips for making this work using FreeBSD, here:

• https://groups.google.com/d/msg/ica-atom-users/1h2c8me8uM8/LahE19GCAQAJ

Remember, if you make edits to the PHP pool or the config/app.yml file, we recommend clearing the application cache and restarting PHP-FPM after.

Clear the cache:

• php symfony cc

Restart PHP-FPM:

• PHP 5.5 with Ubuntu 14.04: sudo service php5-fpm restart
• PHP 7 with Ubuntu 16.04: sudo systemctl restart php7.0-fpm
  

Let us know if that helps!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
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/f4ed3271-b426-40c1-90bb-c4124849c879%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[calima...@gmail.com]

Hi Dan Gillean,

I discovered the error.
In the documentation this settings is these:

• Database username: atom
• Database password: 12345

But the right are:

• Database username: root
• Database password: Password chosen for the MySQL

If we follow exactly the tutorial.

[Dan Gillean]

Hi Caliman,

Thanks for this information!

Just to double check - in the instructions, after creating the database as root, we then include a command in the instructions to create a specific MySQL user for AtoM use, to improve security:

Additionally, it’s always a good idea to create a specific MySQL user for AtoM to keep things safer. This is how you can create an user called atom with password 12345 and the permissions needed for the database created above.

• mysql -h localhost -u root -p -e "GRANT INDEX, CREATE, SELECT, INSERT, UPDATE, DELETE, ALTER, LOCK TABLES ON atom.* TO 'atom'@'localhost' IDENTIFIED BY '12345';"

Did you follow this step as well? If so, and it still didn't work, I will ask our developers to test and review these instructions.

Cheers,

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
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/26bf1c48-5327-497b-9b74-a5098214fcf6%40googlegroups.com.

[Bernhard]

Hello!
I had exactly the same problem as above . I had forgotten to log in as "root" during installation . Now running AtoM 2.3 !
Bernhard

[Jim Adamson]

Hi all,

I resolved this problem by installing apcu_bc from the Debian repo rather than using the documented pecl method:

sudo add-apt-repository "deb http://ftp.uk.debian.org/debian sid main"

sudo apt-get update

sudo apt-get install php-apcu-bc

This worked for me in Ubuntu 16.04.2 LTS, in a vagrant box. This allows me to use the "atom" database user rather than the "root" user, which is safer. Note that "sid" is an unstable repo, and the version of apcu-bc installed is:

php-apcu-bc/unstable,now 1.0.3-2 amd64 [installed]

I guess there's potential for falling foul of other problems as a result of using this variant of php-apcu-bc, but at least it resolves the immediate problem.

An aside: one thing I'm not clear on is why the web installer's default database username is set to root in the form input field, which might to a lot of people's minds suggest that it should be set up with the root user.

Jim

[Freddy Pelayo Huapalla]

Hi.
At the end of installation of ICA-AtoM when configure database show the same error.

Thing is... I followed the instruction for Ubuntu 16.04 and...

• Percona Database
  
• Openjdk-8
  
• Nginx
  
• PHP 7.0
  
• AtoM 2.4

Basically all the components described in the Manual for this distribution:

• https://www.accesstomemory.org/es/docs/2.4/admin-manual/installation/linux/ubuntu-xenial/
  

I tried both the git and tarball but in both cases I get the same result in the end, 

I hope you can help me, thank you so much in advanced 

[Jim Adamson]

Hi Freddy,

Did you install apcu-bc?

wget -q http://ftp.uk.debian.org/debian/pool/main/p/php-apcu-bc/php-apcu-bc_1.0.3-2_amd64.deb && dpkg -i php-apcu-bc_1.0.3-2_amd64.deb

Thanks, Jim

[Dan Gillean]

Hi Freddy, 

Jim is correct in pointing out that the error seems to be that php-apcu-bc seems to be either missing from your installation, or not configured correctly. 

Jim's method may be correct (or an updated method - when we wrote the docs, php-apcu-bc was not supported in official linux apt-get packages), but for reference, here is exactly how we recommend installing and configuring this in our 16.04 documentation: 

We also need php-apcu-bc, which is not available yet in Ubuntu 16.04. Let’s install it manually for now:

sudo apt install php-dev
sudo pecl install apcu_bc-beta
echo "extension=apc.so" | sudo tee /etc/php/7.0/mods-available/apcu-bc.ini
sudo ln -sf /etc/php/7.0/mods-available/apcu-bc.ini /etc/php/7.0/fpm/conf.d/30-apcu-bc.ini
sudo ln -sf /etc/php/7.0/mods-available/apcu-bc.ini /etc/php/7.0/cli/conf.d/30-apcu-bc.ini
sudo systemctl restart php7.0-fpm

In this section: https://www.accesstomemory.org/en/docs/2.4/admin-manual/installation/linux/ubuntu-xenial/#php

Make sure you have also configured your PHP pool, as described in the following section of the documentation. 

After making changes, you may want to clear your cache, reload nginx, and restart PHP-FPM. Run the following from your root AtoM installation directory (if you have followed our recommended installation instructions, this is generally /usr/share/nginx/atom):

• sudo systemctl restart php7.0-fpm
  
• sudo systemctl restart memcached
• sudo systemctl reload nginx
• php symfony cc

Let us know if that helps. 

Regards, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/91f3f30c-dcb5-43cd-9d61-dfa24f610234%40googlegroups.com.

[Freddy Pelayo Huapalla]

Before trying again I remember something. After adding the new PHP pool and inserting some content in  /etc/php/7.0/fpm/pool.d/atom.conf, the recomendations said to use the following command just to check:

sudo php-fpm7.0 --test
I only get one error in line 35, but the rest is ok. 

Does this message alter the outcome of the installation? I checked line 35 but... It's just like the rest of lines.


BTW, I followed this instruction as well :)

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/91f3f30c-dcb5-43cd-9d61-dfa24f610234%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/CAC1FhZJ3sR3H7Uc-Oahm6UgWzZFq65_%3DScKjGKLo_5X8dtsnUQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Bach. Freddy Enrique Pelayo Huapalla
Especialista en Información
freddype...@hotmail.com
freddypela...@gmail.com
Celular: 992145077

[Dan Gillean]

Hi Freddy, 

The test shouldn't alter the outcome of the installation, but if you are getting an error, it might indicate that something is not configured correctly. What is the full error message returned?

Also, did you read the earlier messages in this thread, and check your MySQL installation credentials?

Cheers, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJ3sR3H7Uc-Oahm6UgWzZFq65_%3DScKjGKLo_5X8dtsnUQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Bach. Freddy Enrique Pelayo Huapalla
Especialista en Información
freddype...@hotmail.com
freddypela...@gmail.com
Celular: 992145077

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/CAE-QY_-6sQ5Rkj-QujbDxu8t7F7Ej0iD7YbBveMAZO7UTCah0Q%40mail.gmail.com.

[Jim Adamson]

Hi Dan,

In my earlier reply to this thread from about a year ago I mentioned how installing apcu-bc from the Debian respository resolved an issue that was preventing me from running through the web installer, specifying a dedicated MySQL user instead of the root user, as is recommended in the install instructions.

I just tried to replicate this scenario using the PECL install method, but couldn't. However, this time I did note that I had to append /sfInstallPlugin to the URL to avoid a 500 Internal Server error (/var/log/nginx/error.log: PHP message: Unable to open PDO connection [wrapped: SQLSTATE[HY000] [1045] Access denied for user 'atom'@'localhost'). A lot can change in year, so it doesn't surprise me that the original problem is no more. I'm currently testing with Ubuntu 16.04.5 LTS (Vagrant guest), AtoM 2.4 tar.gz. Having to append /sfInstallPlugin to the URL doesn't seem to relate to the method by which apcu-bc gets installed; I experience this if I install apcu-bc from the .deb, too.

The apcu-bc .deb install method we're using uses a package from the Debian unstable repository, though we've been using it successfully in production for several months. Previouly I mentioned adding the repository with 'add-apt-repository ...'. With hindsight, if admins are going to install the .deb — which I must stress is only the way I've done it, not the official way — probably best to just install that package, not add the repository, i.e. use the 'wget ...' method I mentioned earlier today. This will avoid a situation where newer versions of other installed packages available from the Debian unstable repo get marked as 'upgradeable' and you end up inadvertently upgrading other packages to unstable versions of those packages when you do 'apt-get upgrade'.

Ubuntu 18 actually has a package for apcu_bc: https://packages.ubuntu.com/bionic/php-apcu-bc, though it doesn't look like Ubuntu 18 support has been added for AtoM. Actually, the Ubuntu 18 package looks like the exact same package as the one from the Debian unstable repository - v1.0.3.

Regarding Freddy's situation, it'd certainly be interesting to know if php-apcu-bc from the .deb makes the problem go away, though as you say best to check out whether there's some other misconfiguration first.

Thanks, Jim

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/91f3f30c-dcb5-43cd-9d61-dfa24f610234%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "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/CAC1FhZJ3sR3H7Uc-Oahm6UgWzZFq65_%3DScKjGKLo_5X8dtsnUQ%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

--

Bach. Freddy Enrique Pelayo Huapalla
Especialista en Información
freddype...@hotmail.com
freddypela...@gmail.com
Celular: 992145077

--
You received this message because you are subscribed to the Google Groups "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.

[Dan Gillean]

Hi Jim, 

Thanks so much for sharing your experience in this thread! 

I'm not totally clear on what you mean about the sfInstall thing - are you suggesting this is a bug? You do need to go through the sfInstall web configuration page to finalize the installation process - i.e. confirm your ES port and index name, your database name and credentials, your site name, etc. I believe this error might still be the case if you are trying to access your aliased domain name without first running the web installer - though if you try accessing localhost it *should* redirect to the web installer, if I understand correctly. See: 

• https://www.accesstomemory.org/docs/latest/admin-manual/installation/linux/ubuntu-xenial/#run-the-web-installer
  

Can you clarify a bit if I am misunderstanding? Not sure if I should have the team check for an installation bug :) Thanks! 

Regarding Ubuntu 18.04: 

I believe that our plan for the 2.5 release is to test against 18.04 and 16.04, and drop documentation support for 14.04, since by then 14.04 will be a good ways past the long-term support window, and we want to encourage our users to upgrade to the most stable releases. We can also only maintain so many installation instruction branches properly at once. We do expect to find some minor bugs using 18.04 that we'll need to address, and changes to the documentation to update package installation instructions such as the one you mention. Because of this, and because we really want to get the 2.4.1 bug fix release out the door as soon as we can, for now, we'll be maintaining 14.04 and 16.04 instructions for 2.4.x releases, and updating them in the next major release. 

Regards, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/582f25c5-51cc-4804-91f9-07e5e096b2db%40googlegroups.com.

[Jim Adamson]

Hi Dan,

The problem is that when I first visit https://localhost I see a 500 Internal Server error. If I then append /sfInstallPlugin to the URL in my browser address bar, I correctly see the web installer page and I can fill out the forms etc. I'm really not sure if this is a bug, as I've only just encountered it, and found out about appending /sfInstallPlugin to the URL from another thread: https://groups.google.com/d/msg/ica-atom-users/Lbv9ykr9458/k5onfw66BQAJ. I must admit I didn't read all of that very long thread so there may be more info in there as to why /sfInstallPlugin was needed. I'll have a think about why this might have come about. It could be the way I'm provisioning the box (which is with puppet), rather than a bug in AtoM. I'll report back if I find anything.

Regarding Ubuntu version support: sounds like a sensible policy. I'll be testing against Ubuntu 18 myself, so I can report on any significant experiences if that helps.

Thanks, Jim

[Jim Adamson]

Hi Freddy

I just noticed your other (untitled) thread in this group, which includes a screenshot of the error line. The highlighted error suggests that the content of /etc/php/7.0/fpm/conf.d/30-apcu-bc.ini is incorrect. This file should contain just one line as per the installation instructions:

extension=apc.so

I would suggest you edit the above file, replacing the existing content with the above line. Then re-run your --test command - it should complete with the message NOTICE: configuration file /etc/php/7.0/fpm/php-fpm.conf test is successful. Then restart php-fpm:

sudo systemctl restart php7.0-fpm

Hope that helps.

Jim

[Jim Adamson]

Hi Dan

Just to say the problem I was having was indeed due to the way I was provisioning the server. To fix this so that /sfInstallPlugin isn't required I simply deleted config/config.php. Sorry!

Thanks, Jim

[Dan Gillean]

No worries; thanks for clarifying Jim, and thanks for helping Freddy! 

For anyone following along at home, Freddy's screenshots ended up in another thread, here: 

• https://groups.google.com/d/msg/ica-atom-users/DSXK588m4pw/6q7YbjV7AgAJ
  

Freddy, let us know how it goes!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

--

You received this message because you are subscribed to the Google Groups "AtoM Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/35f32135-c9d2-432f-bf5f-59a33a4ec0db%40googlegroups.com.

[Freddy Pelayo Huapalla]

Hi there!

I've been out for a while but I am back! After following your indications I managed at last to install AtoM 2.4!!!

As Jim Adamson pointed out, the content in /etc/php/7.0/fpm/conf.d/30-apcu-bc.ini was incorrect. And that was because I did this in the begining:

After executing : sudo pecl install apcu_bc-beta I saw a blinking cursor, probably sugesting me to put a command there, so I put 

echo "extension=apc.so" | sudo tee /etc/php/7.0/mods-available/apcu-bc.ini. This was the beginning of my problems. Thanks a lot
Dan and Jim for you help and patience... ++ for you both.

2018-08-09 13:10 GMT-05:00 Dan Gillean <d...@artefactual.com>:

No worries; thanks for clarifying Jim, and thanks for helping Freddy! 

For anyone following along at home, Freddy's screenshots ended up in another thread, here: 

• https://groups.google.com/d/msg/ica-atom-users/DSXK588m4pw/6q7YbjV7AgAJ
  

Freddy, let us know how it goes!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Thu, Aug 9, 2018 at 12:02 PM, 'Jim Adamson' via AtoM Users <ica-atom-users@googlegroups.com> wrote:

Hi Dan

Just to say the problem I was having was indeed due to the way I was provisioning the server. To fix this so that /sfInstallPlugin isn't required I simply deleted config/config.php. Sorry!

Thanks, Jim

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@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/35f32135-c9d2-432f-bf5f-59a33a4ec0db%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/CAC1FhZKA%3DuRXNFB4nV%2BKx6Cd0NxDm_ua%3D-HbrSeUa6AqDk1Mfg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Jim Adamson]

Hi Freddy,

Good to hear it's all working now!

Jim

On Thursday, 16 August 2018 03:56:16 UTC+1, Freddy Pelayo Huapalla wrote:

Hi there!

I've been out for a while but I am back! After following your indications I managed at last to install AtoM 2.4!!!

As Jim Adamson pointed out, the content in /etc/php/7.0/fpm/conf.d/30-apcu-bc.ini was incorrect. And that was because I did this in the begining:

After executing : sudo pecl install apcu_bc-beta I saw a blinking cursor, probably sugesting me to put a command there, so I put 

echo "extension=apc.so" | sudo tee /etc/php/7.0/mods-available/apcu-bc.ini. This was the beginning of my problems. Thanks a lot
Dan and Jim for you help and patience... ++ for you both.

2018-08-09 13:10 GMT-05:00 Dan Gillean <d...@artefactual.com>:

No worries; thanks for clarifying Jim, and thanks for helping Freddy! 

For anyone following along at home, Freddy's screenshots ended up in another thread, here: 

• https://groups.google.com/d/msg/ica-atom-users/DSXK588m4pw/6q7YbjV7AgAJ
  

Freddy, let us know how it goes!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

On Thu, Aug 9, 2018 at 12:02 PM, 'Jim Adamson' via AtoM Users <ica-ato...@googlegroups.com> wrote:

Hi Dan

Just to say the problem I was having was indeed due to the way I was provisioning the server. To fix this so that /sfInstallPlugin isn't required I simply deleted config/config.php. Sorry!

Thanks, Jim

--
You received this message because you are subscribed to the Google Groups "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/35f32135-c9d2-432f-bf5f-59a33a4ec0db%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--
You received this message because you are subscribed to the Google Groups "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/CAC1FhZKA%3DuRXNFB4nV%2BKx6Cd0NxDm_ua%3D-HbrSeUa6AqDk1Mfg%40mail.gmail.com.

For more options, visit https://groups.google.com/d/optout.

[Dan Gillean]

Thanks for updating us, Freddy - glad to hear you are up and running! 

I found this issue, where our team has been addressing APCu compatibility issues. I've added a reminder there to review our documentation and make updates if needed. See: 

• https://projects.artefactual.com/issues/11387
  

Regards, 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-users+unsubscribe@googlegroups.com.
To post to this group, send email to ica-atom-users@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/62f5c497-3668-4d53-853b-3a849e4f18c0%40googlegroups.com.

[Grindlay Forrest]

Hi, appreciate this is quite an old thread but I was directed here when I set up a new AtoM 2.4 dev instance on Ubuntu 20.04 and got a 500 error on startup.

Looking at the nginx log (Version: 1.17.10-0ubuntu1), the problem was:

"PHP message: You must have APC installed and enabled to use sfAPCCache class"

This was odd, as according to apt:

php-apcu is already the newest version (5.1.18+4.0.11-1+ubuntu20.04.1+deb.sury.org+1).

I parked the problem over the weekend, intending to come back to it today. Imagine my surprise when this appeared in the update log:

php-apcu-bc:amd64

and voila, the problem was fixed.

This asks the question, what default packages ship with Ubuntu 20.04 - have they changed something and are now shipping the php-apcu-bc ("backwards compatibility) module separately?

I'm only posting this in case someone has a similar issue.

[Jim Adamson]

Hi Grindlay,

It looks like php-apcu-bc is available from the Ubuntu repositories for Ubuntu 18 (Bionic) and Ubuntu 20 (Focal) (as well as the short-life 19 release (Eoan) ). It does seem strange that your apparent noop action of attempting to install php-apcu triggered the installation of php-apcu-bc. Can you check when php-apcu-bc was installed, in /var/log/dpkg.log (or the rotated dpkg logs) ?

It looks like php-apcu "recommends" php-apcu-bc which means the latter gets installed when you apt-get install the former (unless you use --no-install-recommends as an apt-get option). I suppose it's possible either php-apcu-bc only recently got added to the Ubuntu 20 repository, and/or only recently got added as a "recommendation" — and your apparent noop action did actually install it.

Jim

[Dan Gillean]

Hi there, 

A couple additional thoughts: 

There were a number of changes introduced between Ubuntu 16.04 and 18.04, most notably with the service daemon, and of course many of the default package versions. With 2.4, you'll notice that we didn't include 18.04 (or higher) installation docs, because we expected there to be some breaking changes. Version 2.5 includes instructions for 18.04 and 16.04, and drops support for 14.04. So far, no AtoM release has been tested with Ubuntu 20.04, so you may  encounter some unexpected outcomes! 

Regarding the apcu vs apcu-bc changes - in later versions of AtoM (e.g. 2.5 and later), apcu-bc is no longer required. My knowledge in this area is limited, but see this post for a bit more information and context: 

• https://groups.google.com/d/msg/ica-atom-users/RPIdhC46WVw/9sJpemfDBAAJ
  

If you're going to keep using Ubuntu 20.04, I suspect you'll have a much better time of it if you upgrade your AtoM installation to 2.5.4. 

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

--

You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/fad4ecfa-dc0c-40b0-8f5e-bf3bf08fa5f2%40googlegroups.com.

[Grindlay Forrest]

Thanks Dan, I very much appreciate the insights. This is a dev instance which is a snapshot of the client's live site which is AtoM 2.4. The intent is to fix a few things on this 2.4 instance, then upgrade it to 2.5.

I am in two minds about whether to attempt the 2.5 upgrade first, then fix the issues. Their current live environment is Ubuntu 16.04 so that's a 3rd confounding factor.

[Grindlay Forrest]

Hi Jim. I did a search for "php-apcu" in dpkg.log and it returned the following entries:

2020-05-21 13:43:05 configure php-apcu:amd64 5.1.18+4.0.11-1+ubuntu20.04.1+deb.sury.org+1 <none>
2020-05-21 13:43:05 status unpacked php-apcu:amd64 5.1.18+4.0.11-1+ubuntu20.04.1+deb.sury.org+1
2020-05-21 13:43:05 status half-configured php-apcu:amd64 5.1.18+4.0.11-1+ubuntu20.04.1+deb.sury.org+1
2020-05-21 13:43:06 status installed php-apcu:amd64 5.1.18+4.0.11-1+ubuntu20.04.1+deb.sury.org+1

2020-05-25 14:49:25 upgrade php-apcu-bc:amd64 1.0.5-2build1 1.0.5-2+ubuntu20.04.1+deb.sury.org+1
2020-05-25 14:49:25 status half-configured php-apcu-bc:amd64 1.0.5-2build1
2020-05-25 14:49:25 status unpacked php-apcu-bc:amd64 1.0.5-2build1
2020-05-25 14:49:25 status half-installed php-apcu-bc:amd64 1.0.5-2build1
2020-05-25 14:49:25 status unpacked php-apcu-bc:amd64 1.0.5-2+ubuntu20.04.1+deb.sury.org+1

2020-05-25 14:49:28 configure php-apcu-bc:amd64 1.0.5-2+ubuntu20.04.1+deb.sury.org+1 <none>2020-05-25 14:49:28 status unpacked php-apcu-bc:amd64 1.0.5-2+ubuntu20.04.1+deb.sury.org+1
2020-05-25 14:49:28 status half-configured php-apcu-bc:amd64 1.0.5-2+ubuntu20.04.1+deb.sury.org+1
2020-05-25 14:49:28 status installed php-apcu-bc:amd64 1.0.5-2+ubuntu20.04.1+deb.sury.org+1

21st was when I built the VM, 25th when the noop update ran.

I suppose it would be possible to remove both php-apcu and php-apcu-bc and try to reproduce the behaviour but I'm reluctant to break my now-functioning instance.

[Jim Adamson]

Hi Grindlay,

I checked Google's cache to see if it would reveal whether something in the Ubuntu repositories had very recently changed in relation to these two packages. No, nothing's changed in terms of the availability of php-apcu-bc and it being a recommended package for php-apcu. So we can rule that out.

I'm assuming you loosely followed the official 16.04 instructions to do the install. I wonder what the exact command line was that you used to install php-apcu on the 21st? And the subsequent command line that triggered the installation of php-apcu-bc on the 25th? These should be listed in /var/log/apt/history.log, prefixed Commandline:. Or in your terminal history.

There's nothing in those install instructions that I can see that would explain why you were (albeit temporarily) missing php-apcu-bc; it should of got installed by the following line from the instructions:

sudo apt install php7.0-cli php7.0-curl php7.0-json php7.0-ldap php7.0-mysql php7.0-opcache php7.0-readline php7.0-xml php7.0-fpm php7.0-mbstring php7.0-mcrypt php7.0-xsl php7.0-zip php-apcu

Another possibility (though a long shot) is that your Ubuntu 20 system has apt config set not to install recommended packages by default. You can confirm that this isn't the case with:

apt-config dump | grep "Recommends"

I get the following output which indicates it will install recommended packages by default.

APT::Install-Recommends "1";

BTW, this is all useful for me as I need to update our Puppet module for AtoM to work with Ubuntu 18 & 20.

Jim

[Grant Forrest]

Sorry for the delay in replying, been busy working on a number of unrelated AtoM challenges.

My standard apt command for install PHP 7.0 on an AtoM 2.4 instance on Ubuntu is:

sudo apt install php7.0-cli php7.0-curl php7.0-json php7.0-ldap php7.0-mysql php7.0-opcache php7.0-readline php7.0-xml php7.0-fpm php7.0-mbstring php7.0-mcrypt php7.0-xsl php7.0-zip php-apcu

Here we have the entry in the apt history.log:

Start-Date: 2020-05-21  13:42:48

Commandline: apt install php7.0-cli php7.0-curl php7.0-json php7.0-ldap php7.0-mysql php7.0-opcache php7.0-readline php7.0-xml php7.0-fpm php7.0-mbstring php7.0-mcrypt php7.0-xsl php7.0-zip php-apcu php7.0-bz2

Requested-By: grant (1000)

Install: php7.0-bz2:amd64 (7.0.33-29+ubuntu20.04.1+deb.sury.org+1), libzip4:amd64 (1.6.1-3+ubuntu20.04.1+deb.sury.org+2, automatic)

Upgrade: php7.0-cli:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-fpm:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-opcache:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-common:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-json:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-mbstring:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-readline:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-xml:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-xsl:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-curl:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-zip:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-ldap:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php7.0-mcrypt:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1), php-apcu:amd64 (5.1.18+4.0.11-1+ubuntu19.10.1+deb.sury.org+1, 5.1.18+4.0.11-1+ubuntu20.04.1+deb.sury.org+1), php7.0-mysql:amd64 (7.0.33-27+ubuntu19.10.1+deb.sury.org+1, 7.0.33-29+ubuntu20.04.1+deb.sury.org+1)

End-Date: 2020-05-21  13:43:14

Next, we have the entry from 4 days later:

Start-Date: 2020-05-25  14:49:19

Commandline: aptdaemon role='role-commit-packages' sender=':1.118'

Upgrade: evolution-data-server-common:amd64 (3.36.1-2, 3.36.2-0ubuntu1), php7.4-cli:amd64 (7.4.3-4ubuntu1.1, 7.4.6-1+ubuntu20.04.1+deb.sury.org+1), php-apcu-bc:amd64 (1.0.5-2build1, 1.0.5-2+ubuntu20.04.1+deb.sury.org+1), libedataserverui-1.2-2:amd64 (3.36.1-2, 3.36.2-0ubuntu1), gir1.2-mutter-6:amd64 (3.36.1-3ubuntu3, 3.36.2-1ubuntu1~20.04.1), openssl:amd64 (1.1.1g-1+ubuntu19.10.1+deb.sury.org+1, 1.1.1g-1+ubuntu20.04.1+deb.sury.org+1), php-common:amd64 (2:75+ubuntu19.10.1+deb.sury.org+1, 2:76+ubuntu20.04.1+deb.sury.org+9), php7.4-json:amd64 (7.4.3-4ubuntu1.1, 7.4.6-1+ubuntu20.04.1+deb.sury.org+1), libgd3:amd64 (2.3.0-1+ubuntu19.10.1+deb.sury.org+2, 2.3.0-2+ubuntu20.04.1+deb.sury.org+1), libedata-cal-2.0-1:amd64 (3.36.1-2, 3.36.2-0ubuntu1), php7.4-phpdbg:amd64 (7.4.3-4ubuntu1.1, 7.4.6-1+ubuntu20.04.1+deb.sury.org+1), evolution-data-server:amd64 (3.36.1-2, 3.36.2-0ubuntu1), libmutter-6-0:amd64 (3.36.1-3ubuntu3, 3.36.2-1ubuntu1~20.04.1), mutter-common:amd64 (3.36.1-3ubuntu3, 3.36.2-1ubuntu1~20.04.1), php7.4-opcache:amd64 (7.4.3-4ubuntu1.1, 7.4.6-1+ubuntu20.04.1+deb.sury.org+1), libebackend-1.2-10:amd64 (3.36.1-2, 3.36.2-0ubuntu1), libebook-1.2-20:amd64 (3.36.1-2, 3.36.2-0ubuntu1), php7.4-readline:amd64 (7.4.3-4ubuntu1.1, 7.4.6-1+ubuntu20.04.1+deb.sury.org+1), libxml2:amd64 (2.9.10+dfsg-5, 2.9.10+dfsg-5+ubuntu20.04.1+deb.sury.org+3), libebook-contacts-1.2-3:amd64 (3.36.1-2, 3.36.2-0ubuntu1), libedata-book-1.2-26:amd64 (3.36.1-2, 3.36.2-0ubuntu1), libecal-2.0-1:amd64 (3.36.1-2, 3.36.2-0ubuntu1), php7.4-common:amd64 (7.4.3-4ubuntu1.1, 7.4.6-1+ubuntu20.04.1+deb.sury.org+1), libssl1.1:amd64 (1.1.1g-1+ubuntu19.10.1+deb.sury.org+1, 1.1.1g-1+ubuntu20.04.1+deb.sury.org+1), libcamel-1.2-62:amd64 (3.36.1-2, 3.36.2-0ubuntu1), libedataserver-1.2-24:amd64 (3.36.1-2, 3.36.2-0ubuntu1), libidn2-0:amd64 (2.3.0-1+ubuntu19.10.1+deb.sury.org+2, 2.3.0-1+ubuntu20.04.1+deb.sury.org+2), mutter:amd64 (3.36.1-3ubuntu3, 3.36.2-1ubuntu1~20.04.1)

End-Date: 2020-05-25  14:49:59 

From what I can tell, the second entry was the unattended update (aptdaemon)

I hope this is helpful.

[Jim Adamson]

Hi Grindlay,

Apologies for not responding until now. I think I might be able to explain the apparent delay to the installation of php-apcu-bc on your Ubuntu 20 box. I tried out your apt command line, verbatim, in an Ubuntu 18 Vagrant box. I saw numerous 'Unable to locate package' errors. This happened because the package names specified are invalid for both Ubuntu 18 & 20. Specifically, the 7.0 bit of the package names needs removing for them to be located and installed under Ubuntu 18 & 20. Also, the php mcrypt package does not exist in the Ubuntu 18 & 20 repos. So my guess is that you ran the apt command under Ubuntu 16, the box was subsequently upgraded to Ubuntu 18 then 20, at which point unattended upgrades noticed the absence of php-apcu-bc (due to it not being available in the Ubuntu 16 repos) and installed it. Does my explanation sound likely? This page might be helpful in determining the dates of any O/S upgrades, should you want to check.

Jim

[Grant Forrest]

Hi Jim, I'm wishing I'd paid more attention  to the sequence of events now!
Yes it's quite possible that this was originally an Ubuntu 16 box, as that's what my client has currently in their live setup.

I'm not a fan of in-place OS upgrades in a live environment but there are many reasons why I'd try 18 then 20 in dev, so your explanation sounds plausible.

I guess there is the added complication that some packages are only available in certain repos and I may have added a few e.g. Remi, Ondrej to get access to all the PHP versions.

G

[Cláudio Miguel Costa]

Hello everyone! 

I recently went through the same error on an Ubuntu 20.04 Server machine, and solved it by adding the version-specific package 'php7.2-apcu' in the command that installs the PHP extensions needed for AToM 2.6, as per the install instructions at 
https://www.accesstomemory.org/pt/docs/2.6/admin-manual/installation/linux/ubuntu-bionic/
The command I'm referring to is this one:
sudo apt install php7.2-cli php7.2-curl php7.2-json php7.2-ldap php7.2-mysql php7.2-opcache php7.2-readline php7.2-xml php7.2-fpm php7.2-mbstring php7.2-xsl php7.2-zip php-apcu

So in the end of that command, I just added "php7.2-apcu" and voilá, it finally worked! Not sure if this is the right way to fix this, but it's the only way I've been able to successfully install AToM on an 20.04 machine.
Cheers