similar to: Bug#799122: xen-hypervisor-4.4-amd64: Networking of domUs stops working after a few minutes

>> We tested the current lenny kernel linux-image-3.16.0-4-amd64 as well >> as the backport linux-image-4.1.0-0.bpo.1-amd64 on the dom0 as well >> as the domU. > > (I suppose you meant s/lenny/jessie/ ;-) Oops, yes :) > These are kernel ABI versions, the package release versions are things > like 3.16.7-ckt17-1 or 4.2.5-1~bpo8+1, which yu can either get from >

On Wed, 2015-09-16 at 01:52 +0200, Arne Klein wrote: > [...] > At the moment when the network in the domU completely stops working, > there is the error message > [2178752.854380] vif vif-33-0 vif33.0: Guest Rx stalled > visible in dmesg in the dom0. This will therefore be a kernel issue not a hypervisor one. It sounds like a backend one given the issue is with both new and

Hi, I've been having an issue with the indexer giving me errors on mailbox in dovecot. I managed to narrow it down to a specific email in that mailbox. Various dovecot functions have issues with this email. The email itself is just spam. I can email it to you if you want to analyse it. I did run it through mbox-anonymize but its not clear to me that that would be of any use. Happy to email

Hai, I've (finaly) complete and restructured my apt. All non-samba related packages are removed, so it all dedicated for samba. More Info about my apt found here: http://apt.van-belle.nl/ The apt repo has the following setup. All term like (jessie) and (jessie-backports) and (unstable) are related to this apt repo (apt.van-belle.nl), but everything is builded and tested on Debian

Hi, I'm starting to see, on a pretty standard Debian Jessie installation, some error messages that are apparently related to the ETOOMANYREFS errno. Firstly, the mail log shows this: dovecot: pop3-login: Error: fd_send(pop3, 18) failed: Too many references: cannot splice And then the login process fails: dovecot: pop3-login: Internal login failure (pid=34388 id=1) (internal failure, 1

Hi, A while ago I sent an email regarding these "*ETOOMANYREFS* Too many references: cannot splice." that we've seen since Debian updated the Jessie kernel to 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u3 (2016-01-17) x86_64 while older kernels, like 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1+deb8u6 (2015-11-09) x86_64 showed no errors at all. I was wondering if no one

On 26 Oct 2016, at 11:14, Luis Ugalde <forondarena at gmail.com> wrote: > > Hi, > > Could you please have a look at https://lkml.org/lkml/2016/2/2/538 and see > if this makes any sense to you? I've been checking kernel changes > between linux_3.16.7 and linux_3.16.36, and this has popped out. Could this > be the reason for the "too many references"

https://bugzilla.netfilter.org/show_bug.cgi?id=1082 Bug ID: 1082 Summary: Hard lockup when inserting nft rules (esp. ct rule) Product: nftables Version: unspecified Hardware: x86_64 OS: Debian GNU/Linux Status: NEW Severity: blocker Priority: P5 Component: kernel Assignee:

Currently (samba 4 NT-like domains) i use extensively NTLM auth in freeradius and more mildly in squid, respectively with: Freeradius (mschap module): ntlm_auth = "/usr/bin/ntlm_auth --request-nt-key --domain=SANVITO --username=%{mschap:User-Name:-None} --challenge=%{mschap:Challenge:-00} --nt-response=%{mschap:NT-Response:-00}" squid3: auth_param ntlm program /usr/bin/ntlm_auth

Hello, I expected that when I use ifconfig command to display network traffic RX and TX values both for dom0 and domu machine, there are differences. I run once ping inside the domu. domu ifconfig command show [root@localhost /]# ifconfig eth0 | grep bytes RX packets 705 bytes 55860 (54.5 KiB) TX packets 521 bytes 65074 (63.5 KiB) [root@localhost /]# ping robtex.com PING robtex.com

Might this be related to the Linux version? I'm testing on one of our university servers, and they tend to be deprived of regular updates sometimes... (Dirk, sorry for sending you this twice.) > Sys.info() sysname "Linux" release

On Wed, Jan 27, 2016 at 7:30 PM, Konrad Rzeszutek Wilk < konrad.wilk at oracle.com> wrote: > On Sat, Jan 23, 2016 at 05:12:04PM +0100, Tommi Airikka wrote: > > Xen developers, > > > > After an upgrade of my Debian Jessie dom0 and domUs, my passthroughed > > NIC stopped working. > > This bug was probably introduced in Debian Jessie sometime > > between

Package: xen-hypervisor-4.4-amd64 Version: 4.4.1-9+deb8u3 Severity: grave Hello, I am trying to install the XEN Hypervisor on a Debian Jessie Server. When I am booting without the Hypervisor, everything works fine, but when I am Booting WITH the XEN-Hypervisor, then System crashes / reboots after the "Scrubbing Free RAM" Message without any Error-message, just a blank screen.

I've tried to install the new version of Roundcube but I've got an error message: Unpacking roundcube (1.1.5+dfsg.1-1~bpo8+1) ... Errors were encountered while processing: /var/cache/apt/archives/roundcube-core_1.1.5+dfsg.1-1~bpo8+1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) If anybody can give me instructions on how to correct this, perhaps I should

Hello, I have a server with an NT4-style domain an Samba 4.2.14+dfsg-0+deb8u5. The samba uses an LDAP backend and all is fine so far. Samba users start at uid 1005 (it's not good I know but it's historical) Domain Users Group has UID 513. Now my Problem: The winbind log is full of [2017/04/07 16:35:50.896450, 1] ../source3/winbindd/idmap.c:230(idmap_init_domain) idmap range not

The version of Roundcube I am using is 0.9.5+dfsg1-4.1

16.10.2023 15:50, Ingo Asche via samba wrote: > Hi Michael, > > short question: will the Bullseye-Backports getting 4.17.12, too? > > I saw, Bookworm is already updated... Since oldstable-bpo archive in debian is always subject to manual backports-policy processing (all uploads are processed manually), I don't push stuff to oldstable-bpo often. On the other hand, this

Thanks Aki!! The welcome plugin sounds like the best workaround. To implement this we would need to upgrade our Dovecot installation: dovecot-core: Installed: 1:2.2.24-1~bpo8+1 Candidate: 1:2.2.27-2~bpo8+1 Are there special recommendations for the upgrade process (in addition to the Dovecot NEWS file)? Any special steps we should be aware of during the upgrade? Is it that simple

> On 25 Jul 2016, at 19:49, Rowland penny <rpenny at samba.org> wrote: > > On 25/07/16 19:32, Kevin Davidson wrote: >>> On 25 Jul 2016, at 16:39, Rowland penny <rpenny at samba.org> wrote: >>> >>> On 25/07/16 16:02, Kevin Davidson wrote: >>>> Having problems with rfc2307 user ids. This was working briefly and now it’s not.

Hi all, I Try use shorewall rules with time element but its never works, the rules look like this HTTPS(REJECT) loc net:69.63.181.11,69.63.181.12,69.63.184.142,69.63.187.17,69.63.187.19 localtz&timestart=20:00&timestop=20:10&weekdays=Mon,Tue,Wed,Thu,Fri This rules for block https access to facebook site at working hours & day My system is Debian lenny, shorewall 4.4.4.2 kernel