15 lines
10 KiB
Text
15 lines
10 KiB
Text
version=pmwiki-1.0.5
|
|
newline=²
|
|
text=Under certain conditions PmWiki may exit with an error message. This page describes the most common errors, their causes, and how the WikiAdministrator can resolve them. For more information, feel free to email mailto:pmwiki-help@pmichaud.com, or perhaps check out the [[http://www.pmichaud.com/lists/pmwiki-users pmwiki-users mailing list archives]] and see if your information is there.²²!!![[#Setgid]]Error: PmWiki wants setgid permissions...²²For security reasons, most web server software executes scripts such as @@pmwiki.php@@ under a special restricted account and not as the user who owns the script. Usually this special account has a name such as ''nobody'', ''www'', ''apache'', or ''httpd''. Since scripts typically run under one of these special accounts, when PmWiki creates its various files and directories they are usually owned by the special user account, and therefore the "real" account holder may not have permission to read or delete those files.²²To prevent this from happening, it is a good idea to have ''set group id'' (setgid) permissions on any directories that PmWiki creates. Setgid permissions will cause the files and directories created by @@pmwiki.php@@ to have the same group ownership as the account holder, and thus the account holder will be able to read, edit, and delete them on the server. To enable setgid permissions, simply do "@@chmod 2777 ''dir''@@" on the parent of the directory that PmWiki is trying to create. In most cases this is the directory containing the @@pmwiki.php@@ file. After changing the directory permissions, reload the @@pmwiki.php@@ page and the directory should be created. Once PmWiki has created the directory it needs, the permissions of the parent directory can be restored to normal (usually "@@chmod 755 ''dir''@@").²²Some web hosting providers and systems do not allow directories with set group id permissions. In these cases, one can arrange for all directories and files that PmWiki creates to have full read/write permissions by adding the line² umask(0);²to the ''local/config.php'' configuration file (see LocalCustomizations). Then change the parent directory's permissions to 777 ("@@chmod 777 ''dir''@@") and reload ''pmwiki.php'' to let it create the directory it needs. After this is done, the permissions of the parent can be restored to normal ("@@chmod 755 ''dir''@@).²²Note that setting @@umask(0)@@ will cause all files and directories that PmWiki creates to have global read and write privileges--i.e., anyone that can log into the server could potentially delete or modify these files. If this is not acceptable, you can also put² $ForceMkdir=1;²in ''local/config.php'' instead of the @@umask(0)@@ described above. This will cause @@pmwiki.php@@ to try to create the directory even if the directory's permissions won't be "optimal". Note that with $ForceMkdir set PmWiki may create files and directories that the account owner can not easily delete.²²Finally, if none of the above solutions work for your site/installation, send an email message to mailto:pmwiki-help@pmichaud.com or mailto:pmwiki-users@pmichaud.com describing your setup and the problems you are encountering.²²!!! [[#Mkdir]]Error: Cannot create ''dir''...(mkdir() failed)²²PmWiki attempted to create the directory given by ''dir'' and was unable to do so. Usually this is because the parent directory for ''dir'' doesn't have the appropriate permissions for the ''nobody'' user (or whatever user the server is running scripts as) to be able to create the directory. See the entry above regarding "setgid permissions" for more details.²²!!! [[#Lockfile]]Error: Cannot acquire lockfile²²PmWiki creates a lock file called "''.flock''" in the ''wiki.d'' directory that it uses to prevent multiple simultaneous writes to the same file. When PmWiki is unable to acquire the lock file, it usually means that something or someone on the host server has changed the ownerships or permissions on the ''wiki.d'' directory such that PmWiki can no longer write to the files in that directory. This usually requires the assistance of the server administrator to fix. See FilesAndDirectories for more details about needed file ownerships and permissions.²²!!! [[#Notfound]]Error: File not found²²If your server is running Apache 2.0, you probably need to add the "AcceptPathInfo On" statement to your web server configuration (from step #4 of the Installation instructions. If your server is running something else, or you're still getting this error, try doing "$EnablePathInfo=0" in ''config.php'' and see if that resolves the problem. Or send email to mailto:pmwiki-help@pmichaud.com.²²%trail%<<|PmWiki.DocumentationIndex|>>
|
|
time=1090781709
|
|
diff:1090780464:1090780464:=1,29c1²< Under certain conditions PmWiki may exit with an error message. This page describes the most common errors, their causes, and how the WikiAdministrator can resolve them. For more information, feel free to email mailto:pmwiki-help@pmichaud.com, or perhaps check out the [[http://www.pmichaud.com/lists/pmwiki-users pmwiki-users mailing list archives]] and see if your information is there.²< ²< !!![[#Setgid]]Error: PmWiki wants setgid permissions...²< ²< For security reasons, most web server software executes scripts such as @@pmwiki.php@@ under a special restricted account and not as the user who owns the script. Usually this special account has a name such as ''nobody'', ''www'', ''apache'', or ''httpd''. Since scripts typically run under one of these special accounts, when PmWiki creates its various files and directories they are usually owned by the special user account, and therefore the "real" account holder may not have permission to read or delete those files.²< ²< To prevent this from happening, it is a good idea to have ''set group id'' (setgid) permissions on any directories that PmWiki creates. Setgid permissions will cause the files and directories created by @@pmwiki.php@@ to have the same group ownership as the account holder, and thus the account holder will be able to read, edit, and delete them on the server. To enable setgid permissions, simply do "@@chmod 2777 ''dir''@@" on the parent of the directory that PmWiki is trying to create. In most cases this is the directory containing the @@pmwiki.php@@ file. After changing the directory permissions, reload the @@pmwiki.php@@ page and the directory should be created. Once PmWiki has created the directory it needs, the permissions of the parent directory can be restored to normal (usually "@@chmod 755 ''dir''@@").²< ²< Some web hosting providers and systems do not allow directories with set group id permissions. In these cases, one can arrange for all directories and files that PmWiki creates to have full read/write permissions by adding the line²< umask(0);²< to the ''local/config.php'' configuration file (see LocalCustomizations). Then change the parent directory's permissions to 777 ("@@chmod 777 ''dir''@@") and reload ''pmwiki.php'' to let it create the directory it needs. After this is done, the permissions of the parent can be restored to normal ("@@chmod 755 ''dir''@@).²< ²< Note that setting @@umask(0)@@ will cause all files and directories that PmWiki creates to have global read and write privileges--i.e., anyone that can log into the server could potentially delete or modify these files. If this is not acceptable, you can also put²< $ForceMkdir=1;²< in ''local/config.php'' instead of the @@umask(0)@@ described above. This will cause @@pmwiki.php@@ to try to create the directory even if the directory's permissions won't be "optimal". Note that with $ForceMkdir set PmWiki may create files and directories that the account owner can not easily delete.²< ²< Finally, if none of the above solutions work for your site/installation, send an email message to mailto:pmwiki-help@pmichaud.com or mailto:pmwiki-users@pmichaud.com describing your setup and the problems you are encountering.²< ²< !!! [[#Mkdir]]Error: Cannot create ''dir''...(mkdir() failed)²< ²< PmWiki attempted to create the directory given by ''dir'' and was unable to do so. Usually this is because the parent directory for ''dir'' doesn't have the appropriate permissions for the ''nobody'' user (or whatever user the server is running scripts as) to be able to create the directory. See the entry above regarding "setgid permissions" for more details.²< ²< !!! [[#Lockfile]]Error: Cannot acquire lockfile²< ²< PmWiki creates a lock file called "''.flock''" in the ''wiki.d'' directory that it uses to prevent multiple simultaneous writes to the same file. When PmWiki is unable to acquire the lock file, it usually means that something or someone on the host server has changed the ownerships or permissions on the ''wiki.d'' directory such that PmWiki can no longer write to the files in that directory. This usually requires the assistance of the server administrator to fix. See FilesAndDirectories for more details about needed file ownerships and permissions.²< ²< !!! [[#Notfound]]Error: File not found²< ²< If your server is running Apache 2.0, you probably need to add the "AcceptPathInfo On" statement to your web server configuration (from step #4 of the Installation instructions. If your server is running something else, or you're still getting this error, try doing "$EnablePathInfo=0" in ''config.php'' and see if that resolves the problem. Or send email to mailto:pmwiki-help@pmichaud.com.²\ No newline at end of file²---²> Describe ErrorMessages here.²\ No newline at end of file²
|
|
author=ramsey
|
|
author:1090780464=ramsey
|
|
host:1090780464=24.53.105.4
|
|
name=PmWiki.ErrorMessages
|
|
host=24.53.105.4
|
|
agent=Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7) Gecko/20040706 Firefox/0.9.1
|
|
rev=2
|
|
diff:1090781709:1090780464:=29,31c29²< If your server is running Apache 2.0, you probably need to add the "AcceptPathInfo On" statement to your web server configuration (from step #4 of the Installation instructions. If your server is running something else, or you're still getting this error, try doing "$EnablePathInfo=0" in ''config.php'' and see if that resolves the problem. Or send email to mailto:pmwiki-help@pmichaud.com.²< ²< %trail%<<|PmWiki.DocumentationIndex|>>²\ No newline at end of file²---²> If your server is running Apache 2.0, you probably need to add the "AcceptPathInfo On" statement to your web server configuration (from step #4 of the Installation instructions. If your server is running something else, or you're still getting this error, try doing "$EnablePathInfo=0" in ''config.php'' and see if that resolves the problem. Or send email to mailto:pmwiki-help@pmichaud.com.²\ No newline at end of file²
|
|
author:1090781709=ramsey
|
|
host:1090781709=24.53.105.4
|