Could not determine list owner

[gator]

I have a CPanel server that is sending me an email every 4 hours that reads:

Could not determine list owner for lists at /usr/local/cpanel/scripts/update_mailman_cache line 63.

I'm not aware of anything that is broken per se but the stream of emails is kind of annoying. Any thoughts on how to correct this situation?

 

[Infopro]

I had a ticket open about this last week. It did not mention list owner as yours does, instead is was looking for archives that were not there. The details may be helpful here, or to the next one searching for this issue.

Emails from server told me:

Could not open archive dir for listname_domainname.org: No such file or directory at /usr/local/cpanel/Cpanel/Mailman/DiskUsage.pm line 111.
Could not open archive mbox dir for listname_domainname.org: No such file or directory at /usr/local/cpanel/Cpanel/Mailman/DiskUsage.pm line 146.

cPanel Support:

I created the directories listname_domainname.org and listname_domainname.org.mbox then changed their owner to mailman. I then ran /scripts/fixmailman, then /scripts/update_mailman_cache again and saw no further errors.

You might like to put in a ticket to cPanel support on this so they can take a closer look for you.

 

[jalal]

I have the same problem and the warning is hard coded into the script. The update_mailman_cache gets a list of domains from cpanel, then checks all the lists in /usr/local/cpanel/3rdparty/mailman/lists/ to see if the domain name is the last part of the list name. If, like me, your mailman list names do not contain a valid domain name (e.g.: list_name_domain.tld as a list name) then you will continue to get the warning. Every four hours. For eternity...
One option would be to go through and rename all the lists...
Another option is to comment out the test in the update_mailman_cache script, which is the path I've taken. (Actually, I've forced the $listuser variable to be 'root' which bypasses the check).

HTH

 

[lbeachmike]

I have the same issue. This issue seems to have appeared following an update of my version from STABLE to RELEASE as recommended by cpanel in a different thread.

I went into cpanel and tried to modify the list but that threw an internal server error. I tried to delete the list and it reported that it was successfully deleted, though also reported that the directories did not exist. And the list continues to show in cpanel as an existing list.

I am disappointed that these types of bugs are making their way through the release tree.

I've opened a ticket, because I'm not sure if creating the directories is a solution to the issue since the issue did not previously exist.

mrk

 

[kservik]

I have the same issue also. It is extremly annoying. I have WHM 11.30.0 (build 32)

 

[lbeachmike]

I have the same issue also. It is extremly annoying. I have WHM 11.30.0 (build 32)

Cpanel tech support fixed it for me by deleting some files that were preventing me from being able to delete a defunct mailing list. It would be helpful if cpanel could post some more generic details here on how to resolve for those who find their way to this thread.

mrk

 

[cPanelTristan]

Anyone who is having the issue needs to post the exact email received or error received as different messages have been provided caused for different reasons.

Regardless whether it appears to be the same issue, please always ensure to post the exact message received. Otherwise, please submit a ticket via WHM > Support Center > Contact cPanel or using the link provided in my signature. Once I have sufficient information to provide based on the set issue occurring for the set error message, I would be happy to provide details on how to correct it for that set error or message.

I do know that the ticket created by lbeachmike was due to a list that no longer existed from several years ago and that the newer cPanel detection script provided more verbose details that caused a message to trigger about those files not being entirely cleared for that old mailing list that had only partially been removed.

 

[kservik]

Cron <[email protected]********> /usr/bin/test -x /usr/local/cpanel/scripts/update_mailman_cache && /usr/local/cpanel/scripts/update_mailman_cache

Could not determine list owner for request.pck at /usr/local/cpanel/scripts/update_mailman_cache line 63.
Could not determine list owner for config.pck at /usr/local/cpanel/scripts/update_mailman_cache line 63.
Could not determine list owner for config.pck.last at /usr/local/cpanel/scripts/update_mailman_cache line 63.

 

[santrix]

I'm seeing this exact error myself:

# /scripts/update_mailman_cache
Could not determine list owner for mail_somedomain.co.uk at /scripts/update_mailman_cache line 63.

Anyone got any more clues?

 

[cPanelTristan]

Does the list in question still actually exist?

 

[mtindor]

In my case:

Could not determine list owner for request.pck at /usr/local/cpanel/scripts/update_mailman_cache line 63.
Could not determine list owner for config.pck.last at /usr/local/cpanel/scripts/update_mailman_cache line 63.
Could not determine list owner for config.pck at /usr/local/cpanel/scripts/update_mailman_cache line 63.

-rw-rw---- 1 mailman mailman 4055 Feb 20 2009 /usr/local/cpanel/3rdparty/mailman/lists/config.pck
-rw-rw-r-- 1 mailman mailman 24 Sep 27 2008 /usr/local/cpanel/3rdparty/mailman/lists/request.pck
-rw-rw---- 1 mailman mailman 4055 Feb 20 2009 /usr/local/cpanel/3rdparty/mailman/lists/config.pck.last

The account [list owner] associated with this list was deleted long ago. It looks like the list itself just wasn't deleted.

All the mailing list stuff for legitimate active mailing lists is located in subdirectories under /usr/local/cpanel/3rdparty/mailman/lists such as fakelist_fakedomain.com. But these three files are right in the /usr/local/cpanel/3rdparty/mailman/lists folder itself. If I look at the contents of these files, they all reference one particular list from one particular domain account that was removed years ago.

Will deleting these three files resolve the issue? Or does something more need to be done?

M

 

[kservik]

I have the same question: Can we just delete these files?