Re: Somthing broke! - error 500 on a fresh installation

2018-02-19 Thread Marcin Ciarka
rb-site --version gives this:

[root@vwbank-web logs]# rb-site --version
> rb-site 3.0.3
> Python 2.7.14 (default, Feb 19 2018, 15:53:03) 
> [GCC 4.4.7 20120313 (Red Hat 4.4.7-18)]
> Installed to 
> /opt/python/2.7.14/lib/python2.7/site-packages/ReviewBoard-3.0.3-py2.7.egg/reviewboard



W dniu wtorek, 20 lutego 2018 03:17:40 UTC+1 użytkownik Christian Hammond 
napisał:
>
> Hi Marcin,
>
> This looks like a very old bug. What version of Review Board do you have 
> installed?
>
> Christian
>
> On Mon, Feb 19, 2018 at 09:14 Marcin Ciarka  > wrote:
>
>> CentOS 6.9
>>
>> error_log contains only this:
>>
>> [Mon Feb 19 16:09:03 2018] [error] Traceback (most recent call last):
>>> [Mon Feb 19 16:09:03 2018] [error]   File 
>>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 861, in emit
>>> [Mon Feb 19 16:09:03 2018] [error] msg = self.format(record)
>>> [Mon Feb 19 16:09:03 2018] [error]   File 
>>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 734, in format
>>> [Mon Feb 19 16:09:03 2018] [error] return fmt.format(record)
>>> [Mon Feb 19 16:09:03 2018] [error]   File 
>>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 465, in format
>>> [Mon Feb 19 16:09:03 2018] [error] record.message = 
>>> record.getMessage()
>>> [Mon Feb 19 16:09:03 2018] [error]   File 
>>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 329, in 
>>> getMessage
>>> [Mon Feb 19 16:09:03 2018] [error] msg = msg % self.args
>>> [Mon Feb 19 16:09:03 2018] [error] TypeError: not enough arguments for 
>>> format string
>>> [Mon Feb 19 16:09:03 2018] [error] Logged from file manager.py, line 1161
>>
>> -- 
>> Supercharge your Review Board with Power Pack: 
>> https://www.reviewboard.org/powerpack/
>> Want us to host Review Board for you? Check out RBCommons: 
>> https://rbcommons.com/
>> Happy user? Let us know! https://www.reviewboard.org/users/
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "Review Board Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to reviewboard...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
> -- 
> -- 
> Christian Hammond
> President/CEO of Beanbag
> Makers of Review Board
>

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: PNG picture review and PDF review doesn't work

2018-02-19 Thread Christian Hammond
Hi Ondrej,

Can you check that your Power Pack license is still valid?

If it is, can you open the browser’s developer console, reload the page,
and check for any errors?

Christian


On Mon, Feb 19, 2018 at 01:10 Ondrej Volf  wrote:

> Hello,
>
> after a while without issues the pdf review and picture reviews stopped
> working without any known reason. After uploading files the files are
> correctly uploaded, but thumbnail is not visible and in pdf case there is
> just the "loading circle" instead as can be seen in attached picture. The
> text files including .c, .cpp and .h are working without any problems.
>
>
>
> Files are correctly uploaded to the server and can be downloaded back
> without any problems. MIME types are also correct (application/pdf and
> image/png). Both of these reviews worked after installation.
>
> I have tried to find similar problems but encountered only one similar
> situation without any clue of solution. Any ideas what could be wrong?
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
-- 
Christian Hammond
President/CEO of Beanbag
Makers of Review Board

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Https ( secure connection ) is showing Apache 2 Test Page, not ReviewBoard

2018-02-19 Thread Christian Hammond
That’s likely the cause. You’ll need to remove that file or comment it out
and restart Apache.

Christian


On Mon, Feb 19, 2018 at 01:12 Anil Kumar  wrote:

> Thanks for reply. Below is the VirtualHost section in ssl.cong
>
> 
>
> # General setup for the virtual host, inherited from global configuration
> #DocumentRoot "/var/www/html"
> #ServerName www.example.com:443
>
> # Use separate log files for the SSL virtual host; note that LogLevel
> # is not inherited from httpd.conf.
> ErrorLog logs/ssl_error_log
> TransferLog logs/ssl_access_log
> LogLevel warn
>
> #   SSL Engine Switch:
> #   Enable/Disable SSL for this virtual host.
> SSLEngine on
>
> #   SSL Protocol support:
> # List the enable protocol levels with which clients will be able to
> # connect.  Disable SSLv2 access by default:
> SSLProtocol all -SSLv2
>
> #   SSL Cipher Suite:
> #   List the ciphers that the client is permitted to negotiate.
> #   See the mod_ssl documentation for a complete list.
> SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5:!SEED:!IDEA
>
> #   Speed-optimized SSL Cipher configuration:
> #   If speed is your main concern (on busy HTTPS servers e.g.),
> #   you might want to force clients to specific, performance
> #   optimized ciphers. In this case, prepend those ciphers
> #   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
> #   Caveat: by giving precedence to RC4-SHA and AES128-SHA
> #   (as in the example below), most connections will no longer
> #   have perfect forward secrecy - if the server's key is
> #   compromised, captures of past or future traffic must be
> #   considered compromised, too.
> #SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
> #SSLHonorCipherOrder on
>
> #   Server Certificate:
> # Point SSLCertificateFile at a PEM encoded certificate.  If
> # the certificate is encrypted, then you will be prompted for a
> # pass phrase.  Note that a kill -HUP will prompt again.  A new
> # certificate can be generated using the genkey(1) command.
>   SSLCertificateFile /etc/pki/tls/certs/xxx00jol.xx.x.com.crt
> #  SSLCertificateFile /etc/pki/tls/certs/localhost.crt
>
> #   Server Private Key:
> #   If the key is not combined with the certificate, use this
> #   directive to point at the key file.  Keep in mind that if
> #   you've both a RSA and a DSA private key you can configure
> #   both in parallel (to also allow the use of DSA ciphers, etc.)
>  SSLCertificateKeyFile /etc/pki/tls/private/xxx00jol.xx.xxx.com.key
> #SSLCertificateKeyFile /etc/pki/tls/private/localhost.key
>
> #   Server Certificate Chain:
> #   Point SSLCertificateChainFile at a file containing the
> #   concatenation of PEM encoded CA certificates which form the
> #   certificate chain for the server certificate. Alternatively
> #   the referenced file can be the same as SSLCertificateFile
> #   when the CA certificates are directly appended to the server
> #   certificate for convinience.
> #SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt
>
> #   Certificate Authority (CA):
> #   Set the CA certificate verification path where to find CA
> #   certificates for client authentication or alternatively one
> #   huge file containing all of them (file must be PEM encoded)
> #SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt
>
> #   Client Authentication (Type):
> #   Client certificate verification type and depth.  Types are
> #   none, optional, require and optional_no_ca.  Depth is a
> #   number which specifies how deeply to verify the certificate
> #   issuer chain before deciding the certificate is not valid.
> #SSLVerifyClient require
> #SSLVerifyDepth  10
>
> #   Access Control:
> #   With SSLRequire you can do per-directory access control based
> #   on arbitrary complex boolean expressions containing server
> #   variable checks and other lookup directives.  The syntax is a
> #   mixture between C and Perl.  See the mod_ssl documentation
> #   for more details.
> #
> #SSLRequire (%{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
> #and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
> #and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
> #and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
> #and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20   ) \
> #   or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
> #
>
> #   SSL Engine Options:
> #   Set various options for the SSL engine.
> #   o FakeBasicAuth:
> # Translate the client X.509 into a Basic Authorisation.  This means
> that
> # the standard Auth/DBMAuth methods can be used for access control.
> The
> # user name is the `one line' version of the client's X.509
> certificate.
> # Note that no password is obtained from the user. Every entry in the
> user
> # file needs this password: `xxj31ZMTZzkVA'.
> #   o ExportCertData:
> # This exports two additional environment variables: SSL_CLIENT_CERT
> and
> # SSL_SERVER_CERT. These contain the PEM-encoded 

Re: Somthing broke! - error 500 on a fresh installation

2018-02-19 Thread Christian Hammond
Hi Marcin,

This looks like a very old bug. What version of Review Board do you have
installed?

Christian

On Mon, Feb 19, 2018 at 09:14 Marcin Ciarka 
wrote:

> CentOS 6.9
>
> error_log contains only this:
>
> [Mon Feb 19 16:09:03 2018] [error] Traceback (most recent call last):
>> [Mon Feb 19 16:09:03 2018] [error]   File
>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 861, in emit
>> [Mon Feb 19 16:09:03 2018] [error] msg = self.format(record)
>> [Mon Feb 19 16:09:03 2018] [error]   File
>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 734, in format
>> [Mon Feb 19 16:09:03 2018] [error] return fmt.format(record)
>> [Mon Feb 19 16:09:03 2018] [error]   File
>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 465, in format
>> [Mon Feb 19 16:09:03 2018] [error] record.message =
>> record.getMessage()
>> [Mon Feb 19 16:09:03 2018] [error]   File
>> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 329, in
>> getMessage
>> [Mon Feb 19 16:09:03 2018] [error] msg = msg % self.args
>> [Mon Feb 19 16:09:03 2018] [error] TypeError: not enough arguments for
>> format string
>> [Mon Feb 19 16:09:03 2018] [error] Logged from file manager.py, line 1161
>
> --
> Supercharge your Review Board with Power Pack:
> https://www.reviewboard.org/powerpack/
> Want us to host Review Board for you? Check out RBCommons:
> https://rbcommons.com/
> Happy user? Let us know! https://www.reviewboard.org/users/
> ---
> You received this message because you are subscribed to the Google Groups
> "Review Board Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to reviewboard+unsubscr...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>
-- 
-- 
Christian Hammond
President/CEO of Beanbag
Makers of Review Board

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Somthing broke! - error 500 on a fresh installation

2018-02-19 Thread Marcin Ciarka
CentOS 6.9

error_log contains only this:

[Mon Feb 19 16:09:03 2018] [error] Traceback (most recent call last):
> [Mon Feb 19 16:09:03 2018] [error]   File 
> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 861, in emit
> [Mon Feb 19 16:09:03 2018] [error] msg = self.format(record)
> [Mon Feb 19 16:09:03 2018] [error]   File 
> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 734, in format
> [Mon Feb 19 16:09:03 2018] [error] return fmt.format(record)
> [Mon Feb 19 16:09:03 2018] [error]   File 
> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 465, in format
> [Mon Feb 19 16:09:03 2018] [error] record.message = record.getMessage()
> [Mon Feb 19 16:09:03 2018] [error]   File 
> "/opt/python/2.7.14/lib/python2.7/logging/__init__.py", line 329, in 
> getMessage
> [Mon Feb 19 16:09:03 2018] [error] msg = msg % self.args
> [Mon Feb 19 16:09:03 2018] [error] TypeError: not enough arguments for 
> format string
> [Mon Feb 19 16:09:03 2018] [error] Logged from file manager.py, line 1161

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.


Re: Https ( secure connection ) is showing Apache 2 Test Page, not ReviewBoard

2018-02-19 Thread Anil Kumar
Thanks for reply. Below is the VirtualHost section in ssl.cong



# General setup for the virtual host, inherited from global configuration
#DocumentRoot "/var/www/html"
#ServerName www.example.com:443

# Use separate log files for the SSL virtual host; note that LogLevel
# is not inherited from httpd.conf.
ErrorLog logs/ssl_error_log
TransferLog logs/ssl_access_log
LogLevel warn

#   SSL Engine Switch:
#   Enable/Disable SSL for this virtual host.
SSLEngine on

#   SSL Protocol support:
# List the enable protocol levels with which clients will be able to
# connect.  Disable SSLv2 access by default:
SSLProtocol all -SSLv2

#   SSL Cipher Suite:
#   List the ciphers that the client is permitted to negotiate.
#   See the mod_ssl documentation for a complete list.
SSLCipherSuite HIGH:MEDIUM:!aNULL:!MD5:!SEED:!IDEA

#   Speed-optimized SSL Cipher configuration:
#   If speed is your main concern (on busy HTTPS servers e.g.),
#   you might want to force clients to specific, performance
#   optimized ciphers. In this case, prepend those ciphers
#   to the SSLCipherSuite list, and enable SSLHonorCipherOrder.
#   Caveat: by giving precedence to RC4-SHA and AES128-SHA
#   (as in the example below), most connections will no longer
#   have perfect forward secrecy - if the server's key is
#   compromised, captures of past or future traffic must be
#   considered compromised, too.
#SSLCipherSuite RC4-SHA:AES128-SHA:HIGH:MEDIUM:!aNULL:!MD5
#SSLHonorCipherOrder on

#   Server Certificate:
# Point SSLCertificateFile at a PEM encoded certificate.  If
# the certificate is encrypted, then you will be prompted for a
# pass phrase.  Note that a kill -HUP will prompt again.  A new
# certificate can be generated using the genkey(1) command.
  SSLCertificateFile /etc/pki/tls/certs/xxx00jol.xx.x.com.crt
#  SSLCertificateFile /etc/pki/tls/certs/localhost.crt

#   Server Private Key:
#   If the key is not combined with the certificate, use this
#   directive to point at the key file.  Keep in mind that if
#   you've both a RSA and a DSA private key you can configure
#   both in parallel (to also allow the use of DSA ciphers, etc.)
 SSLCertificateKeyFile /etc/pki/tls/private/xxx00jol.xx.xxx.com.key
#SSLCertificateKeyFile /etc/pki/tls/private/localhost.key

#   Server Certificate Chain:
#   Point SSLCertificateChainFile at a file containing the
#   concatenation of PEM encoded CA certificates which form the
#   certificate chain for the server certificate. Alternatively
#   the referenced file can be the same as SSLCertificateFile
#   when the CA certificates are directly appended to the server
#   certificate for convinience.
#SSLCertificateChainFile /etc/pki/tls/certs/server-chain.crt

#   Certificate Authority (CA):
#   Set the CA certificate verification path where to find CA
#   certificates for client authentication or alternatively one
#   huge file containing all of them (file must be PEM encoded)
#SSLCACertificateFile /etc/pki/tls/certs/ca-bundle.crt

#   Client Authentication (Type):
#   Client certificate verification type and depth.  Types are
#   none, optional, require and optional_no_ca.  Depth is a
#   number which specifies how deeply to verify the certificate
#   issuer chain before deciding the certificate is not valid.
#SSLVerifyClient require
#SSLVerifyDepth  10

#   Access Control:
#   With SSLRequire you can do per-directory access control based
#   on arbitrary complex boolean expressions containing server
#   variable checks and other lookup directives.  The syntax is a
#   mixture between C and Perl.  See the mod_ssl documentation
#   for more details.
#
#SSLRequire (%{SSL_CIPHER} !~ m/^(EXP|NULL)/ \
#and %{SSL_CLIENT_S_DN_O} eq "Snake Oil, Ltd." \
#and %{SSL_CLIENT_S_DN_OU} in {"Staff", "CA", "Dev"} \
#and %{TIME_WDAY} >= 1 and %{TIME_WDAY} <= 5 \
#and %{TIME_HOUR} >= 8 and %{TIME_HOUR} <= 20   ) \
#   or %{REMOTE_ADDR} =~ m/^192\.76\.162\.[0-9]+$/
#

#   SSL Engine Options:
#   Set various options for the SSL engine.
#   o FakeBasicAuth:
# Translate the client X.509 into a Basic Authorisation.  This means 
that
# the standard Auth/DBMAuth methods can be used for access control.  The
# user name is the `one line' version of the client's X.509 certificate.
# Note that no password is obtained from the user. Every entry in the 
user
# file needs this password: `xxj31ZMTZzkVA'.
#   o ExportCertData:
# This exports two additional environment variables: SSL_CLIENT_CERT and
# SSL_SERVER_CERT. These contain the PEM-encoded certificates of the
# server (always existing) and the client (only existing when client
# authentication is used). This can be used to import the certificates
# into CGI scripts.
 o StdEnvVars:
# This exports the standard SSL/TLS related `SSL_*' environment 
variables.
# Per default this exportation is switched off for performance reasons,
# because the extraction 

PNG picture review and PDF review doesn't work

2018-02-19 Thread Ondrej Volf
Hello,

after a while without issues the pdf review and picture reviews stopped 
working without any known reason. After uploading files the files are 
correctly uploaded, but thumbnail is not visible and in pdf case there is 
just the "loading circle" instead as can be seen in attached picture. The 
text files including .c, .cpp and .h are working without any problems.



Files are correctly uploaded to the server and can be downloaded back 
without any problems. MIME types are also correct (application/pdf and 
image/png). Both of these reviews worked after installation.

I have tried to find similar problems but encountered only one similar 
situation without any clue of solution. Any ideas what could be wrong?

-- 
Supercharge your Review Board with Power Pack: 
https://www.reviewboard.org/powerpack/
Want us to host Review Board for you? Check out RBCommons: 
https://rbcommons.com/
Happy user? Let us know! https://www.reviewboard.org/users/
--- 
You received this message because you are subscribed to the Google Groups 
"Review Board Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to reviewboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.