Unable to backup

[lighterrr]

Hi,

I tried to do a backup from the PhotoPost Database Backup but get the following errors...

Warning: filesize(): open_basedir restriction in effect. File(/pp_admingroups.sql) is not within the allowed path(s): (/home/lighter/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/lighter/public_html/gallery/adm-backup.php on line 76
Warning: pp_admingroups.sql is 0 bytes or did not get created.
Warning: filesize(): open_basedir restriction in effect. File(/pp_admlog.sql) is not within the allowed path(s): (/home/lighter/:/usr/lib/php:/usr/local/lib/php:/tmp) in /home/lighter/public_html/gallery/adm-backup.php on line 76
Warning: pp_admlog.sql is 0 bytes or did not get created.

[Chuck S]

What is the backup path in the admin global options set to?

[lighterrr]

The Directory for backups is empty, should i put something there?

[Chuck S]

Yes you need to put the server path to the backup directory and make sure its 777

[lighterrr]

Thanks, i manage to get pass that, but while doing the backup i got this instead...

Results:

Warning: pp_admingroups.sql is 0 bytes or did not get created.Warning: pp_admlog.sql is 0 bytes or did not get created.Warning: pp_categories.sql is 0 bytes or did not get created.Warning: pp_comments.sql is 0 bytes or did not get created.Warning: pp_ecards.sql is 0 bytes or did not get created.Warning: pp_exif.sql is 0 bytes or did not get created.Warning: pp_favorites.sql is 0 bytes or did not get created.Warning: pp_ipcache.sql is 0 bytes or did not get created.Warning: pp_iponline.sql is 0 bytes or did not get created.Warning: pp_laston.sql is 0 bytes or did not get created.Warning: pp_notify.sql is 0 bytes or did not get created.Warning: pp_photos.sql is 0 bytes or did not get created.Warning: pp_settings.sql is 0 bytes or did not get created.Warning: pp_sort.sql is 0 bytes or did not get created.Warning: pp_sortmemb.sql is 0 bytes or did not get created.Warning: pp_usergroups.sql is 0 bytes or did not get created.Warning: pp_users.sql is 0 bytes or did not get created.

You should double-check your .sql files to be sure the backup completed successfully.

[Chuck S]

Did you specify the path to mysqldump in the admin options as well and verify that the path is correct on the server?

[lighterrr]

Yes i have verify with my host that the mysqldump is /usr/bin/mysqldump

For the server path i have /home/name/public_html/gallery/backup

Are those correct?

[Chuck S]

Only you would know if those are correct.

There is also another thread where I posted this bug fix for adm-backup.php

find this line

$dumpcmd = "$mysqldumppath --opt -h $host -u$mysql_user -p$mysql_password $database ";

replace with

$dumpcmd = "{$Gbobals['mysqldumppath']} --opt -h $host -u$mysql_user -p$mysql_password $database ";

[snoopy5]

Hi,

I just upgraded from PP4.8.2 to 4.8.6. Everything worked fine. It is still in "closed" modus.

I tried now to backup this new upgrade. I get the same warnings as described above.

My backup directors is set to 777. The paths to the backup directory is also o.k. But I am not sure what you mean with "path to mysqldump". Should there be a file called "mysqldump"? If yes and I do not find it on my server, how to create one?

Thanks in advance

[snoopy5]

Originally Posted by omegatron

Only you would know if those are correct.

There is also another thread where I posted this bug fix for adm-backup.php

find this line

$dumpcmd = "$mysqldumppath --opt -h $host -u$mysql_user -p$mysql_password $database ";

replace with

$dumpcmd = "{$Gbobals['mysqldumppath']} --opt -h $host -u$mysql_user -p$mysql_password $database ";

Forgot to mention, I made also already this change dscribed above in the adm-backup.php file

[Chuck S]

Does the backup path exist and 777?

Are you sure of the path to mysqldump

Just an FYI mysql on external servers wont work with this if thats the case

[snoopy5]

mmmmhhh,

I am not sure whether I understand you correctly...

I have on one server a couple of photopost installations, although some share the same database). I now only upgraded one of them as a test-upgrade. The back up functionality worked fine before the upgrade. Only after the upgrade it causes these messages:
--------------
Warning: hassydePP_admingroups.sql is 0 bytes or did not get created.Warning: hassydePP_admlog.sql is 0 bytes or did not get created.Warning: hassydePP_categories.sql is 0 bytes or did not get created.Warning: hassydePP_comments.sql is 0 bytes or did not get created.Warning: hassydePP_ecards.sql is 0 bytes or did not get created.Warning: hassydePP_exif.sql is 0 bytes or did not get created.Warning: hassydePP_favorites.sql is 0 bytes or did not get created.Warning: hassydePP_ipcache.sql is 0 bytes or did not get created.Warning: hassydePP_iponline.sql is 0 bytes or did not get created.Warning: hassydePP_laston.sql is 0 bytes or did not get created.Warning: hassydePP_notify.sql is 0 bytes or did not get created.Warning: hassydePP_photos.sql is 0 bytes or did not get created.Warning: hassydePP_settings.sql is 0 bytes or did not get created.Warning: hassydePP_sort.sql is 0 bytes or did not get created.Warning: hassydePP_sortmemb.sql is 0 bytes or did not get created.Warning: hassydePP_usergroups.sql is 0 bytes or did not get created.Warning: hassydePP_users.sql is 0 bytes or did not get created.Warning: leicade_admingroups.sql is 0 bytes or did not get created.Warning: leicade_admlog.sql is 0 bytes or did not get created.Warning: leicade_categories.sql is 0 bytes or did not get created.Warning: leicade_comments.sql is 0 bytes or did not get created.Warning: leicade_ecards.sql is 0 bytes or did not get created.Warning: leicade_exif.sql is 0 bytes or did not get created.Warning: leicade_favorites.sql is 0 bytes or did not get created.Warning: leicade_ipcache.sql is 0 bytes or did not get created.Warning: leicade_iponline.sql is 0 bytes or did not get created.Warning: leicade_laston.sql is 0 bytes or did not get created.Warning: leicade_notify.sql is 0 bytes or did not get created.Warning: leicade_photos.sql is 0 bytes or did not get created.Warning: leicade_settings.sql is 0 bytes or did not get created.Warning: leicade_sort.sql is 0 bytes or did not get created.Warning: leicade_sortmemb.sql is 0 bytes or did not get created.Warning: leicade_usergroups.sql is 0 bytes or did not get created.Warning: leicade_users.sql is 0 bytes or did not get created.



---------------

Backup works fine with all other installations on the same server, which have not yet been upgraded.

In admin panel of the upgrade installation, I can see the right path to the "backup" folder. I also see sql files with the right datestamp in that folder after I did the back-up. This is why I find those messages strange.

In admin panel, I also can see the path to mysqldump "/usr/bin/mysqldump"

OH, maybe it has something to do with a non-upgraded version, which is using the same database, but different prefixes?

Is it safe to upgade versions that sare the same database but use different prefixes? Or does this destroy something in the not-yet upgraded version/database settings?

photo-uploads work by the way in the upgraded version...

[snoopy5]

FYI

... I just checked in the backup folder. The files have the right datestamps, but the file-size is always 0.

[snoopy5]

... more information:

I called my webhoster. It is a dedicated server. They say, the path would be : usr/lib/mysqldump

I changed that in the admin/options, but the result is the same

My webhoster sais, I have no access to this mysqldump and can neither see it on my server. But it would work correctly.

[Chuck S]

Thats why it wont work then. Backup things like this only work when mysql is on the same server and you have access to use mysqldump

Of all the installations I have done I would say only 50% of users can use the backup utility

[snoopy5]

Originally Posted by omegatron

Thats why it wont work then. Backup things like this only work when mysql is on the same server and you have access to use mysqldump

Of all the installations I have done I would say only 50% of users can use the backup utility

But why it does work with my other photopost installations on the same server?

Therefore the problem must be somewhere else.

I saw in the 4.8.5 and 4.8.6 announcemets, that you changed the upgrade script. Since I did an upgrade from 4.82 directly to 4.8.6 with the 4.8.6 upgrade script, could that have caused the problem?

Is the old 4.8.5 file anywhere for download to test this?

[Chuck S]

The change I made to 4.8.6 is well documented. I beleive you stated you made this change to the adm-backup file.

If your global option mysqldump command is entered right and the file is indeed altered accordingly it should work fine.

You would need to post your command when backing up here. I know you posted the 0 table error here but where is the line that shows the mysqldump command? This is what I would have to see to see whats going on.

[snoopy5]

Originally Posted by omegatron

The change I made to 4.8.6 is well documented. I beleive you stated you made this change to the adm-backup file.

If your global option mysqldump command is entered right and the file is indeed altered accordingly it should work fine.

no, I did not mean the ´code change in the adm-backup file. I mean the original upgrade script of PP4.85 which is in the original zip file of 4.8.5

In the announcement of version 4.8.6 it was mentioned, that you replaced various upgrade scripts with only one:

"There is a new upgrade.php script which can be used for all future upgrades; however, the upgrade from 4.85 to 4.86 does not require any database changes."

PhotoPost 4.86 Update posted

So if I could download the original 4.8.5 zip file, I could try to upgrade first to 4.8.5 to see whether the problem exists already there.

Again, all my other installations on the same server do not have this backup problem. But they are all version 4.8.2.

[Chuck S]

This should be a working adm-backup.php file if your running 4.8.6

The backup dir and backup command are in the database options

Content visible to verified customers only.

[snoopy5]

I investigated further. If looked at the text when doing successfully a backup on another (not yet upgraded) photopost 4.8.2 installation.

it shows me this in the first 2 lines:
------------
Command being used to execute dumps (specific tables are executed individually):

/usr/bin/mysqldump --opt -h localhost -uxxxxx -pyyyyy dbzzzz
-----------

after that the normal backup files.

If I compare this to the backup-screen of the upgraded installation, it is missing the path in line 2 in the upgraded version. See below:

------------
Command being used to execute dumps (specific tables are executed individually):

--opt -h localhost -uxxxx -pyyyy dbzzzz
-----------

So this could be a hint to the problem...