LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Fedora (https://www.linuxquestions.org/questions/fedora-35/)
-   -   log warnings and errors - are these serious? (https://www.linuxquestions.org/questions/fedora-35/log-warnings-and-errors-are-these-serious-289066/)

bcal 02-11-2005 04:36 PM

log warnings and errors - are these serious?
 
this seemed to span a few forums so I thought I'd stick it here...i've just discovered the various logs available to me in the system menu in FC2. All I'm using the machine for is a standard (dual-boot with XP) PC - it's not being run as a server or anything. Kernel version is 2.6.10. Everything on the system seems to work, so are any of the following things that I should worry about?

1) what is mdmpd? The last message in boot log is:
Feb 11 19:03:49 Localhost mdmpd: mdmpd failed

2) there is also a repetitive warning in the security log:
Feb 9 22:16:18 Localhost sshd[2140]: error: Bind to port 22 on 0.0.0.0 failed: Address already in use.

3) Also in the security log:
Feb 11 19:01:52 Localhost kernel: There is already a security framework initialized, register_security failed.

4) in the system log
Feb 11 19:01:52 Localhost kernel: vesafb: probe of vesafb0 failed with error -6
and
Feb 11 19:03:41 Localhost kernel: cdrom: open failed.
(although I can mount cd's etc without any problem)

I realise that some of these errors are probably specific to the setup on my machine, but any general ideas on whether they're serious would be appreciated. Thanks in advance.

hob 02-12-2005 10:22 AM

It's definitely a Fedora question, so I think that you posted to the right forum.

I suspect that the basic problem is that you aren't using a supplied kernel for FC2. This error suggests problems with SELinux:

"Feb 11 19:01:52 Localhost kernel: There is already a security framework initialized, register_security failed."

None of these errors are likely to cause your system to just die and lose all your data, but I couldn't guarantee the stability of it because there may be other issues arising from the kernel mismatch.

bcal 02-12-2005 02:26 PM

I did compile the kernel from source because of....err, was it the modem or the graphics card required that...? Modem I think. Is that what you mean by an unsupplied kernel? I'll boot up with the kernel that originally came with the distro and see if the logs show up the same things.

Is there a FC2-specific kernel distributor?

hob 02-12-2005 04:13 PM

It's my mistake - I assumed that 2.6.10 would be too new to have been packaged for FC2, but I can see that there is an official package for it.

Recompiling is probably the root cause, then. You may have recompiled with different graphics or SELinux options.

The SSH error is harmless. The mdmpd error is probably also harmless - the man page says it's for software RAID.


All times are GMT -5. The time now is 10:59 AM.