Daniel,
I reply below with a copy to the Ringlink-open list. Please post
possible follow-up messages to Ringlink-open, since this is an issue
of general interest to Ringlink users.
Daniel Gwozdz wrote:
Well, I've had my ring running happy for 2 or 3 years now on my current host.
However, they've recently done an upgrade and now whenever ringlink creates a
new ring directory, I'm unable to access it. Curious thing is, I'm no longer
able to access my old directories, either. Here's what "support" had to say
(apparently "support" is a euphemism for "customer disservice")
"I think the problem was due to the ownership on
some of your files/directories being reset to the nobody
user. I have reset them back to your login name so you
should now be able to upload, modify, or delete in that
area of your account."
After the response, I tried to create another ring and its data dir is
unaccessible either, so I'm sure that for whatever reason Ringlink is being
allowed to create them this way.
On the flip side, I can now access my real ring's data via FTP and the crappy
online file manager, but I'm getting permission denied errors when I try to run
ring functions.
Does this mean that my server's running my scripts as admin or something? If
there's no ringlink side solution, what do I tell them to do since they seem to
need to be walked through solutions (you wouldn't believe the kind of crap I
had to go through to explain my problem and get them to see it. BTW, though
the dirs were unavailable via FTP, I was able to chdir to them via the online
file manager - inside I saw the core software for Neomail, which my server uses
as its email software. Luckily, though I could see the contents I got errors
whenever I tried to do something in that dir. When the permissions were
restored, my files came back, so I guess I just got redirected somehow.)
They have changed either file ownership or the user under which CGI
scripts are run as. Whatever they did, this should fix it:
1) Take a backup from admin.pl
2) Rename the /data directory to for instance /olddata
3) Create a new /data directory. Maybe there is a need to chmod
it 777, maybe not.
4) Move the backup file to the new /data directory
5) Run "Restore data" from admin.pl
That's it. If it works, you can delete the /olddata tree.
/ Gunnar