Bugs item #2903111, was opened at 2009-11-24 14:29 Message generated for change (Comment added) made by stmane You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2903111&group_id=56967
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Core Group: MonetDB Common CVS Head >Status: Closed >Resolution: Fixed Priority: 5 Private: No Submitted By: Stefan de Konink (skinkie) >Assigned to: Stefan Manegold (stmane) Summary: Wrong error / no check for new database dir Initial Comment: Reproduce with: create (as root) a dbfarm directory switch to the normal user start monet with this dbfarm directory and (thus) a new database The error that arrises is: !FATAL: GDKlockHome: could not move to /home/skinkie/monetdb/monitor/ It seems MonetDB did not check if the directory could not be created. ---------------------------------------------------------------------- >Comment By: Stefan Manegold (stmane) Date: 2009-11-27 08:52 Message: =================================================================== 2009/11/27 - stmane: MonetDB/src/gdk/gdk_utils.mx,1.255.2.6 fixing ID: 2903111 "Wrong error / no check for new database dir" https://sourceforge.net/tracker/?func=detail&aid=2903111&group_id=56967&atid=482468 give more detailed error message, whether we fail to create /dbfarm/dbname, or whether we fail to move (cd) to it =================================================================== Closing w/o test, as this is merely an error message convenience, and making a portable test with platform-invariant output would be an overkill. ---------------------------------------------------------------------- Comment By: Fabian (mr-meltdown) Date: 2009-11-24 15:38 Message: The bug here is that the message is misleading. MonetDB normally creates the directory for the dbname (monitor), however that failed (it must be), but apparently MonetDB didn't complain about that. It only fails once it tries to set its lock. We should complain earlier when we can't create the dbname dir, if it doesn't exist already. ---------------------------------------------------------------------- Comment By: Stefan Manegold (stmane) Date: 2009-11-24 15:36 Message: MonetDB does (try to) "move" (`cd`) to the dbfarm/dbname. If this fails for whatever reason (e.g., because the user isn't allowed to do so by filesystem access rights), this fails and MonetDB returns an error. Perfectly reasonable with me ... ---------------------------------------------------------------------- Comment By: Stefan de Konink (skinkie) Date: 2009-11-24 14:32 Message: Fabian hinted also to write this is a permission error. Hence the dbfarm dir was owned by root, and not by the user that tried to start the database. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=482468&aid=2903111&group_id=56967 ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Monetdb-bugs mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/monetdb-bugs
