Hi Richard, thanks, That really helps!!
It's working again. Cheers Hein Am 31.03.2010 um 20:43 schrieb D. Richard Hipp: > > On Mar 31, 2010, at 1:56 PM, D. Richard Hipp wrote: > >> >> On Mar 31, 2010, at 1:42 PM, Heinrich Huss wrote: >> >>> I have recompiled. Now I do have the following fossil version: >>> >>> Fossil version [a158c4e75d] 2010-03-31 17:14:18 >>> >>> This is the error message I got: >>> >>> SQLITE_CANTOPEN: cannot open file [/share/HDA_DATA/Public/Hein/ >>> fossil.fossil-journal]: No such file or directory >>> >> I think I know the problem. Fossil now opens the database file >> *before* it enters the chroot jail. But SQLite remembers the >> original >> path to the database, not the chroot-ed path. >> >> I guess what I need to do is close the database before entering the >> chroot jail then reopen the database under the new name.... > > OK. This problem should be fixed now (as of > http://www.fossil-scm.org/fossil/info/42ba7b97aa) > . Please let me know if you have any other problems. > >> >> >>> SQLITE_CANTOPEN: statement aborts at 31: [UPDATE user SET >>> cookie='1/0F420A8378AC596FC324F1ED6E647662CF99B3BE8144E2DA70', >>> ipaddr='10.0.0.10', cexpire=julianday('now')+31557600/86400.0 WHERE >>> uid=1] unable to open database file >>> >>> Database Error >>> unable to open database file >>> UPDATE user SET >>> cookie='1/0F420A8378AC596FC324F1ED6E647662CF99B3BE8144E2DA70', >>> ipaddr='10.0.0.10', cexpire=julianday('now')+31557600/86400.0 >>> WHERE uid=1 >>> If you have recently updated your fossil executable, you might need >>> to run "fossil all rebuild" to bring the repository schemas up to >>> date. >>> >>> >>> >>> Thanks for your help. >>> >>> Hein >>> >>> >>> >>> >>> >>> Am 31.03.2010 um 19:15 schrieb D. Richard Hipp: >>> >>>> >>>> On Mar 31, 2010, at 1:04 PM, Heinrich Huss wrote: >>>> >>>>> It seems I'm running in the same problem. After recompile I'm not >>>>> able to login. >>>>> >>>>> It looks like the sqite cannot open the database with write >>>>> access. >>>>> Filepermissions are ok and I did a rebuild. >>>>> >>>>> -rwxrw-rw- 1 admin administ 10977280 Mar 31 18:47 >>>>> fossil.fossil* >>>>> >>>>> >>>>> I've got the following error message: >>>>> SQLITE_CANTOPEN: cannot open file at source line 26160 >>>>> >>>> Please recompile with http://www.fossil-scm.org/fossil/ci/ >>>> a158c4e75d >>>> and let me know what error message you get then. >>>> >>>> >>>> >>>>> SQLITE_CANTOPEN: statement aborts at 31: [UPDATE user SET >>>>> cookie='1/669CBDB7E9AB8F1565A3C3F19FB96E3900C5C9B8F18BE6031C', >>>>> ipaddr='10.0.0.10', cexpire=julianday('now')+31557600/86400.0 >>>>> WHERE >>>>> uid=1] unable to open database file >>>>> >>>>> Database Error >>>>> unable to open database file >>>>> UPDATE user SET >>>>> cookie='1/669CBDB7E9AB8F1565A3C3F19FB96E3900C5C9B8F18BE6031C', >>>>> ipaddr='10.0.0.10', cexpire=julianday('now')+31557600/86400.0 >>>>> WHERE uid=1 >>>>> If you have recently updated your fossil executable, you might >>>>> need >>>>> to run "fossil all rebuild" to bring the repository schemas up to >>>>> date. >>>>> >>>>> >>>>> >>>>> Any ideas? >>>>> >>>>> >>>>> >>>>> Thanks >>>>> >>>>> Hein >>>>> >>>>> >>>>> >>>>> Am 31.03.2010 um 16:56 schrieb D. Richard Hipp: >>>>> >>>>>> >>>>>> On Mar 31, 2010, at 10:45 AM, Zed A. Shaw wrote: >>>>>>> >>>>>>> All signs point to some recent change in the way inetd operation >>>>>>> works >>>>>>> that would cause this to happen now. >>>>>> >>>>>> >>>>>> I don't recall changing anything associated with the inetd >>>>>> logic. Of >>>>>> course, that might just mean that I forgot... >>>>>> >>>>>> What does the /test_env URL to your inetd server tell you? >>>>>> (example: http://www.fossil-scm.org/fossil/test_env) >>>>>> Any clues there? >>>>>> >>>>>> I just checked in a change - >>>>>> http://www.fossil-scm.org/fossil/ci/99fea6cde4 >>>>>> - that logs all SQLite errors to the reply HTML. If you can >>>>>> recompile to the latest, it might give us better clues about what >>>>>> is >>>>>> going wrong. >>>>>> >>>>>> D. Richard Hipp >>>>>> d...@hwaci.com >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> fossil-users mailing list >>>>>> fossil-users@lists.fossil-scm.org >>>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil- >>>>>> users >>>>> >>>>> _______________________________________________ >>>>> fossil-users mailing list >>>>> fossil-users@lists.fossil-scm.org >>>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >>>> >>>> D. Richard Hipp >>>> d...@hwaci.com >>>> >>>> >>>> >>>> _______________________________________________ >>>> fossil-users mailing list >>>> fossil-users@lists.fossil-scm.org >>>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil- >>>> users >>> >>> _______________________________________________ >>> fossil-users mailing list >>> fossil-users@lists.fossil-scm.org >>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil- >>> users >> >> D. Richard Hipp >> d...@hwaci.com >> >> >> >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil- >> users > > D. Richard Hipp > d...@hwaci.com > > > > _______________________________________________ > fossil-users mailing list > fossil-users@lists.fossil-scm.org > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
