Hi,
I have recently upgraded to fedora 21 (kernel version 3.17.8-200.fc20.x86_64) and I cannot find
/var/log/dmesg and /var/log/messages !
Have been removed? Is this because the OS's are going to replace init? Or, this is a problem in my system?
Hello
I am trying to log the Kernel level PPPd raw PPP messages (version 2.4.2) using Linux kernel 2.6.x to the /etc/syslog or /var/log/messages but the logging is not enabled for some reason.
I pass the kdebug 7 or kdebug 31 to the PPPd using /etc/ppp/options but the Kernel level debug logs are not shown in /proc/kmsg or using klogd or syslogd.
Can anyone please help me to fix this. What might be the problem?
Please reply..
Thanks,
Rakesh
Friends ,
Recently I got two problem in my redhat machine :
version :
[root@pbltest ~]# cat /etc/issue
Enterprise Linux Enterprise Linux Server release 5.4 (Carthage)
Kernel \r on an \m
my vsftpd service is not started . I remove it and clean install and when I make restart then it stops but not started successfully .
When I check the log of "/var/log/messages" , then I found 'message' file is empty . I rename it and reboot the server but it doesnt generate any messages .
Please help me to resolve it .. ...
Hello
I have installed a CentOS 6.4 on VmWare.
Now, after several days of using it, it suddenly does not boots. There is a problem with its initialization, here is the error:
Kernel Panic : Unalble to init. Try passing init= option to the kernel.
Pid 1 : Swapper not tainted.
I have used CentOS.iso to rescue it, but it still does not solve it.
My grub.conf contains:
PHP Code:
# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/sda2
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title CentOS (2.6.32-358.el6.x86_64)
root (hd0,0)
kernel /vmlinuz-2.6.32-358.el6.x86_64 ro root=UUID=6082bcf5-00ba-4bf8-86ea-9821d774cb6f rd_NO_LUKS rd_NO_LVM LANG=en_US.UTF-8 rd_NO_MD SYSFONT=latarcyrheb-sun16 crashkernel=auto KEYBOARDTYPE=pc KEYTABLE=us rd_NO_DM rhgb quiet
initrd /initramfs-2.6.32-358.el6.x86_64.img
How should I solve it then? Thanks in advance
hello,
I have a CentOS system and I want to prevent the boot messages from appearing during bootup. I have added the quiet option in grub.conf file which hides the boot messages, but after pressing the esc key or the arrows it shows up again.
Is it possible to hide it permanently?
Or not show the boot logs when the basic(esc or arrow) keys are pressed but assign a different set of key combos which when pressed, then only the boot messages should be visible.
Thankyou
Hi, I can see the below mentioned logs writing every second into /var/log/messages.
"setroubleshoot: SELinux is preventing /usr/bin/perl from ioctl access on the file /usr/share/perl5/Exporter.pm. For complete SELinux messages. run sealert -l e6a1fd7e-a8c0-44bc-91db-b550f85f31c2"
Can anyone help me to find the root cause of this and how to fix it also?
Thanks in advance,
George
Hi. I am relatively new to linux systems. I recently jumped on an endeavor to install a vanilla kernel (3.18.5) from the kernel website. Its Documentation/Changes file mentions the minimum version requirements of the packages needed. For udev, it mentioned
Code:
udevd --version
to check the version number. But looking around I found for Fedora its
Code:
udevadm --version
(I'm using Fedora Workstation 21 64-bit). Is there any fundamental difference between these two utilities? Any explanation would be helpful.
I am going to attempt to dual boot both fedora 17 and fedora 21, as my printer can print from FC17 but not from FC21 - posted about this issue in the hardware forum.
I am rather surprised at the level of competence of people posting here, even though it says newbie forum - so I think that this is possibly where I belong too.
I have set up grub to see my fedora 17 kernel - the only problem is, that the root filesystem needs to belong to the fedora 17 kernel as opposed to the fedora 21 kernel. I can't see myself changing fc 21's fstab to have the old lv root device mounted - as /etc belongs to the root partition of fc 21.
I did change the device to reflect the old kernel's root lv partition in the /etc/fstab (fc17), but this doesn't seem to do it.
Does someone know what I am missing?
When I start the VMware Player on Fedora 21, I am unable to execute the VMware Player 10. It is throwing errors at me.
Here is the error message log when I run the VMware Player GUI startup.
Any help is appreciated. Thanks
Code:
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Log for VMware Workstation pid=4108 version=10.0.4 build=build-2249910 option=Release
2015-04-16T07:14:16.917-08:00| vthread-3| I120: The process is 64-bit.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Host codepage=UTF-8 encoding=UTF-8
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Host is Linux 3.19.3-200.fc21.x86_64 Fedora release 21 (Twenty One)
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Msg_Reset:
2015-04-16T07:14:16.917-08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/usr/lib/vmware/settings": No such file or directory.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: ----------------------------------------
2015-04-16T07:14:16.917-08:00| vthread-3| I120: PREF Optional preferences file not found at /usr/lib/vmware/settings. Using default values.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: Msg_Reset:
2015-04-16T07:14:16.917-08:00| vthread-3| I120: [msg.dictionary.load.openFailed] Cannot open file "/home/asif2k/.vmware/config": No such file or directory.
2015-04-16T07:14:16.917-08:00| vthread-3| I120: ----------------------------------------
2015-04-16T07:14:16.917-08:00| vthread-3| I120: PREF Optional preferences file not found at /home/asif2k/.vmware/config. Using default values.
2015-04-16T07:14:16.917-08:00| vthread-3| W110: Logging to /tmp/vmware-root/vmware-modconfig-4108.log
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Obtaining info using the running kernel.
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Created new pathsHash.
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Setting header path for 3.19.3-200.fc21.x86_64 to "/lib/modules/3.19.3-200.fc21.x86_64/build/include".
2015-04-16T07:14:16.928-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:16.929-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:16.929-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:16.929-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:16.938-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:16.938-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid. Whoohoo!
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmmon module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmnet module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmblock module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vmci module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Reading in info for the vsock module.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Setting vsock to depend on vmci.
2015-04-16T07:14:17.122-08:00| vthread-3| I120: Invoking modinfo on "vmmon".
2015-04-16T07:14:17.125-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2015-04-16T07:14:17.125-08:00| vthread-3| I120: Invoking modinfo on "vmnet".
2015-04-16T07:14:17.128-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.128-08:00| vthread-3| I120: Invoking modinfo on "vmblock".
2015-04-16T07:14:17.132-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.132-08:00| vthread-3| I120: Invoking modinfo on "vmci".
2015-04-16T07:14:17.135-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.135-08:00| vthread-3| I120: Invoking modinfo on "vsock".
2015-04-16T07:14:17.139-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 0.
2015-04-16T07:14:17.154-08:00| vthread-3| I120: to be installed: vmnet status: 0
2015-04-16T07:14:17.154-08:00| vthread-3| I120: to be installed: vmci status: 0
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Obtaining info using the running kernel.
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Setting header path for 3.19.3-200.fc21.x86_64 to "/lib/modules/3.19.3-200.fc21.x86_64/build/include".
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.172-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.172-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.172-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.182-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.182-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid. Whoohoo!
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Kernel header path retrieved from FileEntry: /lib/modules/3.19.3-200.fc21.x86_64/build/include
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Update kernel header path to /lib/modules/3.19.3-200.fc21.x86_64/build/include
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.364-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.364-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.364-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.374-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.374-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid. Whoohoo!
2015-04-16T07:14:17.375-08:00| vthread-3| I120: Found compiler at "/usr/bin/gcc"
2015-04-16T07:14:17.380-08:00| vthread-3| I120: Got gcc version "4.9.2".
2015-04-16T07:14:17.380-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.380-08:00| vthread-3| I120: Using user supplied compiler "/usr/bin/gcc".
2015-04-16T07:14:17.384-08:00| vthread-3| I120: Got gcc version "4.9.2".
2015-04-16T07:14:17.385-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.390-08:00| vthread-3| I120: Trying to find a suitable PBM set for kernel "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.390-08:00| vthread-3| I120: No matching PBM set was found for kernel "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.390-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.390-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.390-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.390-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.390-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.400-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.400-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid. Whoohoo!
2015-04-16T07:14:17.401-08:00| vthread-3| I120: The GCC version matches the kernel GCC minor version like a glove.
2015-04-16T07:14:17.401-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.401-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.401-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.401-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.411-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.411-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid. Whoohoo!
2015-04-16T07:14:17.411-08:00| vthread-3| I120: Using temp dir "/tmp".
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Obtaining info using the running kernel.
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Setting header path for 3.19.3-200.fc21.x86_64 to "/lib/modules/3.19.3-200.fc21.x86_64/build/include".
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Validating path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for kernel release "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.412-08:00| vthread-3| I120: Failed to find /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h
2015-04-16T07:14:17.412-08:00| vthread-3| I120: /lib/modules/3.19.3-200.fc21.x86_64/build/include/linux/version.h not found, looking for generated/uapi/linux/version.h instead.
2015-04-16T07:14:17.412-08:00| vthread-3| I120: using /usr/bin/gcc for preprocess check
2015-04-16T07:14:17.421-08:00| vthread-3| I120: Preprocessed UTS_RELEASE, got value "3.19.3-200.fc21.x86_64".
2015-04-16T07:14:17.422-08:00| vthread-3| I120: The header path "/lib/modules/3.19.3-200.fc21.x86_64/build/include" for the kernel "3.19.3-200.fc21.x86_64" is valid. Whoohoo!
2015-04-16T07:14:17.601-08:00| vthread-3| I120: Invoking modinfo on "vmnet".
2015-04-16T07:14:17.605-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.605-08:00| vthread-3| I120: Invoking modinfo on "vmci".
2015-04-16T07:14:17.609-08:00| vthread-3| I120: "/sbin/modinfo" exited with status 256.
2015-04-16T07:14:17.661-08:00| vthread-3| I120: Setting destination path for vmnet to "/lib/modules/3.19.3-200.fc21.x86_64/misc/vmnet.ko".
2015-04-16T07:14:17.661-08:00| vthread-3| I120: Extracting the vmnet source from "/usr/lib/vmware/modules/source/vmnet.tar".
2015-04-16T07:14:17.667-08:00| vthread-3| I120: Successfully extracted the vmnet source.
2015-04-16T07:14:17.667-08:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-g1ZENn/vmnet-only auto-build HEADER_DIR=/lib/modules/3.19.3-200.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2015-04-16T07:14:19.833-08:00| vthread-3| W110: Failed to build vmnet. Failed to execute the build command.
2015-04-16T07:14:19.836-08:00| vthread-3| I120: Setting destination path for vmci to "/lib/modules/3.19.3-200.fc21.x86_64/misc/vmci.ko".
2015-04-16T07:14:19.836-08:00| vthread-3| I120: Extracting the vmci source from "/usr/lib/vmware/modules/source/vmci.tar".
2015-04-16T07:14:19.844-08:00| vthread-3| I120: Successfully extracted the vmci source.
2015-04-16T07:14:19.844-08:00| vthread-3| I120: Building module with command "/usr/bin/make -j8 -C /tmp/modconfig-g1ZENn/vmci-only auto-build HEADER_DIR=/lib/modules/3.19.3-200.fc21.x86_64/build/include CC=/usr/bin/gcc IS_GCC_3=no"
2015-04-16T07:14:21.915-08:00| vthread-3| W110: Failed to build vmci. Failed to execute the build command.
Thanks
We're unable to upgrade our environment beyond CentOS 5.10. This is a webserver that has certain reliances to the specific version of the OS, long story short.
I was asked to install a plugin for Redmine that requires at least ruby 1.8.7 so I cloned our VM as a new machine to test functional checkout. The problem is, the existing installation of Ruby was also installed ad hoc (not from any repo or yum methods) and it's currently at 1.8.5. The 1.8.7 version I tried to install gives me the following:
Quote:
# rpm -Uvf ruby-1.8.7.374-2.el6.x86_64.rpm warning: ruby-1.8.7.374-2.el6.x86_64.rpm: Header V3 RSA/SHA1 signatu NOKEY, key ID c105b9de error: Failed dependencies: rpmlib(FileDigests) <= 4.6.0-1 is needed by ruby-1.8.7.374-2.el6.x86_64 ruby-libs = 1.8.7.374-2.el6 is needed by ruby-1.8.7.374-2.el6.x86_64 rpmlib(PayloadIsXz) <= 5.2-1 is needed by ruby-1.8.7.374-2.el6.x86_64 ruby = 1.8.5-31.el5_9 is needed by (installed) ruby-irb-1.8.5-31.el5_9.x86_64 ruby = 1.8.5-31.el5_9 is needed by (installed) ruby-rdoc-1.8.5-31.el5_9.x86_64 ruby = 1.8.5-31.el5_9 is needed by (installed) ruby-ri-1.8.5-31.el5_9.x86_64
It appears as though this particular version was intended for CentOS 6 and, as I've known from previous experience, dependency hell is upon me. So, the question becomes, has anyone successfully upgraded ruby without tinkering with the OS version upgrade and, if so, might you have a HOWTO that prevents dependency hell? This, short of installing from source, is headed in the wrong direction real quick so I'm trying to stick with the RPM method. But, obviously, I'll listen to anything at this point.
hello all,
i am using Centos 6. i want to disable boot log messages at the time of boot-up even after pressing any key like.. Esc,Alt+d,any arrow keys..
i tried to disable keys by using the command:
xmodmap -e "remove Escape = Escape" and all...
but its not working.
what should i do?? boot messages like this:
iptables: Applying firewall rules: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0... done.
[ OK ]
Starting system logger: [ OK ]
Starting system message bus: [ OK ]
Retrigger failed udev events[ OK ]
Starting snmpd: netlink: 12 bytes leftover after parsing attributes.
[ OK ]
Starting snmptrapd: [ OK ]
Starting sshd: [ OK ]
Starting mysqld: [ OK ]
Starting Dovecot Imap: [ OK ]
Starting postfix: [ OK ]
Starting mailgraph: [ OK ]
Starting httpd: [ OK ]
Starting crond: [ OK ]
Starting squid: .[ OK ]
Starting fail2ban: [ OK ]
Starting atd: [ OK ]