Seeing "Could not create new lock" messages after migrating lists from old Sympa to new Sympa server #1823
Comments
|
Also seeing these when it comes to tasks: Mar 27 15:36:55 sympa-i-0709b02d07d5596dc task_manager[1442]: err main::#148 > Sympa::Spindle::spin#78 > Sympa::Spool::next#124 > Sympa::Spool::Task::_load#57 > Sympa::Spool::Task::_create_all_tasks#93 > Sympa::List::get_lists#4668 > Sympa::List::new#181 > Sympa::List::load#707 Could not create new lock |
|
Hi @UAProfessorProton , |
|
Hi @ikedas Yes /sympa is an NFS mount. 127.0.0.1:/ on /sympa type nfs4 (rw,relatime,vers=4.1,rsize=1048576,wsize=1048576,namlen=255,hard,noresvport,proto=tcp,port=20557,timeo=600,retrans=2,sec=sys,clientaddr=127.0.0.1,local_lock=none,addr=127.0.0.1,_netdev) |
|
I understand that your Sympa accesses filesystem with NFS mount. What I want to know is that, what is the type of the remote storage that you are mounting through the NFS? |
|
@ikedas thank you for your response. We are using cloud storage (Amazon EFS) to mount /sympa via NFS. The sympa server belong in the same VPC as the EFS server. |
|
If the operating system is RHEL or its clone, have you disabled SELinux? |
|
Hi @ikedas, yes SELINUX is already disabled [root@sympa-i-0709b02d07d5596dc log]# getenforceDisabled Apr 1 04:14:14 sympa-i-0709b02d07d5596dc task_manager[1442]: err main::#148 > Sympa::Spindle::spin#83 > Sympa::Spindle::ProcessTask::_twist#74 > Sympa::Spindle::ProcessTask::_execute#140 > Sympa::Spindle::ProcessTask::_cmd_process#174> Sympa::Spindle::ProcessTask::do_sync_include#1347 > Sympa::List::sync_include#4156 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#213 > Sympa::Request::Handler::include::_update_users#387 > Sympa::DataSource::open#112 > Sympa::DataSource::List::_open#60 > Sympa::List::new#181 > Sympa::List::load#707 Could not create new lock Even tasks are having errors. I'm running this on Amazon Linux 2. Is there a way to identify the path where it is trying to create the locked file? I tried to set to log_level=4 but the path is still not provided. |
|
Please apply this patch, try again and show what you see in the log. |
|
Thank you for your response. I would like to ask if this patch will also apply if Sympa was installed from the EPEL yum repo. The lib files are located in /usr/share/sympa/lib/Sympa. |
|
Yes, it will apply. If you want to confirm, run |
|
Thank you for the patch, I attempted to recreate the issue and found the following messages. Looks like it's saying permission-related but doesn't say the path... Apr 9 08:22:36 sympa-i-0709b02d07d5596dc wwsympa[31475]: err main::#1562 > main::do_lists#4169 > Sympa::List::get_lists#4684 > Sympa::List::new#181 > Sympa::List::load#719 Could not create new lock: Permission denied I made sure that the spool directory is owned by sympa and have 775 permissions: [root@sympa-i-0709b02d07d5596dc sympa]# find /sympa/spool -type d -exec ls -ld {} ; This applies to list_data as well [root@sympa-i-0709b02d07d5596dc sympa]# find /sympa/list_data -type d -exec ls -ld {} ; Configuration: wwsympa.fcgi process is owned by sympa [root@sympa-i-0709b02d07d5596dc sympa]# ps -ef | grep -i wwsympa | grep -v grep [root@sympa-i-0709b02d07d5596dc sympa]# grep -i ^home /etc/sympa/sympa.conf [root@sympa-i-0709b02d07d5596dc sympa]# grep -i spool /etc/sympa/sympa.conf Appreciate your help on this. |
|
Please check NFS and mounted file system. Is it configured to allow writing? This seems not a problem of Sympa but of AWS. |
|
@ikedas, I looked into this further, the problem seem to have disappeared after I deleted all the mailing lists under /sympa/list_data. I have no issues creating mailing lists after that. I suspect some nfs lock files might have been migrated over the old sympa server since the mailing lists were also copied from NFS, while the sympa service was running. I cannot find it in the documentation or most probably missed it, the naming convention of the lock files being created. Are the lock files created end with .lock file extension names? |
|
The extension is sympa/src/lib/Sympa/LockedFile.pm Line 40 in 4f62c3a However it is unlikely that the stale lock was preventing creation of new lock, and something with NFS might cause the problem. |
|
This issue is now resolved, thank you for your support. |
I'm getting multiple lines below and I suspect these come from the lists I just moved from an older sympa server.
wwsympa[2041]: err main::#1562 > main::do_create_list_request#9638 > Sympa::List::get_lists#4668 > Sympa::List::new#181 > Sympa::List::load#707 Could not create new lock
I would like to know how I can identify the lists that are causing theses messages to appear. All lists are owned by sympa:sympa and have 755 permissions.
Version
Sympa 6.2.72
Installation method
rpm method
Expected behavior
I'm not supposed to see the following messages:
wwsympa[2041]: err main::#1562 > main::do_create_list_request#9638 > Sympa::List::get_lists#4668 > Sympa::List::new#181 > Sympa::List::load#707 Could not create new lock
Actual behavior
I'm getting multiple lines below and I suspect these come from the lists I just moved from an older sympa server.
wwsympa[2041]: err main::#1562 > main::do_create_list_request#9638 > Sympa::List::get_lists#4668 > Sympa::List::new#181 > Sympa::List::load#707 Could not create new lock
I would like to know how I can identify the lists that are causing theses messages to appear. All lists are owned by sympa:sympa and have 755 permissions.
Additional information
/sympa/list_data is mounted from NFS. there's only node mounting this filesystem.
Attempt to resolve the issue
What should be the required permissions and ownerships?
The text was updated successfully, but these errors were encountered: