Came to login to my phpgedview setup today. First time in about a month or so and I'm getting a screenful of error messages that start with:
ERROR 2: fopen(./index/pgv-201001.log) : failed to open stream: Permission denied
0 Error occurred on in function fopen
1 called from line 662 of file authentication.php in function AddToLog
2 called from line 115 of file authentication.php in function userLogout
3 called from line 57 of file authentication.php in function authenticateUser
4 called from line 58 of file login.php
Warning: fopen(./index/pgv-201001.log) : failed to open stream: Permission denied in /home/MY_DIR/public_html/WEBSITE.xyz/ftree/includes/authentication.php on line 662
Warning: flock() expects parameter 1 to be resource, boolean given in /home/MY_DIR/public_html/WEBSITE.xyz/ftree/includes/authentication.php on line 663
And so on …
To teh best of my knowledge nothing has changed on the server side and I have no idea where to even begin on this.
Any ideas please?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-01-31
First place to start will be your web host, as something clearly HAS changed on your server. Either restrictions on the use of functions like fopen have been imposed, or permissions / ownership on your index folder may have been changed. These seem the most likely.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The ./index directory should be 777
its contents when installed should be 777, but as logfiles are written by the webprocess, they'll be created by and remain writeable by that process. If you've downloaded a logfile, and then re-uploaded it as your username, that might cause a problem as the ownership is different.
As tomorrow is February, I would just ensure that ./index has 777 permissions. When the logfile becomes pgv-201002.log it'll take care of itself.
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2010-02-01
Actually log files can get quite large by the end of the month, so it might just be that you've reached your space limit. Someone else had a similar issue just recently.
If thats the case, you might want to change it to archiving weekly rather than monthly, and use "Cleanup" (from the Admin page) regularly.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The hoster is still looking into the issue but I've set the folder to 777 - however I can't do that for any of the contents as I get 'permission denied'.
Owner according to filezilla is nobody…
That said I have just tried to login now and have done so successfully. - would this possibly be due to the log file change over? Which as a by the by the largest of these is 11kb dating back to sometime last year.
Thanks for the advice folks - I apprecieate it.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, setting the folder to 777 has allowed the webprocess ("nobody") to create a February log pgv-201002.log there when it needed to (today), which it can now use fine.
what permissions are currently set for the pgv-201001.log ? Strange that although that is owned by nobody, nobody can't open it and write to it. Unless of course the ./index directory permissions were stopping it. And as you've now corrected that, it'll be fine.
Mark
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm still waiting to hear back from the hoster as they may ghave done something / changed it / whatever and my setting permissions in fact did nothing :)
If I hear anything specific I'll report back.
Stuart
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Came to login to my phpgedview setup today. First time in about a month or so and I'm getting a screenful of error messages that start with:
ERROR 2: fopen(./index/pgv-201001.log) : failed to open stream: Permission denied
0 Error occurred on in function fopen
1 called from line 662 of file authentication.php in function AddToLog
2 called from line 115 of file authentication.php in function userLogout
3 called from line 57 of file authentication.php in function authenticateUser
4 called from line 58 of file login.php
Warning: fopen(./index/pgv-201001.log) : failed to open stream: Permission denied in /home/MY_DIR/public_html/WEBSITE.xyz/ftree/includes/authentication.php on line 662
Warning: flock() expects parameter 1 to be resource, boolean given in /home/MY_DIR/public_html/WEBSITE.xyz/ftree/includes/authentication.php on line 663
And so on …
To teh best of my knowledge nothing has changed on the server side and I have no idea where to even begin on this.
Any ideas please?
First place to start will be your web host, as something clearly HAS changed on your server. Either restrictions on the use of functions like fopen have been imposed, or permissions / ownership on your index folder may have been changed. These seem the most likely.
OK thanks for that …
Presuming the worst and it's not the hoster then what permissions should that folder and its contenst have?
Meanwhile I'll go raise an issue with my hoster.
Thanks.
The ./index directory should be 777
its contents when installed should be 777, but as logfiles are written by the webprocess, they'll be created by and remain writeable by that process. If you've downloaded a logfile, and then re-uploaded it as your username, that might cause a problem as the ownership is different.
As tomorrow is February, I would just ensure that ./index has 777 permissions. When the logfile becomes pgv-201002.log it'll take care of itself.
Mark
Actually log files can get quite large by the end of the month, so it might just be that you've reached your space limit. Someone else had a similar issue just recently.
If thats the case, you might want to change it to archiving weekly rather than monthly, and use "Cleanup" (from the Admin page) regularly.
The hoster is still looking into the issue but I've set the folder to 777 - however I can't do that for any of the contents as I get 'permission denied'.
Owner according to filezilla is nobody…
That said I have just tried to login now and have done so successfully. - would this possibly be due to the log file change over? Which as a by the by the largest of these is 11kb dating back to sometime last year.
Thanks for the advice folks - I apprecieate it.
Yes, setting the folder to 777 has allowed the webprocess ("nobody") to create a February log pgv-201002.log there when it needed to (today), which it can now use fine.
what permissions are currently set for the pgv-201001.log ? Strange that although that is owned by nobody, nobody can't open it and write to it. Unless of course the ./index directory permissions were stopping it. And as you've now corrected that, it'll be fine.
Mark
pgv-201002.log has permissions of 644 on it.
I'm still waiting to hear back from the hoster as they may ghave done something / changed it / whatever and my setting permissions in fact did nothing :)
If I hear anything specific I'll report back.
Stuart