Error Failed To Create Lock File Tmp Awstats
to Troubleshooting Back to Centova Cast v2 Back to Top Knowledge Base | Centova Cast v2 | Troubleshooting Unable to create lock file / Failed to start up concurrent users module Question: I'm receiving the following error whenever the Centova Cast cron job runs: Unable to create lock file: Permission denied Failed to start up concurrent users module! How do I fix this? Answer: This error is actually generated by PHP, not Centova Cast, and has nothing to do with Centova Cast itself. The nature of the problem will depend on the exact error message shown after Unable to create lock file:, however if you see Permission denied as shown above, it's likely that your /tmp/ directory is not writable. Running the following commands should fix it: chmod 0777 /tmp chmod +t /tmp Product Details Customer Support Company Centova Cast Billing Products Documentation Knowledge Base Helpdesk Forums About Privacy Policy Contact Copyright 2016, Centova Technologies Inc. Centova is a registered trademark of Centova Technologies Inc.
December November October September August July June May April March February January 2013 December November October September August July June May April March February January 2012 December November October September August July June May April March February January 2011 December November October September August July June May April March February January 2010 December November October September August July June May April March February January 2009 December November October http://www.centova.com/en/faq/cast2/troubleshooting/unable_to_create_lock_file_failed_to_start_up_concurrent_users September August July June May April March February January 2008 December November October September August July June May April March February January 2007 December November October September August July June May April March February January 2006 December November October September August July June May April March February January 2005 December November October September https://lists.stg.fedoraproject.org/archives/list/selinux@lists.fedoraproject.org/thread/4PRP3Y2VGYFH265G2UP35RNBVMU72CCG/ August July June May April March February January 2004 December November October September August July June May April March List overview Download newer AWStats Update-now link has permissions issues older Re: Bug 539519: selinux doesn't... Re: Bug 539519: selinux doesn't... First Post Replies Stats Go to ----- 2016 ----- October September August July June May April March February January ----- 2015 ----- December November October September August July June May April March February January ----- 2014 ----- December November October September August July June May April March February January ----- 2013 ----- December November October September August July June May April March February January ----- 2012 ----- December November October September August July June May April March February January ----- 2011 ----- December November October September August July June May April March February January ----- 2010 ----- December November October September August July June May April March February January ----- 2009 ----- December November October September
for visiting!For those of us still using CVS, rather than the highly acclaimed subversion, I wanted to outline a solution to a common problem http://www.mooreds.com/wordpress/archives/234 I've often seen: One user creates a cvs module (named, for example, project) https://sourceforge.net/p/awstats/discussion/43428/thread/2985beb6/ and checks in a number of files and directories. Then another developer tries to check out the module and sees this error. (Here's another explanation of the solution.) : cvs checkout: failed to create lock directory for
`/usr/local/cvsrepo/project'
(/usr/local/cvsrepo/project/#cvs.lock): Permission denied
: cvs checkout: failed to obtain dir error failed lock in repository
`/usr/local/cvsrepo/project'
: cvs [checkout aborted]: read lock failed - giving up If you go to /usr/local/cvsrepo/project, and run an ls -l, you'll see that the permissions look like: ...
drwxrwxr-x 2 user group 4096 Feb 16 09:40 bin
... This error message comes from the fact that the second user is not a member of group error failed to group. The best way to solve this is to create a second group, perhaps called cvs, and assign both users to that group. Then, you want to make sure that all the files have the correct group bit set: chown -R :cvs /usr/local/cvsrepo/project And, you want to make sure that any new directories (and files) added use the cvs group, rather than the group group: chmod -R g+ws /usr/local/cvsrepo/project Your final permissions should look like: ...
drwxrwsr-x 2 user cvs 4096 Feb 16 09:40 bin
... Now the second user and any other developers should be able to check out the code so safely stored in cvs. Programming | moore | February 16, 2005 29 thoughts on “"cvs checkout: failed to create lock directory" solution” Prateep Kulapalanont says: Exactly what I have the problem after read CVS for Leopard . Thanks Pradeep says: Hats Off Great work! Timely Help.. surendra kumar says: you saved my life man…! hats off thanks for the post man. moore says: All, Glad to help! Krishen says: This just helped me out too on my Leopard-based CVS server! Thanks! Joe says: Ex
you by: eldy, manolamancha Summary Files Reviews Support Wiki Mailing Lists Code Cvs Tickets ▾ Support Requests Bugs Feature Requests Patches News Discussion Donate Create Topic Stats Graph Forums Developers 738 Open Discussion 10062 Help Formatting Help Update config /Permission denied Forum: Open Discussion Creator: Mic Created: 2010-05-31 Updated: 2012-10-11 Mic - 2010-05-31 HI, I'm lost. I tried many thinks. I'm on Windows 2008R2. Ive installed awstats, and when i start the command to update my databse from Logs i have in LogFile: perl awstats.pl -config=mydomain -update i get : SOMETHING HERE D:\Apps\AWStats\wwwroot\cgi-bin>perl awstats.pl -config=mydomain -update Create/Update database for config "./awstats.mydomain.conf" by AWStats version 6.95 (build 1.943) From data in log file "D:\Apps\AWStats\mylogs"... Error: Couldn't open server log file "D:\Apps\AWStats\mylogs" : Permission denie d Setup ('./awstats.mydomain.conf' file, web server or permissio ns) may be wrong. Check config file, permissions and AWStats documentation (in 'docs' directory). This is my conf: # AWSTATS CONFIGURE FILE 6.95 #----------------------------------------------------------------------------- # Copy this file into awstats.www.mydomain.conf and edit this new config file # to setup AWStats (See documentation in docs/ directory). # The config file must be in /etc/awstats, /usr/local/etc/awstats or /etc (for # Unix/Linux) or same directory than awstats.pl (Windows, Mac, Unix/Linux...) # To include an environment variable in any parameter (AWStats will replace # it with its value when reading it), follow the example: # Parameter="__ENVNAME__" # Note that environment variable AWSTATS_CURRENT_CONFIG is always defined with # the config value in an AWStats running session and can be used like others. #----------------------------------------------------------------------------- # $Revision: 1.338 $ - $Author: eldy $ - $Date: 2009/09/08 17:10:30 $ #----------------------------------------------------------------------------- # MAIN SETUP SECTION (Required to make AWStats work) #----------------------------------------------------------------------------- # "LogFile" contains the web, ftp or mail server log file to analyze. # Possible values: A full path, or a relative path from awstats.pl directory. # Example: "/var/log/apache/access.log" # Example: "../logs/mycombinedlog.log" # You can also use tags in this filename if you need a dynamic file name # depending on date or time (Replacement is made by AWStats a