Sounds like the maintainers have Mozilla'd everything up for some of you
here. You may want to use the Apache2 PPA repo of the Debian/Ubuntu PHP
maintainer Ondřej Surý instead of this hot mess, like I have for the
past few years, since I find that I need it for PHP anyway. It can be
found at: https
Cool, glad to hear that an issue I uncovered has been fixed...a little
confused as to why an official fix took 18 months to deploy though,
considering it took me about 18 minutes.
On Fri, Nov 27, 2020 at 8:42 AM Timo Aaltonen <1832...@bugs.launchpad.net>
wrote:
> Hello RedScourge, or an
UPDATE: I just had a server experience downtime due to this bug. An
update of the apache2 package was automatically triggered on a client's
16.04 LTS server on Aug 31 via the unattended-upgrades cron script, and
apparently before this update, the last time the Apache service had been
restarted was
While not relevant to nodejs, I'll add an anecdote that I was trying to build
older versions of php via phpbrew on 18.04 for development purposes, and ran
into a similar issue due to this libssl1.0-dev vs libssl1.1-dev issue.
The issue is that seemingly some of the -dev libraries required to bui
** Also affects: net-snmp (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1794589
Title:
libssl1.0-dev conflicts libssl-dev
To manage notification
(if someone could redact the domain names and file paths from the above
comment that would be much appreciated)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1832182
Title:
systemd unable to detect
Output showing how to reproduce the issue:
root@server:/usr/local/sbin# apache2ctl stop
root@server:/usr/local/sbin# apache2ctl graceful
httpd not running, trying to start
root@server:/usr/local/sbin# systemctl status apache2.service
? apache2.service - The Apache HTTP Server
Loaded: loaded (/l
Public bug reported:
When starting or restarting Apache via the /usr/sbin/apache2ctl script,
systemd becomes unaware of the state of Apache, causing "systemctl
status apache2.service" to report "Active: inactive (dead)". Below I
describe the issue and a fix; attached is the output of the diff comm
** Changed in: samba (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD DC aft
Good news!
I installed the update and rebooted and it did not work, smbclient
commands returned NT_STATUS_NO_LOGON_SERVERS. But after also adding
"client ipc signing = auto" to smbd.conf as per Tony Haley's
recommendation in comment #20, and after another reboot, it is working
as expected with jus
Hi all,
I will try to remember to test the samba update after the users leave
for the day, as I have to take the new PDC which works offline in order
to test this. The "libsoup" thing referred to in the link that Marc
provided does not seem relevant to us, as we did not even have that
package inst
Since it only took me 3-5 hours to build a 16.04 LTS AD DC running 4.3.8
and the bind DNS backend, I suspect that this might just be the easiest
way to go.
Just to repeat as a warning, upgrading my existing DC from 4.1.6 to
4.3.8 on 14.04 LTS resulted in a broken DC for me, so rather than just
upg
Hi all,
I appear to have solved this issue for myself by setting up an entirely
new AD DC today based on 16.04 LTS, and joining it to the existing
domain. I took no action at all on the affected system, and yet today
after setting that new system up, the affected system seems to be
connecting prop
Whoops, that's supposed to be example.org, to match with the above. I
was changing my organization name.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check
To be clear, neither example.org or example.com are my actual samba
domain.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1572824
Title:
Samba Domain Member cannot check passwords against Samba AD D
I am not running winbind on the DC. The options I have tried in their
various combinations are server signing = off, server signing = auto,
and client signing = off. I have tried them on just the 12.04 server,
and also on both the 12.04 server and the AD DC. Nothing seems to
resolve the problem for
Here is my current samba AD DC config, after removing the signing
option:
# Global parameters
[global]
workgroup = SAMDOM
realm = samdom.example.com
netbios name = FILESERV2
server role = active directory domain controller
server services = -dns
os
Public bug reported:
Hi,
I updated Samba on my old web server which is running a fully updated
12.04.5 LTS, and now I cannot get it to act as a domain member anymore.
All password validation requests fail. Only way to access this server
once more is to manually add local users with usernames and
This bug affects me as well, but only one of my several servers, and
about 20% of the time when I reboot, it crashes trying to mount the root
fs on startup. I tried booting to the 3.13.0-24 kernel, fully
uninstalling the 3.13.0-68 kernel, then reinstalling it, but the
Plymouth issue still remains,
I have installed the update, and testing with the latest Chrome and IE
browsers on Windows 7 confirms that they now recognize our server as
running TLS1.2!
Thanks for the fix!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
I get something similar when I run that command for my own domain name:
SSL-Session:
Protocol : TLSv1.2
Cipher: DHE-RSA-AES256-GCM-SHA384
However, I still get the warning in apachectl configtest :
SSLProtocol: Illegal protocol 'TLSv1.2'
Action 'configtest' failed.
I am going to ass
>From the Apache 2.2 documentation:
TLSv1.1 (when using OpenSSL 1.0.1 and later)
A revision of the TLS 1.0 protocol, as defined in RFC 4346.
TLSv1.2 (when using OpenSSL 1.0.1 and later)
A revision of the TLS 1.1 protocol, as defined in RFC 5246.
I suspect that the issue is that the current vers
This should not be considered imcomplete now and thus should not have
expired.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400473
Title:
Apache 2.2 on Ubuntu 12.04 LTS only supports TLS1.0 which
It was a one-off. I can assure you that this should be considered a bug,
whether or not the functionality is intentional. Think about it, let's
say you are a regular user who just restarted your Windows machine, only
to discover that for whatever reason, you suddenly are completely unable
to log in
Tried that just now. I got the following error:
Syntax error on line 29 of /etc/apache2/sites-enabled/{redacted}:
SSLProtocol: Illegal protocol 'TLSv1.1'
Action 'configtest' failed.
The Apache error log may have more information.
Error log did not have more info (probably because it was only a co
Sorry, the output of dpkg-query was rather inconveniently truncated, I
am infact using version "2.2.22-1ubuntu1.7" of those packages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1400473
Title:
Ap
Sorry for the incomplete details.
The problem is when I set the SSLProtocol parameter in Apache as
follows:
SSLProtocol all -SSLv2 -SSLv3 -TLSv1
or:
SSLProtocol TLSv1.1 TLSv1.2
I received the following message in the server logs:
[Mon Dec 08 12:32:38 2014] [error] No SSL protocols available [
The bug was that libaprutil1-dbd-freetds version 1.5.3-1 is missing from
14.04 LTS, whereas 12.04 LTS comes with libaprutil1-dbd-freetds version
1.5.2-1, and the absence of this package prevented what would otherwise
be a reasonably straightforward compiling of a fairly standard program
on 14.04 wh
Public bug reported:
I can find version 1.5.2-1 on one of the sites somewhere and download
it, but that is not compatible with other dependencies. It looks like
either someone forgot to compile this library, or it is perhaps obscured
in some other package that is difficult to find.
Because of thi
This new TLS 1.2 support does not seem to be reflected in Apache2 on
12.04 LTS. It's all well and good that OpenSSL may now be running 1.0.1,
but it does not look as though apache has been recompiled against it,
and so it is still stuck with only TLS 1.0, which is vunerable to the
BEAST attack, the
Public bug reported:
For PCI compliance, one must not be vulnerable to the POODLE or BEAST or
CRIME attacks. POODLE suggests removing SSLv2 and SSLv3, and BEAST
suggests removing TLSv1. However, since TLSv1.1 and TLSv1.2 do not seem
to be supported by apache 2.2 on 12.04 LTS, and since apache 2.4
*** This bug is a duplicate of bug 44609 ***
https://bugs.launchpad.net/bugs/44609
When I tried dropping into a shell at various points during the install,
those commands did not work at any point. I imagine it has to be in
there _SOMEWHERE_ so as to allow actual partitioning, but I wouldn't b
*** This bug is a duplicate of bug 1263540 ***
https://bugs.launchpad.net/bugs/1263540
Have installed several fresh 14.04 and 14.04.1 LTS x64 servers straight
off the iso image in the past few weeks, and this has presented itself
on all of them.
--
You received this bug notification because
14.04 LTS and 14.04.1 LTS x64 both present this error after fresh
install, and again after adding the virtualbox repo.
W: GPG error: http://download.virtualbox.org trusty InRelease: The following
signatures couldn't be verified because the public key is not available:
NO_PUBKEY 54422A4B98AB5139
Same errors came up after reboot, but it seemed to progress past it
anyway. Here's a boot.log after the updates, still quite clearly showing
the failure to map the partition but seemingly eventually succeeding and
getting past it (rather quickly too, actually):
Begin: Mounting root file system ...
I can confirm that this happened to me on a fresh install of Ubuntu
14.04.1 LTS via an expert mode install where I didn't really customize
any of the options that allows, on an older Core 2 Duo E6800 based
system with linux-server kernel choice, with triple drive raid 1 on 1TB
msdos partition table
I tried to find which package it might be, and all I got was either "too
many results" or "no results". Brilliant.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1394091
Title:
Partitioning experienc
Yes, I found this automated message to be inappropriate, not to say that
I believe my tone was, but rather because THE INSTALLER IS NOT A PACKAGE
as far as I can tell.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Public bug reported:
Hi,
I am trying to install Ubuntu 14.04.1 LTS x64 from a freshly burned CD
that passed verification.
I am getting to the part where the partitioner is supposed to let me
configure things, and I wanted to blow away an existing raid+lvm setup
on the drives and install a new sy
And probably worst of all, is the fact that apparently for my own
safety, at various points I would like to be able to write out the
partition table, but it refuses, because OMG, YOU DON'T HAVE ANY MOUNT
POINTS YET, SO NOW ALL YOU CAN DO IS UNDO ALL CHANGES MWAHAHAHA!
--
You received this bug not
Public bug reported:
Problem:
Apparently some package was updated which caused a file /etc/nologin to
be created and not deleted afterward, and this caused me to be unable to
log in to the system. Thank goodness I overrode the default behavior of
10.04 LTS of protecting me from myself by disallow
** Attachment added: "actual_link.jpg"
https://bugs.launchpad.net/bugs/1048776/+attachment/3306029/+files/actual_link.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1048776
Title:
Page on lau
Public bug reported:
If you are an intermediate linux user who is fairly new to Ubuntu and
has chosen an LTS distro (no GUI), when you notice something wrong, it
is pretty damn near impossible to report a bug.
There is one tiny link about 7 pages down on the Reporting Bugs page
which is the right
In the meantime until this is fixed, you can just mv /etc/samba/smb.conf
/etc/samba/smb.conf.backup and finish the install and it should succeed.
Source:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=659775#24
** Bug watch added: Debian Bug tracker #659775
http://bugs.debian.org/cgi-bin/bu
Holy cow you're right, I definitely need to get to 5.2.17 somehow.
I've compiled PHP before with configure and make, but I'm not familiar
at all with any of these other build tools you mention. I'm sure nobody
wants to be teaching everyone how to do all this stuff or be doing it
for them. Could yo
Sorry for being rude, but as you might imagine this whole situation was
frustrating, and it was not the first time some little thing about
Ubuntu LTS caused me much main and suffering. Not as much as RedHat but
that's another story. Getting logged in and posting was even more
frustrating as the sit
would be awesome if this would be done, or if an optional php5-gd-
boutell package could be created that does this. I know this would work,
because I am currently running the default php5 package from karmic and
only had to swap in my recompiled php5-gd package,
php5-gd_5.2.10.dfsg.1-2ubuntu6.10_am
I installed PHP 5.2.X on Lucid which normally comes with 5.3.X as I have
old code I cannot yet change.
This lead to a headache recompiling PHP with the proper GD library
because libaprutil1-dev and apache2-prefork-dev depend on their
respective non-dev packages, so in order to satisfy the dependen
I managed to compile PHP finally, and all it took was several hours and
countless steps. It's so simple your kids can do it!
Process (roughly, your mileage may vary, and i may have forgotten a
step):
cd /tmp
apt-get source php5
apt-get install build-essential debhelper fakeroot
vi /etc/apt/source
Public bug reported:
Background:
Like MANY server admins who use PHP and run some old code, I have two
requirements that are not what the Ubuntu package team has deemed as
they way they want to support out of the box:
- PHP 5.2.X branch on a Lucid server
- Compiled with PHP's original bundled GD
I don't really know what triggered it so reproducing it may take time,
or may never even happen. I am going to try doing another fresh install
of Lucid in the next 30 days and if it happens again on that install, I
will definitely report it here.
--
permissions on /var mysteriously changed to 064
I've come to a workaround solution, adding the following to
/etc/modprobe.d/options and rebooting:
options xt_recent ip_pkt_list_tot=255 ip_list_tot=255
ip_list_hash_size=0
Still, I believe this issue needs to be addressed, since a hitcount
default max of 20 seems extremely useless, especially in
AHA! hitcount cannot be over 20 now...wtf? I used to use 500 in Fedora
Core 5, then I couldn't go over I think 255 in Ubuntu 8.04 (I just
remembered this because that was ages ago), and now I can't go over 20!
WTF!
--
can no longer use iptables recent module multiple times after upgrade to lucid
update: the other "recent" rule seems to be fine, there's something with
this line that's the problem:
-A rate-limit-wall -m comment -m state -m recent --state NEW -j LOGDROP
--update --seconds 20 --hitcount 100 --comment "drop over 300 conn/min"
The only difference with this is that the other ru
er...10/min, not 20/min for ssh connections...whatever, it's a minor
typo in that message.
--
can no longer use iptables recent module multiple times after upgrade to lucid
https://bugs.launchpad.net/bugs/580169
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Binary package hint: iptables
I upgraded from hardy 8..04 LTS to lucid 10.04 LTS and my iptables rules
stopped working.
I use the recent module to mark new connections, and then block if over
X new connections occur in general then again if over X new connections
occur to so
openssh-server was also removed and failed to be re-added in a similar
fashion to samba, but I did not think to grab info regarding how i fixed
it, etc. The same uploaded zip file should contain info about it. It
also broke my iptables somehow but it might be due to my rules and a new
version of ip
** Attachment added: "zipped contents of /var/log/dist-upgrade/"
http://launchpadlibrarian.net/48364121/update-manager.zip
--
upgrade from hardy to lucid uninstalls samba
https://bugs.launchpad.net/bugs/579736
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Public bug reported:
Binary package hint: update-manager
I upgraded from 8.04 LTS to 10.04 LTS. This is a fairly standard install
because all I need to do on this box is apache, mysql, samba, and sshd.
I had customized the config files of samba, (no errors in the config!)
and I guess because of
For what it's worth, I can't think of any need to ever change
permissions on /var and I certainly would not do it. I will provide any
info you require.
New hardware, new install, all I've done is add a bunch of packages
suitable for a webserver (apache, php, mysql, related packages, etc, and
some
60 matches
Mail list logo
