Sorry for the late response. I missed this reply.
For Apache settings the worker and prefork configurations are the exact
same between the two vms:
# prefork MPM
# StartServers: number of server processes to start
# MinSpareServers: minimum number of server processes which are kept spare
#
Hi Ze,
The spikes every 5 minutes are interesting. Sounds like a cronjob or
something, perhaps? Are you using search indexing?
What are you using for the database?
Remind me what version of RB you guys are using?
- Christian
--
Christian Hammond - chip...@chipx86.com
Review Board -
Hi Christian,
We're facing some pretty bad performance issues on our production system
after we moved our application to a different vm with RHEL6.4.
We notice that our performance issues occur especially when the log shows
this:
[Fri Mar 07 00:18:19 2014] [error]
Hi Ze,
Those warnings are probably unrelated.
I want to get a better sense of the performance problems. First thing I
want to check is that your server is properly accessing and using
memcached. If you log into the admin UI, do you see any stats on memcached,
and any keys stored in the cache?
Thanks for the quick reply. Yes, memcached is running. Here is what I see
from the Admin Server Cache page
I've got it running on two different vms, which I've obfuscated as VM1
and VM2
SERVER CACHE
Cache backend:
django.core.cache.backends.memcached.CacheClass
vm1
Memory usage:
1.8 GB
Okay, well, I was hoping it'd be simple :)
Can you give me some examples of operations that are very slow, and
operations that remain fast? Or does everything basically slow to a grind?
How do the Apache settings (worker vs prefork, and their config) compare
between installs?
Christian
On
Hi Christian,
I would like to thank you for your response about upgrade.
I went through with your comments and i was able to bring my server to
1.7.4.
Also also want to bring to your notice regarding below warning i got after
while upgrading my site.
While sent an email to you, I face one issue.
When i clicked to any of the old review request i see error message:
Something broke! (Error 500)
It appears something broke when you tried to go to here. This is either a
bug in Review Board or a server configuration error. Please report this to
Hi Chuck,
Sorry for failing to respond to the previous e-mail. Missed it.
I haven't seen that particular warning before. It'll probably have a log entry
any time pycrypto is imported. What distro/version are you using? Sounds like
maybe it's an older one? You may need to hand-upgrade libgmp,
Here are the logs
its seems it searching for lessc executable.
Environment:
Request Method: GET
Request URL: http://scrrb1.na.software.com/svrrb/dashboard/?view=to-me
Django Version: 1.4.3
Python Version: 2.7.2
Installed Applications:
['django.contrib.admin',
'django.contrib.auth',
Yep, it's looking for lessc, which it shouldn't be. That means it's not finding
the generated static media files, probably. Or some other strange configuration
problem. Probably an installation problem.
To verify, when you upgraded using easy_install -U ReviewBoard, you then ran
'rb-site
yes you are correct i followed the upgrade instruction from
www.reviewboard.org
To verify, when you upgraded using easy_install -U ReviewBoard, you then
ran 'rb-site upgrade /path/to/site'
I also saw below message,
[root@svrrb1 www]# rb-site upgrade /var/www/svrrb
And you restarted Apache afterward?
I'll need to see the contents of the css directories.
I also still need to know what version of what Linux distro you're using.
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. -
Yes, i have restarted the Apache afterward.
Here you go:
here is the content of ccs /var/www/svrrb/htdocs/static/rb/css
admin.1f278e6382ef.css admin.min.c8a349cc3f7d.css
dashboard.cb3f25c48eb7.cssdiffviewer.css
js-tests.70d6ede4e69e.css reviews.css
syntax.5f96383e25b8.css
All the files match correctly, so I'm left to believe that Review
Board/Apache's unable to open them, and is trying to fall back on creating new
ones (using lessc).
Does this happen for all review requests? I'd imagine it'd have to.
Is SELinux turned on? Try turning it off.
You also may want
Thank you !!,
yes it is happening for all the review request, also after restart i am not
able to open login page also and it crashed with the same compilation error.
CompilerError at /svrrb/dashboard/
/usr/bin/env: lessc: No such file or directory
Request Method: GET
Request URL:
This isn't a database problem, or a Review Board problem. It's something screwy
on the system.
When Review Board includes a stylesheet or JavaScript file, it attempts to find
a compiled (*.min.*) file. If it finds it, it uses it. If not, it will attempt
to compile it. For CSS, we compile using
Also SElinux is turned off.
#selinuxenabled echo enabled || echo disabled
disabled
On Wed, Feb 6, 2013 at 3:22 PM, chuck j cjerry2...@gmail.com wrote:
Thank you !!,
yes it is happening for all the review request, also after restart i am
not able to open login page also and it crashed with
Can you provide your settings_local.py file? Make sure to remove your database
information and your SECRET_KEY first!
Christian
--
Christian Hammond - chip...@chipx86.com
Review Board - http://www.reviewboard.org
VMware, Inc. - http://www.vmware.com
On Feb 6, 2013, at 1:58 AM, chuck j
Sure please see below:
# Site-specific configuration settings for Review Board
# Definitions of these settings can be found at
# http://docs.djangoproject.com/en/dev/ref/settings/
# Database configuration
DATABASES = {
'default': {
'ENGINE': 'django.db.backends.mysql',
Okay, looks fine.
I'd suggest creating a second RB site on that server, for testing purposes.
Just set it up, new database, and see if you have the same problem. If so, we
can narrow it down further.
It's 2:30AM here, so I need to head to bed, but I can try to help more with
this tomorrow.
Thanks Christian for the response.
Good to hear that upgrade is possible from 1.6.1 to 1.7.4 RB version, apart
from the database backup do we need to take care of any thing else which
will disturb our production setup and in case of any issue we should be
able to go back to our original state, if
Hi Chuck,
I always recommend backing up your database first, but you should be able to
upgrade from 1.6.1 to 1.7.4 without any real problems.
There is a bug that some people hit a while back in older versions that
introduced some stale upgrade data in the database. I meant to get a final fix
23 matches
Mail list logo
