Skip to first unread message
KUNA SRIRAM
Jun 6, 2023, 1:29:36 PM6/6/23
to AtoM Users
Please help
Failed to make cache directory "/usr/share/nginx/atom/cache/qubit/cli/config" while generating cache for configuration file "config/config_handlers.yml".
Dan Gillean
Jun 6, 2023, 3:27:22 PM6/6/23
to ica-ato...@googlegroups.com
Hi Kuna,
It would be helpful to know more about your AtoM installation for us to be able to help you. For example:
- What version of AtoM are you trying to install?
- Are you following the recommended installation guide for that version (for example, here are the 2.7 installation instructions)?
- If yes, are you installing using our downloadable tarball (Option 1 in the documentation) or from the code repository (Option 2)?
- If no, then what have you changed?
- At what step of the installation process did you encounter this error? What was the command that led to this message?
In any case: at first glance, this looks to me like it could be a filesystem permissions issue. AtoM expects all files and directories below the root installation directory to be owned by the www-data user. You can explicitly set these permissions with:
- sudo chown -R www-data:www-data /usr/share/nginx/atom
- See: https://www.accesstomemory.org/docs/latest/admin-manual/installation/ubuntu/#filesystem-permissions
You can also make sure that you run any other terminal commands explicitly as the www-data user by prefacing CLI commands with sudo -u www-data. For example, running AtoM's clear cache command with this:
- sudo -u www-data php symfony cc
If you use the command above to properly set the filesystem permissions, and then re-run whatever command triggered the error using the www-data prefix, hopefully this will solve the issue. If not, please make sure to let us know more about your installation and the issue you've encountered, and hopefully we can offer further suggestions!
Cheers,
he / him
On Tue, Jun 6, 2023 at 1:29 PM KUNA SRIRAM <sriram....@gmail.com> wrote:
Please helpFailed to make cache directory "/usr/share/nginx/atom/cache/qubit/cli/config" while generating cache for configuration file "config/config_handlers.yml".
--
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/ea93ecb0-704a-4765-b590-bd71f2e289cbn%40googlegroups.com.
KUNA SRIRAM
Jun 6, 2023, 4:10:54 PM6/6/23
to ica-ato...@googlegroups.com
Thank you for your response
Atom 2.7, I'm trying to install...I struck at this point again ( internal server 500 error). Could you please help how to solve it.
You received this message because you are subscribed to a topic in the Google Groups "AtoM Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/ica-atom-users/L6pOYJ8NcKc/unsubscribe.
To unsubscribe from this group and all its topics, 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/CAC1FhZKv0usTBEJGQQRhYygBi5xySUfSH7GQgkUFwZSO_Xb_ag%40mail.gmail.com.
Dan Gillean
Jun 7, 2023, 8:57:14 AM6/7/23
to ica-ato...@googlegroups.com
Hi Kuna,
Did you try my suggestions about 1) resetting the filesystem permissions, and 2) using the sudo -u www-data prefix on any command-line tasks you run during installation?
Can you point to the exact step in the Installation documentation where you encounter this error? Exactly what step were you trying to do when it occurs? See:
Are you following these instructions exactly (i.e. using Ubuntu 20.04, PHP 7.4 MySQL 8.0, Elasticsearch 5.6, etc), or have you made any changes?
Is there any more information about the nature of this error available in the web server logs? If yes, please share the full output. See:
Cheers,
he / him
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAMSsUrSLQGBO1gUTsiO_3D0ZFdsR3JY-ZHYUKk4b1X8b6w5S-g%40mail.gmail.com.
KUNA SRIRAM
Jun 7, 2023, 10:53:03 AM6/7/23
to ica-ato...@googlegroups.com
sudo mkdir /usr/share/nginx/atom
php symfony tools:install
Above two commands I faced an error, but I moved, Followed the 2.7 documentation strictly. Actually I executed those 2 options for downloading atom. Since I have little idea on it...
Now I'm facing this atom-worker saying failed to start.
I'm don't know how to solve I'm just checking, could you plz let me know the process, even to understand basics before solving this issue.
Thanks
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZJcdSRcDCa9L4pVamZVd4P2e61OzHX2Qd%2BX-Y-3LZhDGg%40mail.gmail.com.
Dan Gillean
Jun 7, 2023, 11:44:00 AM6/7/23
to ica-ato...@googlegroups.com
Hi Kuna,
Sure I will try to provide an overview.
AtoM Installation overview
AtoM does not have an exe-type installer that performs all actions for you, like some end-user Windows applications. Instead, our documentation provides instructions on the methods that we use - it assumes that the person doing the installation has some familiarity with Linux, the unix command-line, and software installation and maintenance. It also assumes that you are installing AtoM on a production ready server, and not a personal computer like a desktop or laptop.
Finally, the installation instructions also assume that you have the required system resources to install AtoM on your server. Generally, for a production ready installation, we recommend:
- Processor: 2 vCPUs @ 2.3GHz
- Memory: 7GB
- Disk space (processing): 50GB at a minimum for AtoM’s core stack plus more storage would be required for supporting any substantial number of digital objects.
While it is possible to install AtoM with less system resources, you may also encounter issues - it depends on a lot of factors. As noted in the Technical Requirements, those specs are "intended to provide a starting point for setting up your system. It provides specifications for an “all-in-one” deployment, with all of the services (i.e. nginx, Percona server, ES, memcached) installed in a single virtual machine." See:
Per the installation instructions, we essentially:
- Install the dependencies (MySQL 8, Elasticsearch 5.6, PHP 7.4 and a number of PHP extensions, the Gearman job server, and other packages)
- Download AtoM (either from our website as a tarball, or using git to pull the code from our GitHub code repository)
- Create the database and a specific MySQL user for AtoM
- Run the installer (the step you are currently at)
- Make any configuration changes needed (such as setting the default timezone or default installation culture to be used in the application)
- Finally, configure our filesystem permissions, Gearman workers, PHP-FPM pool, and webserver
In previous AtoM versions there were two differences. First, the installer was a web form, rather than a series of command-line prompts. This regularly led to timeout issues however, and was replaced in 2.7. Second, we previously had users perform step 6 before running the installer - but this regularly led to users missing key steps, leading to problems later. Now users cannot access AtoM in their web browser until all previous steps have been successfully completed.
I hope that helps outline the steps involved at a high level! See the installation documentation for more specific details:
Managing the job scheduler
It sounds like you've gotten past the installer, but are having issues with the Gearman job scheduler and the atom-workers. We have an additional page with more information on managing these, here:
First, let's make sure that:
- You installed Gearman, per this section of the installation docs
- You created the atom-worker.service configuration file, per this section of the installation docs
- You've run sudo systemctl daemon-reload, so that Ubuntu reloads the daemon and becomes aware of this new service configuration file
- You've also run sudo systemctl enable atom-worker, so this worker will be enabled on system boot
If you've done all that, then we have a few other commands we can try to check the atom-worker status, and restart it if it's not running as expected.
First, you can check the status of the atom-worker with:
- sudo systemctl status atom-worker
If it's not running, and running sudo systemctl restart atom-worker does not fix the problem when you check the status again after, then one possibility is that the start rate limit we have added in the service configuration file has been triggered.
That configuration file includes some automation so if the atom-worker fails, the job scheduler can try restarting to see if it resolves the issue. However, to prevent the job scheduler from being caught in an endless loop when a restart does NOT resolve the issue, we have added a restart limit, after which the internal fail counter must be manually reset before restarting will work. By default, the configuration file sets this to 3 restart attempts in 24 hours.
You can try resetting this fail counter with:
- sudo systemctl reset-failed atom-worker
And then try restarting again, and checking the status to see if it worked:
- sudo systemctl restart atom-worker
- sudo systemctl status atom-worker
Hopefully that helps! Good luck!
he / him
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAMSsUrQnZD_P-ZNsunH4a35n-j8D%2BPEena99OT18w2wbV%3D1HtA%40mail.gmail.com.
Dan Gillean
Jun 7, 2023, 11:57:53 AM6/7/23
to ica-ato...@googlegroups.com
Hi again Kuna,
After writing all that, I've just seen the error screenshots that you PM'ed me. I'm not sure exactly what the cause is, but one important note:
It appears from these screenshots that you are attempting to install AtoM inside a Virtualbox Ubuntu image on a personal computer running Windows. This may be part of the issue! As noted in my previous post, AtoM is intended to be installed on a production ready server, not a personal device.
If you are just looking for a local test instance you can install on a personal Windows computer, then I strongly suggest that you check out our Vagrant box instead, as it should simplify the process for you. See:
Keep in mind that the slides are 6 years old, so some of the maintenance commands (such as restarting PHP-FPM) are out of date - for these, use those found in the latest version of the documentation.
You may also need to update the Vagrant environment once installed. I've previously provided some instructions on this in the user forum here:
Hopefully this will be a smoother process for you!
Cheers,
he / him
KUNA SRIRAM
Jun 7, 2023, 12:02:54 PM6/7/23
to ica-ato...@googlegroups.com
Thanks brother for your prompt response
I'm currently as a trainee in library. Even though I'm from non technical background. But I'm interested in technical aspects to improve & learn to meet my needs. Hence I try to learn & to experience the ground level problems I started installing & testing & learning from the library related software. I could install 2.6 atom, o
Of course I'm grateful to the support from friends. I decided to install Atom 2.7. So I'm trying.
So grateful for your efforts. In assisting..
I'll try.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CAC1FhZL_68xtWfJbrqpnB6sUc9od4a3X%2BZ84u4oYgs4LW9vdUA%40mail.gmail.com.
Reply all
Reply to author
Forward
0 new messages