Subject: The mailing list for listmasters using Sympa
List archive
- From: Amos <address@concealed>
- To: Gerard Ranke <address@concealed>
- Cc: "address@concealed >> address@concealed" <address@concealed>
- Subject: Re: [sympa-users] upgrading 6.1.22 to 6.2.16
- Date: Mon, 12 Sep 2016 07:59:41 -0500
I notice Upgrade.pm has the following:
if (lower_version($previous_version, '6.2.10')
and not lower_version($previous_version, '5.3a.8')) {
$log->syslog('notice', 'Upgrading logs_table.');
my $sdm = Sympa::DatabaseManager->instance;
# As the field id_logs is no longer used but it has NOT NULL
# constraint, it should be deleted.
if ($sdm and $sdm->can('delete_field')) {
$sdm->delete_field({table => 'logs_table', field => 'id_logs'});
} else {
$log->syslog('err',
'Can\'t delete id_logs field in logs_table. You must delete it manually.'
);
}
# Newly added subsecond field should be 0 by default.
$sdm->do_query(
q{UPDATE logs_table
SET usec_logs = 0
WHERE usec_logs IS NULL}
);
}
On Mon, Sep 12, 2016 at 7:19 AM, Gerard Ranke <address@concealed> wrote:
Hi Amos,
Thanks for your mail! Changing the data_structure.version file to
reflect the new version indeed did the trick!
Strangely, I also happen to hit this 'INSERT INTO logs_table' error. The
difference is that we are using ldap to authenticate webgui users, and
that there is an entry in the logs that reports the server is unable to
connect to our ldap-server. One more log entry:
Neither ca_file nor ca_path parameter is specified
Which is strange, because a 'ca_path' parameter is actually illegal in
sympa.conf. It should read 'capath' wich however is present and correct.
Further reading of the docs suggests that this might have something to
do with apache's mod_ssl config, so that's what I'm looking into now.
Maybe this is in some way helpful, although it looks like you are using
a database iso ldap.
Best,
gerard
On 09/12/2016 01:49 PM, Amos (via sympa-users Mailing List) wrote:
> actually, something a little off with the db. Getting a lot of these:
>
> bounced[8324]: err main::#157 > Sympa::Spindle::spin#80 >
> Sympa::Spindle::ProcessBounce::_twist#561 > Sympa::Log::db_log#317 >
> Sympa::Database::do_prepared_query#379 Unable to execute SQL statement
> "INSERT INTO logs_table (date_lo
> gs, usec_logs, robot_logs, list_logs, action_logs, parameters_logs,
> target_email_logs, msg_id_logs, status_logs, error_type_logs,
> user_email_logs, client_logs, daemon_logs) VALUES (?, ?, ?, ?, ?, ?, ?,
> ?, ?, ?, ?, ?, ?)": (HY000) Field 'id_logs' doesn't have a default value
>
>
>
> On Sun, Sep 11, 2016 at 3:25 PM, Amos <address@concealed
> <mailto:address@concealed>> wrote:
>
> So, turns out only having problems with login from Safari. With
> Firefox it works. Though, it does report that some content is non-SSL.
>
> On Sun, Sep 11, 2016 at 1:50 PM, Amos <address@concealed
> <mailto:address@concealed>> wrote:
>
> Yeah, I ran into the same thing. The funny thing is that in dev
> and in test and never encountered it. But of course, when
> upgrading prod, I did. So I changed that file. Mail seems to
> be flowing normally to/from the lists. Though, logging into the
> web interface now seems broken (also not experienced in dev and
> test.) Figures.
>
> Amos
>
>
> On Fri, Sep 9, 2016 at 9:16 AM, Gerard Ranke
> <address@concealed <mailto:address@concealed>> wrote:
>
> Dear Sympa users,
>
> I'm in the process of moving our sympa lists to a new
> machine, and
> upgrading sympa at the same time. So I transferred all our
> lists and
> sympa setup to the new machine, installed 6.2.16, did the
> configure,
> make and make install steps, and ran the various upgrade scripts
> mentioned on https://www.sympa.org/faq/upgrade-to-v6.2
> <https://www.sympa.org/faq/upgrade-to-v6.2>.
> Everything seemed to run just fine, including upgrading the
> mysql
> database, but when I try to start sympa it complains:
>
> err main::#234 > Conf::data_structure_uptodate#737 Data
> structure
> (6.1.22) is not uptodate for current release (6.2.16)
>
> But I believe it is up to date! I can see that all the table
> and fields
> modifications are done!
>
> Now, there is file called
> /home/sympa/etc/data_structure.version, which
> reads:
>
> # automatically created file
> # you should not modify it
> 6.1.22
>
> and of course I'm now tempted to modify it... Could it be
> that the sympa
> upgrade scripts just missed this, and that entering the new
> version
> number would solve this? Or am I making this worse that way?
> Best regards,
>
> Gerard Ranke
>
>
>
>
-
[sympa-users] upgrading 6.1.22 to 6.2.16,
Gerard Ranke, 09/09/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/11/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/11/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Gerard Ranke, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Gerard Ranke, 09/12/2016
- Re: [sympa-users] upgrading 6.1.22 to 6.2.16, Amos, 09/12/2016
- Re: [sympa-users] upgrading 6.1.22 to 6.2.16, Amos, 09/12/2016
- Re: [sympa-users] upgrading 6.1.22 to 6.2.16, Gerard Ranke, 09/13/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Gerard Ranke, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Gerard Ranke, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/12/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/11/2016
-
Re: [sympa-users] upgrading 6.1.22 to 6.2.16,
Amos, 09/11/2016
Archive powered by MHonArc 2.6.19+.