log4cxx: Large window sizes are not allowed


#1

We are upgrading from 13.6 to 13.11
We use the same conf.ini file with the obvious changes, and start a clean new database.

scidb.py initall eleven created a single-line init-stderr.log:

log4cxx: Large window sizes are not allowed.

Here is our config.ini. Please, can you see anything really wrong?
We’ve used this with 13.6 and no problem…

[code][eleven]
server-0=10.0.0.100,0
server-1=10.0.0.1,1
server-2=10.0.0.2,1
server-3=10.0.0.3,1
server-4=10.0.0.4,1
server-5=10.0.0.5,1
server-6=10.0.0.6,1
server-7=10.0.0.7,1
server-8=10.0.0.8,1
server-9=10.0.0.9,1
server-10=10.0.0.10,1
server-11=10.0.0.11,1
server-12=10.0.0.12,1
server-13=10.0.0.13,1
server-14=10.0.0.14,1
server-15=10.0.0.15,1
server-16=10.0.0.16,1
server-17=10.0.0.17,1
server-18=10.0.0.18,1
server-19=10.0.0.19,1
server-20=10.0.0.20,1
server-21=10.0.0.21,1
server-22=10.0.0.22,1
server-23=10.0.0.23,1
server-24=10.0.0.24,1
server-25=10.0.0.25,1
server-26=10.0.0.26,1
server-27=10.0.0.27,1
server-28=10.0.0.28,1
server-29=10.0.0.29,1
server-30=10.0.0.30,1
server-31=10.0.0.31,1
server-32=10.0.0.32,1
server-33=10.0.0.33,1
server-34=10.0.0.34,1

db_user=eleven_user
db_passwd=eleven_passwd
install_root=/opt/scidb/13.11
metadata=/opt/scidb/13.11/share/scidb/meta.sql
pluginsdir=/opt/scidb/13.11/lib/scidb/plugins
logconf=/opt/scidb/13.11/share/scidb/log4cxx.properties
chunk-segment-size=104857600
base-path=/bigdata/scidb/1311
base-port=1239
interface=ib0
ssh-port=22
execution-threads=9
operator-threads=8
result-prefetch-threads=8

enable-catalog-upgrade=true

[/code]

Cheers, George


#2

One mo’ thing: I noticed that the log4cxx.properties are different.
For what it’s worth I never touched any of these before…

SciDB Version:        13.6                 13.11
MaxFileSize            10000KB            50000KB
MaxBackupIndex           2                   18

All else are identical. So I must assume that 18 must be excessive, with 50MiB file size limits…
My limited research revealed that beyond 12 is considered too large.

If that is so, others should see the same problem, no?
Cheers, George


#3

We have seen this as well. It is harmless, but annoying, because it appears in your error log. It is merely log4cxx telling you that it is resetting the MaxBackupIndex value of 18 back to 12. If you want to get rid of it, set the value to something more reasonable, like 2, as it was originally.