Topic: DB failure.

[Gerald]

I have a number of Post Nuke web sites running on a SME server. They have been working just fine for quite a long time. Now one of them is experiencing a problem. The front page nolonger displays, the following error message appears:

DB Error: getArticles: 1: Can't create/write to file '/tmp/#sql573_4e_0.MYI' (Errcode: 13)

I have reset the server hoping the data base would reset and the problem would go away. No luck. The site can be viewed at: http://www.emeraldlifestylehomes.com/

TIA

[Ergin]

Do you have the rights to WRIE to /tmp ?
# chmod 777 /tmp "might" help.

[Gerald]

I have attempted to find the tmp directory involved, but haven't as of yet. What has me confused is the fact that this site has been working perfectly for some time. I haven't made any changes to any persmissions so I don't know why it would just fail.

[Ergin]

Can you make sure that you have /tmp catalouge ?

# cd /
# ls

If you dont have /tmp then create /tmp and chmod

# mkdir tmp
# chmod 777 tmp

[Gerald]

I found that the /tmp directory that had improper permissions was at the root. I changed them and the problem went away. What I don't know is how the permissions were changed as the web site had been working properly for some time and other on the same server continued to work. Another strange thing has occured. About a week ago three servers, all at the same location, but running different versions of e-smith, i.e. 4.1.2, 5.1.2 and 5.00 began sending me this message each day:

/etc/cron.daily/slocate.cron:

updatedb: invalid option -f
Usage: updatedb [--localpaths='dir1 dir2...'] [--netpaths='dir1
dir2...']
       [--prunepaths='dir1 dir2...'] [--output=dbfile] [--netuser=user]
       [--old-format] [--version] [--help]
 
I don't know why the message or if I should be concerned about the "invalid option -f" statement.