Cannot start jobs:worker: Fails with "settings.yml does not have a registered handler" Error

[Manny Rodriguez]

Hello,

After getting 500 errors doing routine tasks in AtoM, I noticed that the jobs:worker was down, so I went to restart it.

Restarting via systemctl failed, so I tried to restart it manually. When running `php symfony jobs:worker`, it fails with the following error message:

`Configuration file "/var/www/highlandparkhistory/htdocs/vendor/symfony/lib/config/config/settings.yml, /var/www/highlandparkhistory/htdocs/apps/qubit/config/settings.yml" does not have a registered handler. `

I found one other thread that references this error, but it's 5 years old, a number of the posts are deleted and it's in reference to an upgrade from 1.X, so I'm not sure how much it applies in this case. Here's the thread: https://groups.google.com/g/ica-atom-users/c/joEj3AZj-ko/m/-EcgiOyTDgAJ

Has anyone seen this error recently? 

[Dan Gillean]

Hi Manny, 

Thanks for searching in the forum before posting! However, in this case I can see that the thread you found was rather convoluted and had a lot of different things going on, in addition to being fairly old, so I think you're right that it's not necessarily helpful at this stage. 

First, I can tell from the file path that you've shared that you've made some changes from our recommended installation instructions, and are using Apache instead of Nginx. Can you tell us more about the installation? Specifically: 

• What is the full version number of your AtoM installation, found in Admin > Settings?
• What operating system and version are you using?
• What about other dependencies, such as MySQL, PHP, Elasticsearch?
• Am I correct in assuming that you have previously followed all the installation and configuration steps for the job scheduler?
• See: https://www.accesstomemory.org/docs/latest/admin-manual/installation/asynchronous-jobs/
  

A couple things I'd suggest investigating off the bat: 

First, let's make sure the permissions are properly configured. In an installation that follows our recommended instructions, AtoM expects the www-data user to own all files and directories under the root installation directory. You can try reapplying the filesystem permissions with the following command - note that you'll need to adjust the file path to point to the root AtoM installation directory in your case: 

• sudo chown -R www-data:www-data /usr/share/nginx/atom
  
• See: https://www.accesstomemory.org/docs/latest/admin-manual/installation/linux/ubuntu-bionic/#filesystem-permissions

It's also possible that the cache needs clearing. Let's try clearing Symfony's cache as well as restarting PHP-FPM. Assuming you're using PHP 7.2, try: 

• php symfony cc
• sudo systemctl restart php7.2-fpm

Finally, you could try taking a look at the file in question, and making sure that key information is not missing. Here's the default version in our code repository: 

• https://github.com/artefactual/atom/blob/qa/2.x/vendor/symfony/lib/config/config/settings.yml
  

It's likely okay if a few values in your file have become different during configuration - mainly I just want to make sure that the file is present and not corrupted or incomplete. 

If none of this helps, then hopefully with further information about your installation environment we can provide further suggestions. 

Cheers, 

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/9057b2a7-8909-47c2-8bf1-8b1a90a62b13n%40googlegroups.com.

[Manny Rodriguez]

Hi Dan,

Thanks for the help! I really appreciate it.

Here's some info about the instance:

AtoM Version: 2.6.1 - 184
OS: Ubuntu 16.04.6 LTS
PHP: PHP 7.2.34-9+ubuntu16.04.1+deb.sury.org+1 (cli) (built: Jan 12 2021 11:14:41) ( NTS )
MySQL: 8.0.21
ElasticSearch: 5.6.16

The jobs:worker (and the instance as a whole) was running correctly before, and then wasn't. I realized it wasn't starting after tracking down some 500 errors trying to edit records.

I've recently made a change to the database so it would process dates correctly -- that's the last substantive change made that I can remember.

I did try restoring the settings.yml file -- there was one present and indeed some of the values were different. I've also reset permissions and restarted PHP, none of which seem to have made a difference.

One thing I realized when clearing the cache is that I'm getting the same error running `php symfony cc`: 

`Configuration file "/var/www/highlandparkhistory/htdocs/vendor/symfony/lib/config/config/settings.yml, /var/www/highlandparkhistory/htdocs/apps/qubit/config/settings.yml" does not have a registered handler.`

What else can we try?

Cheers,
Manny Rodriguez

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/Iw0glcWaIDM/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/CAC1FhZ%2B91ngWXy4ZBPUwRexz34%2BteQb--tQUPKK-7d%2BtODhv2Q%40mail.gmail.com.

[Dan Gillean]

Hi Manny, 

So, one thing I've realized is that, when you're using Apache, I'm not sure what the default user is for filesystem permissions. I do think this might still be related to that - the worker needs to be managed with the same user as the web server, so if you're running into issues using systemd, it might suggest that a different user is trying to execute the command. I don't know enough about Apache to tell you what user that might be.

If you've tried reapplying the permissions for your root AtoM installation directory (which in your case appears to be /var/www/highlandparkhistory/htdocs) and assigning them to the www-data user, then it's worth checking to see if the jobs:worker command will run as expected if you explicitly specify the user, like so: 

• sudo -u www-data php symfony jobs:worker

You could try the same with the cache clear command. 

If it still doesn't work, I'm not quite sure what to suggest, as I haven't personally seen an error like this before, and we don't develop or test AtoM with Apache. I know it's an extreme option, but if you've tried everything else you might consider reinstalling with Nginx, so you can follow the installation instructions exactly, and hopefully avoid this issue. 

Let us know how it goes!

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

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/CACdngXYpME3x702_frR1yJjfgzkrARsvkkMBA5nc_1oR-rE%2Bjw%40mail.gmail.com.

[Manny Rodriguez]

Hi Dan,

Got an update:

I wasn't able to resolve the original problem, but I got around it by creating a new instance and then reimporting all of the data. After doing this, jobs:worker started up without that error and the site seems to run normally.

Seems like the old instance got corrupted somehow?

Cheers,

Manny

[Dan Gillean]

Thanks for updating the thread and letting us know! Too bad it's unclear what exactly happened that led to this outcome, but I'm glad to hear you're up and running again, Manny :)

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

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/6077405d-56ab-4c10-a9b1-9e29ef37e7e4n%40googlegroups.com.

[r.ruti...@docuteam.ch]

Hi there

I had the same issue. My Harddisk was 100% full, so and after expanding the disk, the php symfony cc command gave me the same error as described in this ticket.

What immediately helped was the following command (in atom home directory):

rm -fr cache/*

After that, the symfony cc command worked as usual.

See https://kumar.swatantra.info/symfony-does-not-have-a-registered-handler-out-of-free-disk-space/ 

Cheers, Roger

[Dan Gillean]

Interesting - thanks so much for letting us know what helped to resolve the issue for you, Roger! 

Cheers, 

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

@accesstomemory

he / him

To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/2c320e76-8e88-420d-8419-320312782a0cn%40googlegroups.com.