Public bug reported:
Job not run message after any attempt to run a job using console.
A job still can be run if run like:
* run job=jobname yes
Steps To Reproduce * run
It shows me the job parameters and asks: yes/mod/no?
Whether I enter yes or mod, it answers me Job not run.
Exactly. This is a usable though not very easy workaround because you
need to modify every parameter in command line.
This is the decision from the Bacula bug tracker administrator:
It looks like your system or Bacula build is broken. Who build the
binaries?
By the way, I am building and
issue was resolved with chmod 777 for /var/log folder and after that
debug mode was started and service started too!
After chmod i implement chown to folder with root:root and no further
problems were found, so SQUID is now working and configured
successfully. Proxy server tested with 2 PCs(one
Ubuntu 8.10 19build
squid 2.6.stable18
- Original Message -
From: Chuck Short chuck.sh...@canonical.com
To: edgec...@gmail.com
Sent: Tuesday, September 01, 2009 6:32 PM
Subject: [Bug 420729] Re: squid stable permissions problems with log files
Hi,
Which version of squid and Ubuntu are
This is little off-topic, but I have the same problem with Centos 5 and
cyrus-sasl-2.1.22-4.
What I see with strace is
open(/etc/shadow, O_RDONLY) = 8
fcntl(8, F_GETFD) = 0
fcntl(8, F_SETFD, FD_CLOEXEC) = 0
fstat(8, {st_mode=S_IFREG|0400, st_size=753,
