Logins fail after 1.3.0 upgrade; work on 1.2.5

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Logins fail after 1.3.0 upgrade; work on 1.2.5

Paul Schreiber
I have Roundcube checked out from git. When I from upgrade from 1.2.5 to 1.3.0 (git checkout 1.3.0), logins fail with the "Invalid request! No data was saved." error. Reverting to 1.2.5 (git checkout 1.2.5) allows logins to occur successfully.

I tried the following, with no effect:
- Running bin/install-jsdeps.sh, bin/installto.sh, bin/indexcontacts.sh and bin/cleandb.sh
- Enabling both $config['force_https'] and $config['use_https']
- Enabling only $config['force_https']
- Truncating the session and cache_* tables

Logs: nothing is added to logs/imap when these failures occur; logs/sql shows an INSERT to the session table

config:
- Ubuntu 16.04.2
- dovecot 2.2.22
- apache 2.4.18
- postfix 3.1.0
$config['default_port'] = 993;
$config['default_host'] = 'ssl://myhostname.com';


Paul

_______________________________________________
Roundcube Users mailing list
[hidden email]
http://lists.roundcube.net/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Logins fail after 1.3.0 upgrade; work on 1.2.5

Noel Butler

On 01/07/2017 03:00, Paul Schreiber wrote:

I have Roundcube checked out from git. When I from upgrade from 1.2.5 to 1.3.0 (git checkout 1.3.0), logins fail with the "Invalid request! No data was saved." error. Reverting to 1.2.5 (git checkout 1.2.5) allows logins to occur successfully.
 
I tried the following, with no effect:
- Running bin/install-jsdeps.sh, bin/installto.sh, bin/indexcontacts.sh and bin/cleandb.sh
- Enabling both $config['force_https'] and $config['use_https']
- Enabling only $config['force_https']
- Truncating the session and cache_* tables
 
Logs: nothing is added to logs/imap when these failures occur; logs/sql shows an INSERT to the session table
 
config:
- Ubuntu 16.04.2
- dovecot 2.2.22
- apache 2.4.18
- postfix 3.1.0
$config['default_port'] = 993;
$config['default_host'] = 'ssl://myhostname.com';
 
 
 
What version of php?
 
--

Kind Regards,

Noel Butler

This Email, including any attachments, may contain legally privileged information, therefore remains confidential and subject to copyright protected under international law. You may not disseminate, discuss, or reveal, any part, to anyone, without the authors express written authority to do so. If you are not the intended recipient, please notify the sender then delete all copies of this message including attachments, immediately. Confidentiality, copyright, and legal privilege are not waived or lost by reason of the mistaken delivery of this message. Only PDF and ODF documents accepted, please do not send proprietary formatted documents

_______________________________________________
Roundcube Users mailing list
[hidden email]
http://lists.roundcube.net/mailman/listinfo/users
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Logins fail after 1.3.0 upgrade; work on 1.2.5

Paul Schreiber
On Jun 30, 2017, at 7:56 PM, Noel Butler <[hidden email]> wrote:

What version of php?

This is PHP 7. The problem turned out to be update.sh failing to execute the migrations.

    What version are you upgrading from? Type '?' if you don't know.
    ?
    Executing database schema update.
    Updating database schema (2015111100)... [FAILED]
    NOTE: Update dependencies by running `php composer.phar update --no-dev`

Running this manually:
    mysql> ALTER TABLE `users`
        ->   ADD `failed_login` datetime DEFAULT NULL,
        ->   ADD `failed_login_counter` int(10) UNSIGNED DEFAULT NULL;
    ERROR 1067 (42000): Invalid default value for 'created'

Looking in mysql.initial.sql, I see the default values for created are 1000-01-01 00:00:00.

I ran this SQL to fix it:
    alter table users modify created datetime NOT NULL default '1000-01-01 00:00:00';
    alter table session modify changed datetime NOT NULL default '1000-01-01 00:00:00',
       modify created datetime NOT NULL default '1000-01-01 00:00:00';

Filed:
bin/update.sh fails if sql_mode contains NO_ZERO_IN_DATE,NO_ZERO_DATE

bin/update.sh doesn't print SQL errors


Paul


_______________________________________________
Roundcube Users mailing list
[hidden email]
http://lists.roundcube.net/mailman/listinfo/users
Loading...