<div dir="ltr">Hi Ian,<div><br></div><div>As I understand it: The new CNAME is only used for the Pickups. The users will still use the original name and the CNAME will only be valid for the period the pickups on the old server have expired and been deleted.</div><div><br></div><div>Gregg</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Jul 27, 2023 at 10:41 AM Elston, Ian <<a href="mailto:I.Elston@bolton.ac.uk">I.Elston@bolton.ac.uk</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I'm in a similar position - a wiser man than me (Jules) once suggested that this jump is a bit large to handle nicely, and the best thing would be to launch a new server, potentially with a new name to make that simpler. Our service has been called 'zendto' for years so I'm loathe to change it, which makes things trickier to swap over, running two in parallel etc.<br>
<br>
<br>
<br>
-----Original Message-----<br>
From: ZendTo <<a href="mailto:zendto-bounces@zend.to" target="_blank">zendto-bounces@zend.to</a>> On Behalf Of Gregg Douglas via ZendTo<br>
Sent: 27 July 2023 09:36<br>
To: ZendTo Users <<a href="mailto:zendto@zend.to" target="_blank">zendto@zend.to</a>><br>
Cc: Gregg Douglas <<a href="mailto:douglagm@gmail.com" target="_blank">douglagm@gmail.com</a>><br>
Subject: [ZendTo] Another Migration/upgrade of ZendTO<br>
<br>
WARNING: This message originated from outside the University. Use caution when following links or opening attachments.<br>
Hi All,<br>
<br>
I have been neglecting the upgrade on my ZendTO server, it has now come time for me to bite the bullet. I have scoured the mailing lists for recommendations. From what I understand is there are two options:<br>
<br>
1. Implement a new server and change the upload url and create a CNAME<br>
2. Implement a new server copy data and DB across then upgrade the scheme of the DB<br>
<br>
<br>
I have tried both, but I can't seem to get either to work.<br>
<br>
Using option 1, I change the following:<br>
<br>
In the preference.php, I change the serverRoot option to the CNAME<br>
<br>
In the apache configuration, I also change to the CNAME<br>
<br>
Reboot server, just to make sure<br>
<br>
However I can't upload any files and get the following error message:<br>
<br>
Sorry, I failed to drop-off your files! Note that you cannot drop-off directories, only files.<br>
<br>
When I change the above back to the original settings everything works<br>
<br>
<br>
Using the option 2:<br>
<br>
Current server is 5.23-3<br>
<br>
<br>
New server is 6.13-3<br>
<br>
<br>
The DB is MySQL/MariaDB<br>
<br>
<br>
Comment out all cron jobs on new server<br>
<br>
<br>
I export the DB from the current server and import into the new server<br>
<br>
<br>
Then run the following script as suggested: /usr/bin/php /opt/zendto/sbin/cleanup.php /opt/zendto/config/preferences.php<br>
<br>
<br>
However I get the following error:<br>
<br>
<br>
PHP Warning: Undefined array key "authLDAPAdmins" in /opt/zendto/lib/NSSLDAPAuthenticator.php on line 70<br>
<br>
<br>
Cleanup of ZendTo for preference file:<br>
<br>
/opt/zendto/config/preferences.php<br>
<br>
<br>
Updating database schema<br>
<br>
PHP Fatal error: Uncaught mysqli_sql_exception: Duplicate column name 'Passphrase' in /opt/zendto/lib/MySQL.php:889<br>
<br>
Stack trace:<br>
<br>
#0 /opt/zendto/lib/MySQL.php(889): mysqli->query()<br>
<br>
#1 /opt/zendto/lib/MySQL.php(716): Sql->DBReqAddPassphrase()<br>
<br>
#2 /opt/zendto/sbin/cleanup.php(58): Sql->DBUpdateSchema()<br>
<br>
#3 {main}<br>
<br>
thrown in /opt/zendto/lib/MySQL.php on line 889<br>
<br>
<br>
I really like option 1 as I can then also migrate the DB to the default DB, but at this point I would be happy to get either option working.<br>
<br>
Any assistance or guidance will be highly appreciated.<br>
<br>
Regards<br>
Gregg<br>
<br>
<br>
<br>
<br>
[University of Bolton]<<a href="https://www.bolton.ac.uk" rel="noreferrer" target="_blank">https://www.bolton.ac.uk</a>><br>
<br>
This email (and any attachments) is confidential and may contain personal views which are not the views of the University of Bolton unless specifically stated. If you have received it in error, please delete it from your system. Do not use, copy or disclose information in any way nor act in reliance on it and notify the sender immediately. Please note the University of Bolton monitors emails sent or received. Further communication will signify your consent to this.<br>
</blockquote></div>