On 28.03.2007, at 16:36, Stefano Bagnara wrote:
zkn ha scritto:
On 27.03.2007, at 14:31, Stefano Bagnara wrote:
zkn ha scritto:
I run it on RedHat EL3. James is running as root - I don't know
if it is possible to run it as different user and bind it on
port 25.
No, with james 2.3 this is not possible.
In trunk we added support for commons-daemon and this is possible
(but I don't know when this will be released)
I'm starting to thing that this has something to do with the
files under /var repository. We have hundreds of thousands
emails under /var.
What happened is that I started it to test it with the self
created var repository and while it was running we received lots
of emails - 60658 files in address-error, which makes about 30K
emails I think. Then I stopped it and ran it again. This time it
started much slower, I even thought it's not starting again but
it started. This is from the phoenix.log:
I think that James 2.3 keeps *keys* of every message in memory,
but 30K messages should not be enough to fill the memory (it
should use 1-2MB in the heap).
OK, but what if I have much much more emails under /var/mail/
MYOWNPATH, where MYOWNPATH is a separate folder which james
should not care about, and they are sorted in many folders in
there? Will it try to get keys for those files? Cause this could
be the reason for james not starting up when I use my real
repository? If that is the case it may take hours or even days to
read everything in the path :)
Can you try temporarily moving the "address-error" mails
somewhere else and restart to see in this is the problem or not?
Yes, I moved everything and it started without problems. As you
can see the verification is much quicker:
All of this is weird. I checked the code in the verifier (from
phoenix) and I didn't see anything that could take so much time.
Furthermore I have a similar scenario with a symlink pointing to a
lot of files that are never read by James and my james startup is
normal, so I don't really know...
Please let us know if you find out anything useful...
I ran some tests again and these are the results.
The real path to my repository is /var/james/var, James is installed
in /usr/local/james-2.3.0. In /var/james/var/mail/ except all James
store directories (address-error, ougoing ...) there is one MYOWN
where I have a lot of emails sorted in many sub, sub .. folders. This
is folder and everything in it have 755 SOMEUSER.SOMEUSER permissions.
James will start successfully if it uses it's self created /var. When
I link /usr/local/james-2.3.0/apps/james/var/mail/
to the real store /var/james/var/mail it won't start, will not create
any of it's store directories and the last message in phoenix.log is
Verify that if target is null then actions is null.
I created a new directory /var/james/var/newmail and linked it with /
usr/local/james-2.3.0/apps/james/var/mail/. James started and it
created all it's store directories successfully. I stopped it and
then made a link in /var/james/var/newmail/ to /var/james/var/mail/
MYOWN. After this changes James is not starting up again and the last
message in the log again is
Verify that if target is null then actions is null.
Have in mind that this MYOWN directory contains a really big tree of
folders and files - ~50GB. It will be really slow even if james|
phoenix tries only to go trough all of them.
I think that's all I can give as information. If your are not able to
help me I will have to keep using 2.2.
Stefano
INFO 2007-03-27 04:46:55.298 [Phoenix.] (): Verify that if
target is null then actions is null.
INFO 2007-03-27 04:46:55.598 [Phoenix.] (): Verifying that the
name specified for Blocks and BlockListeners are valid.
Otherwise try to temporarily increase the java memory using the "-
Xmx" parameter in the startup script.
Stefano
Ozkan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
