Error Unable To Create Temp File For Writing Status Data
Contents |
• All times are UTC - 6 hours [ DST ] Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group
Permission deniedLog In ExportXporter for JIRAXMLWordPrintable Details Type: Bug Status: Closed Priority: Major Resolution: Fixed Affects Version/s: 5.7.3 Fix Version/s: 6.0.7 Component/s: naemon Labels: None Environment: Operating System: CentOS Platform: x86_64 jira_priority_score: 9.954 Steps to reproduce: Hide Change temp_file back to 'nagios.tmp' and watch the errors come in... Show Change temp_file back to 'nagios.tmp' and watch the errors come in... Severity: major External issue URL: https://bugs.op5.com/view.php?id=6216 Similar Issues: Show Description This is due to the fact that in /opt/monitor/etc/nagios.cfg, tempfile is set to 'nagios.tmp'. When this is changed to '/opt/monitor/var/nagios.tmp', the message doesn't come up again. What bugs me though, is that the message does not say which file it can't write to and https://support.nagios.com/forum/viewtopic.php?f=34&t=29597 in what directory it tries to do so (current directory). AttachmentsIssue Links relates to MON-4862 Nagios temp files are written to /opt/monitor/etc Closed MON-5313 nagios.log full with: Error: Unable to create temp file for writing status data: Permission denied Closed Activity All Comments Work Log History Activity Ascending order - Click to sort in descending order Hide Permalink Andreas Ericsson (Inactive) added a comment - 2012-12-12 17:18 This is more or less fixed, https://jira.op5.com/browse/MON-4698 for a couple of reasons. First off, we now use relative paths in nagios.cfg to mean "relative to the directory where nagios.cfg resides", which means that we'd try to create the file as /opt/monitor/etc/nagios.tmp, which would have succeeded on normal op5 systems. Besides that, I just recently committed the following change: commit e2f99e8720e95d1b18f2a7a59c5fe3b9298752e8 Author: Andreas Ericsson
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn http://serverfault.com/questions/523625/error-on-nagios-starting more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges https://dev.icinga.org/issues/2560 Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Error on nagios starting up vote 0 down vote favorite I had nagios error unable running on centOS. when i restart the nagios with /etc/init.d/nagios restart it not showing any error. But when i check the status with /etc/init.d/nagios status it showing nagios not running. I run nagios with the help of /usr/local/nagios/bin/nagios /usr/local/nagios/etc/nagios.cfg i getting following error Nagios 3.3.1 starting... (PID=12179) Local time is Tue Jul 16 10:08:17 CEST 2013 Error: my_fcopy() failed to write to '/usr/local/nagios/var/spool/checkresults/nebmod2CKuKY': No space left on device Error: my_fcopy() failed to write to '/usr/local/nagios/var/spool/checkresults/nebmodMmhs0U': No space error unable to left on device In the webconsole home page working properly.But when i click service or host i getting following error There doesn't appear to be any service status information in the status log... Make sure that Nagios is running and that you have specified the location of you status log correctly in the configuration files. What would be the error? EDIT output of *df -h* Filesystem Size Used Avail Use% Mounted on /dev/mapper/VolGroup-lv_root 5.5G 5.3G 0 100% / tmpfs 939M 0 939M 0% /dev/shm /dev/sda1 485M 37M 423M 8% /boot nagios share|improve this question edited Jul 16 '13 at 9:40 Sven♦ 65.1k899142 asked Jul 16 '13 at 9:13 sujin 11426 1 That "No space left on device" error is suspect... Did you check the free space? –Lacek Jul 16 '13 at 9:18 Please post the output of df -h. –Sven♦ Jul 16 '13 at 9:19 its working now thanks @SvW –sujin Jul 16 '13 at 10:04 add a comment| 2 Answers 2 active oldest votes up vote 3 down vote accepted You don't have any more room on your disc (see the 100% on that df output for /dev/mapper/VolGroup-lv_root), so all sorts of things will start to break, including this. Free up some space. Specifically in this case, nagios tries to write to some (temp?) file, but can't Error: my_fcopy() failed to write to '/usr/local/nagios/var/spoo
New issues w/o target version open issues grouped by status Bug #2560 Log error reason when failing to create the status file Added by mopp over 4 years ago. Updated over 4 years ago. Status:ResolvedStart date:04/26/2012Priority:LowDue date:Assignee:dnsmichi% Done:100%Category:LoggingTarget version:Icinga 1.x - 1.7 Icinga Version: OS Version: Description Enhancement to Bug #1078.This fix will write the file name instead of just permission denied. --- a/xdata/xsddefault.c 2012-04-26 20:49:38.000000000 0000++ b/xdata/xsddefault.c 2012-04-26 20:52:30.000000000 +0000@ -367,7 +367,7 @ if ((fd = mkstemp(temp_file)) == -1) { /* log an error */
- logit(NSLOG_RUNTIME_ERROR, TRUE, "Error: Unable to create temp file for writing status data: %s\n", strerror(errno));
+ logit(NSLOG_RUNTIME_ERROR, TRUE, "Error: Unable to create temp file '%s' for writing status data: %s\n", temp_file, strerror(errno)); /* free memory */
my_free(temp_file); Associated revisions Revision 6d6a5a70 Added by dnsmichi over 4 years ago core: log error reason when failing to create the status file (Ulf Lange) #2560 fixes #2560 History #1 Updated by dnsmichi over 4 years ago Tracker changed from Feature to Bug Category set to Logging Status changed from New to Assigned Assignee set to dnsmichi Priority changed from Normal to Low Target version set to 1.7 i'll mark that as a bug, adding value to the core, so getting it on the 1.7 stage. pretty useful when debugging & testing. #2 Updated by dnsmichi over 4 years ago Status changed from Assigned to Resolved % Done changed from 0 to 100 Applied in changeset 6d6a5a70b2a6ba1a69aaf6838897fcc3c6701665. Also available in: Atom PDF Loading... Powered by Redmine © 2006-2014 Jean-Philippe Lang