On 27.02.19 14:37, Curt wrote:
On 2019-02-27, Dominik wrote:
I'm looking for help related to three questions:
1) How do I get additional information about what is causing the error?
Why is systemd blocking sudo despite the modifications in the override.conf
2) More generally: How can I run o
On 2019-02-27, Dominik wrote:
>
> I'm looking for help related to three questions:
>
> 1) How do I get additional information about what is causing the error?
> Why is systemd blocking sudo despite the modifications in the override.conf
>
> 2) More generally: How can I run openvpn in a daemon as u
Since a few days (after an update of systemd and openvpn), openvpn fails
while running the learn-address script with the following message:
Feb 25 09:07:56 vpn openvpn[27220]: sudo: unable to send audit message
Feb 25 09:07:56 vpn openvpn[27220]: sudo: pam_open_session: System error
Feb 25 09:07
On 07/10/15 15:32, Reco wrote:
Update initrd after updating /etc/mdadm/mdadm.conf.
I'm afraid that's beyond my expertise
update-initramfs -k all -u
It's all in the handbook, really. All it takes is to read it once.
https://debian-handbook.info/
Thanks for sticking with this.
You're
Hi.
On Wed, Oct 07, 2015 at 02:56:49PM +0100, Tony van der Hoff wrote:
> On 06/10/15 19:00, Reco wrote:
> >> 1) Those should work just fine, and fix the trouble somewhat:
> >>
> >> mdadm --add /dev/md0 /dev/sda5
> >> mdadm --add /dev/md1 /dev/sda6
> >> mdadm --add /dev/md3 /dev/sda8
> >> mdadm --
On 06/10/15 19:00, Reco wrote:
>> 1) Those should work just fine, and fix the trouble somewhat:
>>
>> mdadm --add /dev/md0 /dev/sda5
>> mdadm --add /dev/md1 /dev/sda6
>> mdadm --add /dev/md3 /dev/sda8
>> mdadm --add /dev/md4 /dev/sda9
>> mdadm --add /dev/md6 /dev/sda11
>>
>> 2) A big warning - wait
Hi.
On Tue, Oct 06, 2015 at 08:53:58PM +0300, Reco wrote:
> Hi.
>
> On Tue, Oct 06, 2015 at 06:21:59PM +0100, Tony van der Hoff wrote:
> > On 06/10/15 17:59, Reco wrote:
> > >
> >
> > > Allow me to explain then.
> > >
> > Thank you, Reco, I'm really grateful. I'm learning a lot h
Hi.
On Tue, Oct 06, 2015 at 06:21:59PM +0100, Tony van der Hoff wrote:
> On 06/10/15 17:59, Reco wrote:
> >
>
> > Allow me to explain then.
> >
> Thank you, Reco, I'm really grateful. I'm learning a lot here!
You're welcome.
> OK, here goes:
>
> root@tony-lx:~# cat /proc/mdstat
> Per
On 06/10/15 17:59, Reco wrote:
>
> Allow me to explain then.
>
Thank you, Reco, I'm really grateful. I'm learning a lot here!
> You did not run update-grub, so whatever changes you made to grub.cfg
> were expected to be honored on reboot.
> Yet on reboot "insmod mdraid1x" was there.
> That can
Hi.
On Tue, Oct 06, 2015 at 05:16:29PM +0100, Tony van der Hoff wrote:
> On 06/10/15 16:03, Reco wrote:
> > I propose an experiment.
> >
> > 1) Remove "insmod mdraid1x" from grub.cfg. By using any text editor, *do
> > not* run update-grub.
> > 2) Reboot.
> > 3) While in grub, press 'e' wh
On 06/10/15 16:03, Reco wrote:
> I propose an experiment.
>
> 1) Remove "insmod mdraid1x" from grub.cfg. By using any text editor, *do
> not* run update-grub.
> 2) Reboot.
> 3) While in grub, press 'e' while the default boot entry is selected.
> 4) Check whenever boot entry still contains "insmod
Hi.
On Tue, Oct 06, 2015 at 02:03:37PM +0100, Tony van der Hoff wrote:
> >>>
> >>> As long as "uname -v" output is consistent with "apt-cache policy
> >>> linux-image-3.2.0-4-amd64" output there's nothing to worry about IMO.
> >>>
> >>> They stopped to change kernel version (i.e. 3.2.0-4)
On 06/10/15 13:22, Reco wrote:
> Hi.
>
> On Tue, Oct 06, 2015 at 11:46:31AM +0100, Tony van der Hoff wrote:
>> On 05/10/15 18:33, Reco wrote:
>>> Hi.
>>>
>>> On Mon, Oct 05, 2015 at 06:15:58PM +0100, Tony van der Hoff wrote:
On 05/10/15 17:38, Reco wrote:
> On Mon, Oct 05, 2015
Hi.
On Tue, Oct 06, 2015 at 11:46:31AM +0100, Tony van der Hoff wrote:
> On 05/10/15 18:33, Reco wrote:
> > Hi.
> >
> > On Mon, Oct 05, 2015 at 06:15:58PM +0100, Tony van der Hoff wrote:
> >> On 05/10/15 17:38, Reco wrote:
> >>> On Mon, Oct 05, 2015 at 05:17:49PM +0100, Tony van der H
On 05/10/15 18:33, Reco wrote:
> Hi.
>
> On Mon, Oct 05, 2015 at 06:15:58PM +0100, Tony van der Hoff wrote:
>> On 05/10/15 17:38, Reco wrote:
>>> On Mon, Oct 05, 2015 at 05:17:49PM +0100, Tony van der Hoff wrote:
>> Thanks for the quick response, Reco.
>>
>> 1. Kernel is stock wh
Actually I went back and it's not the region that is the factor... It is
the image that was used to build the droplets. The Debian 7.0 images all
require the kernel to be set in the control panel. Even though I've
upgraded a few of those to 8.x so looks like I need to just rebuild them
(thank goodn
On 10/5/2015 12:05 PM, Reco wrote:
>> 2. I don't know when 3.2.0-4 was released; I suspect the answer is yes.
>>
>> 3. many reboots; the last one earlier today.
>>
>> I note bug=767836 describes this problem, but appears closed with 3.2.0-4
> It was closed because the problem was not in the kerne
Hi.
On Mon, Oct 05, 2015 at 06:15:58PM +0100, Tony van der Hoff wrote:
> On 05/10/15 17:38, Reco wrote:
> > On Mon, Oct 05, 2015 at 05:17:49PM +0100, Tony van der Hoff wrote:
> Thanks for the quick response, Reco.
>
> 1. Kernel is stock wheezy:
> 3.2.0-4-amd64 #1 SMP
On 05/10/15 17:38, Reco wrote:
> On Mon, Oct 05, 2015 at 05:17:49PM +0100, Tony van der Hoff wrote:
Thanks for the quick response, Reco.
1. Kernel is stock wheezy:
3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
>>>
>>> But very old one. Current one is 3.2.68-1+de
On Mon, Oct 05, 2015 at 05:17:49PM +0100, Tony van der Hoff wrote:
> >> Thanks for the quick response, Reco.
> >>
> >> 1. Kernel is stock wheezy:
> >> 3.2.0-4-amd64 #1 SMP Debian 3.2.57-3+deb7u2 x86_64 GNU/Linux
> >
> > But very old one. Current one is 3.2.68-1+deb7u4.
> >
> > It's a shot in th
On 05/10/15 17:05, Reco wrote:
> Hi.
>
> On Mon, Oct 05, 2015 at 04:46:01PM +0100, Tony van der Hoff wrote:
>> On 05/10/15 16:31, Reco wrote:
>>> Hi.
>>>
>>> On Mon, Oct 05, 2015 at 03:51:17PM +0100, Tony van der Hoff wrote:
Hi,
I have a VPS running up to date wheezy, with an O
Hi.
On Mon, Oct 05, 2015 at 04:46:01PM +0100, Tony van der Hoff wrote:
> On 05/10/15 16:31, Reco wrote:
> > Hi.
> >
> > On Mon, Oct 05, 2015 at 03:51:17PM +0100, Tony van der Hoff wrote:
> >> Hi,
> >>
> >> I have a VPS running up to date wheezy, with an OpenVPN server, and a
> >> wheezy box
Hi.
On Mon, Oct 05, 2015 at 03:51:17PM +0100, Tony van der Hoff wrote:
> Hi,
>
> I have a VPS running up to date wheezy, with an OpenVPN server, and a
> wheezy box at home running an OpenVPN client. this used to work fine
> last year. I haven't had cause to use it much recently, and I now
On 05/10/15 16:31, Reco wrote:
> Hi.
>
> On Mon, Oct 05, 2015 at 03:51:17PM +0100, Tony van der Hoff wrote:
>> Hi,
>>
>> I have a VPS running up to date wheezy, with an OpenVPN server, and a
>> wheezy box at home running an OpenVPN client. this used to work fine
>> last year. I haven't had c
Hi,
I have a VPS running up to date wheezy, with an OpenVPN server, and a
wheezy box at home running an OpenVPN client. this used to work fine
last year. I haven't had cause to use it much recently, and I now find
it's died. I don't know when, or what changed to cause the fault.
It appears that t
25 matches
Mail list logo
