several people have commented that they have the same or similar
problems
** Changed in: autofs5 (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to autofs5 in Ubuntu.
https://bugs.launchpad.
on the system where I had the problem I did this to verify the fix
- removed workarounds in main.cf
- sent emails and verified that they trigger the error and remain in the queue
- installed 2.9.3-2~12.04.4
-> bug is gone, mail works normally
** Tags removed: verification-needed
** Tags added: ver
Public bug reported:
on a (freshly installed) system with nis authentication, postfix is no longer
able to read aliases from the nis table mail.aliases.
in 10.04 it worked
symptoms are:
- errors in /var/log/mail.log:
warning: nis:mail.aliases is unavailable. unsupported dictionary type: nis
- an
it is an error for ypbind to not start correctly when the network
interface is managed by network-manager and thus comes up a bit slowly
of course, changing the configuration to not rely on network-manager, as
explained in comment #3 is a workaround
still i would consider this a bug: the manageme
just to add a data point: starting 2012-04-19 my lucid machine is
working with 3.17-31ubuntu0.10.04.3 from proposed with. A few nis
accounts are being used regularly. There have been a large number of
suspend resume cycles and various reboots without any nis related
problems.
--
You received this
I have installed 3.17-31ubuntu0.10.04.3 on lucid after purging the previous
version including our hand crafted upstart configuration.
- Installation went fine
- I have tested the function as a NIS client successfully
- starting after reboot works, it also survives a suspend/resume cycle
But I not
tested with an up-to-date maverick system
same procedure as above -> OK
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/561779
Title:
squid is not started on runlevel transition 1 ->
tested with lucid 10.04.3 -> OK
procedure:
with old package
- access the web through squid
- init 1
- init 2
- ps aux | grep squid # -> squid not running
with proposed package
- access the web through squid
- init 1
- init 2
- ps aux | grep squid # -> squid IS running
- access the web through squ
** Changed in: squid (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to squid in Ubuntu.
https://bugs.launchpad.net/bugs/809526
Title:
squid 2.7.STABLE9-2ubuntu5.1, reload kills squid, called in
this is an issue in maverick only
- lucid already uses 'restart squid' -> ok
- natty uses 'reload squid' and this works fine due to some other changes -> ok
- I do not know about oneiric but I guess it works like natty
yes, the fix is indeed as you describe it in comment #1.
I applied that fix by
well, i guess originally this bug had been about 'reload' not working
correctly (#7), but focus has shifted over time.
To keeps things simple I have created a new bug report for the remaining
maverick problem at
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/809526
--
You received this bug
Public bug reported:
this is a leftover issue from bug
https://bugs.launchpad.net/ubuntu/+source/squid/+bug/561750
I am creating a new bug report to leave complicated history behind.
The maverick squid package 2.7.STABLE9-2ubuntu5.1 calls 'reload squid' in
/etc/resolvconf/update-libc.d/squid
Th
the new maverick package 2.7.STABLE9-2ubuntu5.1 still has the problem that
squid is killed when the
resolvconf script is called, exactly as described in comment #7 above.
The maverick packages still has 'reload squid' in /etc/resolvconf/update-
libc.d/squid. This kills squid, so that it is not r
now I have tested squid 2.7.STABLE7-1ubuntu12.3 on lucid (on a copy of
the system where this bug report originated)
-> squid starts with network not yet available
-> invocation of /etc/resolvconf/update-libc.d/squid does no longer kill it
-> everything else is normal
Thus verified.
There is one t
I tested the package from maverick-proposed against the current package
from maverick: both of the problems that were discussed in this bug
report are now gone (squid starts sucessfully with network not being
available yet, resolvconf script reloads the squid configuration and
does not kill squid)
In my setup this bug causes excessive boot delays. I want to question
the "wishlist" importance.
--
NIS upstart dependancy broken for lucid
https://bugs.launchpad.net/bugs/569757
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nis in ubunt
Runlevel changes have been an essential functionality of unix / linux
for a long time. You could use them for regular administration tasks.
Now this stopped to work. This bug is a regression.
--
squid is not started on runlevel transition 1 -> 2
https://bugs.launchpad.net/bugs/561779
You receive
- there is no respawn option in /etc/init/squid.conf (but I think this
wouldn't normally be a problem, except when squid crashed by itself)
- there is exactly one thing that does something to squid when the dsl-
interface is brought up (I have resolvconf installed which is suggested
by the squid p
$ grep squid /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
$ grep init: /var/log/syslog
Apr 14 07:38:33 rechner6 init: squid main process (1086) killed by HUP signal
Apr 14 07:38:33 rechner6 init: ssh main process (1095) terminated with status
255
** Attachment added: "/etc/default/squid"
http://launchpadlibrarian.net/44118845/squid
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs/561750
You received this bug notification because you are a member of Ubuntu
Server Team, which is
I have an ethernet interface with a static IP address, there is no
traffic routed to the internet over this interface.
Secondly there is a dsl-connection (pppoe) that provides the route to
the internet.
See also attached file /etc/network/interfaces
But I also have changed /etc/default/squid to
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43958720/Dependencies.txt
--
squid is not started on runlevel transition 1 -> 2
https://bugs.launchpad.net/bugs/561779
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed t
Public bug reported:
Binary package hint: squid
when you go to runlevel 1 for maintenance with 'telinit 1', squid is
stopped correctly
when you go back to runlevel 2 with 'telinit 2' squid is not started
because /etc/init/squid.conf does not contain a condition for that.
in karmic, squid would
** Attachment added: "squid log file"
http://launchpadlibrarian.net/43955964/cache.log
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/43955337/Dependencies.txt
--
squid starts and stops immediately (after upgrade from karmic to lucid)
https://bugs.launchpad.net/bugs
Public bug reported:
Binary package hint: squid
after booting, squid starts normally, and then stops again immediately.
There is no error (see logfile).
After that i can start squid with 'sudo start squid' and it works
flawlessly (this bug report is made through it).
ProblemType: Bug
DistroRele
Indeed, a default install of karmic->autofs has
DISABLE_DIRECT=1
in /etc/default/autofs
This is also documented in /usr/share/doc/autofs/README.direct
A workaround might be to use autofs5.
According to the original poster the behaviour changed at some point in
time. The reason remains uncle
this bug is still present in karmic
lines in auto.master starting with /- seem to be just ignored
** Changed in: autofs (Ubuntu)
Status: Won't Fix => Confirmed
--
AutoFS direct maps not working with NFSv4 exports
https://bugs.launchpad.net/bugs/369682
You received this bug notification be
the question asked in the terminal window was "do you want to keep your
smb.conf or install the one provided in the package"
below are some excerpts from /var/log/dist-upgrade/term.log (which is in
German, but you will identify what happens)
for other packages where the questions were asked corre
Public bug reported:
Binary package hint: samba-common
on update to jaunty, configuration questions are asked in curses dialog
inside the terminal-window of the update manager.
But debconf is configured to use kde, and questions for other packages
actually have been asked with kde dialogs
** Af
29 matches
Mail list logo
