[Archivesspace_Users_Group] Local plugin disabled and aspace_diagnostic not present

[Tenenholtz, David]

Hi James,

Thanks so much for your insights on this issue and for those suggestions on where to look for possible errors.

In the end, it was beneficial for me to simply eliminate some errant whitespace in the config.rb file below the AppConfig[:plugins] statement. A larger takeaway is that presence of whitespace in the config.rb file is very unforgiving. In any case, I’m happy to say this issue is now resolved.

Kind regards,
David

--
David Tenenholtz (he/him)
Digital Archivist, RAND Corporation
1776 Main Street
P.O. Box 2138
Santa Monica, CA 90407-2138
(310) 393-0411 x6188
dtenenho at rand.org<mailto:dtenenho at rand.org>


From: James Bullen <james at hudmol.com>
Reply-To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Date: Sunday, February 21, 2021 at 3:02 PM
To: Archivesspace Users Group <archivesspace_users_group at lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Local plugin disabled and aspace_diagnostic not present


Hi David,

Not sure what’s going on, but a few points to note:

-  The absence of an aspace_diagnostic file is a good sign because it only gets written if something goes wrong during start up.
-  There is no need to run 'initialize-plugin.sh local' unless you are using gems in your local plugin. That message is just noting that there is no plugins/local/Gemfile, so there is nothing to do.
-  Check that you have ‘local’ in AppConfig[:plugins].
-  You mention ‘plugin/local/…’, I guess this is a typo, but make sure the directory is ‘plugins/local/…'
-  From memory, that gear icon only appears if you have a plugin that has a config.yml that specifies a menu item.


Cheers,
James




On Feb 20, 2021, at 4:11 AM, Tenenholtz, David <dtenenho at rand.org<mailto:dtenenho at rand.org>> wrote:

Hello!

I’m standing up the v.2.8.1 release in production, and am running into a persistent issue that keeps the local plugin from being enabled. I have not been able to identify if this is related to the prior bug in older releases having to do with the gem bundler, but I suspect that a gem (or the bundler?) is being blocked here. Although I have the same content in plugin/local/frontend and plugin/local/public running happily on a test server on matching infrastructure, I’m not having any luck getting the local plugin to initialize on prod. Under /data/tmp there is also no aspace_diagnostic text file to interrogate. In the staff GUI I’m not seeing the Plug-ins list item within the dropdown under the gear icon.

Tech specs (matching on test server and production server):
RHEL7.9 VM
openjdk 1.8.0_282
mysql Ver 15.1 distrib 5.5.68-MariaDB
Apache/2.4.6

During the building of the production application, I noticed the issue, and so I ran ‘initialize-plugin.sh local’ from within the scripts folder, but got an error related to a Gemfile not being present within the ‘local’ folder.

If anyone has any pointers on how to get the aspace_diagnostic to generate under /data/tmp, or any other avenues for me to pursue here with initializing the local plugin properly, I’d be so grateful!

Kind regards,
David

--
David Tenenholtz (he/him)
Digital Archivist, RAND Corporation
1776 Main Street
P.O. Box 2138
Santa Monica, CA 90407-2138
(310) 393-0411 x6188
dtenenho at rand.org<mailto:dtenenho at rand.org>





__________________________________________________________________________
This email message is for the sole use of the intended recipient(s) and
may contain information that is sensitive, proprietary, and/or privileged.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please contact the sender by reply
email and destroy all copies of the original message.
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group at lyralists.lyrasis.org<mailto:Archivesspace_Users_Group at lyralists.lyrasis.org>
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

__________________________________________________________________________

This email message is for the sole use of the intended recipient(s) and
may contain information that is sensitive, proprietary, and/or privileged.
Any unauthorized review, use, disclosure or distribution is prohibited. If
you are not the intended recipient, please contact the sender by reply
email and destroy all copies of the original message.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20210304/b1501a82/attachment.html>