Re: [fossil-users] sqlite errors after reinstalling fossil
On Fri, Jan 18, 2013 at 9:56 PM, Joseph Mingrone j...@ftfl.ca wrote: What's the equivalent of a virtual beer/coffee/tea/etc? How about a HOWTO doc to save the next guy some pain ;). -- - stephan beal http://wanderinghorse.net/home/stephan/ http://gplus.to/sgbeal ___ 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] sqlite errors after reinstalling fossil
On Sat, Jan 19, 2013 at 6:52 AM, Stephan Beal sgb...@googlemail.com wrote: On Fri, Jan 18, 2013 at 9:56 PM, Joseph Mingrone j...@ftfl.ca wrote: What's the equivalent of a virtual beer/coffee/tea/etc? How about a HOWTO doc to save the next guy some pain ;). I think it would be pretty short: If you are using fossil with nfs mounts, make sure to have the rpcbind/rpclockd/rpcstatd running. :-) ___ 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] sqlite errors after reinstalling fossil
Richard, Martin, Matt and Baptiste;
On Thu, Jan 17, 2013 at 5:58 PM, Martin S. Weber martin.we...@nist.gov wrote:
Wild guess: are you running your rpc services, lockd and statd amongst them?
(server? client?)
On Thu, Jan 17, 2013 at 7:23 PM, Baptiste Daroussin
baptiste.darous...@gmail.com wrote:
Your failure is the following: fcntl(4,F_SETLK,0x7fffcca0)
ERR#45 'Operation not supported'
Something is wrong about your nfs setup imho
Martin, your wild guess, and Baptiste your astute investigation both
seem to be correct. When I started rpc.lockd and rpc.statd on both
the client and server all is well. Here is exactly what I did on both
the client and server.
-- client --
# echo 'rpc_lockd_enable=YES' /etc/rc.conf
# echo 'rpc_statd_enable=YES' /etc/rc.conf
# /etc/rc.d/lockd start
# /etc/rc.d/statd start
# ps -ax | grep rpc | awk '{print $5}'
/usr/sbin/rpc.statd
/usr/sbin/rpc.lockd
/usr/sbin/rpcbind
Thank you all. ..much appreciated. What's the equivalent of a
virtual beer/coffee/tea/etc?
Joseph
___
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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 4:13 PM, Joseph Mingrone j...@ftfl.ca wrote: Hello all; I'm seeing errors like this. % fossil init blah fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk I/O error fossil: SQLITE_IOERR: disk I/O error fossil: disk I/O error I just upgraded to FreeBSD 9.1 and removed all ports. When I reinstalled fossil via the FreeBSD port I had these problems. Thanks for any suggestions, Have you tried compiling Fossil yourself from sources? (It isn't hard.) -- D. Richard Hipp d...@sqlite.org ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 5:25 PM, Richard Hipp d...@sqlite.org wrote: Have you tried compiling Fossil yourself from sources? (It isn't hard.) Yes. Same result. Joseph ___ 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] sqlite errors after reinstalling fossil
I should also mention that everything seems to work fine when I run fossil as root, but not with sudo. It doesn't appear to be anything specific to my environment because the same problem occurs with other users on the box. Joseph ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 4:35 PM, Joseph Mingrone j...@ftfl.ca wrote: I should also mention that everything seems to work fine when I run fossil as root, but not with sudo. It doesn't appear to be anything specific to my environment because the same problem occurs with other users on the box. And, you say, it was working fine on the previous version of FreeBSD? What version did you upgrade from? -- D. Richard Hipp d...@sqlite.org ___ 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] sqlite errors after reinstalling fossil
One change I made when I upgraded the box was that I set home directories to be nfs mounted from a storage server. I'm using the automount daemon to do the mounting. Before home directories were local. To test if this was causing a problem I created a new user with a local home directory. This new user can run fossil without problems. The root user also has a local home directory. Joseph ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 5:46 PM, Richard Hipp d...@sqlite.org wrote: And, you say, it was working fine on the previous version of FreeBSD? What version did you upgrade from? It was working fine on the previous version, which was 8.3. It's also working fine on other machines running 9.1-RELEASE, but with local home directories. ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 4:46 PM, Joseph Mingrone j...@ftfl.ca wrote: One change I made when I upgraded the box was that I set home directories to be nfs mounted from a storage server. I'm using the automount daemon to do the mounting. Before home directories were local. To test if this was causing a problem I created a new user with a local home directory. This new user can run fossil without problems. The root user also has a local home directory. That's a good clue. It makes me think this is probably an NFS problem, perhaps related to posix advisory locking and your NFS implementations' inability to support it. Try setting: export FOSSIL_VFS=unix-dotfile or export FOSSIL_VFS=unix-none Then run Fossil (as a normal) user and see if that fixes the problem. Please let me know what happens -- D. Richard Hipp d...@sqlite.org ___ 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] sqlite errors after reinstalling fossil
On 01/17/13 16:46, Joseph Mingrone wrote: One change I made when I upgraded the box was that I set home directories to be nfs mounted from a storage server. I'm using the automount daemon to do the mounting. Before home directories were local. To test if this was causing a problem I created a new user with a local home directory. This new user can run fossil without problems. The root user also has a local home directory. Wild guess: are you running your rpc services, lockd and statd amongst them? (server? client?) I'd expect sqlite to trip over not being able to (f)lock a file... -Martin ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 5:52 PM, Richard Hipp d...@sqlite.org wrote: That's a good clue. It makes me think this is probably an NFS problem, perhaps related to posix advisory locking and your NFS implementations' inability to support it. Try setting: export FOSSIL_VFS=unix-dotfile or export FOSSIL_VFS=unix-none Setting FOSSIL_VFS didn't help. The storage server is running zfs. When I created the filesystem for the home directories I turned off access times. Here is the full command I used to create the file system: zfs create -o atime=off -o compression=on -o -o sharenfs=maproot=root,network 192.168.0.0,mask 255.255.255.0 tank/home. I just created a new zfs filesystem on the server but I didn't turn off the access times. I then created a new user whose home directory was set to this new file system. This user can run fossil without any problems. I put access times a back on for tank/home (the filesystem all other users except root have as their home directory), but those users still have the fossil errors. On Thu, Jan 17, 2013 at 5:58 PM, Martin S. Weber martin.we...@nist.gov wrote: Wild guess: are you running your rpc services, lockd and statd amongst them? (server? client?) Both the client are server are running rpcbind and mountd. Joseph ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 4:13 PM, Joseph Mingrone j...@ftfl.ca wrote: Hello all; I'm seeing errors like this. % fossil init blah fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk I/O error fossil: SQLITE_IOERR: disk I/O error fossil: disk I/O error What does the following command show? fossil init blah --sqltrace -- D. Richard Hipp d...@sqlite.org ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 5:11 PM, Joseph Mingrone j...@ftfl.ca wrote: On Thu, Jan 17, 2013 at 5:52 PM, Richard Hipp d...@sqlite.org wrote: That's a good clue. It makes me think this is probably an NFS problem, perhaps related to posix advisory locking and your NFS implementations' inability to support it. Try setting: export FOSSIL_VFS=unix-dotfile or export FOSSIL_VFS=unix-none Setting FOSSIL_VFS didn't help. Please try again using the patch to Fossil I just now checked in: http://www.fossil-scm.org/fossil/info/7536c6aea5 The storage server is running zfs. When I created the filesystem for the home directories I turned off access times. Here is the full command I used to create the file system: zfs create -o atime=off -o compression=on -o -o sharenfs=maproot=root,network 192.168.0.0,mask 255.255.255.0 tank/home. I just created a new zfs filesystem on the server but I didn't turn off the access times. I then created a new user whose home directory was set to this new file system. This user can run fossil without any problems. I put access times a back on for tank/home (the filesystem all other users except root have as their home directory), but those users still have the fossil errors. On Thu, Jan 17, 2013 at 5:58 PM, Martin S. Weber martin.we...@nist.gov wrote: Wild guess: are you running your rpc services, lockd and statd amongst them? (server? client?) Both the client are server are running rpcbind and mountd. Joseph ___ 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...@sqlite.org ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 6:18 PM, Richard Hipp d...@sqlite.org wrote: fossil init blah --sqltrace % fossil init blah --sqltrace fossil: SQLITE_IOERR: statement aborts at 1: [BEGIN EXCLUSIVE] disk I/O error fossil: SQLITE_IOERR: disk I/O error fossil: disk I/O error If you have recently updated your fossil executable, you might need to run fossil all rebuild to bring the repository schemas up to date. ___ 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] sqlite errors after reinstalling fossil
The test user I created, whose home directory is set to the new filesystem with access times turned on, is also having the sqlite problems now. ___ 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] sqlite errors after reinstalling fossil
This problem doesn't look much like an issue with fossil itself. Perhaps trying a filesystem test suite would give you some hints as to the root cause? Google provided this link that might be a good starting point: http://nfsv4.bullopensource.org/doc/testing_tools.php Do things such as a kernel compile, video editing or other disk intensive tasks work fine? On Thu, Jan 17, 2013 at 3:32 PM, Joseph Mingrone j...@ftfl.ca wrote: The test user I created, whose home directory is set to the new filesystem with access times turned on, is also having the sqlite problems now. ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 6:24 PM, Richard Hipp d...@sqlite.org wrote: Please try again using the patch to Fossil I just now checked in: http://www.fossil-scm.org/fossil/info/7536c6aea5 It didn't compile for me. ... cc -g -O2 -DHAVE_AUTOCONFIG_H -I. -I./src -Ibld -o bld/db.o -c bld/db_.c ./src/db.c: In function 'db_open_config': ./src/db.c:819: error: 'Global' has no member named 'zConfigDbType' ./src/db.c:823: error: 'Global' has no member named 'zConfigDbType' ./src/db.c: In function 'db_close': ./src/db.c:1193: error: 'Global' has no member named 'zConfigDbType' ./src/db.c: In function 'db_swap_connections': ./src/db.c:1669: error: 'Global' has no member named 'zConfigDbType' ./src/db.c:1671: error: 'Global' has no member named 'zConfigDbType' gmake: *** [bld/db.o] Error 1 ___ 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] sqlite errors after reinstalling fossil
2013/1/18 Joseph Mingrone j...@ftfl.ca: On Thu, Jan 17, 2013 at 6:24 PM, Richard Hipp d...@sqlite.org wrote: Please try again using the patch to Fossil I just now checked in: http://www.fossil-scm.org/fossil/info/7536c6aea5 It didn't compile for me. ... cc -g -O2 -DHAVE_AUTOCONFIG_H -I. -I./src -Ibld -o bld/db.o -c bld/db_.c ./src/db.c: In function 'db_open_config': ./src/db.c:819: error: 'Global' has no member named 'zConfigDbType' ./src/db.c:823: error: 'Global' has no member named 'zConfigDbType' ./src/db.c: In function 'db_close': ./src/db.c:1193: error: 'Global' has no member named 'zConfigDbType' ./src/db.c: In function 'db_swap_connections': ./src/db.c:1669: error: 'Global' has no member named 'zConfigDbType' ./src/db.c:1671: error: 'Global' has no member named 'zConfigDbType' gmake: *** [bld/db.o] Error 1 ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Can you host somewhere the file.out created by truss -o file.out fossil init bla ? regards, Bapt (maintainer of fossil for FreeBSD) ___ 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] sqlite errors after reinstalling fossil
Hello Baptiste; On Thu, Jan 17, 2013 at 7:02 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: Can you host somewhere the file.out created by truss -o file.out fossil init bla ? Sure. http://gly.ath.cx/misc/file.out Joseph ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 7:03 PM, Richard Hipp d...@sqlite.org wrote: I don't know why not... Did you start from fresh sources? What did you do to get the error below? Apparently I didn't start from fresh sources or I messed something else up. After... tar -xf tar -xvf fossil-src-20121022124804.tar.gz cd fossil-src-20121022124804/src/ fetch 'http://www.fossil-scm.org/fossil/raw/src/db.c?name=1b058e27e61edc91b7a5ce404ac5add09328b16d' cd .. ./configure gmake It compiles fine. But, in the same directory I just did: fossil init blah and I get the same error. Joseph ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 7:21 PM, Joseph Mingrone j...@ftfl.ca wrote: fossil init blah Make that ./fossil init blah and I get the same error. ___ 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] sqlite errors after reinstalling fossil
2013/1/18 Joseph Mingrone j...@ftfl.ca: On Thu, Jan 17, 2013 at 7:03 PM, Richard Hipp d...@sqlite.org wrote: I don't know why not... Did you start from fresh sources? What did you do to get the error below? Apparently I didn't start from fresh sources or I messed something else up. After... tar -xf tar -xvf fossil-src-20121022124804.tar.gz cd fossil-src-20121022124804/src/ fetch 'http://www.fossil-scm.org/fossil/raw/src/db.c?name=1b058e27e61edc91b7a5ce404ac5add09328b16d' cd .. ./configure gmake It compiles fine. But, in the same directory I just did: fossil init blah and I get the same error. Joseph ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Your failure is the following: fcntl(4,F_SETLK,0x7fffcca0) ERR#45 'Operation not supported' Something is wrong about your nfs setup imho regards, Bapt ___ 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] sqlite errors after reinstalling fossil
On Thu, Jan 17, 2013 at 6:23 PM, Baptiste Daroussin baptiste.darous...@gmail.com wrote: 2013/1/18 Joseph Mingrone j...@ftfl.ca: On Thu, Jan 17, 2013 at 7:03 PM, Richard Hipp d...@sqlite.org wrote: I don't know why not... Did you start from fresh sources? What did you do to get the error below? Apparently I didn't start from fresh sources or I messed something else up. After... tar -xf tar -xvf fossil-src-20121022124804.tar.gz cd fossil-src-20121022124804/src/ fetch ' http://www.fossil-scm.org/fossil/raw/src/db.c?name=1b058e27e61edc91b7a5ce404ac5add09328b16d ' cd .. ./configure gmake It compiles fine. But, in the same directory I just did: fossil init blah and I get the same error. Joseph ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users Your failure is the following: fcntl(4,F_SETLK,0x7fffcca0) ERR#45 'Operation not supported' Something is wrong about your nfs setup imho The FOSSIL_VFS=unix-none environment variable setting to Fossil should prevent Fossil from using posix advisory locking. That should work around the NFS problem shown above. I do not know why that part isn't working. regards, Bapt ___ 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...@sqlite.org ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
