search for: deb9u11

Hello, Sacha, le ven. 08 févr. 2019 18:00:22 +0100, a ecrit: > On  Debian GNU/Linux 9.7 (stretch) amd64, we have a bug on the last Xen > Hypervisor version: > > xen-hypervisor-4.8-amd64 4.8.5+shim4.10.2+xsa282 (Read: 4.8.5+shim4.10.2+xsa282-1+deb9u11) > The rollback on the previous package version corrected the problem: > > xen-hypervisor-4.8-amd64 4.8.4+xsa273+shim4.10.1+xsa273-1+deb9u10 (Only the hypervisor needed to be downgraded to fix the issue) > The errors are on the domU a frozen file system until a kernel panic. (n...

...> I have forwarded the original mail: all VM I/O get stuck, and thus the > > VM becomes unusable. > > These are in many cases the symptoms of running out of "grant frames". Oh! That could be it indeed. I'm wondering what could be monopolizing them, though, and why +deb9u11 is affected while +deb9u10 is not. I'm afraid increasing the gnttab max size to 32 might just defer filling it up. > -# ./xen-diag gnttab_query_size 5 > domid=5: nr_frames=11, max_nr_frames=32 The current value is 31 over max 32 indeed. > With Xen 4.8, you can add gnttab_max_f...

...I/O get stuck, and thus the >>>> VM becomes unusable. >>> >>> These are in many cases the symptoms of running out of "grant frames". >> >> Oh! That could be it indeed. I'm wondering what could be monopolizing >> them, though, and why +deb9u11 is affected while +deb9u10 is not. I'm >> afraid increasing the gnttab max size to 32 might just defer filling it >> up. >> >>> -# ./xen-diag gnttab_query_size 5 >>> domid=5: nr_frames=11, max_nr_frames=32 >> >> The current value is 31 over...

...;> VM becomes unusable. >>>>> >>>>> These are in many cases the symptoms of running out of "grant frames". >>>> >>>> Oh! That could be it indeed. I'm wondering what could be monopolizing >>>> them, though, and why +deb9u11 is affected while +deb9u10 is not. I'm >>>> afraid increasing the gnttab max size to 32 might just defer filling it >>>> up. >>>> >>>>> -# ./xen-diag gnttab_query_size 5 >>>>> domid=5: nr_frames=11, max_nr_frames=32 >&gt...

Hi, To upgrade my secondary DC Samba 4.5-16 to 4.8 should I remove the smb.conf file in /etc/samba first? I remember I tried last month to upgrade from 4.5-16 to 4.7 and broke the installation. Or are just the procedures below enough? Create this file repo file for apt. echo "deb http://apt.van-belle.nl/debian stretch-samba48 main contrib non-free" | sudo tee -a

.../nmbd.conf ... Removing obsolete conffile /etc/init/reload-smbd.conf ... Removing obsolete conffile /etc/init/samba-ad-dc.conf ... Removing obsolete conffile /etc/init/smbd.conf ... A processar 'triggers' para libc-bin (2.24-11+deb9u4) ... A processar 'triggers' para systemd (232-25+deb9u11) ... Replication looks OK (samba-tool drs showrepl), but dbcheck does not. samba-tool dbcheck --cross-ncs ERROR(<type 'exceptions.KeyError'>): uncaught exception - 'No such element' ? File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _r...

.... Setting up libwbclient0:amd64 (2:4.10.4+nmu-1debian1) ... Setting up libldb1:amd64 (2:1.5.4-1debian3) ... Setting up samba-common (2:4.10.4+nmu-1debian1) ... Setting up python3-ldb (2:1.5.4-1debian3) ... Processing triggers for libc-bin (2.24-11+deb9u4) ... Processing triggers for systemd (232-25+deb9u11) ... Processing triggers for man-db (2.7.6.1-2) ... Setting up ldb-tools (2:1.5.4-1debian3) ... Setting up samba-libs:amd64 (2:4.10.4+nmu-1debian1) ... Setting up samba-vfs-modules:amd64 (2:4.10.4+nmu-1debian1) ... Setting up libsmbclient:amd64 (2:4.10.4+nmu-1debian1) ... Setting up smbclient (2:4....

.../nmbd.conf ... Removing obsolete conffile /etc/init/reload-smbd.conf ... Removing obsolete conffile /etc/init/samba-ad-dc.conf ... Removing obsolete conffile /etc/init/smbd.conf ... A processar 'triggers' para libc-bin (2.24-11+deb9u4) ... A processar 'triggers' para systemd (232-25+deb9u11) ... Replication looks OK (samba-tool drs showrepl), but dbcheck does not. samba-tool dbcheck --cross-ncs ERROR(<type 'exceptions.KeyError'>): uncaught exception - 'No such element' ? File "/usr/lib/python2.7/dist-packages/samba/netcmd/__init__.py", line 177, in _r...

...;>> Removing obsolete conffile /etc/init/samba-ad-dc.conf ... >>>>> Removing obsolete conffile /etc/init/smbd.conf ... >>>>> A processar 'triggers' para libc-bin (2.24-11+deb9u4) ... >>>>> A processar 'triggers' para systemd (232-25+deb9u11) ... >>>>> >>>>> Replication looks OK (samba-tool drs showrepl), but dbcheck does not. >>>>> >>>>> samba-tool dbcheck --cross-ncs >>>>> ERROR(<type 'exceptions.KeyError'>): uncaught exception - 'No such &gt...

Package: xen-utils-common Version: 3.0.3-0-2 Severity: wishlist The "xendomains" init script will start domains according to the order of config files found in /etc/xen/auto/*. I use this so that, in the event of a hard reboot, the more important domains will start first. Some of these contain essential services like DNS resolvers, slapd and so on, and since starting xen domains