brian.fleming

I just determined that the superuser password is being reset after I login as the superuser account SOMETIMES. The password is being reset to the same value every time (by looking in the postgres db) What is this about??

Happened again. This is in the logs. Annoying that there is no date timestamp, but can someone confirm my suspicion that this is being reset from within the UI? LOG: execute <unnamed>: update JIUser set username=$1, tenantId=$2, fullname=$3, emailAddress=$4, password=$5, externallyDefined=$6, enabled=$7, previousPasswordChangeTime=$8 where id=$9DETAIL: parameters: $1 = 'superuser', $2 = '3', $3 = 'superuser', $4 = '', $5 = '<new password???!>', $6 = 'f', $7 = 't', $8 = '2015-05-20 18:08:33.834', $9 = '11'

We're not importing anything. This is a new server has not seen much activity. I noticed there is a script on the AWS instance /etc/init.d/jrs_init_password This sets the password to the instance ID. But I thought I tried the instance id password as one of my guesses at what the password might have been reset to. We created a new superuser account just in case this one keeps giving us trouble. I moved that /etc script out of /etc/init.d. Seems like our password hasn't changed since.

Our superuser account seems to periodically just not respond to it's normal password. I can go into postgres and set it to empty, then create a new one, it works fine for some unknown amount of time and then it's reset again. Any clue at all at what might be happening? I thought maybe it's resetting the password back to the initial default password, which is the EC2 instance ID, but that doesn't work either. Thanks for any ideas how to debug this.

Figured it out. I found a post to change it from postgres. psql --u postgres pw: postgres c jasperserver select * from jiuser where username = 'superuser'; <then do an update and set the password to blank or an empty space> - don't have that handy,

I tried to set the password to empty or just a space but I still can't login. I went through the postgres db on the server.

We're running Jasper Reports on AWS, Multi-Tennant. superuser login was always present. But after a couple reboots debugging an MTU issue I can't login as superuser, and I can't find superuser when I login as "jasperadmin". How do I reset this?

I'm kind of surprised this hasn't been reported before. The Jasper Reports instance runs on an amazon linux OS, and I finally got the right information. The MTU setting on the network interface defaults to jumbo frames (9001). It needs to be set to 1500, OR in my case, it only worked if I set it to 1000. http://docs.aws.amazon.com/redshift/latest/mgmt/connecting-drop-issues.html

We're using JDBC drivers with MYSQL. I took out all the complexity in our query and am running a simple select statement with a inner join. Nothing fancy at all, no calculations or anything. Our fields from our query are numeric values that are very large. For example 14719606800.00. For the hell of it, I changed the query so these large values are all 0s in the table result. I was then able to increase the number of rows I could receive. Could there be some kind of transfer limit somewhere? Maybe it isn't the number of rows, so much as the amount of data that has to be returned. Just one idea we had.