Why might it be a mdadm problem?
All of the md devices are up and accessible from the 64-bit OS, and the
/etc/mdadm/mdadm.conf file appears to match the output of the command ' mdadm
--detail --scan' suggesting it is correct. Even if I mount the previous 32-bit
systems root partition (that just
Public bug reported:
I have a system with two main HDD configured as several md RAID-1 devices and I
installed the 32-bit version of 12.04.2 on to one of these partitions (using
the "alternate installer" ISO), with most of the others being user data (e.g.
one for /home, another for virtual mach
It is probably true that this has not been seen much as a bug due to DNS
normally being available, hence NIS dependency (if present) being a
secondary issue. However, we found that ntp did not recover by itself,
so possibly it only tries to find the nameservers once, but will re-try
for the time se
Yes, you are right in that our NIS servers are solaris boxes, and they
do support behind-the-scenes DNS lookups as it turns out. It is also
true that NIS is depreciated, though a lot of older installations like
ours still use it, and for most machines DNS is available and will
probably fix our spec
I think this bug should concentrate on the key issue: that ntp (and
maybe others?) is being brought up on the wrong event, that is it comes
up with the interface, and not with the chosen type of name server.
In our case NIS provides user and name server resolution, and ntp comes
up before it with
Yes, it looks very much like the DNS system is broken here, but when I
tried to look things up I get Bug #1001189 so overall not impressed with
12.04 so far :(
Still, adding some "dns-nameservers" lines to /etc/network/interfaces is
the next obvious thing to try.
--
You received this bug notific
These are the nsswitch results:
--
$ ls -l /etc/nsswitch.conf
-rw-r--r-- 1 root root 600 May 1 11:28 /etc/nsswitch.conf
--
$ cat /etc/nsswitch.conf
# /etc/nsswitch.conf
#
# Example configuration of GNU Name Service Switch functionality.
# I
It is somewhat odd, as I get this:
$ ping ntp0.dundee.ac.uk
PING ntp0.dundee.ac.uk (172.30.254.253) 56(84) bytes of data.
64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253):
icmp_req=1 ttl=254 time=0.281 ms
64 bytes from 443-gb-core-6513.private.dundee.ac.uk (172.30.254.253):
i
Results for 12.04 machine are:
$ ls -l /etc/resolv.conf
lrwxrwxrwx 1 root root 29 Apr 30 17:39 /etc/resolv.conf ->
../run/resolvconf/resolv.conf
$ cat /etc/resolv.conf
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGE
I am not 100% sure of how the network was configured (the guy who did it
is away today) but can report that the contents of
/etc/network/interfaces are:
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).
# The
Public bug reported:
We recently installed 12.04 LTS (32-bit) with NIS authentication and found two
bugs with ntp, the first was ntp was not installed (even though the clock
manager allowed, and defaulted to, "internet time") and the second more serious
bug reported here is we discovered that n
Thanks Robie for the quick reply, but I though 10.04.4 LTS would have
such bug-fixes included?
After all the ISO used to install is from after the date of the fix, and
the major package numbers are the same (comment #1 mentions 1:4.2.4p8
+dfsg-1ubuntu4 and my machine is reporting 1:4.2.4p8+dfsg-
This appears to be broken again, the 10.04 default profile has:
# vim:syntax=apparmor
# Last Modified: Tue Aug 11 16:14:21 CDT 2009
# Updated for Ubuntu by: Jamie Strandboge
@{NTPD_DEVICE} r,
So it only allows read-access to the devices. Also broken/reverted is
the tunables which has:
# La
So folks, what IS happening about this bug, already fixed, for a
package that is SUPPOSED to be supported in 10.04?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nagios3 in Ubuntu.
https://bugs.launchpad.net/bugs/669808
Title:
Nag
I see no activity here. Why is this not being maintained? It is not like
there is no bug fix - can someone at Canonical actually do something
useful about updating a *supported* LTS package?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed
If this is supposedly fixed, how come using "ssh -X user@server" still
hangs if you have run an X-windows program like 'eog' or similar?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/
Same here - would have thought that an update should be out by now.
It is supposed to be supported in LTS for 5 years and I presume
'support' includes pushing out established bug-fixes!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to n
Well it is not yet fixed for 10.04 with the 'proposed' updates. Tonight
just rebooted after updates to kernal 2.6.32-29 and guess what? Yes, my
syslog contained the following sort of message:
"Feb 15 21:45:24 paul-ubuntu kernel: [2.341704] EXT4-fs (sda5): 4
orphan inodes deleted"
So is 'propo
Public bug reported:
Binary package hint: pptpd
I tried building the pptpd-1.3.4 package from source to debug the
crashing behaviour it shows, however, I found that 'make install' put
the executables in the wrong location.
Line 175 of the Makefile had 'prefix = /usr/local' but the Ubuntu
locatio
With 10.04 i386 on my Dell Latitude 2100 laptop I find that attempting
to exit from "ssh -X usern...@remotemachine" is not returning to the
local command prompt after using an X-session on the remote machine. It
returns fine when I don't start an X program though.
Is this related to port forwardin
While I agree that the system should honour the chosen settings (so if you say
'manual time' that is really all you get), I would argue that all systems,
desktop and server, should ship with a minimum NTP setup. If the load on the
Ubuntu time server is of concern, then you could use the minpoll
*** This bug is a duplicate of bug 596859 ***
https://bugs.launchpad.net/bugs/596859
Is the segmentation-fault induced death of ntpd the expected result of
apparmor intervention?
If so then I guess this bug is closed with the bug #596859 closure
fixing (hopefully) the apparmor profile.
--
n
Public bug reported:
Binary package hint: ntp
While reporting and testing for bug #596010 using the 10.04 release
candidate I found that the intended user-tunable apparmor options in
/etc/apparmor.d/tunables/ntpd do not work correctly due to the settings
in /etc/apparmor.d/usr.sbin.ntpd including
Looking at the /etc/apparmor.d/usr.sbin.ntpd file it seems that any
@{NTPD_DEVICE} device is added as read-only, but most of the GPS like
things I have seen using serial ports are subject to writing to
configure and/or poll them for the time. Will raise that as another
bug...
--
ntpd sementation
Yes, the problem starts with the apparmour protection system not knowing
it should be allowed serial port access. However, I tried to edit
/etc/apparmor.d/tunables/ntpd to change the line to:
@{NTPD_DEVICE}=/dev/ttyS0
then restarted /etc/init.d/apparmor but that did to help, however,
adding this
If I remove the symlink, it works but without the GPS (as one might
reasonably expect) and this is the corresponding syslog message:
Jun 18 17:59:02 pscpc ntpd[3075]: refclock_open /dev/gps0: No such file or
directory
Jun 18 17:59:02 pscpc ntpd[3075]: configuration of 127.127.20.0 failed
So it l
Just to add, if I try gtkterm I can open and see the NMEA messages just
fine, so I don't know why it should report "refclock_open /dev/gps0:
Permission denied" in the first place.
--
ntpd sementation fault using NMEA driver
https://bugs.launchpad.net/bugs/596010
You received this bug notification
Public bug reported:
Binary package hint: ntp
I have an old Garmin GPS that I though I could use as a local time
source with NTP. It supports NMEA messages so I added the line to my
ntp.conf file:
server 127.127.20.0 # NMEA GPS
and created a symbolic link from /dev/gps0 -> /dev/ttyS
28 matches
Mail list logo
