[fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread Zed A. Shaw 
Hey,

I upgraded to the latest fossil, with mine not being that old at all
(only a few months), and even after several rebuilds I get a ton of
bizarre errors:

-- logging into the server
unable to open database file
UPDATE user SET
cookie='1/02AAB0D7FFB698CD97B848BEC1159977A498AA58CDD03213E9',
ipaddr='127.0.0.1',   cexpire=julianday('now')+31557600/86400.0 WHERE
uid=1

-- fossil up
Error: Database error: unable to open database file
DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private)

-- fossil clone
Error: Database error: unable to open database file
DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private)


So what's going on?  Is it some kind of permissions problem?  The files
are owned by the user, and the web interface works right until it tries
to write like the above UPDATE and DELETE commands.  They're being run
out of inetd with:

4545 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http
/home/USER/fossils/source.fossil

Did fossil change this or something?

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread Zed A. Shaw 
On Wed, Mar 31, 2010 at 07:25:47AM -0700, Zed A. Shaw wrote:
 Hey,
 
 I upgraded to the latest fossil, with mine not being that old at all
 (only a few months), and even after several rebuilds I get a ton of
 bizarre errors:
... 
 4545 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http
 /home/USER/fossils/source.fossil
 
 Did fossil change this or something?

Yep, looks like running out of inetd is now read only.  If I run it with
fossil serve it's just fine.

Is there a reason this changed?  What was the change for?

Sending out a changelog to the mailing list when there's a new drop, and
using version numbers that aren't giant hashes with a date in them would
*really* help people keep up.

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread D. Richard Hipp 

On Mar 31, 2010, at 10:25 AM, Zed A. Shaw wrote:

 Hey,

 I upgraded to the latest fossil, with mine not being that old at all
 (only a few months), and even after several rebuilds I get a ton of
 bizarre errors:

 -- logging into the server
 unable to open database file
 UPDATE user SET
 cookie='1/02AAB0D7FFB698CD97B848BEC1159977A498AA58CDD03213E9',
 ipaddr='127.0.0.1',   cexpire=julianday('now')+31557600/86400.0 WHERE
 uid=1

 -- fossil up
 Error: Database error: unable to open database file
 DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private)

 -- fossil clone
 Error: Database error: unable to open database file
 DELETE FROM unclustered WHERE rid IN (SELECT rid FROM private)


 So what's going on?  Is it some kind of permissions problem?  The  
 files
 are owned by the user, and the web interface works right until it  
 tries
 to write like the above UPDATE and DELETE commands.  They're being run
 out of inetd with:

 4545 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http
 /home/USER/fossils/source.fossil

 Did fossil change this or something?

Nothing has changed in Fossil, that I know of, that would cause this.

Are you sure your permissions are right?  Do you have write permission  
on the directory that contains the source.fossil file?



 -- 
 Zed A. Shaw
 http://zedshaw.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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread D. Richard Hipp 

On Mar 31, 2010, at 10:33 AM, Zed A. Shaw wrote:

 On Wed, Mar 31, 2010 at 07:25:47AM -0700, Zed A. Shaw wrote:
 Hey,

 I upgraded to the latest fossil, with mine not being that old at all
 (only a few months), and even after several rebuilds I get a ton of
 bizarre errors:
 ...
 4545 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http
 /home/USER/fossils/source.fossil

 Did fossil change this or something?

 Yep, looks like running out of inetd is now read only.  If I run it  
 with
 fossil serve it's just fine.

 Is there a reason this changed?  What was the change for?

Perhaps this:  http://www.fossil-scm.org/fossil/info/7ba10f1a6a

But that change (really a bug fix) was in August 2009.  How old was  
your prior version of Fossil, did you say?



 Sending out a changelog to the mailing list when there's a new drop,  
 and
 using version numbers that aren't giant hashes with a date in them  
 would
 *really* help people keep up.

 -- 
 Zed A. Shaw
 http://zedshaw.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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread Zed A. Shaw 
On Wed, Mar 31, 2010 at 10:34:16AM -0400, D. Richard Hipp wrote:
 
  4545 stream tcp nowait.1000 root /usr/bin/fossil /usr/bin/fossil http
  /home/USER/fossils/source.fossil
 
  Did fossil change this or something?
 
 Nothing has changed in Fossil, that I know of, that would cause this.
 
 Are you sure your permissions are right?  Do you have write permission  
 on the directory that contains the source.fossil file?

The previous binary was only a couple months old.  In fact, if you go
look at the list archives I had problems back when you changed how logins
work and had to upgrade all my sites.

So, that means I've been running fine, through multiple upgrades since
that change you posted, including with the chroot jail working, and only
just today did it break.

These files are stored in the user's home directory, accessible by that
user, so a chroot to become that user should work.

All signs point to some recent change in the way inetd operation works
that would cause this to happen now.

-- 
Zed A. Shaw
http://zedshaw.com/
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread 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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread Heinrich Huss 
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 adminadminist 10977280 Mar 31 18:47 fossil.fossil*


I've got the following error message:
SQLITE_CANTOPEN: cannot open file at source line 26160

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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread 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 adminadminist 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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread Heinrich Huss 

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


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 adminadminist 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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread D. Richard Hipp 

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

SQLite is unable to create and open a new rollback journal.  Does your  
process have write permission on the directory?



 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 adminadminist 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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread 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 adminadminist 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

Re: [fossil-users] TONS of errors after upgrade, rebuild does not help

2010-03-31 Thread Heinrich Huss 
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 adminadminist 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