| Re: Xoops info and Backup Module Problems |
| by Anonymous on 2008/5/16 8:01:19 I had the open_basedir problem on a shared server when I first started. It was cured by making a /tmp directory my webspace root folder and then setting the php.ini file such that upload_tmp_dir and session.save_path pointed to this new directory. See if your CPanel allows you to alter some php settings. If not then ask your host to do it for you. |
| Re: Xoops info and Backup Module Problems |
| by Rocketfuel on 2008/5/15 22:27:23 Hi i did a little more digging on this issue and also contacted my host. For the following error i got them to increase the memory in the php.ini Fatal error: Allowed memory size of 16777216 bytes exhausted This did not fix this error, it seems when you try to back up the db for the first time in gzip it works perfect as you add modules and back up again it fails and gives a memory error(mabey it cant delete the original db files before it replaces them?)If you change this to back up to sql it works perfect, so mabey the back module is buggy in gzip mode? The only problem i can'nt fix is all the errors in Xoopsinfo/systeminfo tab Warning: is_executable() [function.is-executable]: open_basedir restriction in effect. File(/usr/local/sbin/mount) is not within the allowed path(s): My host stated the following open_basedir is installed on your server. it blocks scripts if they try to open files outside of their accounts. It is security patch and we can't disable it on a shared server Has anyone else got the same problem? and has anyone found a solution for this? a patch or something? Everything works on the site its just the errors in Xoopsinfo/systeminfo that worries me incase it causes issues later on down the track. Any help on this would be appreciated. Thanks |
| Re: Xoops info and Backup Module Problems |
| by stefan88 on 2008/5/13 14:32:39 Quote: why did it work when i first installed it? Hi, was it on the same server? And the same module varsion (phpsysinfo was introdused in xoopsinfo 2.13 I think)? If yes, probably there are some changes on the server - you may ask your host. As for the memory (Fatal error: Allowed memory size of 16777216 bytes exhausted) - your site grows and some action may require more memory than when it is new. You may try to do some cleaning... (check your sessions table for example) Xoopscare module may help in some tasks. You may try to do DB backup in your host control panel if you have phpmyadmin or somthing like it and copy the file structure with ftp... |
| Re: Xoops info and Backup Module Problems |
| by Rocketfuel on 2008/5/13 10:03:39 hey thanks for the reply. If alot of this is a server issue, why did it work when i first installed it? Has something changed mabey? |
| Re: Xoops info and Backup Module Problems |
| by stefan88 on 2008/5/13 9:54:19 Hi Quote: Warning: is_executable() [function.is-executable]: open_basedir restriction in effect. File(/usr/local/sbin/mount) is not within the allowed path(s): This is related to server settings. It is not a bug in XOOPS core, XOOPS module and not a bug in server. Just one of the ways the server may be set for security. But this prevents script (phpsysinfo) for working. Quote: Fatal error: Allowed memory size of 16777216 bytes exhausted This is aslo a server related. XOOPS needs more memory than you have. It is set in php.ini file and is controled by your hosting company. Quote: Warning: fopen(/uploads/backup/bkp0805130221_xoops_avatar.zip) [function.fopen]: failed to open stream: Permission denied in file /modules/backup/admin/backup.php line 156 This is a permission problem. First check that the folder /uploads/backup exists and check the cmod settings - try 0777. |
Search
Recent Posts
Who's Online
Donat-O-Meter
| Stats | |
| Goal: | $15.00 |
| Due Date: | Jul 31 |
| Gross Amount: | $0.00 |
| Net Balance: | $0.00 |
| Left to go: | $15.00 |
|
|