Koozali.org: home of the SME Server
Obsolete Releases => SME Server 9.x => Topic started by: hjnvejlen on March 14, 2021, 05:38:37 PM
-
Sorry if this has been posted earlier, but I was not able to detect this problem in the other posts :(
Due to a server breakdown I had to install a fresh SME 9.2 on a new PC. I installed my backup and most went fine, but one of my webpages did not wortk, since it requires higher php version that SME 9.2 default.
On my old box I used smeserver-php-scl to solve this problem, but I can not install this contribs now.
A lot of dependeny errors come up :-(
Any suggestions to solve my problem?
I have tried to install SME 10 Beta 1 but when I roll my backup from the 9.2 on top of it, a lot of stuff don't work, including e-mail and web pages so , for now, I have to stick with SME 9.2 until the other issue is solved.
-
It seems that I have "solved the problem.
The "normal" command for installing would be:
yum install smeserver-php-scl --enablerepo=smecontribs
But this ends in various problems.
Modifying the command to :
yum install smeserver-php-scl
seems to work. At least all packages installs as expected.
-
There are links here on updating the archived repos.
Restoring to v10 should work from USB but there is a known bug restoring a workstation backup. Check bugzilla for more.
If you have issues then please document them and if needs be open a bug.
-
What was the sme9 backup format? dar?
There is a Bug with the beta effecting workstation backup, fixed in two updates, e-smith-mysql and e-smith-backup
Added: the gunslinger beat me to the draw :-)
-
I believe it is tar format. The backup was created from the admin menu on the old system, and it was used during the installation, when the installation asks if you want to restore from backup. The backup file is called smeserver.tgz or something like that.
I have tried it both during the installation process but also around 1 week after installation and a number of updates of the sme-10 installation.
And the result was more or less the same...
After restore it looked as if mysql could not start.. and therefore neither my webpages would work or webmail, or imap mail either.
I will try later, here during the weekend I have been in a hurry, since my old box broke down :-(
And when I try again to install a backup from SME-9 to a fresh SME-10 install, I will document better and try to create an issue /bug report regarding the issue.. Even if the bug report might become quite big ;-)
-
Added: the gunslinger beat me to the draw :-)
Cheeky :lol:
-
And when I try again to install a backup from SME-9 to a fresh SME-10 install, I will document better and try to create an issue /bug report regarding the issue.. Even if the bug report might become quite big ;-)
It should work. Please do it again and give us a proper bug report so we can take a look.
Make sure you take a system/bug report from server-manager on v9 before you start so we can see if you have any customisations etc.
-
Regarding:
Make sure you take a system/bug report from server-manager on v9 before you start so we can see if you have any customisations etc.
I'm not an EXPERT in Linux. I can find my way around aand configure fstab a.o. but I am unsure how to take a system/bug report.
Could you please tell me how?
-
Regarding:
Make sure you take a system/bug report from server-manager on v9 before you start so we can see if you have any customisations etc.
I'm not an EXPERT in Linux. I can find my way around aand configure fstab a.o. but I am unsure how to take a system/bug report.
Could you please tell me how?
From Server-manager , Miscellaneous, Report a bug.
Click on Create configuration Report. Report is generated in the Server manager Panel, you can then copy it
-
From Server-manager , Miscellaneous, Report a bug.
Click on Create configuration Report. Report is generated in the Server manager Panel, you can then copy it
Ahh, thanks :-) I expected it to be easy, but not SO easy
-
Ahh, thanks :-) I expected it to be easy, but not SO easy
We do our best ;-)
Miracles usually take a few days. The impossible takes a little longer..... :lol: :pint:
-
a little less easy can you paste here the result of
ll /etc/e-smith/sql/init/
addendum: I am pretty sure you did not have the last e-smith-mysql, and you will have the file : 00_restore_dumped_dbs blocking the process of restoring
then you should
rm /etc/e-smith/sql/init/00_restore_dumped_dbs
yum update e-smith-mysql --enablerepo=smeupdates-testing
expand-template /etc/e-smith/sql/init/00_restore_dumped_dbs
systemctl restart mysql.init
if you start from scratch again then update to the last e-smith-mysql BEFORE restoring.
This can be done by adding smeupdates and smeupdates-testing repo in the iso gui as external repo, or by manual update after installin and before running the restore utility form console
-
Quick short term workaround for the beta1 iso, it will be fixed in beta 2
Install sme10beta1 as normal, when finished open a terminal, and do a
# yum update - of these two rpms
e-smith-mysql-2.6.0-20.el7.sme.noarch.rpm
e-smith-backup-2.6.0-24.el7.sme.noarch.rpm
currently in smeupdates-testing, will soon be moved to updates and will be in new iso
This will resolve restore issues with a sme9 backup using console restore and/or the workstation backup/restore using dar
Added, JP beat me to it, pretty sure this is the issue..cant hurt either way :-)
-
Clean sme10beta1, at prompt during install restored sme9.2 console backup - Can confirm it is the issue with mysql,init as JP wrote..so until beta 2 just follow JPs or my suggested workarounds..
-
just to add to Terry,
update is enought before you started the restore. if you did you must delete the responsible file and expand it after the update.
long story: this templated file is to upgrade mysql before restoring your db. it was using a syntax pre mariadb and pre systemd which fails now.
when mysql.init fails it keeps the failed file and other not yet processed to not lose anything.
usually expanding template will overwrite the file, but this precise situation is made to not do this.
so by clearing the wrong old file, and creating it with new code you can finish your process of restoring. but if you have restart from scratch better updating before.
-
TRhanks to all of you. I think I will try the fix from Terry, and see if this can do the job, I tried yesterday again, and thought that these fixes came in automatically, but I can see that this is not the case. So...
Thanks to you all. I will post again if I need further help.
I'm happy that it looks as if my prefered Linux server is on track again.
Best regards
Henning
-
I tried yesterday again, and thought that these fixes came in automatically, but I can see that this is not the case. So...
I'm happy that it looks as if my prefered Linux server is on track again.
Best regards
Henning
No worries mate, those updates will be in the normal updates repo shortly, so a straight yum update will pull them, we were just doing testing etc with different backups/restores etc just trying to make sure we didn't completely stuff up your server :-)
-
Hi Terry and JP
I have tried your suggested work around, but somehow it does not work.
When I try : yum update e-smith-mysql --enablerepo=smeupdates-testing
I get:
[root@sme-10b1 init]# yum update e-smith-mysql --enablerepo=smeupdates-testing
Indlæste udvidelsesmoduler: fastestmirror, post-transaction-actions, priorities, smeserver
Loading mirror speeds from cached hostfile
* base: mirror.softaculous.com
* smeaddons: mirrors.rbx.opencare.nl
* smeextras: mirrors.rbx.opencare.nl
* smeos: mirrors.rbx.opencare.nl
* smeupdates: mirrors.rbx.opencare.nl
* smeupdates-testing: mirrors.rbx.opencare.nl
* updates: mirrors.dotsrc.org
427 packages excluded due to repository priority protections
No packages marked for update
Sorry that some of the text is in Danish, but I expect that you get the meaning.
And When I try to find what version of e-smith-mysql that is installed, I get following:
[root@sme-10b1 /]# yum list e-smith-mysql
Indlæste udvidelsesmoduler: fastestmirror, post-transaction-actions, priorities, smeserver
Loading mirror speeds from cached hostfile
* base: mirror.softaculous.com
* smeaddons: mirrors.rbx.opencare.nl
* smeextras: mirrors.rbx.opencare.nl
* smeos: mirrors.rbx.opencare.nl
* smeupdates: mirrors.rbx.opencare.nl
* updates: mirrors.dotsrc.org
427 packages excluded due to repository priority protections
Installerede pakker
e-smith-mysql.noarch 2.6.0-18.el7.sme @anaconda/rawhide
So it looks as if I have to wait until e-smith-mysql becomes available in smeupdates :-(
Best regards
Henning
-
:-) Both updates are now in the normal smeupdates, a simple # Yum update - will pull them and any others, and I always doa reboot reconfig just to be safe, its nots always needed, but I do anyway..
Added: the pace has picked up again, much like the final days of the alpha, updates coming fast as we test and verify, often mul;ti packages at once..and you need to update them all to fix an issue..means the next Beta or even RC is not far away
-
Heya Henning
Heres another little trick I often use when testing, often repos haven't synced up and being down here it can sometimes take some hours or even more, use the full URL for the package and if there are any deps also the repos..
yum update http://mirror.canada.pialasse.com/releases/testing/10/smetest/x86_64/RPMS/smeserver-php-3.0.0-32.el7.sme.x86_64.rpm --enablerepo=smetest,smeupdates-testing
Be careful with above its a real update in the /smetest repo, know hat you are updating and why - eg there will be a Bug
-
Its not something you do all the time, only when its important to get a test done
-
:-) Both updates are now in the normal smeupdates, a simple # Yum update - will pull them and any others, and I always doa reboot reconfig just to be safe, its nots always needed, but I do anyway..
Added: the pace has picked up again, much like the final days of the alpha, updates coming fast as we test and verify, often mul;ti packages at once..and you need to update them all to fix an issue..means the next Beta or even RC is not far away
Thanx for update. I will try this once I'm done with my normal / official work, which means within the next 4 hours 8-)
-
:-) Both updates are now in the normal smeupdates, a simple # Yum update - will pull them and any others, and I always doa reboot reconfig just to be safe, its nots always needed, but I do anyway..
Added: the pace has picked up again, much like the final days of the alpha, updates coming fast as we test and verify, often mul;ti packages at once..and you need to update them all to fix an issue..means the next Beta or even RC is not far away
Now I could not wait any longer :-) .
I had to try and update as described.
I tried first to see if I through the server-manager could get the updates, but they did not show up.
Then I manually installed the updates for e-smith-mysql and e-smith-backup. And they arived as described.
I could install from my backup, and... without running on exact same IP verify that my two webpages can be accessed and I can access webmail on the new server as well.
Now I have one question.
When the Beta 2 arives, do I then have to perform the same thing again or.. will the update from Beta1 to Beta2 and further up, happen automatically?
And can I help with other verifications, while I have my test installation?
Best regards
Henning
-
When beta 2 or even perhaps RC1 hits, all updates will be incorporated,, no need to update again..
Actually both those updates are now in smeupdates so a simple yum update on a beta1 install will pull those and others that have also now been released.
Enjoy, big push now is validating contribs that have been resolved (just means have been migrated to sme10 and had a cursory look) and now need verifying install and operation is as expected, log any issues in the Bug for that contrib, see here
https://bugs.contribs.org/buglist.cgi?action=wrap&bug_status=RESOLVED&f1=bug_status&list_id=93146&o1=notequals&product=SME%20Contribs&v1=CLOSED
Added: and if it does what it is supposed to do, put that in the Bug as well
-
I could install from my backup, and... without running on exact same IP verify that my two webpages can be accessed and I can access webmail on the new server as well.
Yes, something to be aware of, when restoring from the sme9 backup it will set IP and domain name as per the sme9 install, so if you try and access the ip of what was the original sme10 install it may not play :-) just needs a Configure this Server from the console menu to get it firing on all cylinders again..
Enjoy, sme10 is good, real good :-)
-
Enjoy, big push now is validating contribs that have been resolved (just means have been migrated to sme10 and had a cursory look) and now need verifying install and operation is as expected, log any issues in the Bug for that contrib, see here
https://bugs.contribs.org/buglist.cgi?action=wrap&bug_status=RESOLVED&f1=bug_status&list_id=93146&o1=notequals&product=SME%20Contribs&v1=CLOSED
Added: and if it does what it is supposed to do, put that in the Bug as well
Thanks Terry. I will have a look at the list and see if I can find items that I can verify in the bug list you have mentioned :-)
I hope I still can read and understand Bugzilla, it's a few years since I last used bugzilla.
I will update my "normal" server to sme-10 but I will still have a test PC running SME-10 where I can "play around" and try various things.