<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
To manually run the DB schema update, run<br>
/opt/zendto/sbin/cleanup.php<br>
as root. The output of that should tell you what it's doing.<br>
<br>
Cheers,<br>
Jules.<br>
<br>
<div class="moz-cite-prefix">On 28/09/2020 14:21, Lieven De
Puysseleir via ZendTo wrote:<br>
</div>
<blockquote type="cite"
cite="mid:WM!5315cf407e32cdf642dd2fc3ebf848eb70779c588d60df042449034c9a466a94b1a5d8fcd473dc01e301cc3dd3b7bbe1!@mx.jul.es">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div>Dear,</div>
<div>On one system running zendto 5.17-6 I fail to have the
sqlite3 schema updating while upgrading to 6.05-4.</div>
<div>to update I use the zendto repository on sles 15 sp2 and
then run the script that handles config file changes.</div>
<div><br>
</div>
<div>after the update, it's impossible to make dropoffs "unable
to add a dropoff record to the database". I notice that there
are 2 fields missing from the dropoff table: "lifeseconds and
subject"<br>
</div>
<div><br>
</div>
<div>So I deleted the file zendto.sqlite, restarted apache2 and
zendto created a new one with the correct schema. <br>
</div>
<div>Next, I did a dump of the old db to file, found the INSERT
lines for the dropoff table and added a value for the
lifeseconds which (I think) corresponds to the max 14days we
put as preference when it's not overridden in the new version
dropoff form. Also added a value empty string '' for the
subject field.</div>
<div>Lastly I did a cat of the (edited) dump file, piped it to
sqlite3 into the newly created empty db file.</div>
<div>This seemed to work fine, I could see the dropoffs in the
interface but couldn't see the files when I opened a dropoff.</div>
<div>I verified that for each dropoff line in the database, the
claimid corresponded to the name of the folder in /var/zendto
where the dropoff directory/files resided and it matched.</div>
<div>The logs don't say anything about this.</div>
<div>Apache logs indicate that pickup.php is used but again, the
php code with the nssdrop class stuff is something I can't
seem to understand how it works. (or if it even matters in
this case)<br>
</div>
<div><br>
</div>
<div>This worked fine on another system upgrading 5.17-6 to
6.05-4. The update was done with zypper, the upgrade script
run and that was it, everything looked fine in the dropoffs.<br>
</div>
<div><br>
</div>
<div>Any ideas what part of the install script I should run to
simulate the schema upgrade? I've been looking into
cleanup.php but I'm not much of a programmer and can't figure
how it actually works by calling some class or something. (I'm
probably wrong here)</div>
<div><br>
</div>
<div>Thanks for your help.<br>
</div>
<div><br>
-- <br>
<div dir="ltr" class="gmail_signature"
data-smartmail="gmail_signature">Lieven<br>
</div>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
ZendTo mailing list
<a class="moz-txt-link-abbreviated" href="mailto:ZendTo@zend.to">ZendTo@zend.to</a>
<a class="moz-txt-link-freetext" href="http://jul.es/mailman/listinfo/zendto">http://jul.es/mailman/listinfo/zendto</a>
</pre>
</blockquote>
<br>
<pre class="moz-signature" cols="72">Jules
--
Julian Field MEng CEng CITP MBCS MIEEE MACM
The current UK shipping forecast:
East Forties: Cyclonic becoming northerly 4 or 5. Slight or moderate. Rain,
fog patches. Moderate or very poor.
<a class="moz-txt-link-abbreviated" href="http://www.Zend.To">www.Zend.To</a>
Twitter: @JulesFM
</pre>
</body>
</html>