cyrus-imapd not starting after upgrade from Jessie to Stretch

Hi all! After quite some time, today I decided to update the mail server to Debian Stretch. All without problems until I reach the part of cyrus-imapd that does not start. This is what I see in the log: -- Jan 14 23:10:45 mail systemd[1]: Started Cyrus IMAP/POP3 daemons. Jan 14 23:10:45

Re: Unable to Access a Foreign Volume Group

On Sun, Jan 13, 2019 at 05:39:20PM +0100, Martin wrote: > Hi Jens, > > my first shot would be setting the actual system id to > 'zaphod1105820973' like described in the lvmsystemid man page. I'm not > sure, how this uname or lvmlocal work, so I would try setting > system_id_source to machineid or

Re: Command line mounting all partitions of pluggable device

On 01/14/2019 02:18 PM, David Wright wrote: On Mon 14 Jan 2019 at 10:20:51 (-0600), Richard Owlett wrote: On 01/14/2019 09:22 AM, Thomas Schmitt wrote: rhkra...@gmail.com wrote: Assuming there are entries in fstab for each partition, [...] for i in /dev/sd*; do mount $i; done Rchard Owlet

Re: We've got a problem. Debian "Jessie" box won't launch X or Tomcat, and USB drive won't mount

James H. H. Lampert wrote: > Ladies and Gentlemen: > > We've got a Debian 8 box (an old Dell 400SC) that won't launch X (it boots > to a command line) or Tomcat, nor mount a USB hard drive that we use for > backups. > > It will, however, accept ssh connections. > > In the boot sequence, I see "

We've got a problem. Debian "Jessie" box won't launch X or Tomcat, and USB drive won't mount

Ladies and Gentlemen: We've got a Debian 8 box (an old Dell 400SC) that won't launch X (it boots to a command line) or Tomcat, nor mount a USB hard drive that we use for backups. It will, however, accept ssh connections. In the boot sequence, I see "Failed" where it tries to mount the USB d

Re: Migrate Stretch to New UEFI Build?

Patrick Bartek wrote: >> Patrick Bartek wrote: >> >> > I never could understand that type of "reasoning." With me, if there's >> > no NEED, it's not done. I'm very much the pragmatist. Always have >> > been even as a child, and never likely to change. >> >> you need it but you don't know yet >

Re: Migrate Stretch to New UEFI Build?

On Sun, 13 Jan 2019 22:37:47 -0500 Stefan Monnier wrote: > >> > more research, I've concluded I have no need for LVM, but encryption > >> Side note: whether I need LVM or not, I just always use it. > > I never could understand that type of "reasoning." With me, if there's > > no NEED, it's

Re: Migrate Stretch to New UEFI Build?

On Sun, 13 Jan 2019 23:19:35 +0100 deloptes wrote: > Patrick Bartek wrote: > > > I never could understand that type of "reasoning." With me, if there's > > no NEED, it's not done. I'm very much the pragmatist. Always have > > been even as a child, and never likely to change. > > you need it b

Re: kernel "unsigned" in sid

On 14/01/19 11:20 PM, Vincent Lefevre wrote: > On 2019-01-11 09:52:04 -0500, Michael Stone wrote: >> On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote: >>> I recently came across an inconsistency in sid that it seems difficult (to >>> me) >>> to overcome. >>> >>> A kernel package na

Re: Command line mounting all partitions of pluggable device

On Mon 14 Jan 2019 at 10:20:51 -0600, Richard Owlett wrote: > On 01/14/2019 09:22 AM, Thomas Schmitt wrote: > > Hi, > > > > rhkra...@gmail.com wrote: > > > > Assuming there are entries in fstab for each partition, [...] > > > > for i in /dev/sd*; do mount $i; done > > > > Rchard Owlett wrote:

Re: Command line mounting all partitions of pluggable device

On Mon 14 Jan 2019 at 10:20:51 (-0600), Richard Owlett wrote: > On 01/14/2019 09:22 AM, Thomas Schmitt wrote: > > rhkra...@gmail.com wrote: > > > > Assuming there are entries in fstab for each partition, [...] > > > > for i in /dev/sd*; do mount $i; done > > > > Rchard Owlett wrote: > > > There

Re: /dev/disk/by-id/ in testing

Le 14/01/2019 à 11:09, Vincent Lefevre a écrit : On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote: On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote: This issue is not specific to lilo. It would affect grub-pc updates too, because the boot device is specified by device id. For example on

Re: Command line mounting all partitions of pluggable device

On 01/14/2019 09:22 AM, Thomas Schmitt wrote: Hi, rhkra...@gmail.com wrote: Assuming there are entries in fstab for each partition, [...] for i in /dev/sd*; do mount $i; done Rchard Owlett wrote: There are not. In the most general case i would have a where-to-mount directory with lots o

Re: Command line mounting all partitions of pluggable device

On 01/14/2019 09:02 AM, rhkra...@gmail.com wrote: Top posting intentionally: I guess the key is something has to know where to mount those devices, and you are the one that has to decide that and tell mount in one way or another. Using your scheme of "/dev/sd" the desired mount point can be "

Re: kernel parallel builds?

I am sort of bound to using the packaged kernel source, since I wanted to minimize the changes (applying only *ONE* known debugging patch) and also get a nice deb to install on the laptop. I'll have to check the earlier suggestion of the environment variable, if that works with no further changes

Re: Command line mounting all partitions of pluggable device

Hi, rhkra...@gmail.com wrote: > > Assuming there are entries in fstab for each partition, [...] > > for i in /dev/sd*; do mount $i; done Rchard Owlett wrote: > There are not. In the most general case i would have a where-to-mount directory with lots of directories for the various partitions (

Re: kernel parallel builds?

Andrea Borgia wrote: > I'm using this command from within the unpacked kernel source: > fakeroot debian/rules binary If you are not bound to using Debian's packaged kernel source, then you could simply use the bindeb-pkg target of the vanilla kernel. For example: cp /path/to/working/kernel-co

Re: Command line mounting all partitions of pluggable device

Top posting intentionally: I guess the key is something has to know where to mount those devices, and you are the one that has to decide that and tell mount in one way or another. On Monday, January 14, 2019 10:01:15 AM rhkra...@gmail.com wrote: > On Monday, January 14, 2019 09:12:30 AM Richar

Re: Command line mounting all partitions of pluggable device

On Monday, January 14, 2019 09:12:30 AM Richard Owlett wrote: > On 01/14/2019 07:33 AM, rhkra...@gmail.com wrote: > > On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote: > >> How do I mount all partitions of a specific device > >> (e.g. /dev/sdc)? > > > > Assuming there are entries in f

Re: Command line mounting all partitions of pluggable device

On 01/14/2019 07:33 AM, rhkra...@gmail.com wrote: On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote: I have competing mount requirements. I have 2 1TB USB drives with a dozen or more partitions, only one of which may be of current interest. Disabling automoun is a suitable solution to

Re: kernel parallel builds?

I'm using this command from within the unpacked kernel source: fakeroot debian/rules binary I'll have another look, thanks. Il giorno lun 14 gen 2019 alle ore 13:59 Celejar ha scritto: > On Mon, 14 Jan 2019 12:55:40 +0100 > Andrea Borgia wrote: > > > Hi. > > > > How do I find out, and possibl

Re: apt won't put config files back

On Mon, Jan 14, 2019 at 01:36:10PM +, aces and eights wrote: > after failing to get my roundcube dovecot installations to work again, as a > last resort I apt removed dovecot and also /etc/dovecot. > Thinking "that's OK apt will put them back." > except > "Not replacing deleted config file /etc

apt won't put config files back

hello, after failing to get my roundcube dovecot installations to work again, as a last resort I apt removed dovecot and also /etc/dovecot. Thinking "that's OK apt will put them back." except "Not replacing deleted config file /etc/dovecot/conf.d/20-managesieve.conf" for all the conf files which is

Re: Command line mounting all partitions of pluggable device

On Monday, January 14, 2019 08:11:11 AM Richard Owlett wrote: > I have competing mount requirements. > I have 2 1TB USB drives with a dozen or more partitions, only one of > which may be of current interest. Disabling automoun is a suitable > solution to mounted clutter. > > However I have several

Command line mounting all partitions of pluggable device

I have competing mount requirements. I have 2 1TB USB drives with a dozen or more partitions, only one of which may be of current interest. Disabling automoun is a suitable solution to mounted clutter. However I have several USB drives (64GB - 250GB) with multiple partitions. How do I mount a

Re: kernel parallel builds?

On Mon, 14 Jan 2019 12:55:40 +0100 Andrea Borgia wrote: > Hi. > > How do I find out, and possibly tune, the degree of parallelization in the > kernel build process? The "Kernel Handbook" doesn't say. > > I've got a fairly recent PC with plenty of RAM and a NVME drive, so I was > shocked to find

Re: Debian 9 /boot && /boot/efi partition

Jonathan Dowland wrote: >On Sun, Jan 13, 2019 at 02:00:02PM +0100, Pascal Hambourg wrote: >>/boot can be the EFI partition in the systemd boot specification. >> > >Thanks, I had seen in the past but had forgotten about it. Do you know >whether Debian ha

Re: APT candidate does not match package on Debian repo

Hi, > Thanks for your reply. Is it possible to extract this information from the > mirror server (CentOS based)? > > Where the information is stored on the repository server specifying a > package as stable? http://ftp.de.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz -nik signa

Re: APT candidate does not match package on Debian repo

Hi Nik Thanks for your reply. Is it possible to extract this information from the mirror server (CentOS based)? Where the information is stored on the repository server specifying a package as stable? regards Martin On Mon, Jan 14, 2019 at 11:49 AM Dominik George wrote: > Hi, > > On Mon, Ja

kernel parallel builds?

Hi. How do I find out, and possibly tune, the degree of parallelization in the kernel build process? The "Kernel Handbook" doesn't say. I've got a fairly recent PC with plenty of RAM and a NVME drive, so I was shocked to find that rebuilding the debian kernel package took a few hours. Shocked bec

Re: APT candidate does not match package on Debian repo

Hi Nik Thanks for your reply. Is it possible to extract this information from the mirror server (CentOS based)? Where the information is stored on the repository server specifying a package as stable? regards Martin On Mon, Jan 14, 2019 at 12:12 PM plataleas plataleas wrote: > Hi Nik > > Tha

Re: APT candidate does not match package on Debian repo

Hi, On Mon, Jan 14, 2019 at 11:18:55AM +0100, plataleas plataleas wrote: > Hello, > > We are upgrading our Debian servers (AMD64). We found that the following > kernels are available on public Debian mirrors: > > kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb >

Re: Debian 9 /boot && /boot/efi partition

On Sun, Jan 13, 2019 at 02:00:02PM +0100, Pascal Hambourg wrote: /boot can be the EFI partition in the systemd boot specification. Thanks, I had seen in the past but had forgotten about it. Do you know whether Debian has plans to follow this spec?

Re: kernel "unsigned" in sid

On 2019-01-11 09:52:04 -0500, Michael Stone wrote: > On Fri, Jan 11, 2019 at 09:55:45AM +0100, dot...@gmail.com wrote: > > I recently came across an inconsistency in sid that it seems difficult (to > > me) > > to overcome. > > > > A kernel package named linux-image-4.19.0-1-amd64-unsigned provide

APT candidate does not match package on Debian repo

Hello, We are upgrading our Debian servers (AMD64). We found that the following kernels are available on public Debian mirrors: kernel-image-4.9.0-8-amd64-di_4.9.130-2_amd64.udeb 28-Oct-2018 05:

Re: /dev/disk/by-id/ in testing

On 2019-01-14 11:06:01 +0100, Vincent Lefevre wrote: > On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote: > > This issue is not specific to lilo. It would affect grub-pc updates too, > > because the boot device is specified by device id. > > > > For example on my system : > > $ debconf-show grub

Re: /dev/disk/by-id/ in testing

On 2019-01-08 20:12:43 +0100, Pascal Hambourg wrote: > This issue is not specific to lilo. It would affect grub-pc updates too, > because the boot device is specified by device id. > > For example on my system : > $ debconf-show grub-pc > (...) > * grub-pc/install_devices: /dev/disk/by-id/ata-WDC_

Re: /dev/disk/by-id/ in testing

On 2019-01-06 10:30:26 +, Johan en Katrien Dewaele wrote: > Hi, > > my weekly upgrade on testing failed yesterday as,  after an initrd.img was > generated, lilo could not run successfully. > > > After checking my /etc/lilo.conf, where I had my boot disk identified by ID > as : > > > "boo