No listmaster notification sent for sync_include_failed

[Vincent3187]

Hello, Some of our lists configured with datasources (remote file or LDAP) fail to synchronize members but no notification corresponding is sent to listmaster. The corresponding error is displayed in the logfile, for example : Unable to fetch data source Sympa::DataSource::RemoteFile ....Can't connect to… Can we have accidentally disabled this type of notification ? We used to receive them few weeks ago.

Sympa 6.2.54

Thanks for your help

[ikedas]

Hi @Vincent3187 ,

Could you please show us the full log lines indicating the errors?

[Vincent3187]

Hello Ikedas, These are 3 examples of error :

Example with remote file : Aug 3 01:57:12 tcgpsympa2 task_manager[91000]: 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#1349 > Sympa::List::sync_include#4798 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#181 > Sympa::Request::Handler::include::_update_users#289 > Sympa::DataSource::open#134 > Sympa::DataSource::RemoteFile::_open#101 Unable to fetch data source Sympa::DataSource::RemoteFile context=XXXXXXX@services.cnrs.fr;id=bcb241c6;role=member;name=XXXX: Can't connect to XXXX:80 (Connexion refusée)

Example with LDAP : Jul 10 21:57:28 tcgpsympa2 task_manager[123809]: 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#1349 > Sympa::List::sync_include#4798 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#181 > Sympa::Request::Handler::include::_update_users#289 > Sympa::DataSource::open#134 > Sympa::DataSource::LDAP::_open#46 > Sympa::DataSource::LDAP::_open_operation#72 LDAP search (single level) failed: (52) Proxy can't contact remote server with data source Sympa::DataSource::LDAP context=XXXXXX@services.cnrs.fr;id=8ac65c25;role=member;name=XXXXX

Example with include file : (It is a test list and I moved the source file to generate the error) Aug 3 10:28:28 tcgpsympa2 task_manager[27513]: 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#1349 > Sympa::List::sync_include#4798 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#181 > Sympa::Request::Handler::include::_update_users#289 > Sympa::DataSource::open#134 > Sympa::DataSource::File::_open#40 Unable to open file "/datasan/sympa/abonnes/liste_test_vm.txt": Aucun fichier ou dossier de ce type

Regards

[Vincent3187]

Hello Ikedas, did you manage to reproduce the problem ? Do you think it is a bug or a setup issue ?

Thanks for you feedback. Regards

[ikedas]

I think they are setup issues.

Can't connect to XXXX:80 (Connexion refusée)

This means that HTTP connection was refused by remote host.

(52) Proxy can't contact remote server

This means that your Sympa cannot contact LDAP server (maybe via LDAP proxy?).

Aucun fichier ou dossier de ce type

This means that specified file does not exist.

[Vincent3187]

Hello Ikedas, we know the reason why the list didn't synchronized. This is not the problem. Problem is that Sympa does not send notification.

Regards

[kazimkoybasi]

Hello Ikedas,

We are using sympa 6.2.64 and we also does not get notification in listmaster about sync_include from db errors. I think this is critical for users because changing sql query becames hard to manage in case of errors.

Regards.

[ikedas]

Hi @kazimkoybasi ,

Could you please show us the full log lines indicating the errors?

[kazimkoybasi]

Hi @ikedas ,

I added logs below with loglevel 3 configuration. Thanks.

Mar 25 10:20:34 smtp wwsympa[3280]: info main::do_sync_include(xxx, member) [robot xxx.sabanciuniv.edu] [session 53203222164649] [client xxx] [user xxx@sabanciuniv.edu] [list xxx]
Mar 25 10:20:34 smtp wwsympa[3280]: info main::do_sync_include(xxx, member) [robot xxx.sabanciuniv.edu] [session 53203222164649] [client xxx] [user xxx@sabanciuniv.edu] [list xxx]
Mar 25 10:20:34 smtp wwsympa[3280]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action=include;context=xxx@xxx.sabanciuniv.edu;role=member>
Mar 25 10:20:34 smtp wwsympa[3280]: notice Sympa::Spindle::ProcessRequest::_twist() Processing Sympa::Request <action=include;context=xxx@xxx.sabanciuniv.edu;role=member>
Mar 25 10:20:34 smtp wwsympa[3280]: err main::#1556 > main::do_sync_include#16585 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#201 > Sympa::Request::Handler::include::_update_users#369 > Sympa::DataSource::open#134 > Sympa::DataSource::SQL::_open#99 > Sympa::Process::eval_in_time#472 > (eval)#479 > (eval)#479 > Sympa::DataSource::SQL::__ANON__#51 > Sympa::DatabaseDriver::PostgreSQL::do_prepared_query#112 > Sympa::Database::do_prepared_query#382 Unable to execute SQL statement "xxx": (42601) ERROR:  syntax error at or near "sr"#012LINE 1: xxx...#012                ^
Mar 25 10:20:34 smtp wwsympa[3280]: err main::#1556 > main::do_sync_include#16585 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#201 > Sympa::Request::Handler::include::_update_users#369 > Sympa::DataSource::open#134 > Sympa::DataSource::SQL::_open#99 > Sympa::Process::eval_in_time#472 > (eval)#479 > (eval)#479 > Sympa::DataSource::SQL::__ANON__#51 > Sympa::DatabaseDriver::PostgreSQL::do_prepared_query#112 > Sympa::Database::do_prepared_query#382 Unable to execute SQL statement "xxx": (42601) ERROR:  syntax error at or near "sr"#012LINE 1: xxx...#012                ^
Mar 25 10:20:34 smtp wwsympa[3280]: err main::#1556 > main::do_sync_include#16585 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#201 > Sympa::Request::Handler::include::_update_users#369 > Sympa::DataSource::open#134 > Sympa::DataSource::SQL::_open#99 > Sympa::Process::eval_in_time#472 > (eval)#479 > (eval)#479 > Sympa::DataSource::SQL::__ANON__#53 Unable to connect to SQL data source Sympa::DataSource::SQL <context=xxx@xxx.sabanciuniv.edu;id=ca7b92ae;role=member;name=>
Mar 25 10:20:34 smtp wwsympa[3280]: err main::#1556 > main::do_sync_include#16585 > Sympa::Spindle::spin#95 > Sympa::Request::Handler::include::_twist#201 > Sympa::Request::Handler::include::_update_users#369 > Sympa::DataSource::open#134 > Sympa::DataSource::SQL::_open#99 > Sympa::Process::eval_in_time#472 > (eval)#479 > (eval)#479 > Sympa::DataSource::SQL::__ANON__#53 Unable to connect to SQL data source Sympa::DataSource::SQL <context=xxx@xxx.sabanciuniv.edu;id=ca7b92ae;role=member;name=>
Mar 25 10:20:34 smtp wwsympa[3280]: info Sympa::Request::Handler::include::_twist() Sympa::Request <action=include;context=xxx@xxx.sabanciuniv.edu;role=member>: Failure, 0 added, 0 held, 0 updated
Mar 25 10:20:34 smtp wwsympa[3280]: info Sympa::Request::Handler::include::_twist() Sympa::Request <action=include;context=xxx@xxx.sabanciuniv.edu;role=member>: Failure, 0 added, 0 held, 0 updated

Regards

[bboyle262]

Found this report and would like to add a comment, that in many of our lists at least, the synchronization feature is quite heavily relied upon and a very important function for list owners and listmasters. I imagine this is the case for others too.

Therefore, it seems like failures should be reported at the same logging level that generates other notifications to listmasters and list owners...or perhaps have its own setting available that would "Notify" when subscriber syncs fail.

Thanks