SIGSEGV inside pylucene
Hello, I was tinkering with the search function of ReviewBoard for some time now. I got it to run, but it is quite unusable since almost every query results in a Review Board is taking a nap page being shown. After some time then (one minute I guess?) ReviewBoard answers with No requests matching your query: (No matter if there would be a result normally). I looked into the apache2-log and found a strange error: # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x7fab1f777874, pid=16468, tid=140373040924416 # # JRE version: 6.0_26-b03 # Java VM: Java HotSpot(TM) 64-Bit Server VM (20.1-b02 mixed mode linux-amd64 compressed oops) # Problematic frame: # C [libjcc.so+0x7874] JCCEnv::setClassPath(char const*)+0x24 # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp I found one user reporting the same, strange behavior within another function: http://groups.google.com/group/reviewboard/browse_thread/thread/86f8eb35dc9 15652/9380fca82aaaefa3 Is there any recent wisdom about what is wrong with my setup? I recently built a recent pylucene manually and swapped the open-jdk with sun's jdk without any result. Regards, Ruben ReviewBoard: 1.6.1 Pylucene: 3.4.0-1 (also tried 2.3.1-1.1u from aptitude) Python: 2.6.5 --- S Y S T E M --- OS:squeeze/sid uname:Linux 2.6.32-22-server #36-Ubuntu SMP Thu Jun 3 20:38:33 UTC 2010 x86_64 libc:glibc 2.11.1 NPTL 2.11.1 rlimit: STACK 8192k, CORE 0k, NPROC infinity, NOFILE 1024, AS infinity load average:0.51 0.66 0.53 CPU:total 1 (1 cores per cpu, 1 threads per core) family 6 model 23 stepping 8, cmov, cx8, fxsr, mmx, sse, sse2, sse3, ssse3, sse4.1 Memory: 4k page, physical 505492k(65320k free), swap 2095096k(1992788k free) vm_info: Java HotSpot(TM) 64-Bit Server VM (20.1-b02) for linux-amd64 JRE (1.6.0_26-b03), built on May 4 2011 01:13:47 by java_re with gcc 3.2.2 (SuSE Linux) -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Unable to upload screenshots
Thilo-Alexander Ginkel wrote: On Mon, Feb 14, 2011 at 23:01, Christian Hammond chip...@chipx86.com wrote: I don't believe they're stored temporarily anywhere. If so, it's internal to Django and I don't know it off-hand. The only thing I've ever seen permission-wise is when there's a directory within media/uploaded that doesn't have the proper write permissions for the server. Hm... Actually, after doing some more testing I think that permissions aren't an issue as GIF files can be uploaded properly. I also can't imaging why libpng should be loadable from the command line, but not from the Apache process... Arise zombie thread, live again! ;-) OK, so it turns out after years of happily running with RB we've hit this too. I KNOW this used to work (as my image testing when we first deployed was with PNG files). Our problem appears to be identical to this, regular RB install (i.e. easy_install based) which always seems to pull down PIL even though it is already installed (we're running Ubuntu server and I always ensure the debian PIL package is installed that has full image support). We could only attach new GIF screen shots to reviews. Using PIL in a Python terminal always worked (i.e. open the supposedly bad image via Image.open), but RB/Django would always fail with: -- Cut here -- Upload Screenshot One or more fields had errors Caption: Path: * Upload a valid image. The file you uploaded was either not an image or a corrupted image. -- Cut here -- On a hunch I thought I'd have a look at what PIL instances are on the file system (e.g. all the eggs that easy_install pulled down), after upgrading a few times over the years we had 2. reviews:~$ find / -name \*PIL\* 2/dev/null /usr/share/pyshared/PIL.pth /usr/share/pyshared/PIL /usr/share/pyshared/PIL/PIL-1.1.6.egg-info /usr/lib/python2.5/site-packages/PIL.pth /usr/lib/python2.5/site-packages/PIL-1.1.6-py2.5-linux-i686.egg /usr/lib/python2.5/site-packages/PIL-1.1.6-py2.5-linux-i686.egg/PIL /usr/lib/python2.5/site-packages/PIL /usr/lib/python2.5/site-packages/PIL/PIL-1.1.6.egg-info /usr/lib/python2.4/site-packages/PIL ... So I removed all the PIL eggs (remember I already have PIL installed): sudo rm -rf /usr/lib/python2.5/site-packages/PIL-1.1.6-py2.5-linux-i686.egg /usr/lib/python2.5/site-packages/PIL/PIL-1.1.6.egg-info Followed by a reviewboard restart: sudo /etc/init.d/apache2 restart And we can now attach PNGs and not just GIFs. So what out for easy_install and PIL. I know pip purports to support removal (and would probably be a better solution) so this is not a recommendation of resolution! I'm just sharing what I found on my system, don't go deleting files if you don't know the impact/dependencies! Chris -- Want to help the Review Board project? Donate today at http://www.reviewboard.org/donate/ Happy user? Let us know at http://www.reviewboard.org/users/ -~--~~~~--~~--~--~--- To unsubscribe from this group, send email to reviewboard+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/reviewboard?hl=en
Re: Issue 2050 in reviewboard: Filtering files to review
Comment #2 on issue 2050 by gotische...@yahoo.de: Filtering files to review http://code.google.com/p/reviewboard/issues/detail?id=2050 Seems like it is related to this issue: I am a default reviewer, in my settings I've specified a regular expression .*\.java to be default reviewer for java files. Now on my dashboard I see only requests with java files, but I get mails for all requests (even for those which do not have java files at all). Do I miss anything? Is here any special checkbox to make it synchronized (so I want to receive only letters for my requests which I see on my dashboard)? -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2346 in reviewboard: easy_install ReviewBoard fails on Pycrypto
Status: New Owner: Labels: Type-Defect Priority-Medium New issue 2346 by jimcurti...@gmail.com: easy_install ReviewBoard fails on Pycrypto http://code.google.com/p/reviewboard/issues/detail?id=2346 * NOTE: Do not post confidential information in this bug report. * * If you need immediate support, please contact* * reviewbo...@googlegroups.com * What version are you running? Installing latest version via instructions on Cento6 VM What's the URL of the page containing the problem? What steps will reproduce the problem? 1. Follow instructions 2. 3. What is the expected output? What do you see instead? Successful Installation. Instead I see: It fails trying to install PyCrypto with a fatal error about src/config.h: No such file or directory What operating system are you using? What browser? Centos 6 x86_64 Please provide any additional information below. It is related to a change to pycrypto in the latest version 2.4 -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Re: Issue 2346 in reviewboard: easy_install ReviewBoard fails on Pycrypto
Updates: Status: NeedInfo Comment #1 on issue 2346 by chip...@gmail.com: easy_install ReviewBoard fails on Pycrypto http://code.google.com/p/reviewboard/issues/detail?id=2346 Can you file a bug with them? We don't have any control over PyCrypto. -- You received this message because you are subscribed to the Google Groups reviewboard-issues group. To post to this group, send email to reviewboard-issues@googlegroups.com. To unsubscribe from this group, send email to reviewboard-issues+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/reviewboard-issues?hl=en.
Issue 2347 in reviewboard: InvalidCacheBackendError at /admin/ Backend URI must start with scheme://
Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 2347 by netzhu@gmail.com: InvalidCacheBackendError at /admin/
Backend URI must start with scheme://
http://code.google.com/p/reviewboard/issues/detail?id=2347
* NOTE: Do not post confidential information in this bug report. *
* If you need immediate support, please contact*
* reviewbo...@googlegroups.com *
What version are you running?
1.6.1
What's the URL of the page containing the problem?
http://*/admin
What steps will reproduce the problem?
1. at first, I install with memcached. Later, I disable it in the admin
dashboard by delete memcached://localhost:11211/ directly.
2. Then I cannot use the http://*/admin any more
3.
What is the expected output? What do you see instead?
I should see the admin settings.
What operating system are you using? What browser?
Amazon EC2, Amazon OS
Please provide any additional information below.
Environment:
Request Method: GET
Request URL: http://11.11.1.1:10001/admin/
Django Version: 1.3.1
Python Version: 2.6.7
Installed Applications:
['django.contrib.admin',
'django.contrib.auth',
'django.contrib.contenttypes',
'django.contrib.markup',
'django.contrib.sites',
'django.contrib.sessions',
'djblets.datagrid',
'djblets.feedview',
'djblets.gravatars',
'djblets.log',
'djblets.siteconfig',
'djblets.util',
'djblets.webapi',
'reviewboard.accounts',
'reviewboard.admin',
'reviewboard.attachments',
'reviewboard.changedescs',
'reviewboard.diffviewer',
'reviewboard.notifications',
'reviewboard.reports',
'reviewboard.reviews',
'reviewboard.scmtools',
'reviewboard.site',
'reviewboard.webapi',
'django_evolution']
Installed Middleware:
('django.middleware.gzip.GZipMiddleware',
'django.middleware.common.CommonMiddleware',
'django.middleware.doc.XViewMiddleware',
'django.middleware.http.ConditionalGetMiddleware',
'django.middleware.locale.LocaleMiddleware',
'django.contrib.sessions.middleware.SessionMiddleware',
'django.contrib.auth.middleware.AuthenticationMiddleware',
'djblets.siteconfig.middleware.SettingsMiddleware',
'reviewboard.admin.middleware.LoadSettingsMiddleware',
'djblets.log.middleware.LoggingMiddleware',
'reviewboard.admin.middleware.CheckUpdatesRequiredMiddleware',
'reviewboard.admin.middleware.X509AuthMiddleware',
'reviewboard.site.middleware.LocalSiteMiddleware')
Traceback:
File /usr/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/handlers/base.py
in
get_response
111. response = callback(request, *callback_args,
**callback_kwargs)
File /usr/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/contrib/admin/views/decorators.py
in
_checklogin
19. return view_func(request, *args, **kwargs)
File /usr/lib/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/admin/views.py
in
dashboard
33. 'has_cache_stats': get_has_cache_stats(),
File /usr/lib/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/admin/cache_stats.py
in
get_has_cache_stats
34. return get_memcached_hosts() != None
File /usr/lib/python2.6/site-packages/ReviewBoard-1.6.1-py2.6.egg/reviewboard/admin/cache_stats.py
in
get_memcached_hosts
22. scheme, host, params = parse_backend_uri(settings.CACHE_BACKEND)
File /usr/lib/python2.6/site-packages/Django-1.3.1-py2.6.egg/django/core/cache/__init__.py
in
parse_backend_uri
60. raise InvalidCacheBackendError(Backend URI must start with
scheme://)
Exception Type: InvalidCacheBackendError at /admin/
Exception Value: Backend URI must start with scheme://
--
You received this message because you are subscribed to the Google Groups
reviewboard-issues group.
To post to this group, send email to reviewboard-issues@googlegroups.com.
To unsubscribe from this group, send email to
reviewboard-issues+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/reviewboard-issues?hl=en.
