On Tue, Aug 30, 2022 at 08:16:12PM -0700, Porter Smith wrote:
> Jeremy,
>
> Have you tried to completely wipe the hard drive that your using in the
> machine mentioned in the post. This of course would intail a through backup
> of all important data sets.
>
> To nuke your stove I would like
On 31/8/22 11:11 am, Greg Wooledge wrote:
apt-cache policy libdbi-perl perlapi-5.28.1
On Debian 11, libdbi-perl should depend on perlapi-5.32.0 not
perlapi-5.28.1 so I suspect you've got the wrong libdbi-perl somehow.
It would also help if you showed the full error message, instead of only
a
Jeremy,
Have you tried to completely wipe the hard drive that your using in the
machine mentioned in the post. This of course would intail a through backup of
all important data sets.
To nuke your stove I would like to recommend dban.
On August 30, 2022 8:03:29 PM PDT, Jeremy Ardley wrote:
On Wed, Aug 31, 2022 at 11:03:29AM +0800, Jeremy Ardley wrote:
> I am install a VM for a LEMP server using the latest ISO
> debian-11.4.0-amd64-DVD-1.iso
> The following packages have unmet dependencies:
> libdbi-perl : Depends: perlapi-5.28.1
apt-cache policy libdbi-perl perlapi-5.28.1
On Debi
I am install a VM for a LEMP server using the latest ISO
debian-11.4.0-amd64-DVD-1.iso
The problem is installing mariadb (after installing nginx and php-fpm
and doing apt update and apt upgrade)
sudo apt install default-mysql-server
...
The following packages have unmet dependencies:
libdb
On 2022-08-30 at 20:18, Jeremy Ardley wrote:
> On 31/8/22 7:36 am, Jon Leonard wrote:
>
>> On Tue, Aug 30, 2022 at 04:27:09PM -0700, L L wrote:
>>
>>> I'm on bullseye, and installed chromium from the bullseye repos.
>>> In Chromium I get the message that the browser is "managed by
>>> your organ
On Wed, Aug 31, 2022 at 08:49:29AM +0800, Jeremy Ardley wrote:
> One of my problems with systemd is the that name resolution is by default
> done by resolved.
Not in Debian.
unicorn:~$ systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
Loaded: loaded (/lib
On 30/8/22 9:56 am, Ross Boylan wrote:
Now everything just works.
Thanks again to everyone.
There are probably some general lessons, though I'm not sure what they
are. Clearly the systemd semantics tripped me up; it's kind of an odd
beast. I understand one of its major goals was to allow st
On 31/8/22 7:36 am, Jon Leonard wrote:
On Tue, Aug 30, 2022 at 04:27:09PM -0700, L L wrote:
I'm on bullseye, and installed chromium from the bullseye repos. In
Chromium I get the message that the browser is "managed by your
organization." I didn't do any special setup for work or school. Is the
On Tue, Aug 30, 2022 at 04:27:09PM -0700, L L wrote:
> I'm on bullseye, and installed chromium from the bullseye repos. In
> Chromium I get the message that the browser is "managed by your
> organization." I didn't do any special setup for work or school. Is the
> management part of the Debian pack
I'm on bullseye, and installed chromium from the bullseye repos. In
Chromium I get the message that the browser is "managed by your
organization." I didn't do any special setup for work or school. Is the
management part of the Debian packaging, or is something sketch going on?
> On Aug 30, 2022, at 1:40 PM, Nicholas Geovanis wrote:
>
> When you run check_dns by hand on Host B, you don't say who you are logged-in
> as. That can make a difference. Nagios runs its scripts in a known
> environment which may be different than you expect.
>
Thanks for the question. I
On Tue, Aug 30, 2022, 2:13 PM Casey Deccio wrote:
> Hi all,
>
> I am having trouble tracking down a bug in my monitoring setup. It all
> happened when I upgraded the monitored host (host B in my example below) to
> bullseye. Note that Host A is also running bullseye, but the problem
> didn't sh
Hello folks,
In testing, ledger returns:
```
ledger: error while loading shared libraries:
libboost_python310.so.1.74.0: cannot open shared object file: No such
file or directory
```
Do other folks see this?
Cheers!
--
Boyan Penkov
Hi all,
I am having trouble tracking down a bug in my monitoring setup. It all
happened when I upgraded the monitored host (host B in my example below) to
bullseye. Note that Host A is also running bullseye, but the problem didn't
show itself until Host B was upgraded.
Here is the setup:
Ho
On Wednesday, August 10, 2022 08:55:20 AM Dan Ritter wrote:
> rhkra...@gmail.com wrote:
> > I.e., if a computer on the LAN contacted a computer outside the LAN, NAT
> > would allow incoming data from that external computer, but not allow
> > incoming data from other external computers.
>
> That's
16 matches
Mail list logo
