By default, people should not see this message in 10.04 LTS because the
default syslog daemon was swiched from sysklogd to rsyslog, which does
not generate it.
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ub
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubu
Hey, I have checked through this to try and reproduce this issue and I
can't find this error in my kernel logs (or any other log).
Thanks for checking back, I totally forgot about this bug.
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification
Hi Brian,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
If it remains a
** Changed in: sysklogd (Ubuntu)
Assignee: Lars Wirzenius (liw) => (unassigned)
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubu
** Tags added: review-request
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
Running Karmic with kernel 2.6.31-5-generic, this scary message still
exist; searching this file return /boot. My system hangs too & i have to
type exit in initramfs to continue booting ( same than post 40).
Suggestion: as this message is useless but scary, can we redirect it to
> null , waiting t
Thank you for the fast reply, Lars.
This is indeed a different bug, although I have no RAID:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/278176
Adding "rootdelay=90" works for me.
/boot/grub/menu.lst:
kernel /boot/vmlinuz-2.6.28-13-server
root=UUID=d1f6f883-efff-43cd-af15-110b7
metastable, as discussed above by Adam Conrad, the message about not
being able to find a map file is harmless, it just sounds scary. Your
problem is almost certainly caused by something else, so please file a
new bug about that, or ask on one of the support channels for help.
** Changed in: syskl
Same problem !
Jul 17 13:45:16 srv syslogd 1.5.0#5ubuntu3: restart.
Jul 17 13:45:16 srv kernel: Inspecting /boot/System.map-2.6.28-13-server
Jul 17 13:45:16 srv kernel: Cannot find map file.
The map file is present. This bug causes problems after issuing a
reboot. The server reboots, but hangs at
Hello!
I'm not sure if this is of any use at this point, but I just found this
too, running 2.6.30rc5
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
Adam, I think the issue there is that klogd does not (as far as I know)
have any reliable way of detecting that the running kernel was compiled
with that option enabled; while it's true on ubuntu systems that
/boot/config-$(uname -r) exists, it's not guaranteed to exist
generically, and I don't see
The code in sysklogd, file ksym.c, seems to be looking for a symbol
Version_[0-9]+ in all System.map-$version files it knows. However, the
Ubuntu map files don't seem to include that symbol.
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification
from init/version.c:
#ifndef CONFIG_KALLSYMS
#define version(a) Version_ ## a
Looks like this is an intentional optimization, and the real buglet here
is just that klogd should perhaps be made intelligent enough to realize
it's loading on a KALLSYMS kernel, and suppress its error message (or
print
For the record, though the error message from klogd is both misleading
and (for some) a bit scary, the fact that klogd isn't loading System.map
appears to be completely harmless for us.
Our kernels are built with KALLSYMS=y, so we're getting symbol names in
stack traces anyway, despite klogd's ina
** Changed in: sysklogd (Ubuntu)
Assignee: Ubuntu Foundations Team (ubuntu-foundations) => Lars Wirzenius
(liw)
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: sysklogd (Ubuntu)
Assignee: (unassigned) => Ubuntu Foundations Team (ubuntu-foundations)
--
sysklogd cannot find map file
https://bugs.launchpad.net/bugs/277924
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
If you look at the top of /etc/init.d/klogd there is the following
comment and option line
# Use KLOGD="-k /boot/System.map-$(uname -r)" to specify System.map
#
KLOGD="-P $kmsgpipe"
I changed it to the following like the comment suggested.
KLOGD="-P $kmsgpipe -k /boot/System.map-$(uname -r)"
I
18 matches
Mail list logo
