Geeklog Forums

Ok..I just installed Geeklog over @ www.ghost-hunters.us, which is forwarded to sourceforge. I have geeklog set up, and tried to chmod articles and user photos with 775, and 777 via chmod, via putty and WinSCP. I can't seem to stop getting that error, even though most things report its working. I deleted the install directory for geeklog so can't do the check easily. Does ANYONE have any thoughts as to why sourceforge is being a dink!? I tried the install documentation, tried searching and found that nothing is working! HELP

Also check the permissions of the images directory.

bye, Dirk

Uh..yeah..not to be rude but uh...tried chmoding it...its not working..

Anyone with sourceforge experience, PLEASE HELP!

drwxrwsrwx 2 erichweihrauch teghc 4096 Feb 20 19:01 articles
just to give an example..

Testing your Geeklog installation ...

Testing logs directory /home/groups/t/te/teghc/htdocs/logs/ ...
Could not open error.log and access.log for writing.
Please check that you have set the logs directory and the files error.log and access.log in that directory to chmod 775.
Current permissions for logs: 777
Current permissions for error.log: 777
Current permissions for access.log: 777

Testing backend directory /home/groups/t/te/teghc/htdocs/backend/ ...
Could not open the RSS file /home/groups/t/te/teghc/htdocs/backend/geeklog.rss for writing.
Please check that you have set both the backend directory and the geeklog.rss file in that directory to chmod 775.
Current permissions for backend: 775
Current permissions for geeklog.rss: 775

User photos are disabled - userphotos directory not tested.

Testing articles directory /home/groups/t/te/teghc/htdocs/images/articles/ ...
Could not write to /home/groups/t/te/teghc/htdocs/images/articles/.
Please make sure this directory exists and is set to chmod 775.
Current permissions for articles: 777

Testing topics directory /home/groups/t/te/teghc/htdocs/images/topics/ ...
Could not write to /home/groups/t/te/teghc/htdocs/images/topics/.
Please make sure this directory exists and is set to chmod 775.
Current permissions for topics: 777

Testing backups directory /home/groups/t/te/teghc/htdocs/backups/ ...
Could not write to /home/groups/t/te/teghc/htdocs/backups/.
Please make sure this directory exists and is set to chmod 775.
Current permissions for backups: 775

Testing data directory /home/groups/t/te/teghc/htdocs/data/ ...
Could not write to /home/groups/t/te/teghc/htdocs/data/.
Please make sure this directory exists and is set to chmod 775.
Current permissions for data: 775

Results: 6 of 7 tests performed: 0 successful, 6 failed.
Test failed!

Warning! Your Geeklog site is not set up properly. Please fix the errors listed above!

Note: If the above instructions tell you to chmod files and/or directories to 775 but they already are at 775, try chmod 777 instead.

Testing your Geeklog installation ...

Testing logs directory /home/groups/t/te/teghc/htdocs/logs/ ...
Could not open error.log and access.log for writing.
Please check that you have set the logs directory and the files error.log and access.log in that directory to chmod 775.
Current permissions for logs: 775
Current permissions for error.log: 777
Current permissions for access.log: 777

Testing backend directory /home/groups/t/te/teghc/htdocs/backend/ ...
Could not open the RSS file /home/groups/t/te/teghc/htdocs/backend/geeklog.rss for writing.
Please check that you have set both the backend directory and the geeklog.rss file in that directory to chmod 775.
Current permissions for backend: 775
Current permissions for geeklog.rss: 775

User photos are disabled - userphotos directory not tested.

Testing articles directory /home/groups/t/te/teghc/htdocs/images/articles/ ...
Could not write to /home/groups/t/te/teghc/htdocs/images/articles/.
Please make sure this directory exists and is set to chmod 775.
Current permissions for articles: 775

Did you figure this out?

Geeklog was hosted at SourceForge a few years ago and I remember that we had to chmod 777 pretty much every file and directory that should be writable. Of course, this was pretty insecure and caused a big data loss one day. It's possible that SF has changed something since then ...

bye, Dirk