cron error : gate_news, permission denied
Hi,
I get this error almost every minute. If check the permissions I seethat config.db of all lists are owned by nobody ( web user ). Is it not okey? Should I chown?
Your "cron" job on mail /usr/local/bin/python -S /export/home/mailman//cron/gate_news
produced the following output:
Traceback (most recent call last): File "/export/home/mailman//cron/gate_news", line 222, in ? main() File "/export/home/mailman//cron/gate_news", line 203, in main process_lists(lock) File "/export/home/mailman//cron/gate_news", line 140, in process_lists mlist = MailList.MailList(listname, lock=0) File "/export/home/mailman//Mailman/MailList.py", line 79, in __init__ self.Load() File "/export/home/mailman//Mailman/MailList.py", line 891, in Load dict, e = self.__load(dbfile) File "/export/home/mailman//Mailman/MailList.py", line 868, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/export/home/mailman/lists/test1/config.db'
It is getting about time to make my feature request (again).
The first and most important: Keep real names as well as rmail addresses. My real preference would be to use PostgreSQL (preferred) or MySQL for the list info database.
My second, and almost as important, request: Provide a way to specify the list domain name at the time of list creation instead of having to change it after creation. This causes confusion for users of virtual domains.
Thanks for a great product.
--Richard
Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2
"Richard B. Pyne" wrote:
My second, and almost as important, request: Provide a way to specify the list domain name at the time of list creation instead of having to change it after creation. This causes confusion for users of virtual domains.
Don't see why you have to do that. I run mailman across threedifferent vdomains and I never have to change the list domain name. It automatically knows what its (correct) vdomain is when it gets created.
AMK4-- H | Hi, I'm currently out of my mind. Please leave a message. BEEEEP! |____________________________________________________________________
Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130
Director of Internet Operations / SysAdmin . 800.441.3873 x130
Photo Craft Laboratories, Inc. . eFax 248.671.0909
http://www.pcraft.com . 3550 Arapahoe Ave, #6
.................. . . . . Boulder, CO 80303, U.S.A.
You must be running IP virtual domains rather than named virtual domains.
With named vrtual domains, mailing lists are always created defaulted to the domain where Mailman was originally installed (the machine's default domain) and then I have to log in to the admin page and change them to the correct domain for the list. The welcome message to the list owner shows the default domain rather than the domain for the list.
There are also some minor issues on the list of lists for a domain. If the domain is set to foo.com and the user browses to http://www.foo.com/mailman/listinfo they will not see the list but will if they browse to http://foo.com/mailman/listinfo.
On 29 Mar 2001, at 8:46, Ashley M. Kirchner wrote:
"Richard B. Pyne" wrote:
My second, and almost as important, request: Provide a way to specify the list domain name at the time of list creation instead of having to change it after creation. This causes confusion for users of virtual domains.
Don't see why you have to do that. I run mailman across threedifferent vdomains and I never have to change the list domain name. It automatically knows what its (correct) vdomain is when it gets created.
AMK4
Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2
"Richard B. Pyne" wrote:
You must be running IP virtual domains rather than named virtual domains.
Nope, they're named virtual domains.With named vrtual domains, mailing lists are always created defaulted to the domain where Mailman was originally installed (the machine's default domain)
I run named vdomains, to the same IP. However, I do have a separateinstallation for each vdomain (though they all run under ~mailman as mailman.mailman)
There are also some minor issues on the list of lists for a domain. If the domain is set to foo.com and the user browses to http://www.foo.com/mailman/listinfo they will not see the list but will if they browse to http://foo.com/mailman/listinfo.
That's not mailman's fault, that's your web server's problem.Misconfigured.
AMK4-- W | | I haven't lost my mind; it's backed up on tape somewhere. |____________________________________________________________________
Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130
SysAdmin / Websmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . eFax 248.671.0909
http://www.pcraft.com . 3550 Arapahoe Ave #6
.................. . . . . Boulder, CO 80303, USA
On 29 Mar 2001, at 11:44, Ashley M. Kirchner wrote:
"Richard B. Pyne" wrote:
With named vrtual domains, mailing lists are always created defaulted to the domain where Mailman was originally installed (the machine's default domain)
I run named vdomains, to the same IP. However, I do have a separateinstallation for each vdomain (though they all run under ~mailman as mailman.mailman)
There is the difference, I run ONE copy of Mailman for the entire server. There should be no need to run a separate copy for each virtual domain.
There are also some minor issues on the list of lists for a domain. If the domain is set to foo.com and the user browses to http://www.foo.com/mailman/listinfo they will not see the list but will if they browse to http://foo.com/mailman/listinfo.
That's not mailman's fault, that's your web server's problem.Misconfigured.
No, not msconfigured. Mailman looks at the FQDN when deciding what lists to show, not just the second level domain. Changing this behaviour COULD cause other undesirable effects though.
--Richard
Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2
"RBP" == Richard B Pyne <rpyne@kinfolk.org> writes:
RBP> There is the difference, I run ONE copy of Mailman for the
RBP> entire server. There should be no need to run a separate copy
RBP> for each virtual domain.There should be no problem with this /except/ if you want lists with the same name in different virtual domains. That is the missing feature that should be added to Mailman.
-Barry
Which is a good addition to what I was asking for as a feature. My request was and is that we can set the default domain at the time of list creation so that the welcome email goes out with the right domain and the list is pre-configured with the right domain so I don't have to go into the admin screen and change it.
Thanks,
Richard
On 30 Mar 2001, at 10:56, Barry A. Warsaw wrote:
"RBP" == Richard B Pyne <rpyne@kinfolk.org> writes:
RBP> There is the difference, I run ONE copy of Mailman for the RBP> entire server. There should be no need to run a separate copy RBP> for each virtual domain.There should be no problem with this /except/ if you want lists with the same name in different virtual domains. That is the missing feature that should be added to Mailman.
-Barry
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users
Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2
"Richard B. Pyne" wrote:
No, not msconfigured. Mailman looks at the FQDN when deciding what lists to show, not just the second level domain. Changing this behaviour COULD cause other undesirable effects though.
You have mailman installed as 'foo.com', so it never knows about the'www' part. Mailman is not responsible for how you set it up, it does what you tell it to. If you told it to install as 'www.foo.com', it will also work that way.
All of my lists sit on 'lists.vdomain.com' and they work just fine assoon as I add a new list. There is no editing to be done anywhere, no domains to be changed, nothing. None of them conflict with one another, and I can have the same list name under several domains and everything works just fine (as separate lists). The web interface works the same way. I can hit 'abc-list' on any of the vdomains (provided it exists on them) and it would be a different list.
Another solution would be to tell your webserver to serve mailmanthrough www.foo.com if mailman only knows about foo.com. Set a pass through proxy.
AMK4-- W | | I haven't lost my mind; it's backed up on tape somewhere. |____________________________________________________________________
Ashley M. Kirchner <mailto:ashley@pcraft.com> . 303.442.6410 x130
SysAdmin / Websmith . 800.441.3873 x130
Photo Craft Laboratories, Inc. . eFax 248.671.0909
http://www.pcraft.com . 3550 Arapahoe Ave #6
.................. . . . . Boulder, CO 80303, USA
Unless you are using the "gateway to news" functions in mailman, this cron entry can be commented out or removed. Not sure why you are getting the error, but commenting out the cron entry is a quick fix :-)
Steve orion@deathcon.com Owner/Admin deathcon.com - pirk.com webops.com - disclaimer.com
On Thu, 29 Mar 2001, Murat Balkas wrote:
Hi,
I get this error almost every minute. If check the permissions I seethat config.db of all lists are owned by nobody ( web user ). Is it not okey? Should I chown?
Your "cron" job on mail /usr/local/bin/python -S /export/home/mailman//cron/gate_news
produced the following output:
Traceback (most recent call last): File "/export/home/mailman//cron/gate_news", line 222, in ? main() File "/export/home/mailman//cron/gate_news", line 203, in main process_lists(lock) File "/export/home/mailman//cron/gate_news", line 140, in process_lists mlist = MailList.MailList(listname, lock=0) File "/export/home/mailman//Mailman/MailList.py", line 79, in __init__ self.Load() File "/export/home/mailman//Mailman/MailList.py", line 891, in Load dict, e = self.__load(dbfile) File "/export/home/mailman//Mailman/MailList.py", line 868, in __load fp = open(dbfile) IOError: [Errno 13] Permission denied: '/export/home/mailman/lists/test1/config.db'
Mailman-Users maillist - Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users
participants (5)
-
Ashley M. Kirchner -
barry＠digicool.com -
Murat Balkas -
Richard B. Pyne -
Steve Pirk