Koozali.org: home of the SME Server

tried to chmod.. and then everything went offline..

Kristian Groenevet

tried to chmod.. and then everything went offline..
« on: April 29, 2003, 01:15:41 AM »
Okay.. I got report from the users on my (very new) server that they couldnt chmod files in their own directories..

So I decided to try and fix this.. searched up some info on the subject.. (should probably have researched a bit more)

and then I tried to give MY account on the server access to chmod all the files in the /primary directory.. so I punched this command:

[root@unityouth files]# chown -R eyedee.hosted primary


when I had done that.. I still didnt have access to chmod files in the /primary directory.. AND I had also accomplished to somehow block access for all http requests to the server..

but I do manage to connect to the server with the http://hostname/server-manager thing.. so I dont know..

Any clues/ideas?

Terry Brummell

Re: tried to chmod.. and then everything went offline..
« Reply #1 on: April 29, 2003, 02:11:45 AM »
Sounds to me like you changed permissions on the primary website now apache doesn't have rights to read the directory.  Try setting the permissions back to admin:shared or root:root and I think you'll see your website come back online.

Terry

Kristian Groenevet

Re: tried to chmod.. and then everything went offline..
« Reply #2 on: April 29, 2003, 04:19:01 AM »
hmm.. nope.. I tried both of them.. and it didnt work.. seems like Ive "broken" something here.. but I have no idea what.. ssh and email from remote access works fine.. its just the http that doesnt work.. and Ive modified the hosts.allow and hosts.deny files to approve all incomming traffic now aswell.. this is strange.. very strange..

Jesper Holck

Re: tried to chmod.. and then everything went offline..
« Reply #3 on: April 29, 2003, 01:10:35 PM »
What does the http error log say (/var/log/httpd/error_log) ?

Michael Soulier

Re: tried to chmod.. and then everything went offline..
« Reply #4 on: May 03, 2003, 02:14:49 AM »
Kristian Groenevet wrote:
>
> Okay.. I got report from the users on my (very new) server
> that they couldnt chmod files in their own directories..
>
> So I decided to try and fix this.. searched up some info on
> the subject.. (should probably have researched a bit more)
>
> and then I tried to give MY account on the server access to
> chmod all the files in the /primary directory.. so I punched
> this command:
>
> [root@unityouth files]# chown -R eyedee.hosted primary
>
>
> when I had done that.. I still didnt have access to chmod
> files in the /primary directory.. AND I had also accomplished
> to somehow block access for all http requests to the server..

What version of SME is this? In 5.6 the non-priviledged web server runs as user www, in group "shared". The files should belong to group shared, and be readable to such. Directories should additionally be SGID.

Mike