I am running
PHP 4.3.1
Apache 2
Mysql 4.0.18
xoops 2.0.6

I have finally successfully installed XOOPS but on entering the site for the first time I am greeted with the header and footer only.

I managed to manually get to user.php and login and then manually go to admin.php for the first time. I found the debugging modes and turned on mysql/blocks debugging.

On trying to view the front page again there were still no blocks but I finally notice that firefox was blocking a pop-up. In the popup I found this error

SELECT b.* FROM xoops_newblocks b, xoops_block_module_link m WHERE m.block_id=b.bid AND b.isactive=1 AND b.visible=1 AND m.module_id IN (0,-1) AND b.bid IN (1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16) ORDER BY b.weight,b.bid
Error number: 1
Error message: Can't create/write to file '/root/tmp/#sql_2aeb_0.MYI' (Errcode: 13)

Why is XOOPS attempting to write here and how do I stop that?

Stu.

If I
chmod 777 /root
chmod 777 /root/tmp
it works but that is not how I want to leave my root acount. Does anyone know why XOOPS want to write to /root/tmp? Apache2 instantiates itself as 'root' but all child processes are run by user 'apache'.

Is it because the files are owned by 'root' that it is using root's tmp? What if I changed the ownership to someone else?
Or is there a config setting that points to /root/tmp?

I tried changing the ownership of all the files to the httpd2 user 'apache' before re-installing. That is not the problem it appears. So it is either a PHP config setting somewhere or a XOOPS setting. I will recheck phpinfo(). Nope nothing obvious there.

It seems that it is just a temp file that gets written but not left. /root/tmp/#sql_2aeb.MYI

Can a developer out there assist me in troubleshooting this please. It is rather urgent. My mac installed without a hitch yet this linux install has been going over a few days ironing out access issues, ownership issues, missing modules etc.

Stu.

New problem.

My linux system keeps looking after me by correcting the file permissions on /root and /root/tmp so even if I set /root/tmp to 777 after so many minutes it reverts and the blocks once again disappear.

It only seems to be the menu blocks that seem to want to temporarily write to /root/tmp

Stu

Hi Stu,

I think it's your MySQL setting's problem. MySQL uses $TMPDIR to store temporary files, these files are usually hidden and removed once mysqld is terminated. If you do not have $TMPDIR set for mysql, it uses system default, usually /tmp, /var/tmp, etc, in your case, MySQL picks up /root/tmp, which is the $TMPDIR under root environment.

To fix this problem, you can specify a tmpdir path to a directory which is writeable by globle user, to do this, just add tmpdir to the option file (my.cnf) under [mysqld] section.

Good luck.

Yay!!!!

Your a champion myc1229.

After some odd restarts and "can't connect" messages it has all settled down and that seems to be the fix. Thank you.

I hope this will help some other people that come across the same problem. I know someone else has but they got no answer. This will likely help them too.

Stu.