Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Latest post by TBliss on Wednesday, 29 June 2022 14:07 CDT
Hi, I am trying to restore one of my website and while restoring the site it is showing the error message as shown in screen shot (could not open database dump file sql/site.s44) and also generatef 20-80gb worth of error log file in the new site. I have about 7 websites and I used another site's akeeba backup and able to restore with out any errors. Is there any thing that I need to tweak while generating the back up for the site where I am having trouble to restore?
Best Wishes,
Brigitte
Hello,
that seems a bit strange, is it possible to have access to the site you're trying to restore?
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
About the log files. Ask your host how to disable reporting PHP notices and deprecated notices to the log file. Since most software, like ours, needs to run on a wide range of PHP versions (the restoration script runs from 5.4 to 8.1 inclusive right now) we can't eliminate all notices / deprecated messages and you definitely don't need them in your log file. Only having errors or warnings and errors is a better option for a production (as opposed to development) site.
About the restoration issue, does the file installation/sql/site.s44 exist?
If not, did you get any errors during the archive extraction? If so, what was the extraction error?
Nicholas K. Dionysopoulos
Lead Developer and Director
🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi, My tech capabilities are a bit limited but hopefully good enough. Do not have any issues while generating the back up from the live original site. While restoring I get this error as well as large log files. I am not sure where to check the existence of installation/sql/site.s44. On the live site under public_html or in akeeba backup or else where. I do not see a installation folder under public_html either on the source site or destination site. To me, it looks like despite the error the restoration went through. Originally I had a .zip as the akeeba backup file. With this backup file the site did not get restored. Then I ran the configuration wizard which started producing JPA format and reduced size. With this back up, I still get the error but the restored site is functional. Since my other site back ups are working with out errors, wondering if there is a way I could fix this.
Best Wishes,
Brigitte
Most likely there's a "piece" of the site that is missing. My suggestion is to try restoration again, if you still have issues, please give me access to the site you want to restore (FTP + database access details)
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi, Thank you for looking into it. Here are the details. I am sure it is understood but to let you know this is a live site! (no down time please)
FTP Username:
[email protected]
FTP server:
ftp.goalaskatours.com
Password:
y77s3ehA}[E
FTP Port
403
Database details
Username = goalaska_goalask
Password = goalaska2011
DB=goalaska_goalaska
Kindly let me know once you are finished using then I can disable FTP for this server as we do not use the backend often.
Best Wishes,
Brigitte
I just tried to connect to the website using FTP, but my connection hangs and then gets a timeout. Is there any IP filtering? My current IP is 176.207.14.110
By the way, the backup archive that should be restored is already there? Can I simply overwrite everything currently existing on the website?
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi,
This is a live site and it is working normal as far as I can understand. Please do not make any changes to this site directly.
I have added the akeeba backup to the sites' public_html. I have also added your IP to whitelists (just in case). Let me know if you have access now.
Best Wishes,
Brigitte
In order to understand what happened, I'd have to perform restoration on your site again.
However, if everything is working fine, we can simply put a pin on this topic and keep an eye on it. If you see something weird, we can perform restoration once again.
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Davide,
If you need to test, I can give you a test site which has akeeba backup of the live site. Following are the details. It also has the akeeba backup from the live site. Please install on this site and then you can see the error. Kindly do not modify the live site (goalaskatours.com). Once you find out the reason why the backup is not working, then we can tweak the live site accordingly, if needed.
Test site
FTP Username: [email protected]
FTP server: ftp.alaskatravelnetworkgroup.com
FTP & explicit FTPS port: 403
password:
6bMiWHh8L4Db(eijL%
Database details
User Name: alaskatravelnetw_goak12
Password: ak969427tnk
Please let me know if you need any further details
Best Wishes,
Brigitte
Thank you for the test site. I'd need database name and host as well
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi,
Here are the complete details for the test site
Database type: MySQLi
Database Server host name: localhost
User Name: alaskatravelnetw_goak12
Password: ak969427tnk
Database name: alaskatravelnetw_goak12
database table name prefic: alaskatravelnetw_
FTP Username: [email protected]
FTP server: ftp.alaskatravelnetworkgroup.com
FTP & explicit FTPS port: 403
password:
6bMiWHh8L4Db(eijL%
Please feel free to let me know if I missed out something
Best Wishes,
Brigitte
Hello,
thank you for access details. The is indeed that there's a missing SQL file, so the restoration hangs. This means that the backup is no good, can you please try to take another one?
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi,
There is another issue when we try to restore the backup to a new site. It is giving super large log files. This time it is around 250 GB! My server (which hosts the test site) does not have so much of space. So I deleted the log file. When you do fresh installation, in case it fails, kindly check the log file size and delete it from our test site so that the server does not run out of disk space and stop loading our live sites. The test site login that I have provided has the access to the log files as well (one level above public_html). A new copy of the backup is under public_html.
Hope this helps to find out the problem.
Best wishes,
Brigitte
I did some troubleshooting and I found the source of the error.
Since there was a missing file, we have a loop that never finishes. This loop is generating an error that fills up your disk, so we can not even write down a single line to keep the session alive and proceed with restoration.
We are going to fix this issue, but you should get in touch with your host reporting that you have a "rogue" PHP process that doesn't stop, so they have to kill it.
This is something that only your host can do.
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Davide,
Thank you for your reply. The test account that I gave you had an unlimited quota and I did not realize that the restoration of akeeba backup is creating super large file. It crashed our server few times. Now I am aware of this problem, I have already limited the quota for the test site so that it does not kill our entire server disk space.
You can remove the log file from the test site and then you can write one more time or I can do that for you. I am not sure if you need the log file. Please let me know
Keep me updated on the fix.
We have a dedicated server. If you can give me some guidance, probably I can kill the rogue PHP process myself. If a restart of the server does it, then I can do that as well.
Best Wishes,
Brigitte
I think the easiest thing to do is to restart the server, so you'll be 100% sure to work on a clean state. Plan it accordingly with your traffic load and then let me know, so I can confirm the fix.
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Davide,
I restarted the server. The process should be killed now
Best Wishes,
Brigitte
Thank you!
I can confirm that everything is working as expected, I was able to restore your database.
The fix will be included in the next version, I think you'll never have the same issue again, since everything was triggered by a missing part of the SQL database.
Thanks again for the report!
Davide Tampellini
Developer and Support Staff
🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!
Hi Davide,
Thank You. Will wait for the update for akeeba backup
Best Wishes,
Brigitte
Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.
Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!