Skip to Content.
Sympa Menu

en - Re: [en@sympa] Lock issues after upgrading OS

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Erik Olson <address@concealed>
  • To: address@concealed
  • Subject: Re: [en@sympa] Lock issues after upgrading OS
  • Date: Sat, 6 Jul 2024 18:56:16 -0700

Answering my own question... Switching to the systemd socket method has solved the problem.

I had been using the old deprecated setuid wrapper method.  Not sure what changed in the OS between Fedora 39 and Fedora 40, but the lock was failing with the error "read-only filesystem".

  - Erik

On 2024-07-06 17:11, Erik Olson wrote:

Longtime sympa admin for small hobbyist lists.  Upgraded underlying OS to Fedora 40 today, and now getting tons of these errors in the log:

Jul  6 17:07:12 pulcher wwsympa[10736]: err main::#1562 > main::do_lists#4169 > Sympa::List::get_lists#4586 > Sympa::List::new#181 > Sympa::List::load#701 > Sympa::List::_load_list_config_file#4994 Could not create new lock on /home/sympa/list_data/gsas.org/gsasfunds/config
Jul  6 17:07:12 pulcher wwsympa[10736]: err main::#1562 > main::do_lists#4169 > Sympa::List::get_lists#4586 > Sympa::List::new#181 > Sympa::List::load#707 Could not create new lock

I tried upgrading sympa itself to the latest version, which was successful, but am still getting the errors.

Thanks for any insight,

   - Erik




Archive powered by MHonArc 2.6.19+.

Top of Page