[Bug 924739] Re: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated
Some options could be translated. http://www.squid-cache.org/Doc/config/ shows what's compatible and what's not. The release notes list which tags have been added, changed and removed. E.g. header_access was replaced by request_header_access and reply_header_access so the one tag becomes two for more fine grained control. A pointer to the Squid release notes is what Red Hat did for RHEL 6.0's notes: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Migration_Planning_Guide/ch04s12.html And I think it was referenced elsewhere too. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid3 in Ubuntu. https://bugs.launchpad.net/bugs/924739 Title: after upgrade from oneiric to precise, previous squid config unused, cannot be used when relocated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid3/+bug/924739/+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 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
Hi,
I'm willing to rebuild and test the fix myself when I get some time, but I
thought it might be faster and easier for a maintainer to do.
I apologise if this comment seems negative, it's not intended as such.
1) lucid's qemu does not seem to support boot=on, but maybe my testing
is wrong? Certainly libvirt's upstream says that not all versions of
qemu do even though the documentation may say that it does. I can get
ReactOS to boot without this parameter, but I can't get it to boot with
this parameter. I isolated the commands to that one difference.
2) qemu-kvm does not require kvm. Many peices of hardware, including
mine don't support kvm. Perhaps this is what's misleading you.
3) I did attach a patch from upstream. I figured attaching a patch would
make it easier to spot rather than having to see that there's a link to
a patch in the git repository. It looks like the patch doesn't effect
qemu when in kvm mode, and it looks like lucid's qemu without kvm
doesn't support boot=on (but perhaps my testing is flawed? See point 1).
4) I'm using lucid. Is maverick's libvirt already in a supported
backported archive? I don't see it, but I do see a bug that says it's
not there: https://bugs.launchpad.net/lucid-backports/+bug/724026
5) I've added the tags patch and patch-accepted-upstream. I hope
that's appropriate.
Here's the metadata about the patch:
- cut -
author Daniel Veillard veill...@redhat.com
Fri, 30 Jul 2010 14:38:48 + (16:38 +0200)
committer Daniel Veillard veill...@redhat.com
Fri, 30 Jul 2010 14:38:48 + (16:38 +0200)
Basically the 'boot=on' boot selection device is something present in
KVM but not in upstream QEmu, as a result if we boot a QEmu domain
without KVM acceleration we must disable boot=on ... even if the front
end kvm binary expose that capability in the help page.
* src/qemu/qemu_conf.c: in qemudBuildCommandLine if -no-kvm is passed, then
deactivate QEMUD_CMD_FLAG_DRIVE_BOOT
--
Here's the patch inline:
-
--- a/src/qemu/qemu_conf.c
+++ b/src/qemu/qemu_conf.c
@@ -3707,9 +3707,17 @@ int qemudBuildCommandLine(virConnectPtr conn,
* 2. The qemu binary has the -no-kvm flag
*/
if ((qemuCmdFlags QEMUD_CMD_FLAG_KVM)
-def-virtType == VIR_DOMAIN_VIRT_QEMU)
+def-virtType == VIR_DOMAIN_VIRT_QEMU) {
disableKVM = 1;
+/*
+ * do not use boot=on for drives when not using KVM since this
+ * is not supported at all in upstream QEmu.
+ */
+if (qemuCmdFlags QEMUD_CMD_FLAG_DRIVE_BOOT)
+qemuCmdFlags -= QEMUD_CMD_FLAG_DRIVE_BOOT;
+}
+
/* Should explicitly enable KVM if
* 1. Guest domain is 'kvm'
* 2. The qemu binary has the -enable-kvm flag
-
Drew Daniels
** Tags added: patch patch-accepted-upstream
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libvirt in Ubuntu.
https://bugs.launchpad.net/bugs/835818
Title:
Can't boot qemu w/o kvm (no boot=on param, upstream patch)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
** Tags added: lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] [NEW] Can't boot qemu w/o kvm (no boot=on param, upstream patch)
Public bug reported: I can't boot ReactOS's qemu when using libvirt, but I can from the command line when I remove the -drive parameter's boot=on, text (along with vnc and -S to get it to show a window and start outside of libvirt). http://sourceforge.net/projects/reactos/files/ReactOS/0.3.13/ReactOS-0.3.13-REL-qemu.zip/download The problem *seems* to be patched upstream at: http://libvirt.org/git/?p=libvirt.git;a=commitdiff;h=e7da872294bd1cfaa9733e1292476221659ab47b The git tree shows version 0.8.2 for this patch so Lucid is affected, maverick and later likely aren't affected. Drew Daniels Blog: http://www.boxheap.net/ddaniels/blog ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 835818] Re: Can't boot qemu w/o kvm (no boot=on param, upstream patch)
** Patch added: Do not activate boot=on on devices when not using KVM (by Daniel Veillard) https://bugs.launchpad.net/bugs/835818/+attachment/2324811/+files/qemu-no-kvm-do-not-use-drive-boot-on-parameter.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/835818 Title: Can't boot qemu w/o kvm (no boot=on param, upstream patch) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/835818/+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 207791] Re: winbind forgets uid/name gid/name mappings in regulary periods
To people saying they have related bugs: This bug is for the idmap working fine on initial login, but the mapping being lost after the cache time is exceeded (with no other related winbind activity like authentications/logins). The id mapping can be seen (or seen as failed) using ls in a directory with files owned by an active directory user (success shows names, failure shows numbers). Preferably in a single comment please answer the following questions/steps: 0. Please file a separate bug if it's a separate issue. 1. If you find a configuration or specific set of versions that work, please list all the differences. 2. Please try everything below with a fresh install of lucid on a separate non-production system, if possible. 3. Please list the most recent package versions (e.g.: dpkg -l|grep -i samba, and maybe other packages. ubuntu-bug might help). It'd also be useful to list your distribution even if it's clear from the version numbers, just to save time looking it up. 4. Please list relevant configuration options (e.g. both winbind and idmap sections of /etc/samba/smb.conf and maybe more. ubuntu-bug might post the entire configuration file). 5. Check the log files for related information. /var/log/samba/log.winbind* might be more useful than some of the other log files. Post anything that might be relevant. 6. If using rid or ads as the backend, try to find out if you can still query the domain controller with wbinfo -u and wbinfo -g. You may need to check klist, net ads status, net ads info to see if your kerberos key didn't get renewed. Some of this should be run under sudo with an Active Directory (AD) authenticated user. Consider posting some of the output. 7. Try disabling the cache. Maybe try both winbind cache time 0 in smb.conf and with the line missing if you're not sure which disables the cache. Post to the bug the results of trying to get the mapping (e.g. by ls on a file owned by an Active Directory mapped user). 8. Try winbind offline logon = false in smb.conf and post the results of before and after cache timeout. 9. Post any information you can about the cache and mapping files. This could be a tbl file. The log files might give some information about this. 10. List whether you did a fresh install of Ubuntu or an upgrade. If it was an upgrade, what version(s) did you upgrade from? 11. Did you try any other idmap backends? If so, please list which ones and what order. I believe there might be a bug on switching backends without deleting a mapping file. Thanks, Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html -- winbind forgets uid/name gid/name mappings in regulary periods https://bugs.launchpad.net/bugs/207791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 207791] Re: winbind forgets uid/name gid/name mappings in regulary periods
I would like to know how the issue can be fixed (package upgrade to what version?). Torsten Krah indicated this was a problem as of 2010-02-23, there has been no new release of winbind since 2010-02-02, and that release didn't mention any issues like this. In my research, I also found that some idmap backends don't support certain features. There was an upstream documentation bug discussed recently. Thanks, Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html -- winbind forgets uid/name gid/name mappings in regulary periods https://bugs.launchpad.net/bugs/207791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 207791] Re: winbind forgets uid/name gid/name mappings in regulary periods
Hi Torsten Krah,
Thanks for your friendly reply. Part of the reason I asked the questions was
for other readers of the bug to be able to diagnose similar problems.
Also, for more detailed debugging, here's a link to the current development
version 3 source code:
http://gitweb.samba.org/?p=samba.git;a=tree;f=source3/winbindd;hb=HEAD
I don't know what's going to happen to winbindd with samba4's new code.
I'm guessing that the expiration and failure to re-get the UID mapping can be
seen at the top level in:
http://gitweb.samba.org/?p=samba.git;a=blob;f=source3/winbindd/wb_uid2sid.c;hb=HEAD
The only thing that might show up in a log at this level (or from this file
anyway) looks to be:
50 DEBUG(10, (idmap_cache_find_uid2sid found %d%s\n,
51(int)uid, expired ? (expired): ));
1 Any chance you see the above log line?
Unless I misunderstand, the cache is expired, and requesting a mapping fails.
That means the following is executed:
66 for (domain = domain_list(); domain != NULL; domain =
domain-next) {
67 if (domain-have_idmap_config
68 (uid = domain-id_range_low)
69 (uid = domain-id_range_high)) {
70 state-dom_name = domain-name;
71 break;
72 }
73 }
74
75 child = idmap_child();
76
77 subreq = rpccli_wbint_Uid2Sid_send(
78 state, ev, child-rpccli, state-dom_name,
79 uid, state-sid);
80 if (tevent_req_nomem(subreq, req)) {
81 return tevent_req_post(req, ev);
82 }
83 tevent_req_set_callback(subreq, wb_uid2sid_done, req);
84 return req;
85 }
So I'm guessing that means that the domain name isn't found, or there's a
problem with rpccli_wbint_Uid2Sid_send(), but there are a few other
possibilities. The next steps would be to:
* Check if upstream's got any new information
* Look at rpccli_wbint_Uid2Sid_send()
* Check how the cache is initially populated and check if it's different
code than the above code.
* Test with caching disabled if possible.
* Test in offline mode if possible.
I haven't looked to see if this bug is filed upstream, or if it's
mentioned on a mailing list of theirs. If it is, then any links would be
nice.
Drew Daniels
Resume: http://www.boxheap.net/ddaniels/resume.html
--
winbind forgets uid/name gid/name mappings in regulary periods
https://bugs.launchpad.net/bugs/207791
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba 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 282751] Re: Winbind package does not provide PAM configuration
Debian bug: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566890 Since it's not the Samba project, I don't know how to link to this bug. An alternate, but similar pam-config is discussed at: http://mattonrails.wordpress.com/2008/10/27/vpc-ubuntu-810-beta-and-active-directory/ Name: Active Directory via Winbind Default: yes Priority: 500 Auth-Type: Primary Auth: [success=end default=ignore]pam_winbind.so krb5_auth krb5_ccache_type=FILE try_first_pass Auth-Initial: [success=end default=ignore]pam_winbind.so krb5_auth krb5_ccache_type=FILE Account-Type: Primary Account: [success=end default=ignore]pam_winbind.so Session-Type: Additional Session: requiredpam_mkhomedir.so umask=0022 skel=/etc/skel Drew Daniels Resume: http://www.boxheap.net/~ddaniels/resume.html ** Bug watch added: Debian Bug tracker #566890 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=566890 -- Winbind package does not provide PAM configuration https://bugs.launchpad.net/bugs/282751 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 207791] Re: winbind forgets uid/name gid/name mappings in regulary periods
uid/name gid/name mappings depend on the backend chosen. If the backend doesn't cache or calculate the uids and gids then it's likely trying to query a Domain Controller. 1. Check your idmap backend setup in /etc/samba/smb.conf 2. Check /var/log/samba/log.winbind* for relevant errors/warnings 3. If using rid or ads as the backend, try to find out if you can still query the domain controller with wbinfo -u and wbinfo -g. You may need to check klist, net ads status, net ads info to see if your kerberos key didn't get renewed. Some of this should be run under sudo with an Active Directory (AD) authenticated user. 4. Try re-logging in with an AD user and see if the problem is fixed. If so, it might be that a new key was issued. I kind of wonder if the winbind refresh tickets option isn't working for some reason. Drew Daniels Resume: http://www.boxheap.net/ddaniels/resume.html -- winbind forgets uid/name gid/name mappings in regulary periods https://bugs.launchpad.net/bugs/207791 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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
