>then decided to rollback the
>BerkeleyDB to previous version
Upgrading the BerkleyDB engine version from version 4 to 5 needs a
conversion of all BDB databases - follow the oracle roadmap or - export
the db's, delete all BDB files and import the DB's.
ASSP will delete and recreate the BDB-ENV's (/tmpDB) if a engine version
is changed, but not the database files.
>it will start listening and *accepting*
This is not true! SMTP-connection will be accepted only by the
SMTP-Workers. The first transfer of a connection from Main_Thread to a
worker is done after the statup line
Sep-16-10 09:28:46 [init] Info: central signalhandler ....
up to this point, only the OS handles the incomming connections for the
opened listeners.
The Main_Thread simply establish listeners for the SMTP stuff and is
'talking' with the OS about new connections - and is doing the full web
stuff.
But I think, it is possible to start the listeners at a later time in the
startup sequence - so the time between opening the listeners to the first
transfer could be reduced to 2 seconds or even less (from possibly over
one minute). If it is working for me - this will be changed in the next
version.
The reason for the early start of the listeners was (in a early state of
dev) to have all the time the same (low) file handle numbers for debuging
- the last two numbers in the connection log line
Sep-16-10 10:10:51 [Worker_1] Info: Worker_1 got connection from
MainThread - 7/7
which was
Aug-17-10 09:59:15 [Worker_1] Info: Worker_1 got connection from
MainThread - 4/4
Both - the startup and the shutdown (I also saw it) issues will be
possibly fixed in 2.0.2_1.2.11
Thomas
Von: "GrayHat" <[email protected]>
An: "ASSP development mailing list" <[email protected]>
Datum: 16.09.2010 09:29
Betreff: Re: [Assp-test] fixes and changes in 2.0.2_1.2.10
>> Hmmm... sounds like there are some problems; updated
>> the optimizer.pm and the BerkeleyDB to latest versions,
> Possibly, I've observed similar behavior while testing shutdown via
> 'https://'"$lo...@$hport"'/shutdown_frame?action= Proceed '
> with 2.0.1(1.1.27) - ASSP would seem to hang, but I didn't wait
> long - after 150s my script sends TERM, to which ASSP then properly
> reacts to.
Yes, I have a fallback to "kill" as well, but I was trying to check
how ASSP was running and in any case I suspect the issue
may be caused by some kind of "deadlock"; anyways, tried
several workarounds to no luck, then decided to rollback the
BerkeleyDB to previous version and things seem to be back
to normal behaviour; not sure if it's a coincidence or not (still
monitoring the box), just trying to give some informations to
help tracking the issue
Also and since we're at it; if start monitoring connections on
a box and then start ASSP from cmdline, you'll notice that
it will start listening and *accepting* connections even if
it didn't fully initialize (you'll find established connections)
and since it happened to me that in some cases ASSP
hung/crashed during startup, I wonder if the above may
be another cause of issues; while the "accept" happens
constantly it doesn't always cause problems, so there
may be some particular "conditions" causing such an
issue; for this latter problem (don't think it's related to
the other one) a solution could be setting up a global
"semaphore" so that ASSP won't accept connections
until it won't fully complete its initialization (incoming
connections may just be rejected till that moment)
and it's ready to serve them
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test
DISCLAIMER:
*******************************************************
This email and any files transmitted with it may be confidential, legally
privileged and protected in law and are intended solely for the use of the
individual to whom it is addressed.
This email was multiple times scanned for viruses. There should be no
known virus in this email!
*******************************************************
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test