Re: [Archivesspace_Users_Group] Vagrant: "unable to connect to backend" error
We just had a similar issue where we had to upgrade MySQL Connector/J to be able to successfully connect to a database that has been upgraded from MariaDB 10.2 to 10.4. The symptom was AS being unable to connect to the database and it logging a 'communications link failure' error. We'd previously been using version 8.0.23 of the connector and were only able to connect after an upgrade to 8.0.29. Hope that helps, p Mark Cyzyk wrote on 2022-06-11 17:08:30: > All, > > I am trying to duplicate our Archivesspace production app in a local Vagrant > box. > > I am getting an "unable to connect to backend" error when it boots. > > I've checked to make sure the database is indeed present. > > I've checked permissions for the "archivesspace" user to the "archivesspace" > DB: > >MariaDB [archivesspace]> SHOW GRANTS for archivesspace@localhost; > > +--+ >| Grants for archivesspace@localhost | > > +--+ >| GRANT USAGE ON *.* TO `archivesspace`@`localhost` IDENTIFIED >BY PASSWORD '*2C2611CEB83E695935FB2CA67F9EE3D56514F1CC' | >| GRANT ALL PRIVILEGES ON `archivesspace`.* TO >`archivesspace`@`localhost` WITH GRANT >OPTION | > > +--+ >2 rows in set (0.000 sec) > >MariaDB [archivesspace]> > > > Then I do same for 127.0.0.1: > >MariaDB [archivesspace]> SHOW GRANTS for archivesspace@127.0.0.1; > > +--+ >| Grants for archivesspace@127.0.0.1 | > > +--+ >| GRANT USAGE ON *.* TO `archivesspace`@`127.0.0.1` IDENTIFIED >BY PASSWORD '*2C2611CEB83E695935FB2CA67F9EE3D56514F1CC' | >| GRANT ALL PRIVILEGES ON `archivesspace`.* TO >`archivesspace`@`127.0.0.1` WITH GRANT >OPTION | > > +--+ >2 rows in set (0.000 sec) > >MariaDB [archivesspace]> > > > I AM able to restore into the "archivesspace" database with: > >sudo mysql -u archivesspace -pREDACTED archivesspace < >/vagrant/archivesspace_CURRENT.sql > > > The connect string in my config.rb file: > >AppConfig[:db_url] = > > "jdbc:mysql://localhost:3306/archivesspace?user=archivesspace&password=REDACTED&useUnicode=true&characterEncoding=UTF-8" > > > And yet I get the "unable to connect to backend" error. No fair! > > Advice in previous posts down through the years suggested this was a > permissions problem, or running MySQL on something other than > localhost/127.0.0.1, but I think what I've done above rules this out. > > Are there other reasons why I might be getting the "unable to connect to > backend" error? > > Advice appreciated! > > Mark > > PS: I don't think this is relevant to the connection issue, but here are the > permissions I've set on the file system: > >vagrant@vagrant:/usr/share/archivesspace$ ls -la >total 84 >drwxr-xr-x 16 archivesspace archivesspace 4096 Jun 11 18:59 . >drwxr-xr-x 122 root root 4096 Jun 11 18:59 .. >-rwxr-xr-x 1 archivesspace archivesspace 813 Jun 11 18:54 >archivesspace.bat >-rwxr-xr-x 1 archivesspace archivesspace 5364 Jun 11 18:53 >archivesspace.sh >drwxr-xr-x 4 archivesspace archivesspace 4096 Jun 11 18:53 >clustering >drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 21:05 config >-rwxr-xr-x 1 archivesspace archivesspace 665 Jun 11 18:53 COPYING >drwxr-xr-x 9 archivesspace archivesspace 4096 Jun 11 18:59 data >drwxr-xr-x 14 archivesspace archivesspace 4096 Jun 11 18:54 docs >drwxr-xr-x 9 archivesspace archivesspace 4096 Jun 11 18:54 gems >drwxr-xr-x 8 archivesspace archivesspace 4096 Jun 11 18:54 >launcher >drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 18:59 lib >drwxr-xr-x 4 archivesspace archivesspace 4096 Jun 11 18:53 locales >drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 18:59 logs >drwxr-xr-x 22 archivesspace archivesspace 4096 Jun 11 18:54 plugins >-rwxr-xr-x 1 archivesspace archivesspace 2326 Jun 11 18:53 >README.md >drwxr-xr-x 12 archivesspace archivesspace 4096 Jun 11 18:53 reports >drwxr-xr-x 3 arch
[Archivesspace_Users_Group] Vagrant: "unable to connect to backend" error
All, I am trying to duplicate our Archivesspace production app in a local Vagrant box. I am getting an "unable to connect to backend" error when it boots. I've checked to make sure the database is indeed present. I've checked permissions for the "archivesspace" user to the "archivesspace" DB: MariaDB [archivesspace]> SHOW GRANTS for archivesspace@localhost; +--+ | Grants for archivesspace@localhost | +--+ | GRANT USAGE ON *.* TO `archivesspace`@`localhost` IDENTIFIED BY PASSWORD '*2C2611CEB83E695935FB2CA67F9EE3D56514F1CC' | | GRANT ALL PRIVILEGES ON `archivesspace`.* TO `archivesspace`@`localhost` WITH GRANT OPTION | +--+ 2 rows in set (0.000 sec) MariaDB [archivesspace]> Then I do same for 127.0.0.1: MariaDB [archivesspace]> SHOW GRANTS for archivesspace@127.0.0.1; +--+ | Grants for archivesspace@127.0.0.1 | +--+ | GRANT USAGE ON *.* TO `archivesspace`@`127.0.0.1` IDENTIFIED BY PASSWORD '*2C2611CEB83E695935FB2CA67F9EE3D56514F1CC' | | GRANT ALL PRIVILEGES ON `archivesspace`.* TO `archivesspace`@`127.0.0.1` WITH GRANT OPTION | +--+ 2 rows in set (0.000 sec) MariaDB [archivesspace]> I AM able to restore into the "archivesspace" database with: sudo mysql -u archivesspace -pREDACTED archivesspace < /vagrant/archivesspace_CURRENT.sql The connect string in my config.rb file: AppConfig[:db_url] = "jdbc:mysql://localhost:3306/archivesspace?user=archivesspace&password=REDACTED&useUnicode=true&characterEncoding=UTF-8" And yet I get the "unable to connect to backend" error. No fair! Advice in previous posts down through the years suggested this was a permissions problem, or running MySQL on something other than localhost/127.0.0.1, but I think what I've done above rules this out. Are there other reasons why I might be getting the "unable to connect to backend" error? Advice appreciated! Mark PS: I don't think this is relevant to the connection issue, but here are the permissions I've set on the file system: vagrant@vagrant:/usr/share/archivesspace$ ls -la total 84 drwxr-xr-x 16 archivesspace archivesspace 4096 Jun 11 18:59 . drwxr-xr-x 122 root root 4096 Jun 11 18:59 .. -rwxr-xr-x 1 archivesspace archivesspace 813 Jun 11 18:54 archivesspace.bat -rwxr-xr-x 1 archivesspace archivesspace 5364 Jun 11 18:53 archivesspace.sh drwxr-xr-x 4 archivesspace archivesspace 4096 Jun 11 18:53 clustering drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 21:05 config -rwxr-xr-x 1 archivesspace archivesspace 665 Jun 11 18:53 COPYING drwxr-xr-x 9 archivesspace archivesspace 4096 Jun 11 18:59 data drwxr-xr-x 14 archivesspace archivesspace 4096 Jun 11 18:54 docs drwxr-xr-x 9 archivesspace archivesspace 4096 Jun 11 18:54 gems drwxr-xr-x 8 archivesspace archivesspace 4096 Jun 11 18:54 launcher drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 18:59 lib drwxr-xr-x 4 archivesspace archivesspace 4096 Jun 11 18:53 locales drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 18:59 logs drwxr-xr-x 22 archivesspace archivesspace 4096 Jun 11 18:54 plugins -rwxr-xr-x 1 archivesspace archivesspace 2326 Jun 11 18:53 README.md drwxr-xr-x 12 archivesspace archivesspace 4096 Jun 11 18:53 reports drwxr-xr-x 3 archivesspace archivesspace 4096 Jun 11 18:54 scripts drwxr-xr-x 3 archivesspace archivesspace 4096 Jun 11 18:54 stylesheets drwxr-xr-x 2 archivesspace archivesspace 4096 Jun 11 18:54 wars vagrant@vagrant:/usr/share/archivesspace$ -- <><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><><> Mark Cyzyk, M.A., M.L.S. Library Applications Group The Sheridan Libraries The Johns Hopkins University mcy...@jhu.edu Verba volant, scripta manent. ___ Archivesspace_Users_Group mailing list Archivesspace_Users_Group@lyralists.lyrasis.org http://lyralists.lyrasis.org/mailman/lis
