[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ozone should exit cleanly upon control-C
Falko Braeutigam wrote:
> On Tue, 27 Mar 2001, you wrote:
> > Falko Braeutigam wrote:
> >
> > > Jan, can you please keep this in the list? Thanks.
>
> Hello???????????????
Sorry
>
>
> CAN YOU PLEASE KEEP THIS I N T H E M A I L L I S T ?????? Thanks.
>
> > >
> > > On Tue, 27 Mar 2001, Jan van Oort wrote:
> > > > Anyway, I reproduced the phenomenon on my Solaris/intel box. The exception thrown is the
> > > > following one:
> > > >
> > > > bash-2.03$ ozone -ddata
> > > > ozone server - version 0.6.1
> > > > initializing environment...
> > > > ozoneDB.adminPort = 3000
> > > > ozoneDB.classicStore.clusterSize = 65536
> > > > ozoneDB.classicStore.clusterSpaceSize = 5120000
> > > > ozoneDB.classicStore.tableBufferSize = 12800
> > > > ozoneDB.classicStore.tableCacheSize = 4096
> > > > ozoneDB.dbID = 0
> > > > ozoneDB.fileLog = INFO, WARN, ERROR
> > > > ozoneDB.port = 3333
> > > > ozoneDB.stdoutLog = INFO, WARN, ERROR
> > > > ozoneDB.store = org.ozoneDB.core.wizardStore.WizardStore
> > > > ozoneDB.wizardStore.clusterSize = 65536
> > > > ozoneDB.wizardStore.clusterSizeRatio = 256
> > > > ozoneDB.wizardStore.compressClusters = true
> > > > ozoneDB.wizardStore.tableBufferSize = 15
> > > > ozoneDB.wizardStore.tableCacheSize = 12
> > > > ozoneDB.wizardStore.tableSubtableSize = 11
> > > > Unable to initialize server.
> > > > java.io.FileNotFoundException: data/log (Permission denied)
> > > > at java.io.FileOutputStream.open(Native Method)
> > > > at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
> > > > at java.io.FileOutputStream.<init>(Compiled Code)
> > > > at org.ozoneDB.core.Env.initLogs(Compiled Code)
> > > > at org.ozoneDB.core.Env.<init>(Env.java:174)
> > > > at org.ozoneDB.core.Server.main(Compiled Code)
> > > >
> > > > There is very clearly NO permission problem, contrarily to what the exception says, as I
> > > > always run as the same user, and the first time the server runs fine... but maybe I am
> > > > doing something wrong somewhere else ?
> > >
> > > Does data/log exists? Which access rights does it have? And what content?
> >
> > Yes, data/log exists. I did chmod 777 as root, and chown jan. ozone runs as user jan, both
> > times. data/log has one or two small files as contents, sorry I cannot show them now. If you
> > want, I can send them tomorrow.
>
> The data directory does not contain a ozone generated log file. If data is your
> ozone directory then there is data/log but it is a file and no directory.
> So....??????
>
Will send you the contents tomorrow.
>
> Falko
>
> >
> > >
> > >
> > > Falko
> > >
> > > >
> > > > Falko Braeutigam wrote:
> > > >
> > > > > On Mon, 26 Mar 2001, Jan van Oort wrote:
> > > > > > Falko Braeutigam wrote:
> > > > > >
> > > > > > > On Mon, 26 Mar 2001, Jan van Oort wrote:
> > > > > > > > I have noticed that datafile corruption may occur when an ozone Server
> > > > > > > > instance is aborted brutally (for example, by doing control-C, or by
> > > > > > > > doing kill -STOP <ozone_process_number> on Unix).
> > > > > > >
> > > > > > > A server abort (regardless of its level of brutality) should not cause any
> > > > > > > datafile corruption. The small timeframe between begin and end of commit of
> > > > > > > update transactions (excluding prepare-commit) is to only real dangorous spot.
> > > > > > > What did you do to corrupt files? Can you recreate this?
> > > > > > >
> > > > > >
> > > > > > Yes, I can recreate this. With ozone-0.6.1 On Solaris for x86/Intel:
> > > > > > - build with ant
> > > > > > - run ozoneInst -d/test/data (test is a mountpoint for a newly created filesystem
> > > > > > on a very recently formatted, brand-new Fujitsu disk); everything goes fine
> > > > > > - run ozone with the "&" sign at the end of the bash command line (as I want to
> > > > > > re-use that terminal for occasional things like sar or vmstat to see system
> > > > > > health) on this newly created database
> > > > > > - run the AdminClient in order to create a user, and exit cleanly from AdminClient
> > > > > >
> > > > > > - with ps -ef get the ozone process number (e.g. 10014)
> > > > > > - then "kill -STOP 10014"
> > > > > > - then re-start ozone; I get a message (forgot the exact trace, it happened last
> > > > > > nigth, I can send you the exact trace tomorrow morning) something like 'data file
> > > > > > not found' or 'bad data file', and ozone exits.
> > > > >
> > > > > -STOP does not actually kill the process and so the port is not released which
> > > > > will cause the next ozone server that starts to throw an "unable to bind"
> > > > > exception. However, -SIGSEGV is for sure the most brutal abort. But it causes
> > > > > no problems on my linux based ozone server.
> > > > >
> > > > > Falko
> > > > >
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > >
> > > > > > > > Is it possible to implement Runtime.addShutdownHook( Thread _hook) ?
> > > > > > > > This method is available in the JDK1.3 only. It enables the JVM to exit
> > > > > > > > cleanly in case of such "unclean" process abortion.
> > > > > > >
> > > > > > > Not all users have a 1.3 JVM. Some time ago some users tried to come up with a
> > > > > > > JVM independent solution. Unfortunately they did not get too far.
> > > > > > >
> > > > > >
> > > > > > We tried the same thing for our piece of software under JDK 1.2.x; we never got
> > > > > > something like a ShutdownHook working before JDK 1.3
> > > > > >
> > > > > > Anyway, I'll create a shutdown hook, test it thoroughly, then send it to you. You
> > > > > > see what you do with it. I will use it anyway, as my installer also installs the
> > > > > > JVM.
> > > > > >
> > > > > > >
> > > > > > > Falko
> > > > > > >
> > > > > > > >
> > > > > > > > I will fist try it on my own machine (Solaris 8 on Intel), will then
> > > > > > > > report back.
> > > > > > > >
> > > > > > > > --
> > > > > > > > Jan van Oort
> > > > > > > >
> > > > > > > >
> > > > > > > > Database Fire Fighter
> > > > > > > --
> > > > > > > ______________________________________________________________________
> > > > > > > Falko Braeutigam mailto:falko@smb-tec.com
> > > > > > > SMB GmbH http://www.smb-tec.com
> > > > > >
> > > > > > --
> > > > > > Jan van Oort
> > > > > >
> > > > > >
> > > > > > Database Fire Fighter
> > > > > --
> > > > > ______________________________________________________________________
> > > > > Falko Braeutigam mailto:falko@smb-tec.com
> > > > > SMB GmbH http://www.smb-tec.com
> > > >
> > > > --
> > > > Jan van Oort
> > > >
> > > >
> > > > Database Fire Fighter
> > > --
> > > ______________________________________________________________________
> > > Falko Braeutigam mailto:falko@smb-tec.com
> > > SMB GmbH http://www.smb-tec.com
> >
> > --
> > Jan van Oort
> >
> >
> > Database Fire Fighter
> --
> ______________________________________________________________________
> Falko Braeutigam mailto:falko@smb-tec.com
> SMB GmbH http://www.smb-tec.com
--
Jan van Oort
Database Fire Fighter