Hi,
Xi is broken at the moment. This XenServer version won't boot jessie kernel.
Can't fix this myself, so this may take some time.
Regards,
Stephan.
On 04/30/2015 01:52 PM, Stephan Bosch wrote:
Hi,
Xi is broken at the moment. This XenServer version won't boot jessie kernel.
Can't fix this myself, so this may take some time.
Regards,
Stephan.
I had this issue too with XenServer. Changed to hvm to make it boot. It worked.
On 4/30/2015 7:52 PM, Stephan Bosch wrote:
Hi,
Xi is broken at the moment. This XenServer version won't boot jessie kernel.
Can't fix this myself, so this may take some time.
Since we could not upgrade XenServer any time soon, we reverted the build systems back to Debian wheezy (oldstable) by re-installing them from scratch. It should all work as normal, with the difference that wheezy is built first.
Added Debian stretch (current testing) repository, while the Debian squeeze (current oldoldstable) repository was removed. I also removed repositories for dovecot-2.1 and older. The repositories can now also be used with the release names (e.g. wheezy-auto rather than oldstable-auto).
Don't hesitate to notify me if there are any problems.
Regards,
Stephan.
- Stephan Bosch <stephan@rename-it.nl> 2015.05.10 17:34:
Don't hesitate to notify me if there are any problems.
Thanks for fixing this. As this repo stuff is mostly bleeding edge, I noticed that the systemd service file needs to be modified to allow coredumps. Not sure how it is supposed to interact with the file /etc/default/dovecot and its ALLOW_COREDUMPS=1 variable, but one needs to explicitly add LimitCORE=infinity in the 'Service' section (until someone with more systemd foo fixes it):
$ cat /lib/systemd/system/dovecot.service [Unit] Description=Dovecot IMAP/POP3 email server After=local-fs.target network.target
[Service] Type=simple LimitCORE=infinity ExecStart=/usr/sbin/dovecot -F NonBlocking=yes
[Install] WantedBy=multi-user.target
On 05/10/2015 04:01 PM, Thomas Leuxner wrote:
... Not sure how it is supposed to interact with the file /etc/default/dovecot and its ALLOW_COREDUMPS=1 variable, but one needs to explicitly add LimitCORE=infinity in the 'Service' section (until someone with more systemd foo fixes it):
The attached patch could solve the problem.
Regards, Pascal
The trapper recommends today: cafebabe.1513019@localdomain.org
On 5/10/2015 7:29 PM, Pascal Volk wrote:
On 05/10/2015 04:01 PM, Thomas Leuxner wrote:
... Not sure how it is supposed to interact with the file /etc/default/dovecot and its ALLOW_COREDUMPS=1 variable, but one needs to explicitly add LimitCORE=infinity in the 'Service' section (until someone with more systemd foo fixes it):
The attached patch could solve the problem.
I base this directly on the official Debian unstable packages. So, it would be best if it is fixed there first by someone who knows how to do this properly. I'm mainly worried a bit about the fact that dovecot.service is generated by Dovecot install and /etc/default/dovecot is from Debian.
Regards,
Stephan.
participants (4)
-
Gedalya
-
Pascal Volk
-
Stephan Bosch
-
Thomas Leuxner