[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 29, 7:40 am, Michael Brickenstein [EMAIL PROTECTED] wrote: Hello! The same problem appears here. I suppose, it could be a problem with the NFS home directories. Best regards, Michael (the real Michael) Ok, any chance you could strace a failing sage session? Please also tell us if you are using NFS or some other network filesystem for your home directory. If so does moving the install to /tmp or some other local filesystem fix the issue? Cheers, Michael [the non-real one :)] --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Hi!
The program is located on a local disc, it is just my home on a NFS
file system.
I tried linking .sage to /tmp/blupper (I hope, that is not a
trademark)
and everything worked.
Then I removed the link and tried again with my normal nfs home and
produced the following strace.
Best regards,
Michael
strace sage
execve(/usr/local/bin/sage, [sage], [/* 28 vars */]) = 0
brk(0) = 0x5be000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba41fcd2000
uname({sys=Linux, node=biberach, ...}) = 0
access(/etc/ld.so.preload, R_OK) = -1 ENOENT (No such file or
directory)
open(/etc/ld.so.cache, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=53492, ...}) = 0
mmap(NULL, 53492, PROT_READ, MAP_PRIVATE, 3, 0) = 0x2ba41fcd3000
close(3)= 0
open(/lib/libncurses.so.5, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0
\0\1\0\0\0\200\1\2\0\0\0\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=370728, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba41fce1000
mmap(NULL, 1420648, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x2ba41fce2000
mprotect(0x2ba41fd2f000, 1044480, PROT_NONE) = 0
mmap(0x2ba41fe2e000, 61440, PROT_READ|PROT_WRITE, MAP_PRIVATE|
MAP_FIXED|MAP_DENYWRITE, 3, 0x4c000) = 0x2ba41fe2e000
close(3)= 0
open(/lib/libdl.so.2, O_RDONLY) = 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0\0\1\0\0\0`
\16\0\0\0\0\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=14528, ...}) = 0
mmap(NULL, 2109728, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x2ba41fed3000
mprotect(0x2ba41fed5000, 2097152, PROT_NONE) = 0
mmap(0x2ba4200d5000, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_FIXED|
MAP_DENYWRITE, 3, 0x2000) = 0x2ba4200d5000
close(3)= 0
open(/lib/libc.so.6, O_RDONLY)= 3
read(3, \177ELF\2\1\1\0\0\0\0\0\0\0\0\0\3\0
\0\1\0\0\0\220\334\1\0\0\0\0\0..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1293456, ...}) = 0
mmap(NULL, 3399928, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3,
0) = 0x2ba4200d7000
mprotect(0x2ba42020d000, 2093056, PROT_NONE) = 0
mmap(0x2ba42040c000, 20480, PROT_READ|PROT_WRITE, MAP_PRIVATE|
MAP_FIXED|MAP_DENYWRITE, 3, 0x135000) = 0x2ba42040c000
mmap(0x2ba420411000, 16632, PROT_READ|PROT_WRITE, MAP_PRIVATE|
MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x2ba420411000
close(3)= 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba420416000
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba420417000
arch_prctl(ARCH_SET_FS, 0x2ba420416dd0) = 0
mprotect(0x2ba42040c000, 16384, PROT_READ) = 0
mprotect(0x2ba4200d5000, 4096, PROT_READ) = 0
mprotect(0x2ba41fed1000, 4096, PROT_READ) = 0
munmap(0x2ba41fcd3000, 53492) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open(/dev/tty, O_RDWR|O_NONBLOCK) = 3
close(3)= 0
brk(0) = 0x5be000
brk(0x5df000) = 0x5df000
getuid()= 1136
getgid()= 1103
geteuid() = 1136
getegid() = 1103
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
gettimeofday({1196340233, 97680}, NULL) = 0
open(/proc/meminfo, O_RDONLY) = 3
fstat(3, {st_mode=S_IFREG|0444, st_size=0, ...}) = 0
mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1,
0) = 0x2ba41fcd3000
read(3, MemTotal: 16411324 kB\nMemFre..., 1024) = 630
close(3)= 0
munmap(0x2ba41fcd3000, 4096)= 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGCHLD, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGINT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigaction(SIGQUIT, {SIG_DFL}, {SIG_DFL}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
rt_sigaction(SIGQUIT, {SIG_IGN}, {SIG_DFL}, 8) = 0
uname({sys=Linux, node=biberach, ...}) = 0
stat(/home/michael, {st_mode=S_IFDIR|0700, st_size=9216, ...}) = 0
stat(., {st_mode=S_IFDIR|0700, st_size=9216, ...}) = 0
getpid()= 21204
getppid() = 21203
getpgrp() = 21203
rt_sigaction(SIGCHLD, {0x434dd0, [], SA_RESTORER, 0x2ba420107430},
{SIG_DFL}, 8) = 0
rt_sigprocmask(SIG_BLOCK, NULL, [], 8) = 0
open(/usr/local/bin/sage, O_RDONLY) = 3
ioctl(3, SNDCTL_TMR_TIMEBASE or TCGETS, 0x7fff8adeff80) = -1 ENOTTY
(Inappropriate ioctl for device)
lseek(3, 0, SEEK_CUR) = 0
read(3, #!/bin/sh\n\n# Set SAGE_ROOT to th..., 80) = 80
lseek(3, 0, SEEK_SET) = 0
getrlimit(RLIMIT_NOFILE, {rlim_cur=1024, rlim_max=1024}) = 0
dup2(3, 255)= 255
close(3)
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 29, 1:51 pm, Michael Brickenstein [EMAIL PROTECTED] wrote: Hi! Hi Michael, The program is located on a local disc, it is just my home on a NFS file system. I tried linking .sage to /tmp/blupper (I hope, that is not a trademark) and everything worked. Then I removed the link and tried again with my normal nfs home and produced the following strace. interesting about NFS, the strace output doesn't help much since you only captured the inital sage process. :( Could you run strace with -ff -o sage-something, so that you strace all children and write each process to a logfile? You might have to play a little with the parameters (add -F), but I am fairly certain that I can reproduce this behavior locally if NFS is the culprit. Best regards, Michael Cheers, Michael SNIP --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Michael, there is an issue with sqlite on NFS, specifically from http://www.sqlite.org/faq.html: SQLite uses reader/writer locks to control access to the database. (Under Win95/98/ME which lacks support for reader/writer locks, a probabilistic simulation is used instead.) But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. *This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time.* On Windows, Microsoft's documentation says that locking may not work under FAT filesystems if you are not running the Share.exe daemon. People who have a lot of experience with Windows tell me that file locking of network files is very buggy and is not dependable. If what they say is true, sharing an SQLite database between two or more Windows machines might cause unexpected problems. So: fix you installation ;) Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 30, 12:05 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: Michael, there is an issue with sqlite on NFS, specifically fromhttp://www.sqlite.org/faq.html: SQLite uses reader/writer locks to control access to the database. (Under Win95/98/ME which lacks support for reader/writer locks, a probabilistic simulation is used instead.) But use caution: this locking mechanism might not work correctly if the database file is kept on an NFS filesystem. *This is because fcntl() file locking is broken on many NFS implementations. You should avoid putting SQLite database files on NFS if multiple processes might try to access the file at the same time.* On Windows, Microsoft's documentation says that locking may not work under FAT filesystems if you are not running the Share.exe daemon. People who have a lot of experience with Windows tell me that file locking of network files is very buggy and is not dependable. If what they say is true, sharing an SQLite database between two or more Windows machines might cause unexpected problems. So: fix you installation ;) Actually, some more info: from http://www.sqlite.org/cvstrac/tktview?tn=1556,31 [begin quote] 2005-Dec-07 14:27:26 by drh: This is a bug in either Gentoo linux or in your setup. SQLite is using the fcntl(F_SETLK) interface and linux is telling SQLite that the file is already locked. Not much SQLite can do about this. In version 3.3.0 (or perhaps in a release soon to follow that) we will be offering a version of SQLite that uses lockfiles rather than fcntl() to control file access. There are disadvantages to the use of filelocks: slower, courser grain access, and stale lockfiles that must be manually deleted following a program crash. But lockfiles will work on network filesystems. 2005-Dec-07 16:20:21 by anonymous: I submitted this ticket: It is not a bug in gentoo. Same behaviour on boxes running different versions of SuSE (static build of my binary, executed on different hosts within the same NFS share). 2005-Dec-08 10:56:01 by anonymous: After realizing that it doesn't mean much if I tranfer a static build from gentoo to SuSE, I rebuild my project from scratch on a SuSE box (sqlite-3.2.7). Again, the results are the same: database locked. Since the NFS is up for about three years, it is hard to assume that there's a config error left?! Any hints are highly appreciated! Regards 2005-Dec-08 13:14:24 by anonymous: Please close this ticket. The solution: I hadn't had nfs-utils installed. After merging those and starting rpc.statd, everythings works as expected. Sorry for the fuss. [begin quote] So once we update sqlite to something more current we should actually build with lock files instead. I don't think it will have a performance impact on our use pattern and it will make things less likely for the user to screw up. Yi has already provided an updated spkg, but that cause segfaults in the sfa doctest. As it turns out by now I suspect that symmetrica is at fault in those cases, but I cannot prove that yet. So stay tuned and use the above work around for now. Cheers, Michael Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 28, 1:38 am, trio123 [EMAIL PROTECTED] wrote: Renaming $HOME/.sage did not help and I've upgraded to 2.8.14. I still get the same error message. Kelly Hello Kelly, sorry I couldn't be more help, but I am out of ideas then. Hopefully somebody else will have a clue what is wrong. You could try starting the notebook without SSL, i.e. notebook(secure=false) - see notebook? in a sage session. William: any ideas? Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 28, 12:18 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 28, 1:38 am, trio123 [EMAIL PROTECTED] wrote: Renaming $HOME/.sage did not help and I've upgraded to 2.8.14. I still get the same error message. Kelly Hello Kelly, sorry I couldn't be more help, but I am out of ideas then. Hopefully somebody else will have a clue what is wrong. You could try starting the notebook without SSL, i.e. notebook(secure=false) - see notebook? in a sage session. Sorry, try 3. I just want to run the server locally on my laptop at a coffee shop with no wifi and do not want to be bothered with SSL, accounts, etc., and I am *absolutely certain* I am the only user logged into my laptop so I do not have to worry about somebody else using the notebook on localhost and deleting my files. Use notebook(secure=False) William: any ideas? Cheers, Michael Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Hi! I have the same problem here on our compute server. Could it be a problem with file locking in NFS-home-directories? Best regards, Michael (the real Michael) On 28 Nov., 20:50, trio123 [EMAIL PROTECTED] wrote: Thanks Michael notebook(secure=False) works like a charm but it would be nice to get the secure notebook working properly. Thanks again. Kelly On Nov 28, 3:19 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 28, 12:18 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 28, 1:38 am, trio123 [EMAIL PROTECTED] wrote: Renaming $HOME/.sage did not help and I've upgraded to 2.8.14. I still get the same error message. Kelly Hello Kelly, sorry I couldn't be more help, but I am out of ideas then. Hopefully somebody else will have a clue what is wrong. You could try starting the notebook without SSL, i.e. notebook(secure=false) - see notebook? in a sage session. Sorry, try 3. I just want to run the server locally on my laptop at a coffee shop with no wifi and do not want to be bothered with SSL, accounts, etc., and I am *absolutely certain* I am the only user logged into my laptop so I do not have to worry about somebody else using the notebook on localhost and deleting my files. Use notebook(secure=False) William: any ideas? Cheers, Michael Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Hello! The same problem appears here. I suppose, it could be a problem with the NFS home directories. Best regards, Michael (the real Michael) On 28 Nov., 20:50, trio123 [EMAIL PROTECTED] wrote: Thanks Michael notebook(secure=False) works like a charm but it would be nice to get the secure notebook working properly. Thanks again. Kelly On Nov 28, 3:19 am, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 28, 12:18 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 28, 1:38 am, trio123 [EMAIL PROTECTED] wrote: Renaming $HOME/.sage did not help and I've upgraded to 2.8.14. I still get the same error message. Kelly Hello Kelly, sorry I couldn't be more help, but I am out of ideas then. Hopefully somebody else will have a clue what is wrong. You could try starting the notebook without SSL, i.e. notebook(secure=false) - see notebook? in a sage session. Sorry, try 3. I just want to run the server locally on my laptop at a coffee shop with no wifi and do not want to be bothered with SSL, accounts, etc., and I am *absolutely certain* I am the only user logged into my laptop so I do not have to worry about somebody else using the notebook on localhost and deleting my files. Use notebook(secure=False) William: any ideas? Cheers, Michael Cheers, Michael --~--~-~--~~~---~--~~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://sage.math.washington.edu/sage/ and http://sage.scipy.org/sage/ -~--~~~~--~~--~--~---
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
Renaming $HOME/.sage did not help and I've upgraded to 2.8.14. I still get the same error message. Kelly On Nov 23, 12:33 pm, mabshoff [EMAIL PROTECTED] dortmund.de wrote: On Nov 23, 8:58 pm, trio123 [EMAIL PROTECTED] wrote: Hi Hello, I'm running SAGE 2.8.12 on Ubuntu 6.06 built from source and I can't seem to get notebook() to run. Any ideas? Just a hunch: can you rename $HOME/.sage to something else and start Sage again? It seems odd that you are overwriting the dsage key. 2.8.13 is out by the way ;) Thanks in advance. Cheers, Michael Error message down below: control:~ sage -- | SAGE Version 2.8.12, Release Date: 2007-11-06 | | Type notebook() for the GUI, and license() for information.| -- sage: notebook() In order to use an SECURE encrypted notebook, you must first run notebook.setup(). Now running notebook.setup() Using dsage certificates. -- Generating public/private key pair for authentication... Your key will be stored in /home/chook/.sage/dsage/dsage_key Just hit enter when prompted for a passphrase -- /home/chook/.sage/dsage/dsage_key already exists. Overwrite (y/n)? n Client configuration finished. Worker configuration finished. Choose a domain name for your SAGE notebook server, for example, localhost (personal use) or control.uvic.ca (to allow outside connections). Domain name [localhost]: Using default localhost -- Generating SSL certificate for server... Using openssl to generate key openssl genrsa /home/chook/.sage/dsage/cacert.pem Generating RSA private key, 512 bit long modulus . e is 65537 (0x10001) Generating a self signed certificate... X.509 certificate info: Version: 3 Serial Number (hex): 52:CB:5D Subject: C=US,O=SAGE (at localhost),OU=389,ST=Washington,CN=localhost,UID=sage_user Validity: Not Before: Fri Nov 23 11:54:41 2007 Not After: Tue Apr 10 12:54:41 2035 Subject Public Key Info: Public Key Algorithm: RSA (512 bits) X.509 Extensions: Basic Constraints: (critical) CA:FALSE Key usage: (critical) Digital signature. Key encipherment. Key purpose OIDs: TLS WWW Server. Subject Key ID: 1C:87:E3:3D:FB:26:EF:15:67:6D:06:EE:1A:9D:79:EC:0A:9F: 34:BD Other information: Public Key ID: 1C:87:E3:3D:FB:26:EF:15:67:6D:06:EE:1A:9D:79:EC: 0A:9F:34:BD Signing certificate... -- --- class 'sqlite3.OperationalError'Traceback (most recent call last) /home/chook/ipython console in module() /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/notebook_object.py in __call__(self, *args, **kwds) 135 136 def __call__(self, *args, **kwds): -- 137 return self.notebook(*args, **kwds) 138 139 notebook = run_notebook.notebook_twisted /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/run_notebook.py in notebook_twisted(self, directory, port, address, port_tries, secure, reset, accounts, server_pool, ulimit, timeout, open_viewer, sagetex_path, start_path) 211 if open_viewer: 212 Open viewer automatically isn't fully implemented. You have to manually open your web browser to the above URL. -- 213 run(port) 214 215 return True /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/run_notebook.py in run(port) 119 print In order to use an SECURE encrypted notebook, you must first run notebook.setup(). 120 print Now running notebook.setup() -- 121 notebook_setup() 122 if not os.path.exists(private_pem) or not os.path.exists(public_pem): 123 print Failed to setup notebook. Please try notebook.setup() again manually. /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/run_notebook.py in notebook_setup(self) 37 dsage = os.path.join(DOT_SAGE, 'dsage') 38 import sage.dsage.all --- 39 sage.dsage.all.dsage.setup() 40 shutil.copyfile(dsage + '/cacert.pem', private_pem) 41 shutil.copyfile(dsage + '/pubcert.pem', public_pem) /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/dsage/ dsage.py in setup(self, template) 262 263 from
[sage-support] Re: class 'sqlite3.OperationalError': database is locked
On Nov 23, 8:58 pm, trio123 [EMAIL PROTECTED] wrote: Hi Hello, I'm running SAGE 2.8.12 on Ubuntu 6.06 built from source and I can't seem to get notebook() to run. Any ideas? Just a hunch: can you rename $HOME/.sage to something else and start Sage again? It seems odd that you are overwriting the dsage key. 2.8.13 is out by the way ;) Thanks in advance. Cheers, Michael Error message down below: control:~ sage -- | SAGE Version 2.8.12, Release Date: 2007-11-06 | | Type notebook() for the GUI, and license() for information.| -- sage: notebook() In order to use an SECURE encrypted notebook, you must first run notebook.setup(). Now running notebook.setup() Using dsage certificates. -- Generating public/private key pair for authentication... Your key will be stored in /home/chook/.sage/dsage/dsage_key Just hit enter when prompted for a passphrase -- /home/chook/.sage/dsage/dsage_key already exists. Overwrite (y/n)? n Client configuration finished. Worker configuration finished. Choose a domain name for your SAGE notebook server, for example, localhost (personal use) or control.uvic.ca (to allow outside connections). Domain name [localhost]: Using default localhost -- Generating SSL certificate for server... Using openssl to generate key openssl genrsa /home/chook/.sage/dsage/cacert.pem Generating RSA private key, 512 bit long modulus . e is 65537 (0x10001) Generating a self signed certificate... X.509 certificate info: Version: 3 Serial Number (hex): 52:CB:5D Subject: C=US,O=SAGE (at localhost),OU=389,ST=Washington,CN=localhost,UID=sage_user Validity: Not Before: Fri Nov 23 11:54:41 2007 Not After: Tue Apr 10 12:54:41 2035 Subject Public Key Info: Public Key Algorithm: RSA (512 bits) X.509 Extensions: Basic Constraints: (critical) CA:FALSE Key usage: (critical) Digital signature. Key encipherment. Key purpose OIDs: TLS WWW Server. Subject Key ID: 1C:87:E3:3D:FB:26:EF:15:67:6D:06:EE:1A:9D:79:EC:0A:9F: 34:BD Other information: Public Key ID: 1C:87:E3:3D:FB:26:EF:15:67:6D:06:EE:1A:9D:79:EC: 0A:9F:34:BD Signing certificate... -- --- class 'sqlite3.OperationalError'Traceback (most recent call last) /home/chook/ipython console in module() /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/notebook_object.py in __call__(self, *args, **kwds) 135 136 def __call__(self, *args, **kwds): -- 137 return self.notebook(*args, **kwds) 138 139 notebook = run_notebook.notebook_twisted /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/run_notebook.py in notebook_twisted(self, directory, port, address, port_tries, secure, reset, accounts, server_pool, ulimit, timeout, open_viewer, sagetex_path, start_path) 211 if open_viewer: 212 Open viewer automatically isn't fully implemented. You have to manually open your web browser to the above URL. -- 213 run(port) 214 215 return True /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/run_notebook.py in run(port) 119 print In order to use an SECURE encrypted notebook, you must first run notebook.setup(). 120 print Now running notebook.setup() -- 121 notebook_setup() 122 if not os.path.exists(private_pem) or not os.path.exists(public_pem): 123 print Failed to setup notebook. Please try notebook.setup() again manually. /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/server/ notebook/run_notebook.py in notebook_setup(self) 37 dsage = os.path.join(DOT_SAGE, 'dsage') 38 import sage.dsage.all --- 39 sage.dsage.all.dsage.setup() 40 shutil.copyfile(dsage + '/cacert.pem', private_pem) 41 shutil.copyfile(dsage + '/pubcert.pem', public_pem) /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/dsage/ dsage.py in setup(self, template) 262 263 from sage.dsage.scripts.dsage_setup import setup -- 264 setup(template=template) 265 266 def setup_server(self, *args): /usr/local/sage-2.8.12/local/lib/python2.5/site-packages/sage/dsage/ scripts/dsage_setup.py in setup(template) 191 setup_client() 192
