[Bug 1004494] Re: "Job not run" message after any attempt to run a job using bconsole
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 running Bacula on Ubuntu 12.04, and it works fine for me. - And yes, I think you need to report this to Ubuntu's package maintainer. I am closing this ticket, because it seems to me that it is caused by a bad build." -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1004494 Title: "Job not run" message after any attempt to run a job using bconsole To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1004494/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1004494] [NEW] "Job not run" message after any attempt to run a job using bconsole
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". Additional Information The problem may be related to the director or to the bconsole. I cannot run a job using bat too because of a bat's bug. I filed the bug here: http://bugs.bacula.org/view.php?id=1873 and got the decision that the bug is because of a bad build and it is not present in the main source tree. ** Affects: bacula (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1004494 Title: "Job not run" message after any attempt to run a job using bconsole To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bacula/+bug/1004494/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 114601] Re: sasl segfault restart
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, ...}) = 0 mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0x2abde20b7000 read(8, "root:!*:35456:0:9:7:::\nbin:*"..., 4096) = 753 close(8)= 0 munmap(0x2abde20b7000, 4096)= 0 --- SIGSEGV (Segmentation fault) @ 0 (0) --- SASL is started as following: $saslauthd -a shadow -c -O /etc/saslauthd.conf -n 1 On the other hand, my SASL is working fine with LDAP. -- sasl segfault restart https://bugs.launchpad.net/bugs/114601 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 420729] Re: squid stable permissions problems with log files
Ubuntu 8.10 19build squid 2.6.stable18 - Original Message - From: "Chuck Short" To: 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 you using? Thanks chuck ** Changed in: squid (Ubuntu) Importance: Undecided => Low ** Changed in: squid (Ubuntu) Status: New => Incomplete -- squid stable permissions problems with log files https://bugs.launchpad.net/bugs/420729 You received this bug notification because you are a direct subscriber of the bug. Status in “squid” package in Ubuntu: Incomplete Bug description: Binary package hint: firefox-3.0 Hi i'm newbie in ubuntu has installe squid proxy in debuging mode has error message permissions for parent directory is FATAL: Cannot open '/var/log/squid/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user drwxrwxrwx 2 proxy proxy 4096 2009-08-28 23:13 squid running debug has message again r...@unixoid-desktop:/var/log# sudo squid -NCd10 WARNING: Cannot write log file: /var/log/squid/cache.log /var/log/squid/cache.log: Permission denied messages will be sent to 'stderr'. 2009/08/28 23:29:39| WARNING: Closing open FD2 2009/08/28 23:29:39| Starting Squid Cache version 2.6.STABLE18 for i386-debian-linux-gnu... 2009/08/28 23:29:39| Process ID 7794 2009/08/28 23:29:39| With 1024 file descriptors available 2009/08/28 23:29:39| Using epoll for the IO loop 2009/08/28 23:29:39| Performing DNS Tests... 2009/08/28 23:29:39| Successful DNS name lookup tests... 2009/08/28 23:29:39| DNS Socket created at 0.0.0.0, port 39762, FD 5 2009/08/28 23:29:39| Adding nameserver 195.112.96.34 from /etc/resolv.conf 2009/08/28 23:29:39| Adding nameserver 172.16.254.1 from /etc/resolv.conf 2009/08/28 23:29:39| User-Agent logging is disabled. 2009/08/28 23:29:39| Referer logging is disabled. FATAL: Cannot open '/var/log/squid/access.log' for writing. The parent directory must be writeable by the user 'proxy', which is the cache_effective_user set in squid.conf. Squid Cache (Version 2.6.STABLE18): Terminated abnormally. CPU Usage: 0.008 seconds = 0.008 user + 0.000 sys Maximum Resident Size: 0 KB Page faults with physical i/o: 0 Aborted user "proxy" is the owner of parent directory ProblemType: Bug Architecture: i386 Date: Fri Aug 28 23:23:34 2009 DistroRelease: Ubuntu 8.04 Package: firefox-3.0 3.0.13+nobinonly-0ubuntu0.8.04.1 PackageArchitecture: i386 ProcEnviron: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games LANG=en_US.UTF-8 SHELL=/bin/bashSourcePackage: firefox-3.0Uname: Linux 2.6.24-19-generic i686 -- squid stable permissions problems with log files https://bugs.launchpad.net/bugs/420729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 420729] Re: squid stable permissions problems with log files
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 with Wi-fi adapter) acording to acl all resolved. Thank you for your unswer! Micah -- squid stable permissions problems with log files https://bugs.launchpad.net/bugs/420729 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs